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

            Bug ID: 408967
           Summary: trying to discover dolphin development leads to
                    unrewarding maze
           Product: dolphin
           Version: 18.04.3
          Platform: unspecified
                OS: All
            Status: REPORTED
          Severity: minor
          Priority: NOR
         Component: general
          Assignee: dolphin-bugs-n...@kde.org
          Reporter: skierp...@gmail.com
                CC: elvis.angelac...@kde.org
  Target Milestone: ---

SUMMARY
I wanted more information about Dolphin for developers, so I Googled "dolphin
KDE source code". The first search result is 
  KDE/dolphin: KDE File Manager - GitHub
  https://github.com/KDE/dolphin
  Contribute to KDE/dolphin development by creating an account on GitHub. ... 
  together to host and review code, manage projects, and build software
together.

For most projects GitHub is the best link for developer info, but a) GitHub is
just a mirror for Dolphin, it's not where bugs or project management or pull
requests happens (despite what the snippet in search results promises). b)
https://github.com/KDE/dolphin has a one-line README

    See http://dolphin.kde.org for information about Dolphin.

which redirects to https://userbase.kde.org/Dolphin , but that also has no info
for developers.

STEPS TO REPRODUCE
(as above)

OBSERVED RESULT
Developers wondering about changes ("pull requests" on GitHub), issues/bugs,
project status, contributing, etc. will either realize the info is not on
GitHub and give up, or follow the link in the README... and find no information
for developers and give up.  Great software, poor signposts.

EXPECTED RESULT

Either 
A) The barebones GitHub README should be expanded to point developers to
relevant resources (https://www.kde.org/applications/system/dolphin/development
, Phabricator project, bugs.kde.org ?).
B) The page the GitHub README links to, https://userbase.kde.org/Dolphin ,
needs to have something for developers.
C) http://dolphin.kde.org should redirect to some other page (again
https://www.kde.org/applications/system/dolphin/development , or
https://community.kde.org/Dolphin , or ??) with the relevant info. It's in the
sidebar of the user-centric https://kde.org/applications/system/org.kde.dolphin
as "Dolphin Homepage", so wherever it redirects needs to serve users as well as
developers.

If Dolphin developer info ends up on some page other than GitHub README,
optimize it in search results so it shows up before the unhelpful GitHub
result.


SOFTWARE/OS VERSIONS
n/a

ADDITIONAL INFORMATION
I had similar problems looking for other KDE project development info.

The distinction between the web sites community, techbase, userbase,
kde.org/applications, Phabricator... is too subtle for anyone not intimately
familiar with KDE.

I first brought up this problem on the Userbase talk page for Dolphin,
https://userbase.kde.org/index.php?title=Talk:Dolphin&offset=20180930074757#GitHub_links_here.2Fneeds_developer_info_2802

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to