[Ardour-Users] new bug/feature tracker features

[John Emmas]

----- Original Message ----- 
From: "Paul Davis" <paul at linuxaudiosystems.com>
Subject: Re: [Ardour-Users] new bug/feature tracker features
>>
>> Along with the existing Mantis categories (Unassigned / Resolved /
>> Recently Modified etc) might there be a case for having a new category
>> called 'Feature Proposals'?  Anyone requesting a particular feature could
>> then check quite easily whether a dev has already offered to implement
>> it.  Having all the information in one place would also make it easier
>> for devs to provide progress reports and for users to view status
>> information such as cost, number of existing sponsors, estimated delivery
>> date and the like.
>
> i think that this is an excellent idea. but it has raised the secondary
> question in my mind over whether or not perhaps such a feature proposal
> list should be a separate mantis system? any thoughts?
>
Some more user & developer feedback is needed here but my personal view is
that feature requests and proposals would benefit from being in their own
separate Mantis system.  In fact, if someone were to enter a feature request
into the existing system, perhaps the action of selecting 'features' (from
the Category list) could pop up a message, directing them to the alternative
Mantis system.  And in the new system, the action of initiating a feature
request could maybe prompt users to check if their request is already among
the existing proposals.

John



----- Original Message ----- 
From: "Paul Davis" <paul at linuxaudiosystems.com>
To: "John Emmas" <johne53 at tiscali.co.uk>
Cc: <ardour-users at lists.ardour.org>
Sent: 17 June 2008 13:42
Subject: Re: [Ardour-Users] new bug/feature tracker features


>
> On Tue, 2008-06-17 at 09:21 +0000, John Emmas wrote:
>> ----- Original Message ----- 
>> From: "Paul Davis" <paul at linuxaudiosystems.com>
>> Subject: [Ardour-Users] new bug/feature tracker features
>> >
>> > Please let me know if there any problem arising from the Mantis upgrade
>> > and any thoughts anybody has on this system.
>> >
>> I don't know whether this is worth considering (or even possible) but
>> when I
>> looked at the Mantis entries marked as 'features', it struck me that the
>> vast majority (in fact, all the ones I looked at) were feature 'requests'
>> as
>> opposed to feature 'proposals'.
>>
>> If a price is to be put on features, it seems more sensible to me that
>> the
>> price should apply to proposed features, rather than requested features.
>> The reason being that several dozen users might all request the same
>> feature.  Therefore any dev who offers to implement that feature would
>> need
>> to track down dozens of requests and make sure they all get set to the
>> same
>> price.
>>
>> Along with the existing Mantis categories (Unassigned / Resolved /
>> Recently
>> Modified etc) might there be a case for having a new category called
>> 'Feature Proposals'?  Anyone requesting a particular feature could then
>> check quite easily whether a dev has already offered to implement it.
>> Having all the information in one place would also make it easier for
>> devs
>> to provide progress reports and for users to view status information such
>> as
>> cost, number of existing sponsors, estimated delivery date and the like.
>
> i think that this is an excellent idea. but it has raised the secondary
> question in my mind over whether or not perhaps such a feature proposal
> list should be a separate mantis system? any thoughts? it has the
> problem that there would be a lot of reasons to transfer information
> back and forth. it has the benefit that it would be easier to see and
> use.
>
> i can't add a new category to mantis, but i can add a custom field that
> would identify something as a feature proposal, and allowing filtering
> on that.
>
>
>