Hello, You can count me as available mentor. I currently got one idea for possible projects and I'll try to add it to the ideas page this weekend.
Andrius aka thunderstruck On 8 February 2014 00:42, Nils Kneuper <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Am 07.02.2014 23:56, schrieb Ignacio R. Morelle: > > Hello, > > > > I have taken a look at the SummerOfCodeIdeas [1] page in the wiki and > > changed some formatting [2] and content [3] for the sake of clarity and > > style. > > > > 1: http://wiki.wesnoth.org/SummerOfCodeIdeas 2: > > > http://wiki.wesnoth.org/index.php?title=SummerOfCodeIdeas&diff=52985&oldid=52970 > > > > > 3: > http://wiki.wesnoth.org/index.php?title=SummerOfCodeIdeas&diff=52986&oldid=52985 > > > > However, there are still a couple of important points left -- I don't > know > > what to do with them at the moment. > > > >> If you haven't done so yet, create an account on gna.org (required for > >> committing later on) [...] Though not mandatory, it is highly advisable > >> to go to the EasyCoding and NotSoEasyCoding pages and implement one of > >> these ideas (or any idea of similar scope) so we have an idea how you > >> work. Be sure to use your gna account when submitting these patches so > we > >> know who it is coming from. You can also implement some features from > our > >> feature request database at gna. When you implement something, also list > >> it on your own page with a reference to the patch. This should give you > a > >> good idea what the Wesnoth sourcecode is like and will provide a good > >> start to getting used to our coding style, too. You can also start > >> working on your project and submit patches/prototypes related to it > > > > I had improved their wording in a separate copy some months ago, but > > referring to GitHub and pull requests (since that's what we are using > > nowadays) instead of Gna.org and patches: > > > >> If you haven't done so yet, create an account on [https://github.com/ > >> Github.com] (required for pull requests and for granting you commit > >> access to the main repository). [...] Though not mandatory, it is highly > >> advisable to take a look at the [[EasyCoding]] and [[NotSoEasyCoding]] > >> pages and implement one of the proposed ideas ideas (or any idea of > >> similar scope) so we can have an idea of how you work. Be sure to use > >> your GitHub account when submitting pull requests so we know who it is > >> coming from. You can also implement some features from our feature > >> request database at Gna.org. When you implement something, also list it > >> on your own page with a reference to the patch. This should give you a > >> good idea what the Wesnoth source code is like and will provide a good > >> start to getting used to our coding style, too. You can also start > >> working on your project and submit patches/prototypes related to it. > > > > However, the Patch Submission Guidelines [4] still refer to patches on > > Gna.org since the new version lipkab has been working on [5] is not ready > > yet. > > > > 4: http://wiki.wesnoth.org/PatchSubmissionGuidelines 5: > > http://forums.wesnoth.org/viewtopic.php?f=16&t=39838 > > > > Should I go and apply those pending edits on the SoC ideas page anyway? > > Should I mention Gna.org for bug reports separately as well? > > Yes, please go ahead and apply the pending changes to the wiki page. > Mention > gna.org separately as location for the mailing list as well as the bug > reports. > > Today I had a look at getting the questions we need to answer. I updated > the > information for google page [1] with those questions. There are still some > "TODOs" on that page. It would be great if you could help me with those. > > Please also make sure to have a rough look at [2] to check if you are > represented correctly. After todays cleanup it should already be in a good > shape (thanks folks!) but please make sure you are represented justly to > be sure. > > In addition we also need to get some ideas together. Currently there is > nothing written out. You can see the available ideas when looking at the > category for 2014 [3]. It might be good to have a look at the 2013 ideas > [4] > and move over what is still valid into no pages which belong into the > category > [3]. > > One important thing though is to get to know the list of available > mentors. So > who would be really willing to mentor either as single mentor or in a team > with another dev. This is also important information for the application > form, > so please make sure to tell me. > > I plan to submit the form sometime later tomorrow, ehm, today. That is the > information can of course still be updated, especially the list of ideas > should be updated until Friday. > > Cheers, > Nils Kneuper aka Ivanovic > > PS: Thanks for your help and support getting things setup! > > > [1] http://wiki.wesnoth.org/SoC_Information_for_Google > [2] http://wiki.wesnoth.org/SoC_People_to_bug_on_IRC > [3] http://wiki.wesnoth.org/Category:Summer_of_Code_2014 > [4] http://wiki.wesnoth.org/Category:Summer_of_Code_2013 > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (GNU/Linux) > > iEYEARECAAYFAlL1fXEACgkQfFda9thizwX54ACfdUdtJOxOcUd5tNRSqdJHtLL7 > kRAAn06JyFr9qPvmWtcdWBiYIuLgHrrG > =Hxlt > -----END PGP SIGNATURE----- > > _______________________________________________ > Wesnoth-dev mailing list > [email protected] > https://mail.gna.org/listinfo/wesnoth-dev >
_______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
