Commitfest namespacing (was: TODO, FAQs to Wiki?)
in [PgSql]
|
Prev: pgstat SRF?
Next: WIP: psql default banner patch
From: "Brendan Jurd" on 21 Apr 2008 11:20 On Sun, Apr 20, 2008 at 1:45 AM, Alvaro Herrera <alvherre(a)commandprompt.com> wrote: > Bruce Momjian wrote: > > I am impressed at the state of the May wiki patch queue: > > > > http://wiki.postgresql.org/wiki/CommitFest:May > > > > It is even tracking the psql wrap patch I am working on now. > > Thanks. We've put a certain amount of effort on it. Credit for the > templating system goes to Brendan Jurd, who implemented the way to make > it display as tables but without the messy markup. I think the > templates that are now in place make for a reasonably comfortable > environment. Not as simple as editing a plain text file, but I expect > it is lean enough. I appreciate your positive comment Bruce. Credit must also go to Alvaro for supplying valuable feedback and encouragement offlist while I worked on those templates =) I wonder if we should namespace the CommitFest pages by year as well as month (i.e., move CommitFest:May to CommitFest:May2008). This way, even after we've had a CommitFest:May in 2009/2010/etc., the history of the May 2008 CommitFest will still be easily viewable as a discrete item. Thoughts? Cheers, BJ -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Alvaro Herrera on 21 Apr 2008 11:38 Brendan Jurd escribi�: > I wonder if we should namespace the CommitFest pages by year as well > as month (i.e., move CommitFest:May to CommitFest:May2008). This way, > even after we've had a CommitFest:May in 2009/2010/etc., the history > of the May 2008 CommitFest will still be easily viewable as a discrete > item. Agreed -- this same idea occurred to me some days ago, but I then forgot it :-) For now, it would be good to ensure that CommitFest:May is a redirect to May2008. (I think it would make sense to have a CommitFest:Current redirect and perhaps CommitFest:Next.) -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: "Brendan Jurd" on 21 Apr 2008 12:37 On Tue, Apr 22, 2008 at 1:38 AM, Alvaro Herrera <alvherre(a)commandprompt.com> wrote: > Brendan Jurd escribió: > > I wonder if we should namespace the CommitFest pages by year as well > > as month (i.e., move CommitFest:May to CommitFest:May2008). This way, > > even after we've had a CommitFest:May in 2009/2010/etc., the history > > of the May 2008 CommitFest will still be easily viewable as a discrete > > item. > > Agreed -- this same idea occurred to me some days ago, but I then forgot > it :-) For now, it would be good to ensure that CommitFest:May is a > redirect to May2008. (I think it would make sense to have a > CommitFest:Current redirect and perhaps CommitFest:Next.) > We may need to draw some kind of distinction between the "open" commitfest (which is where developers should submit new patches) and the "current" commitfest (which is where reviewers should be directing their attention). There'll be a substantial time period where the "open" and "current" commitfests are the same thing, but, for example, when the May commitfest closes for new submissions, it will still be the "current" commitfest, but will no longer be the appropriate place for developers to post their new patches (that will become July). I've started thinking of a commitfest as moving through the following stages in its lifetime: 1. Future 2. Open for submissions 3. In progress (closed for submissions) 4. Complete We probably need to have the following redirects in place: * CommitFest:Current (for reviewers) * CommitFest:Open (for submitters) * CommitFest:Next Suggestions for alternative (less ambiguous) nomenclature are welcome ... Cheers, BJ -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Andrew Dunstan on 21 Apr 2008 12:44 Brendan Jurd wrote: > On Tue, Apr 22, 2008 at 1:38 AM, Alvaro Herrera > <alvherre(a)commandprompt.com> wrote: > >> Brendan Jurd escribi�: >> > I wonder if we should namespace the CommitFest pages by year as well >> > as month (i.e., move CommitFest:May to CommitFest:May2008). This way, >> > even after we've had a CommitFest:May in 2009/2010/etc., the history >> > of the May 2008 CommitFest will still be easily viewable as a discrete >> > item. >> >> Agreed -- this same idea occurred to me some days ago, but I then forgot >> it :-) For now, it would be good to ensure that CommitFest:May is a >> redirect to May2008. (I think it would make sense to have a >> CommitFest:Current redirect and perhaps CommitFest:Next.) >> >> > > We may need to draw some kind of distinction between the "open" > commitfest (which is where developers should submit new patches) and > the "current" commitfest (which is where reviewers should be directing > their attention). > > There'll be a substantial time period where the "open" and "current" > commitfests are the same thing, but, for example, when the May > commitfest closes for new submissions, it will still be the "current" > commitfest, but will no longer be the appropriate place for developers > to post their new patches (that will become July). > > I've started thinking of a commitfest as moving through the following > stages in its lifetime: > > 1. Future > 2. Open for submissions > 3. In progress (closed for submissions) > 4. Complete > > We probably need to have the following redirects in place: > > * CommitFest:Current (for reviewers) > * CommitFest:Open (for submitters) > * CommitFest:Next > > Suggestions for alternative (less ambiguous) nomenclature are welcome ... > > > Why not use a form for posting new patches that would automatically put it on the right page? (I have no idea if you can do that sort of thing using mediawiki - it's just what I would do if I were designing a patch submission system from scratch). cheers andrew -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: "Brendan Jurd" on 21 Apr 2008 12:54
On Tue, Apr 22, 2008 at 2:44 AM, Andrew Dunstan <andrew(a)dunslane.net> wrote: > > Why not use a form for posting new patches that would automatically put it > on the right page? (I have no idea if you can do that sort of thing using > mediawiki - it's just what I would do if I were designing a patch submission > system from scratch). > Well at that point you're basically talking about using a patch tracker =) As a matter of fact, I'm hoping that managing commitfests via the wiki will demonstrate what patch tracking can bring to the project, as well as help illuminate what we would actually require from patch tracking software. There's been a lot of conjecture on that topic, but putting the wiki into practice might give us some real empirical results to mull over. Being able to submit patches via a web form is one of the more obvious benefits of a real patch tracker. I'm not aware of any way to accomplish this in mediawiki without resorting to some nasty script hackery. Cheers, BJ -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |