Re: [LAD] meta issue tracker idea

>On Mon, June 14, 2010 7:40 am, Robin Gareus wrote:
>> On 06/14/2010 03:51 PM, Philipp wrote:
>> If a custom tracker should be developed at some point, then
>> it shouldn't happen behind LAD doors but together with other parties
who could benefit from it and likely have more expertise in that area.
>>
>> The closest existing thing I know is http://openhatch.org/, which pulls
all or some bugs from lots of trackers, but I'm not sure it's close to
what is needed here.
>
> AFAICT openhatch tackles a different problem: get people on a project. I
don't know if it can be useful for improving interoperability and
inter-project problems; but it could be a start.
>

It makes sense to me to integrate the functionality it provides as another
option. The trick is to figure out how to best integrate it...

>> My idea for the near future was to simply use an existing wiki,
possibly on linuxaudio.org (mainly because of the domain name). In the
simplest form I believe, tags could be used for applications (to find
all issues involving the specific app), pages for the issues and page
subscriptions for notification.
>
> Those features are all already present at wiki.linuxaudio.org.
>
> There's been some complaints about the current style; but no-one has
stepped forward and provided a better template yet. FWIW you can switch
the look&feel at http://wiki.linuxaudio.org/wiki/user/rgareus
> the "experimental" there is a contender for the new default. but it's
not yet XHTML clean and requires javascript.
>
> If one wants to pick up a project he/she can already find
> http://wiki.linuxaudio.org/apps/categories/unmaintained
> and
> http://wiki.linuxaudio.org/apps/categories/dead_link
>

It's true that you can find it but how many people actually do find it?
IMO brining this info out to the forefront should be a prerequisite for
the tracker page. In fact it would be useful to add these links to the
planet-bugs page so they have additional SEO for people coming to the site
from an engine.

>
> From the top-of-my head, here's how we could start:
>
> go to http://wiki.linuxaudio.org/wiki/bugs/ISSUE
>
> Where ISSUE eg: synchronization
> - create or edit the wiki-page
> - describe the problem
> - add links to affected software
> eg. [[apps:all:ardour]], [[apps:all:hydrogen]]
> - optionally add external links to upstream trackers.
> - optionally add {{rss>TRACKER-FEED-URL}} for issue upstream.
>
> The backlinks ("what links here") feature of the eg.
> http://wiki.linuxaudio.org/apps/all/hydrogen
> page will show related bugs. It will be easy to make a "show only
backlinks in the 'bug' namespace" feature.)
>
> Once we have a few test/example pages we can add wiki-shortcuts to ease
the workflow. There's also the possibility to have a small form that
will create a new wiki-page according to a template using
> http://www.dokuwiki.org/plugin:bureaucracy
>

I think this is a prerequisite for any form of wider adoption. Just
looking at the method described herein is enough to scare most people ;-)
I will be happy to assist with the form once we have defined and tested
the basic system if this turns out to be the preferred way to handling the
meta tracker.

> Then we'll "only" need to make developers of said application aware of
the bug-reports:
>
> This could happen using feeds:
> http://wiki.linuxaudio.org/feed.php?mode=list&ns=wiki:bugs:ISSUE
>
> or subscribing them to the "page change notification" of said issue.
>

Both options should be provided but the most likely to be useful will be
email notifications and automatically adding the bug to the applications
existing tracker.

> or it can be one of us, playing man-in-the-middle forwarding these bug
upstream.
>

Who's gonna pay for that persons time?

> A nice feature would be subscribe to 'pages with tag XXX'; that is not
yet possible; but I can whip up a plugin for that if once need it.
>
>> I'm no expert on wikis, so I'm not sure whether there
>> are more features that could be used to fulfill more of what we'd want.
>
> right; so far we have a problem description and brainstorm about
possible solutions but not actually a use-case list of "what we want".
>

I think it is being clarified now.

-- 
Patrick Shirkey
Boost Hardware Ltd.
-- 
Patrick Shirkey
Boost Hardware Ltd.
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@email-addr-hidden
http://lists.linuxaudio.org/listinfo/linux-audio-dev