On Sat, Apr 25, 2009 at 9:39 AM, mrts wrote:
> As an example I've tagged a couple of tickets with gsoc09-admin-
> refactor:
Please don't do that. You're effectively trying to order Zain to do
some work without consulting him, me (his mentor), or anyone else
first.
Further, it appears you haven'
On Sat, Apr 25, 2009 at 9:12 AM, mrts wrote:
> To get more visibility and community input for the scope of GSOC
> projects, let me propose the following workflow.
The time to suggest this was months ago when the GSoC process *began*,
and the *place* to do it was on the GSoC mailing list, not her
On Sat, Apr 25, 2009 at 11:39 AM, mrts wrote:
>
> As an example I've tagged a couple of tickets with gsoc09-admin-
> refactor:
>
> http://code.djangoproject.com/query?status=new&status=assigned&status=reopened&status=closed&keywords=~gsoc09-admin-refactor&order=priority
Hrm, none of these three
As an example I've tagged a couple of tickets with gsoc09-admin-
refactor:
http://code.djangoproject.com/query?status=new&status=assigned&status=reopened&status=closed&keywords=~gsoc09-admin-refactor&order=priority
--~--~-~--~~~---~--~~
You received this message be
To get more visibility and community input for the scope of GSOC
projects, let me propose the following workflow.
1. A keyword is chosen for each project
---
* model validation: model-validation (already existing)
* multiple database support: multi-db
* admin
