[kde-doc-english] [docs] [Bug 325409] New: Kate "get-it" page has broken link (404) to Kate git repo

[steveL]

https://bugs.kde.org/show_bug.cgi?id=325409

            Bug ID: 325409
           Summary: Kate "get-it" page has broken link (404) to Kate git
                    repo
    Classification: Unclassified
           Product: docs
           Version: unspecified
          Platform: unspecified
               URL: http://kate-editor.org/get-it/
                OS: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Corrections
          Assignee: kde-doc-english at kde.org
          Reporter: slong at rathaus.eclipse.co.uk

Where it says "Right now, Kate’s source code is located on git.kde.org." the
old URL used:
https://projects.kde.org/projects/kde/kde-baseapps/kate  is incorrect.
It needs to be changed to:
https://projects.kde.org/projects/kde/applications/kate/repository
The actual git url in the sample shell session, is fine.

This matters because the main page for new Kate developers:
http://kate-editor.org/join-us/
links to the "get-it" page and the first thing people try to do is review
what's already going on, via the link given. 404 just leaves a bad impression,
and stops newbies from seeing what's going on easily. (There's a psychological
barrier to going and cloning a git repo in a terminal session, that isn't there
with clicking a link on a webpage.)

I have seen this myself several times in #kate, and from my own experience: it
took a bit of perseverance to find the correct link, but it is so much more
useful, especially with newcomers to the channel, who express interest in
hacking.

Along the same lines, it would be useful if we could have that link in the
/topic for the IRC channel: it makes all the difference in terms of
collaboration around the codebase, as I have seen in other project channels.
I've mentioned it a few times, and no one seems to have permission to change
the /topic. Or at least, if they do, they're keeping quiet about it, and in the
meantime the opportunity to recruit new people is hampered by clearly
unintentional lack of transparency.

No I don't think it's the end of the world either ;) but it's really annoying
to have to go and dig out the correct link for people, instead of just being
able to give them the get-it link on its own, and let them explore the code
themselves.

Or even better, having the repo web url in /topic as something we're _proud_
of, that they can click on as soon as they /join, and get started sooner.

Reproducible: Always




None of the above should be misconstrued as an attack on anybody; managing an
IRC channel and programming an editor are very different skill-sets. And I'm
grateful that kate is progressing so well.

-- 
You are receiving this mail because:
You are the assignee for the bug.