Re: [Inkscape-devel] GSoC 2011 announced
So for students to even be considered, let alone accepted accepted, they must first have commit access to the repo? I didn't think you had to be completely familiar with the code since you are a 'student'. Please help me with this because I want to apply but haven't had the time to go through all the doxygen docs and become familiar with the code yet.
On Jan 25, 2011 10:49 AM, "Josh Andler" <scislac@...400...> wrote:
-----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
------------------------------------------------------------------------------
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 Jan 26, 2011, at 9:16 AM, Eric Kuzmenko wrote:
So for students to even be considered, let alone accepted accepted, they must first have commit access to the repo? I didn't think you had to be completely familiar with the code since you are a 'student'. Please help me with this because I want to apply but haven't had the time to go through all the doxygen docs and become familiar with the code yet.
Well... the first step is to be able to pull and build.
Then you need to be able to change *something*. Hopefully in a way that might eventually lead to fixing a bug or improving the codebase.
Then just push up two of these. They can be smaller.
In general, a student will need the basic ability to work on code already. Just in getting to the state of being able to submit small changes as patches, many things will be discovered and problems will arise and be overcome.
Drop into the chat room if you need guidance on where to poke at the code once you have your local build successfully going.
On Wed, 2011-01-26 at 10:28 +1000, Jon Cruz wrote:
On Jan 26, 2011, at 9:16 AM, Eric Kuzmenko wrote:
So for students to even be considered, let alone accepted accepted, they must first have commit access to the repo? I didn't think you had to be completely familiar with the code since you are a 'student'. Please help me with this because I want to apply but haven't had the time to go through all the doxygen docs and become familiar with the code yet.
Well... the first step is to be able to pull and build.
I want to stress this as there are so many student projects I've worked on where time has been wasted setting up a build environment. More time than I want to talk about. That's what I think is most important about the two patch requirement.
--Ted
Setting up build environments is not hard so long has I have some docs to show me how to set it up. I just to get used to the code is all, and I want to make sure I know enough to start submitting patches by the time I apply, I just have a hard time starting off.
On Tue, Jan 25, 2011 at 9:24 PM, Ted Gould <ted@...11...> wrote:
On Wed, 2011-01-26 at 10:28 +1000, Jon Cruz wrote:
On Jan 26, 2011, at 9:16 AM, Eric Kuzmenko wrote:
So for students to even be considered, let alone accepted accepted, they must first have commit access to the repo? I didn't think you had to be completely familiar with the code since you are a 'student'. Please help me with this because I want to apply but haven't had the time to go through all the doxygen docs and become familiar with the code yet.
Well... the first step is to be able to pull and build.
I want to stress this as there are so many student projects I've worked on where time has been wasted setting up a build environment. More time than I want to talk about. That's what I think is most important about the two patch requirement.
--Ted
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, Jan 25, 2011 at 7:36 PM, Eric Kuzmenko <eric.gralco@...400...> wrote:
Setting up build environments is not hard so long has I have some docs to show me how to set it up. I just to get used to the code is all, and I want to make sure I know enough to start submitting patches by the time I apply, I just have a hard time starting off.
Hi Eric,
Okay, so have you checked out Inkscape from launchpad yet? That is a great first step (don't hesitate to choose to do a lightweight checkout if you're not looking for a ton of revision history at this point).
Next, visit http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape and find the instruction which pertain to your OS/Distro. See how far you can get with configuration and/or compilation.
If and when you run into any issues, please don't hesitate to drop a message to the devel list (in a new thread) or to drop in irc to see if you can get some interactive assistance. Good luck on getting started.
Cheers, Josh
P.S. I'm sorry if it sounded daunting earlier, we're not looking for patches that fix our oldest and highest priority bugs. Aim for some low hanging fruit in the bug tracker. :)
On Tue, Jan 25, 2011 at 9:36 PM, Eric Kuzmenko <eric.gralco@...400...> wrote:
Setting up build environments is not hard so long has I have some docs to show me how to set it up. I just to get used to the code is all, and I want to make sure I know enough to start submitting patches by the time I apply, I just have a hard time starting off.
(I'm not a developer, more like a hobbyist ;)
FWIW here is my history (typos too, with [notes]) from getting Inkscape to build on a freshly-installed Ubuntu 10.10:
361 sudo aptitude install bazaar [wrong package name] 362 sudo aptitude install bzr 363 mkdir projects 364 cd projects/ 365 bzr launchpad-login cr33dog 366 bzr branch lp:inkscape [oops, need to generate a public key for this machine] 367 ssh-keygen -t rsa 368 cat /home/cr33/.ssh/id_rsa.pub [pasted this into launchpad] 369 bzr branch lp:inkscape 370 ls 371 cd inkscape/ 372 ls 373 sudo aptitude build-dep inkscape [c++ compiler, plus deps] 374 ./autogen.sh --prefix=/opt/inkscape-bzr [did not need --prefix here] 375 ./configure --prefix=/opt/inkscape-bzr 376 make [grab some coffee...] 377 sudo make install 378 /opt/inkscape-bzr/bin/inkscape [eet's aliiiiiive!] 379 history
More info on Inkscape/Bazaar: http://wiki.inkscape.org/wiki/index.php/Working_with_Bazaar
Chris
-----Original Message----- From: Eric Kuzmenko [mailto:eric.gralco@...400...] Sent: Wednesday, January 26, 2011 00:16 To: Inkscape-devel Subject: Re: [Inkscape-devel] GSoC 2011 announced
So for students to even be considered, let alone accepted accepted, they must first have commit access to the repo? I didn't think you had to be completely familiar with the code since you are a 'student'. Please help me with this because I want to apply but haven't had the time to go through all the doxygen docs and become familiar with the code yet.
See what I wrote [1]: " Inkscape is a large project, and you really should not try to understand all the code. Many (all?) developers know only parts of the program code! "
I think our doxygen docs are in bad shape; making it better would be a GSoC project itself!
Here the story of how I got involved, *without* reading any documentation on Inkscape's code: For most bugfixes, what you should do is search all code files for a certain string that is related to the bug. This way you localize where the bug is likely to be. Read the code around the string and you are well on your way to fix it. My first patch was the "Save a copy..." menu entry: 1. "Save as..." is very similar to the functionality what I want. 2. Search all code files for string "Save as..." 2.a I can't find it... hmm... 2.b Search for statusbar text "Save document under a new name" 3. Found it! Hey this file looks like it defines the menus. Let's add a "Save a copy..." thingie similar to "Save as...". 3.a Search code for anything related to what I find in the file I found (in this case, FileSaveAs, SP_VERB_FILE_SAVE_AS), and make a smart copy of that for SaveACopy 4. Build. 5. There is my menu item! Click on it... ah, it opens the save as dialog. Good. 6. The menu entry in the code file I just changed points to a certain "VERB", which leads to a function "sp_file_save_as"; so copy that function, rename to "sp_file_save_a_copy", etc. 7. ...
I did not understand much about Inkscape's code, I didn't need to.
What I want to say is: don't start with reading doxygen or documentation. Start with fixing something small, or add/improve simple functionality that is very similar to what already exists. Once you have something that works, you can always send it for code-review to the mail list! :-)
Cheers, Johan
[1] http://wiki.inkscape.org/wiki/index.php/Google_Summer_Of_Code#The_.22two _patches.22_rule
2011/1/26 <J.B.C.Engelen@...1578...>:
I think our doxygen docs are in bad shape; making it better would be a GSoC project itself!
Unfortunately GSoC doesn't accept documentation-only projects.
As for the project ideas, I think the most dire thing that needs fixing is flowtext. Problems with flowtext are tied to two facts 1. SP tree elements can only be created by adding XML nodes - so you need to know the representation to actually create something (very bad, this should be private to the element's implementation!) 2. svg:switch is present in the SP hierarchy as a group-like element; I think when processing a switch Inkscape should just pick the first element it understands and put it in the SP tree
PS in case anyone is wondering whether I'll participate this year - I don't know yet; there are some nuclear chemistry-related internships open this year at the Paul Scherrer Institute in Switzerland and I'm considering applying there.
Regards, Krzysztof
I want to stress this as there are so many student projects I've worked on where time has been wasted setting up a build environment. More time than I want to talk about. That's what I think is most important about the two patch requirement.
Perhaps you could talk Amazon Web Services into donating a virtual machine for each confirmed GSoC participant. A veteran Inkscape developer could set up the VM with a build environment ready to go. You can use thier Micro VMs for free.
Bill
participants (8)
-
unknown＠example.com -
Chris Mohler -
Eric Kuzmenko -
Jon Cruz -
Josh Andler -
Krzysztof Kosiński -
Ted Gould -
william.crocker＠...2318...