Hi Reinier, Only project admins can remove Tasks and Forums tabs. I did this.
Well done for your work! You have an excellent notion how to organise these things, so proceed with the same manner. One comment by me about the feature requests and bugs. Let's not concentrate the responsibility about this on one or two persons (Elpidio and me). We cannot assign anybody a bug or feature, because every contribution is voluntary and not obligating. There are people asking what they can help with. Solving a bug or implementing feature request is an excellent contribution. There should be, of course, further discussions on the topic how to handle this issues - part of the main discussion how to organise the community. Greetings Kaloyan On Thu, 2006-06-22 at 16:03 +0300, Reinier Battenberg wrote: > Hi, > > I made my changes. A few things I do not know or were not possible: > > - I could not change the Status fields for bugs. However I found a > Resolution option which contains lots of values to manage the > Bugs/Feature Requests. I enabled it. > - Although I removed all Tasks and Forums, the tabs are still visible. > If someone knows how to get rid of them, drop me an email. > - I added some extra descriptions & guidelines to the bug & feature > request trackers. If you think these are inadequate, tell me. > - I updated some of the Feature Requests already, in order to make them > a bit more meaningful. > > > TODO > > - We have 31 open bugs. This means, we either have to do some proper > coding, or for bugs that have actually been fixed already, we need to > manage the bugs in the Tracker.(close them, propose a workaround, etc) > - We have 4 open Feature Requests. I think it's a good idea if Elpidio > or Kaloyan pick these up and assign them to a release, or reject them. > - I dont think ultimately the current Categories will suit our needs. > Suggestions for improvement are welcome. > > but most importantly: > > - We have lots and lots of wishes that have been discussed here in the > list. I suggest we start putting some of these ideas into the Feature > Requests Tracker. This will give Elpidio and Kaloyan the possibility to > formalize them, get some more detail into them, assign them to a release > and ultimately for someone(s), to code them. > > rgds, > Reinier > > > > Reinier Battenberg wrote: > > Hi, > > > > In an attempt to make the use of Sourceforge more productive for > > everyone, i would like to propose the following changes. If you have an > > interest in these and would like to respond, please do so. If everyone > > is ok, i will make these changes from june 23d onwards. > > > > > > Forums > > > > I would like to remove all forums. The last post actually is a reminder > > to post to the mailinglist instead. > > > > Support Requests > > > > I would like to remove the Support Requests. There are only 2, one from > > 2003, the other from last october. > > > > Patches > > > > Nothing personal, Claudio Torbinio, but I suggest to remove the Patches > > tracker as well. 6 posts in 2 years is not enough. > > > > > > Tasks > > > > The amount of active tasks is very minimal. I think we are not really > > using this. So, again, i would like to remove this section. > > > > > > Bugs > > > > Bugs we probably will have. And the bugtracker is used. What could use > > some improvement is the categorisation. My proposal is the following: > > > > Status: Keep the same > > Category: Keep the same (although suggestions are welcome here) > > Groups: > > > > Change the list to: > > > > 1- Main - 1.x > > 2- Main - 2.1.0.x > > 2- Main - 2.1.x (Beta) > > 3- ELCT - 0.2 (this is a fork that is used in Arusha Tanzania only) > > > > To clean up, i'll mass assign all current items to the Main - 1.x group. > > After that, all 2.x Issues should be re-assigned manually by their > > respective owners. > > > > > > Feature Request > > > > Although this section is not very much used, it might actually be very > > valuable. I would like to keep this section. Although some changes in > > the categorisation: > > > > Status: > > Change to: > > Proposed > > Accepted > > Rejected > > Implemented > > (the list could be longer, this is the minimum i think) > > > > I will assign all open Requests to a status of Proposed when doing the > > transition. > > > > Category: > > For now, keep the same, unless anyone has other ideas. > > > > Group: > > Change to: > > 2.1.x > > 2.2 > > 3.0 > > > > > > I will assign all Requests to the 2.2 release in the transition. > > > > > > Lastly, when the care2x.org website has been restored, I would like to > > check all URL's in the Docs section. > > > > > > I hope that will boost the usability of the sourceforge website and > > encourage even more people to participate in enhancing the care2x product. > > > > rgds, > > > > Reinier Battenberg > > > > > > _______________________________________________ > > Care2002-developers mailing list > > Care2002-developers@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/care2002-developers > > > > > All the advantages of Linux Managed Hosting--Without the Cost and Risk! > Fully trained technicians. The highest number of Red Hat certifications in > the hosting industry. Fanatical Support. Click to learn more > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 > _______________________________________________ > Care2002-developers mailing list > Care2002-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/care2002-developers Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Care2002-developers mailing list Care2002-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/care2002-developers
