> > The main issue before was that users need a feature, they implement it
> > as per their needs only, then start talking to us about getting it
> > into the product. I've always tried to make sure that we include
> > features where they are mature and generic enough to serve the needs
> > of the Mantis users in general.
> This is the best approach. What can you add, which adds value for the
> most number of users, without impacting the current userbase. Continue
> to keep that mindset. Its the same one I've used over the years with my
> hundred or so Mantis fixes/patches/reports.
> I've seen this "I need <obscure feature X> in your project, so I can
> convince management its the right tool for our company" kind of thing in
> many projects over the last decade or more, and its somewhat
I agree, but as I'm thinking about developing a
<hopefully-not-so-obscure-feature> I feel it could be useful to discuss
this possible feature in forum before I start coding.
I'd like to know answers to questions like:
* Is anybody out there with similar intents? Or is someone already working
on the same problem?
* If my feature has more solutions, which one is the most compatible with
core-team visions of future development?
* Are there any potential users of this feature willing to share ideas?
What do you think?