DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG� RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=15952>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND� INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=15952 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Component|Documentation |Enhancements Product|Velocity |BugZilla Resolution|FIXED | Version|1.0-Release |Current ------- Additional Comments From [EMAIL PROTECTED] 2004-12-01 11:06 ------- Thx for the hint. Unfortunately, I don't see a "product" for the "jakarta top level web site", so I use "BugZilla" now (Bug 32466). Observation aside: ================== I see it often that RFEs get resolved as fixed or invalid or wontfix unless the technical enhancement-fix is present. Is there somewhere an apache mission statement that says that (contrary to http://issues.apache.org/bugzilla/page.cgi?id=fields.html#bug_severity) "RFE" stands for "Ready-tested-CVS-committable-solution for enhancing" and that "requests" are banned to mailing lists? My personal opinion is that the community process looses a lot if this were the case. IMHO bugzilla is a better place to have enhancement ideas being "seeded" and then shaped by the community (by adding comments and cross-refences) until somebody takes the initiative and "accepts" it and starts implementation. I also contend that with mailing list discussions, many of the valuable community inputs get overlooked once implementation starts while if an RFE resides inside the powerful structure of bugzilla, these nuances have a much better chance to be honoured. I don't think it is a problem if an RFE is dormant for a few months in an unresolved state. I even would say that if I see many open RFEs, this can well be a good sign for the state of the community: "the community is not lacking vision for its baby going forward, it only might be short of resources for now". On the other hand - seeing many RFEs closed without these RFEs apparently having been given due attention leaves a bad taste about community governance and the egos of its committers. P.S. agreed that posting docu-diffs may be more effective than unstructured text but still (especially for novices to a community, their insights might be new to the "routine-blinded" insiders and they don't have the skills to create a diff) I contend that an non-technical docu-RFE still may have merits justifying it remaining inside bugzilla until addressed substantially. In this sense, right now, I don't have the time to add the diff-attachment, but I may have it later and hope this RFE is still here when I get around it. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
