Menu
▾
▴
[Rosegarden-bugs] SF.net SVN: rosegarden: [7167] trunk/docs/web/guidelines
|
From: <dmm...@us...> - 2006-02-25 16:56:31
|
Revision: 7167 Author: dmmcintyr Date: 2006-02-25 08:56:25 -0800 (Sat, 25 Feb 2006) ViewCVS: http://svn.sourceforge.net/rosegarden/?rev=7167&view=rev Log Message: ----------- More piddly changes, and verification that my new user side SVN tweaks are working as expected. Modified Paths: -------------- trunk/docs/web/guidelines/RFE-guidelines.html trunk/docs/web/guidelines/RFE-priorities.html Modified: trunk/docs/web/guidelines/RFE-guidelines.html =================================================================== --- trunk/docs/web/guidelines/RFE-guidelines.html 2006-02-25 16:33:15 UTC (rev 7166) +++ trunk/docs/web/guidelines/RFE-guidelines.html 2006-02-25 16:56:25 UTC (rev 7167) @@ -9,27 +9,24 @@ alt="Rosegarden"></div> <div id="main"> <H1>Feature Request Guidelines</H1> -<P STYLE="margin-bottom: 0in">Feature requests are called “RFEs” -for some reason unknown to me. I'm not even sure what RFE stands -for. Request for Feature Evaluation? Ask the people at SourceForge -if you're curious. In any event, RFEs are less critical to our -operation than RFE reports, and we are therefore commensurately less +<P STYLE="margin-bottom: 0in">Feature requests are less critical to our +operation than bug reports, and we are therefore commensurately less nitpicky about the whole process. Nevertheless, you increase the odds that someone might implement your brilliant new idea someday if -you bear the following guidelines in mind when submitting new RFEs.</P> +you bear the following guidelines in mind when submitting new feature requests.</P> <P STYLE="margin-bottom: 0in"><BR> </P> -<H2>Check for Similar RFEs</H2> +<H2>Check for Similar Requests</H2> <UL> - <LI><P STYLE="margin-bottom: 0in">Go to our RFE tracker at + <LI><P STYLE="margin-bottom: 0in">Go to our feature request tracker at <A HREF="https://sourceforge.net/tracker/?group_id=4932&atid=354932">https://sourceforge.net/tracker/?group_id=4932&atid=354932</A> </P> <LI><P STYLE="margin-bottom: 0in">Try to come up with a word or expression that anyone who submitted this idea previously would have used in the description. You have a better chance of finding the - previous RFEs if you use terms that are as generic and simple as + previous feature requests if you use terms that are as generic and simple as possible. SourceForge will not return any hits unless it finds <B>all</B><SPAN STYLE="font-weight: medium"> - of the terms you enter in one of the RFE summaries, and it cannot + of the terms you enter in one of the feature request summaries, and it cannot search the text of the reports directly. Consequently, a search for “audio” or “audio segment” is more likely to find something than a search for “audio segment resize idea.” @@ -47,11 +44,11 @@ don't expect you to waste an hour of your life trying to coax something out of that admittedly very lame search facility either.</P> <LI><P STYLE="margin-bottom: 0in">If you did find a result, or - results, read through the previous reports and see if your RFE is + results, read through the previous reports and see if your feature request is already described. If it is not described to your satisfaction, you can add additional comments to existing reports, if appropriate.</P> <LI><P STYLE="margin-bottom: 0in">If there is no previous work to - draw on, then you should continue on to file a new RFE.</P> + draw on, then you should continue on to file a new feature request.</P> </UL> <P STYLE="margin-bottom: 0in"><BR> </P> @@ -59,7 +56,7 @@ <P>Once you have made a reasonable effort to ensure that you have discovered a new idea, then please continue with the following guidelines in mind.</P> -<H3>RFEs to Avoid</H3> +<H3>Feature Requests to Avoid</H3> <P>Porting to Windows and doing a GTK2 rewrite have both been requested to death, and both are about as likely as waking up in the morning to find out your house transmuted into solid gold while you @@ -69,62 +66,19 @@ built it the way on purpose, so try to be realistic.</P> <H3>Don't Be a Nobody</H3> <P>Please take the time to create a SourceForge account for yourself -and use it for submitting and tracking your RFEs. The process of +and use it for submitting and tracking your feature requests. The process of working out an implementation of a new idea works best when you make yourself available for followup questions, and when you take an active interest in looking after your report. Having said that, it is less important for you to be held accountable when making feature requests than when you are submitting bug reports.</P> -<H3>One RFE per Report</H3> +<H3>One Request per Report</H3> <P>You should avoid the temptation to save yourself effort by combining different ideas into one massive report. If there are three related aspects to the same overriding problem, then file each of these aspects separately. Under no circumstances should you ever -file a “big RFE list” report that reels off a laundry -list of separate, unrelated ideas.</P> -<P STYLE="margin-bottom: 0in"><BR> -</P> -<P STYLE="margin-bottom: 0in"><BR> -</P> -<P STYLE="margin-bottom: 0in"><BR> -</P> -<P STYLE="margin-bottom: 0in"><BR> -</P> -<P STYLE="margin-bottom: 0in"><BR> -</P> -<P STYLE="margin-bottom: 0in"><BR> -</P> -<P STYLE="margin-bottom: 0in"><BR> -</P> -<P STYLE="margin-bottom: 0in"><BR> -</P> -<P STYLE="margin-bottom: 0in"><BR> -</P> -<P STYLE="margin-bottom: 0in"><BR> -</P> -<P STYLE="margin-bottom: 0in"><BR> -</P> -<P STYLE="margin-bottom: 0in"><BR> -</P> -<P STYLE="margin-bottom: 0in"><BR> -</P> -<P STYLE="margin-bottom: 0in"><BR> -</P> -<P STYLE="margin-bottom: 0in"><BR> -</P> -<P STYLE="margin-bottom: 0in"><BR> -</P> -<P STYLE="margin-bottom: 0in"><BR> -</P> -<P STYLE="margin-bottom: 0in"><BR> -</P> -<P STYLE="margin-bottom: 0in"><BR> -</P> -<P STYLE="margin-bottom: 0in"><BR> -</P> -<P STYLE="margin-bottom: 0in"><BR> -</P> -<P STYLE="margin-bottom: 0in"><BR> -</P> +file a “big request list” report that reels off a laundry +list of separate, unrelated ideas. It will go straight to priority 1, and +remain there forever.</P> </BODY> </HTML> Modified: trunk/docs/web/guidelines/RFE-priorities.html =================================================================== --- trunk/docs/web/guidelines/RFE-priorities.html 2006-02-25 16:33:15 UTC (rev 7166) +++ trunk/docs/web/guidelines/RFE-priorities.html 2006-02-25 16:56:25 UTC (rev 7167) @@ -1,5 +1,5 @@ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> - <title>Rosegarden RFE Priorities</title> + <title>Rosegarden feature request Priorities</title> <BODY LANG="en-US" DIR="LTR"> <head> <div id="heading" STYLE="background: #315e13"> @@ -7,12 +7,12 @@ height="104"><img src="title-rosegarden.png" alt="Rosegarden"></div> <div id="main"> -<H1>RFE Priorities</H1> -<P>RFEs should be submitted with a default priority of 5. A new +<H1>feature request Priorities</H1> +<P>Feature requests should be submitted with a default priority of 5. A new priority will be assigned once someone looks at the idea and considers how likely it is to be implemented in the foreseeable future. (Please bear in mind that “foreseeable” could -still be a long, long time, and sometimes it never gets here at all.)</P> +still be years away, or never.)</P> <TABLE WIDTH=100% BORDER=1 CELLPADDING=4 CELLSPACING=3> <COL WIDTH=30*> <COL WIDTH=226*> @@ -107,7 +107,8 @@ <P ALIGN=RIGHT>1</P> </TD> <TD WIDTH=88% VALIGN=TOP> - <P>forget it; this is just shy of a categorical no</P> + <P>your suggestion has effectively been + refused</P> </TD> </TR> </TBODY> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |