Re: [LAD] meta issue tracker idea

On Sun, June 13, 2010 5:14 am, Robin Gareus wrote:
> On 06/10/2010 04:11 AM, Patrick Shirkey wrote:
>>
>> On Tue, June 8, 2010 1:35 pm, Robin Gareus wrote:
>>> On 06/08/2010 10:31 AM, Patrick Shirkey wrote:
>>>>
>>>> On Mon, June 7, 2010 8:09 am, Robin Gareus wrote:
>>>>> On 06/07/2010 05:26 AM, Patrick Shirkey wrote:
>>>>>>
>>>>
>>>>>> But that is
>>>>>> really just replicating existing functionality. A more productive
>>>>>> approach
>>>>>> is to improve on the bugs page now that it exists. For example an
>>>>>> "add"
>>>>>> /
>>>>>> "submit" new feed button/link would be helpful.
>>>>>
>>>>> There's a 'tiny' link labeled "FAQ & Subscribe" in the bar on the
>>>>> right.
>>>>>
>>>>
>>>> That should be good enough for most people.
>>>>
>>>>
>>>>> I don't think automating the submit/add system is a good idea; Marc,
>>>>> Ico
>>>>> & me are are quite quick filtering SPAM and editing the planetplanet
>>>>> config-file.
>>>>>
>>>>
>>>> Agreed.
>>>>
>>>>> We'll need to update the wiki-page though and improve the
>>>>> HTML-template
>>>>> for "planet bug". Anyway so far it's just an experiment, not a
>>>>> maintained service.
>>>>>
>>>>
>>>> It's looking quite useful already. Another idea is to aggregate the
>>>> bugs
>>>> as they are fixed and maintain a record for the most active projects.
>>>> I
>>>> s'pose most of that data can be extracted directly from the trackers?
>>>> As
>>>> in no need for us to write a database specifically for that info.
>>>>
>>> Alas that's not so simple with most systems.
>>> Only trac is good at that - providing a feed or statistics for recently
>>> resolved and closed bugs, that is.
>>>
>>> MantisBT requires the administrator to create a filter [1] and I don't
>>> think it's even possible with the sourceforge tracker. SF.net provides
>>> their own statistics but there's no feed for those.
>>> If googlecode-issue-tracker can do it it's a feature well hidden.
>>> I have not checked flyspray, bugzilla and debbugs.
>>>
>>> so long,
>>> robin
>>>
>>> [1]
>>> http://www.futureware.biz/blog/index.php?title=rss_feeds_in_mantis_1_0_0a3&more=1
>>>
>>
>> That makes that idea fairly difficult to implement in the short term.
>>
>> So far we have the list of apps being tracked on the right hand column,
>> and add/submit link and the actual feeds. You suggested an extension
>> that
>> allows tickets to be tracked cross app but I think that is a lot of
>> effort
>> for minimal gain at this point as there isn't yet a huge user base for
>> the
>> tracker portal.
>>
>> I think it would be useful for the idea if we could bring out the user
>> contribution side a little more before building code to handle cross app
>> bug tracking.
>>
>> Maybe a few links to add a new ticket, join the project and donate if
>> the
>> project has that facility that could be displayed next to each project
>> and/or item in each feed?
>>
> Adding extra information is not a big deal. The problem is: All trackers
> require a user to log in in order to access the "submit ticket" page..
> and the minority of them has OpenID or OAuth enabled.
>
> Clicking on the link in the "Subscriptions" sidebar already gets you to
> the main site of each trackers from where you can proceed to "add
> ticket" if you're logged in there.
>
> If you want to go ahead and improve the layout: I can give you write
> permissions on linuxaudio.org:/var/lib/planet/templates/ and
> /etc/planet-bugs.conf
>

Might as well do that. I'm not gonna be able to make any progress for the
next couple of weeks but I will be able to get stuck into it at some
point.

> One idea would be to create a linuxaudio account on all upstream
> trackers and provide a form on LAO that submits tickets upstream using
> this account; but it'd be a major task to do so: SPAM filtering,
> aggregate upstream versions & options; templates for the multitude of
> different trackers out there etc etc, not to mention handling email
> notifications that come back from the trackers.
>

I think the main issue right now is doing enough to make it useful without
investing too much time into it. A single LAO account seems like a lot of
hassle for not much gain and in a way reinventing the wheel. If we
implement support for all OpenID type protocols for sharing logins and
encourage developers to enable that feature for their trackers that would
take us a fairly large step forward.

openID, oAuth, facebook, wordpress, google connect,

Which ones do we need to support and which ones are most likely to get
people using the system? Given that the idea is to make it easy for new
users to get involved, IMO we should aim to support the most popular
methods and not just the open source options.

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