On Tue, 2008-02-26 at 13:12 -0800, Bryce Harrington wrote:
On Tue, Feb 26, 2008 at 09:15:53AM +0100, J.B.C.Engelen@...1578... wrote:
Behalf Of Jon Phillips
How about this rule:
1.) Newbies to Inkscape must submit proposal with the infrastructure using the extension system
2.) Established developers who have either SVN commit access or 2 substantial patches can submit a proposal in any area.
To be honest, I find the 'extensions only' very limiting, so I like this compromise. Maybe incorrect, but I read the 'extensions only' as: python scripts only. I understand that new developers need time to get used to Inkscape's codebase, but devs like me can (and, personally, want to) go much much deeper.
Well, for past participants who would like to spend their summer working again on Inkscape, I certainly wouldn't want to impose a restriction that would prevent this from happening.
For #2, I think it would fit within our underlying motivation for GSoC if proposals to work on inkscape-core for the summer fit within our refactoring/code-cleanup plans. So for instance:
- Fix bugs reported in LP against the code they worked on last summer
- Rearchitect code to fit better within the overall Inkscape framework
- Extracts shareable code from Inkscape into a library
Bryce
That's sounds like a great plan that keeps the project on target and focused gSoc'rs
:) Jon