View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003890 | mantisbt | sponsorships | public | 2004-05-27 19:12 | 2008-10-18 18:34 |
Reporter | Assigned To | vboctor | |||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | closed | Resolution | fixed | ||
Platform | Any | OS | Any | OS Version | Any |
Product Version | git trunk | ||||
Summary | 0003890: Ability to enable sponsorship not only globally, but on per-project basis also | ||||
Description | Sponsorship is nice idea and good iimplementation, but, in case when projects with bugs separated from projects with wishes and feature requests, sponsorship of bugs can generate additinonal hardly-answered questuions from customers - bugfixing of real bugs must be free for customers | ||||
Additional Information | Probably additional checkbox in project's properties "Enable sponsorship" - from user's side | ||||
Tags | No tags attached. | ||||
I agree with the feature, but don't agree with the reasoning behind the need. In my opinion, a project will include bug fixes and enhancements, rather than being split into two projects. However, per project sponsorship flag may be useful for the case where a company has more than one product, some are open source, and others are not. For the ones that are not, sponsorship doesn't make sense. This can be added as a field to the projects table, or as many other features, as a per-project-flag. Per-project-flags will be supported when the configuration is moved to the database. This will definately be after 0.19.0. |
|
Victor, my needs was born in real life :-)
Will we can to see any form of per-project sponsorship in 0.19-CVS? |
|
Maybe you need to sponsor it then :) |
|
I can :-), together w/XOOPS integration - I want something unusual, I'm ready pay for dreams... |
|
per-project settings is now possible. Please use 1.1.x releases. |
|