-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, Apr 22, 2008 at 4:07 AM, Dave Page wrote:
> > The idea is to have a really obvious marker at the top of each
> > commitfest page, showing whether it is currently finished, open for
> > submissions, under review, or not yet current. My hope is that this
> > will reduce the instance of people adding their patch to the wrong
> > page once we start directing new submitters to the wiki.
> >
> Looks good - I did something similar on the old wiki to mark pages as
> they got migrated to the new site:
> http://developer.postgresql.org/index.php/Main_Page
>
Okay, I've created the following three templates:
* http://wiki.postgresql.org/wiki/Template:CommitFestOpen* http://wiki.postgresql.org/wiki/Template:CommitFestCurrent*
http://wiki.postgresql.org/wiki/Template:CommitFestClosed
Each of these templates uses the generic Template:CommitFestStatus to
do the layout.
The templates automatically add Category:CommitFest to any page which
includes them, so there's no need to explicitly add a commitfest page
to the category. As long as you're using the status templates, it'll
be categorised already.
I didn't create a template for "future" commitfests, because I thought
that in practice we will probably only create commitfest pages as they
become needed. So the process for feature-freezing the May commitfest
would be something like:
1. Create the empty July commitfest page (i.e., CommitFest 2008-07)2. Tag the July page with status
{{CommitFestOpen}}3.Update any permanent redirects to point new submitters to the July page.4. Change the May page's
statusfrom {{CommitFestOpen}} to
{{CommitFestCurrent}}
Once the May commitfest is over, we just change the status from
{{CommitFestCurrent}} to {{CommitFestClosed}}.
Cheers,
BJ
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: http://getfiregpg.org
iD8DBQFIDifC5YBsbHkuyV0RAjfYAJ9UVslCLDsrGGCR/yj1xN/h+T0y0wCgndxv
LrpT5rvRURGjsJQ3lS4Ww4M=
=I9hJ
-----END PGP SIGNATURE-----
