Hello, teams :)
Google has just announced GSoC2011.
http://google-opensource.blogspot.com/2011/01/google-summer-of-code-announce...
The timeline is here: http://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/tim...
</crossposting-is-evil>
Alexandre Prokoudine http://libregraphicsworld.org
good maybe we can get some Django love somewhere in there.... since our team pretty much bailed...
On Mon, Jan 24, 2011 at 8:52 PM, Alexandre Prokoudine < alexandre.prokoudine@...400...> wrote:
Hello, teams :)
Google has just announced GSoC2011.
http://google-opensource.blogspot.com/2011/01/google-summer-of-code-announce...
The timeline is here:
http://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/tim...
</crossposting-is-evil>
Alexandre Prokoudine http://libregraphicsworld.org
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Tue, 2011-01-25 at 07:52 +0300, Alexandre Prokoudine wrote:
Hello, teams :)
Google has just announced GSoC2011.
http://google-opensource.blogspot.com/2011/01/google-summer-of-code-announce...
The timeline is here: http://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/tim...
Excellent!
A few thoughts:
1. We need to update the Inkscape GSOC Wiki page:
http://wiki.inkscape.org/wiki/index.php/Google_Summer_Of_Code
2. I may be wrong, but I have the sense that we have a fairly high failure rate for accepted projects. What can we do to improve the project selection?
3. I would like to see some projects devoted to improving Inkscape fundamentals:
1. SVG support. You can see the current status of our performance on the W3C test suite at:
http://tavmjong.free.fr/INKSCAPE/W3C_SVG_1.1F2/harness/htmlInkscapeApproved/...
and compare it to browser support at:
http://dev.w3.org/SVG/profiles/1.1F2/test/status/implementation_matrix.html
2. Improved handling of CSS. The CSS parser we use (libcroco) is not maintained.
http://www.freespiders.org/projects/libcroco/
The SVG output of Inkscape is full of unnecessary style attributes.
3. Improving Inkscape SVG for web use. Here's a list we came up with earlier:
* Fix "Plain" SVG to not remove <script>, etc. * Fix saving SVG to not modify CDATA (e.g. change & to &). * Add option to set viewbox attribute to Document Properties. (multiple viewbox support would be good) * Move flowed text into Inkscape namespace. * Font fallbacks * Easily add/edit hyperlinks * Better CSS support * Option to add title to SVG (searchability and accessibility) * Remove XML prolog/DOCTYPE * Move sodipodi namespace items to Inkscape namespace
Tav
On 1/25/11, Tavmjong Bah wrote:
We need to update the Inkscape GSOC Wiki page:
http://wiki.inkscape.org/wiki/index.php/Google_Summer_Of_Code
I'll poke around later today if noone gets there first.
- I may be wrong, but I have the sense that we have a fairly high
failure rate for accepted projects. What can we do to improve the project selection?
Not exactly high. The previous year was a 2/5 failure indeed, but the year before was 100% success, if my memory serves me well, and we are talking about 6 or 7 projects in 2009.
One of disappeared students last year had been around in the community for a rather long time, and the other disappeared student did a successful project for GIMP in 2009, so it's quite possible that we just had our bit of bad luck. We did have disappearing students in even earlier GSoCs though. IIRC, this is where the "two patches" rule comes from.
- I would like to see some projects devoted to improving Inkscape
fundamentals:
<list snipped>
All great ideas. Especially the use of CSS is one of the things that really needs doing.
* Easily add/edit hyperlinks
We recently had a blueprint (by Pajarico?) for that.
Alexandre Prokoudine http://libregraphicsworld.org
-----Original Message----- From: Alexandre Prokoudine [mailto:alexandre.prokoudine@...400...] Sent: dinsdag 25 januari 2011 7:45 To: Inkscape Devel List Subject: Re: [Inkscape-devel] GSoC 2011 announced
On 1/25/11, Tavmjong Bah wrote:
- I may be wrong, but I have the sense that we have a fairly high
failure rate for accepted projects. What can we do to improve the project selection?
Not exactly high. The previous year was a 2/5 failure indeed, but the year before was 100% success, if my memory serves me well, and we are talking about 6 or 7 projects in 2009.
One of disappeared students last year had been around in the community for a rather long time, and the other disappeared student did a successful project for GIMP in 2009, so it's quite possible that we just had our bit of bad luck. We did have disappearing students in even earlier GSoCs though. IIRC, this is where the "two patches" rule comes from.
There was some discussion on the GSoC mentor list about this some months ago. I think what I learned from that is that when selecting students, one should ignore the awesome feature that is proposed, but look at the student's skills instead. Also, I think we/I "forgot" about the two-patches-rule. Note that this rule is not only to assess coding capability, but also to see if the student is capable of actually building Inkscape on his PC (yes, this was a time-consuming problem in last year's SoC). Perhaps a good idea to make it easier for aspiring students is to provide a list of "easy" to tackle bugs or very small improvements. Perhaps this is more important than a list of GSoC projects.
Cheers, Johan
-----Original Message----- From: Engelen, J.B.C. (Johan) Sent: dinsdag 25 januari 2011 11:47 To: 'Alexandre Prokoudine'; Inkscape Devel List Subject: RE: [Inkscape-devel] GSoC 2011 announced
-----Original Message----- From: Alexandre Prokoudine [mailto:alexandre.prokoudine@...400...] Sent: dinsdag 25 januari 2011 7:45 To: Inkscape Devel List Subject: Re: [Inkscape-devel] GSoC 2011 announced
On 1/25/11, Tavmjong Bah wrote:
- I may be wrong, but I have the sense that we have a
fairly high
failure rate for accepted projects. What can we do to improve the project selection?
Not exactly high. The previous year was a 2/5 failure
indeed, but the
year before was 100% success, if my memory serves me well,
and we are
talking about 6 or 7 projects in 2009.
One of disappeared students last year had been around in
the community
for a rather long time, and the other disappeared student did a successful project for GIMP in 2009, so it's quite possible that we just had our bit of bad luck. We did have disappearing students in even earlier GSoCs though. IIRC, this is where the "two patches" rule comes from.
There was some discussion on the GSoC mentor list about this some months ago. I think what I learned from that is that when selecting students, one should ignore the awesome feature that is proposed, but look at the student's skills instead. Also, I think we/I "forgot" about the two-patches-rule. Note that this rule is not only to assess coding capability, but also to see if the student is capable of actually building Inkscape on his PC (yes, this was a time-consuming problem in last year's SoC). Perhaps a good idea to make it easier for aspiring students is to provide a list of "easy" to tackle bugs or very small improvements. Perhaps this is more important than a list of GSoC projects.
Following up on my previous mail, I have started a list of suggestions here: http://wiki.inkscape.org/wiki/index.php/Google_Summer_Of_Code#The_.22two _patches.22_rule
-----Original Message----- From: Alexandre Prokoudine [mailto:alexandre.prokoudine@...400...]
Not exactly high. The previous year was a 2/5 failure
indeed, but the
year before was 100% success, if my memory serves me well,
and we are
talking about 6 or 7 projects in 2009.
In 2010 we actually had 3/5 fail. :( It was very unfortunate and I hope we can avoid that this year as the "acceptable" (desired) rate is 80% successful.
One of disappeared students last year had been around in
the community
for a rather long time, and the other disappeared student did a successful project for GIMP in 2009, so it's quite possible that we just had our bit of bad luck. We did have disappearing students in even earlier GSoCs though. IIRC, this is where the "two patches" rule comes from.
Actually the two patches rule comes from it's the minimum requirement to get commit access to the repo. It was part of the change in attitude from sodi podi to be more welcoming. It's honestly a pretty low bar. It was decided that it would be good to require this before the students would even be considered as it was "proof" of them checking out the code and showing a form of commitment/desire to participate in GSoC (plus what Johan said about it allowing us to see to some extent if they really can read/write code).
I really think that SVG compliance projects should be a focus this year as well (not exclusive by any means though). The list Tav posted does have some really great ideas, so I think we need to really analyze what those tasks really look like and which would be reasonable GSoC projects.
Cheers, Josh
participants (5)
-
unknown＠example.com -
Alexandre Prokoudine -
Ian Caldwell -
Josh Andler -
Tavmjong Bah