I may be incorrect, but I think the way it happened (during 0.88-94 days) was a feature was first proposed on the mailing list with the [FEATURE] tag in the subject line. It was then extensively discussed, and then at some later point a wiki page was created, which was (supposed to be) useful at the time of feature-freeze to make a go/no-go call for code-inclusion in mainline, so having the current state summarized in a wiki page was useful.
(Just giving historical reference) On Thu, Oct 31, 2013 at 6:49 PM, James Cameron <qu...@laptop.org> wrote: > On Thu, Oct 31, 2013 at 09:18:42PM -0400, Walter Bender wrote: > > Not sure there is too much more overhead for writing a wiki page vs > > writing an email. I don't recall hearing anything concrete about the > > feature proposal process recently. It has be refactored periodically, > > usually under the guidance of the release manager :) > > Agreed, the overhead isn't much; only about double the time, but it is > mostly borne by the feature proposer. The same template could be used > in e-mail, and this would give a discussion thread view rather than a > finished filled-in template view. As mostly a reader of the features, > I'm okay with either, but the Wiki doesn't show much in the way of the > discussion. > > -- > James Cameron > http://quozl.linux.org.au/ > _______________________________________________ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel >
_______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
