[Bug 789672] New: Not easy to get started and find a file to edit

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=789672

            Bug ID: 789672
           Summary: Not easy to get started and find a file to edit
    Classification: Platform
           Product: GStreamer
           Version: unspecified
                OS: All
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: www
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: kornel at geekhood.net
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

I've tried to use gstreamer, and got an error pointing to a .cpp file. I
thought I'd check out the file to investigate my problem further. However, I've
found that it's not easy to obtain relevant gstreamer source code, because:

- the code is split into many git repositories, but I don't know which one I
need. 

- the git command/url on https://gstreamer.freedesktop.org/dev/ is not a real
url, but a bogus "/modulename"

- the search on https://cgit.freedesktop.org/gstreamer/ does not find files by
file path (I've searched for "Driver/AVD_loader.cpp" and got no results
https://cgit.freedesktop.org/?q=AVD_loader.cpp )


So I'm left with impression that I will need to manually clone and search about
30 repositories just to find where this one file is, and it's not even easy to
copy the repository names since they are links, so text selection in the
browser gets fiddly. 

My suggestion how to improve this:

- Help cloning all of the repos, e.g. on the /dev/ page instead of showing one
incomplete command with /modulename suffix, list full complete commands for all
most commonly needed repositories (so I could copy&paste 30 lines of script and
then search that), or create another git repository with all the others as git
submodules, and then suggest using `git clone --recursive` on the root one.

- Use more advanced git web gui that has better search. Maybe gitlab?

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