DokuWiki

It's better when it's simple

User Tools

Site Tools


devel:gsoc

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
devel:gsoc [2012-03-05 21:30]
ach added link to odt initiative
devel:gsoc [2014-02-27 00:24] (current)
Klap-in
Line 3: Line 3:
 (Mentors should read [[devel:​gsoc_organization]]) (Mentors should read [[devel:​gsoc_organization]])
  
-DokuWiki was a mentoring organization for 2011's [[http://​www.google-melange.com/​gsoc/​program/​home/​google/​gsoc2011|Google Summer of Code]] and has decided to apply for 2012.+DokuWiki was a mentoring organization for 2011's [[http://​www.google-melange.com/​gsoc/​program/​home/​google/​gsoc2011|Google Summer of Code]] and applied ​for 2012 but has been rejected.
  
-If you are interested in applying for getting ​stipend ​for working at DokuWiki make sure you've read and understood the information on [[http://​www.google-melange.com/​gsoc/​program/​home/​google/​gsoc2012|the official GSoC 12]] website and the information below. Noting the dates you can find on the [[http://​www.google-melange.com/​document/​show/​gsoc_program/​google/​gsoc2012/​timeline|timeline]] ​in order to make sure you don't miss them is probably a good idea, too.  +Even though DokuWiki is not mentoring organization ​for Google Summer of Code 2012 you can still get in touch with us and work on these ideas, ​however there will be no stipend
- +
-Below you can find our [[#ideas]] you can use, but we encourage you to discuss your own ideas with us, too. You should however discuss your ideas before you submit your application so we can make sure your ideas match our expectations ​and you've really understood what you need to do in order to implement a certain feature. All of our ideas aren't like "I take this idea" but require your ownadditional ideas, too. You need to put more details about how exactly you want to implement an idea into your application,​ for some of the ideas we've also listed some special points you should include into your application.+
  
 If you want to get in contact with us you can write mails to the [[:​mailinglist]] or join the [[:​irc|IRC]] channel. If you want to get in contact with us you can write mails to the [[:​mailinglist]] or join the [[:​irc|IRC]] channel.
  
-You can already get started getting familiar with DokuWiki, fix bugs, implement small features etc.. Of course your official GSoC project needs to be different from that, but being already familiar with DokuWiki gives you both advantages during application (because you will understand much better how a certain feature ​can be implemented) and during the actual work where you can get started right away. The [[http://​www.google-melange.com/​document/​show/​gsoc_program/​google/​gsoc2012/​faqs#already_opensource|FAQ]] of the Google Summer of Code states explicitly that as long as you fulfill all requirements ​you can continue working for projects during GSoC you have been working for before.+Below you can find our [[#ideas]] you can use, but we encourage ​you to discuss your own ideas with us, too.  All of our ideas aren't like "I take this idea" but require your own, additional ideas, too.
  
 If you want some more detailed information on how the whole Google Summer of Code works the [[http://​www.booki.cc/​gsocstudentguide/​|GSoCStudentGuide]] is a really good and extensive guide for students. If you want some more detailed information on how the whole Google Summer of Code works the [[http://​www.booki.cc/​gsocstudentguide/​|GSoCStudentGuide]] is a really good and extensive guide for students.
Line 17: Line 15:
 ===== Ideas ===== ===== Ideas =====
  
-This is list shall give you a rough overview over each idea. You can find a lot more information at the pages of the individual ​pages. Please don't add your own ideas here but instead contact the mailinglist or one of the mentors ​listed above if you have your own ideas (which is of course great). These ideas aren't sorted in any particular order so please don't pick just the first idea.+This is list shall give you a rough overview over each idea. You can find a lot more information at the pages of the individual ​ideas. Please don't add your own ideas here but instead contact the mailinglist or one of the mentors if you have your own ideas (which is of course great). These ideas aren't sorted in any particular order so please don't pick just the first idea.
  
 :!: The green headings are links to a page for each idea that provides much more information than these short summaries. :!: :!: The green headings are links to a page for each idea that provides much more information than these short summaries. :!:
Line 36: Line 34:
     * Possible mentors: [[user>​andi|Andreas Gohr]], [[user>​hakans|Håkan Sandell]], [[user>​adrianlang|Adrian Lang]]     * Possible mentors: [[user>​andi|Andreas Gohr]], [[user>​hakans|Håkan Sandell]], [[user>​adrianlang|Adrian Lang]]
     * Difficulty: Medium     * Difficulty: Medium
-  * **Work on some plugin(s)**:​ There are plugins like the [[plugin:​tag]] plugin, ​the [[plugin:​discussion]] plugin or the [[plugin:​blogtng]] plugin that work but their internal design could be improved, they could make use of newer DokuWiki features like the [[devel:​metadata#​metadata index]] ​or some functionality is still missing like caching for blogtng. Look at their issue trackers and the code and discuss the details of the project with us on the [[:​mailinglist]]. We can also give you further ideas what could be improved in these plugins. You can also propose any other plugin or something more general like adding [[plugin:​odt]] export support for [[:odt_initiative|a list of plugin]]. It just needs to be coordinated with the plugin author/​maintainer if there is somebody maintaining the plugin currently. +  * **Work on some plugin(s)**:​ There are plugins like the the [[plugin:​discussion]] plugin or the [[plugin:​blogtng]] plugin that work but their internal design could be improved or some functionality is still missing like caching for blogtng. Look at their issue trackers and the code and discuss the details of the project with us on the [[:​mailinglist]]. We can also give you further ideas what could be improved in these plugins. You can also propose any other plugin or something more general like adding [[plugin:​odt]] export support for [[plugin:odt:rendersupport|a list of plugins]]. It just needs to be coordinated with the plugin author/​maintainer if there is somebody maintaining the plugin currently. 
-  * **your own idea**: Apart from the above we're of course ​also open for your own ideas, if they shouldn'​t fit into DokuWiki core we can also elaborate on how you can implement them as a plugin (you can also work on plugins and other software related to DokuWiki during GSoC). ​But please do discuss your idea in the mailinglist before you submit your application so we can make sure your ideas match our expectations. ​+  * **Your own ideas**: We are also open for your own ideas, if they shouldn'​t fit into DokuWiki core we can also elaborate on how you can implement them as a plugin (you can also work on plugins and other software related to DokuWiki during GSoC). ​Please ​discuss your ideas on the [[:mailinglist]] before you submit your application so we can make sure your ideas match our expectations. 
 ===== What we expect of you ===== ===== What we expect of you =====
  
-  ​* Subscribe to the [[:​mailinglist]] - you can't do this early enough. The mailinglist is our main communication channel and also the best way how you can contact us. Once you will be accepted by us (April ​25 19:00 UTC) we will announce your participation on the mailinglist and then you should be available on the mailinglist in order to present yourself and what you will be doing. There are usually also some developers in our [[:​irc|IRC]] channel so joining the IRC channel would be good, too. +This is just for reference in the case you're wondering what a full GSoC project would be like, if you want to implement any of these ideas outside of GSoC these expections won't apply. 
-  * Integrate yourself in the DokuWiki community. Write mails to the mailinglist about what you've done so far, which parts of your work can already be tested etc. In the first phase you should also try [[http://bugs.dokuwiki.org/|fixing some bugs]] or implementing some smaller features so you get familiar with the whole development workflow in DokuWiki.+ 
 +  ​* Subscribe to the [[:​mailinglist]] - you can't do this early enough. The mailinglist is our main communication channel and also the best way how you can contact us. Once you will be accepted by us (April ​23 19:00 UTC) we will announce your participation on the mailinglist and then you should be available on the mailinglist in order to present yourself and what you will be doing. There are usually also some developers in our [[:​irc|IRC]] channel so joining the IRC channel would be good, too. 
 +  * Integrate yourself in the DokuWiki community. Write mails to the mailinglist about what you've done so far, which parts of your work can already be tested etc. In the first phase you should also try [[https://github.com/​splitbrain/​dokuwiki/issues|fixing some bugs]] or implementing some smaller features so you get familiar with the whole development workflow in DokuWiki.
   * Be responsive. You should write regular mails to your mentor and answer questions both by private mail from the mentor(s) and also questions concerning your work on the mailinglist. Make sure you're also available for questions directly after the application period because we'll probably ask you some more questions then.   * Be responsive. You should write regular mails to your mentor and answer questions both by private mail from the mentor(s) and also questions concerning your work on the mailinglist. Make sure you're also available for questions directly after the application period because we'll probably ask you some more questions then.
-  * Commit early, commit often. You shouldn'​t create one huge patch with your changes but instead a series of small commits ​that each of them cover one small and understandable change. Depending on the feature you are working ​at we should also be able to merge your changes into the main repository from time to time (or we'll even ask you to work directly in the main repository).+  * Commit early, commit often. You shouldn'​t create one huge patch with your changes but instead a series of small commits. Each of them should ​cover one small and understandable change. Depending on the feature you are working ​on we should also be able to merge your changes into the main repository from time to time (or we'll even ask you to work directly in the main repository).
   * Be prepared to have two short demo's in IRC during GSoC, to show other developers the progress of your project.   * Be prepared to have two short demo's in IRC during GSoC, to show other developers the progress of your project.
   * Make clear when you'll be available/​working and when not. The idea is that you'll work around 40 hours/week, if you can't do this during the whole time we need to know this in advance.   * Make clear when you'll be available/​working and when not. The idea is that you'll work around 40 hours/week, if you can't do this during the whole time we need to know this in advance.
Line 54: Line 55:
 ===== The application ===== ===== The application =====
  
-If DokuWiki ​should be accepted as mentoring organization you will be able to apply between March 26 19:00 UTC and April 6 19:00 UTC as student for GSoC on the official ​website. Please make sure you include the following points into your application. This is meant as help for you, if you don't follow this list but still cover the points this is okay, too.+ 
 +As DokuWiki ​is no mentoring organization ​for Google Summer of Code 2012 you don't need to apply in any official ​way. If you are interested in any project just contact us. You can answer some of the questions mentioned below in order to give us a better idea what we could expect of you and which kind of mentoring you need. 
 + 
 +Please make sure you include the following points into your application. This is meant as help for you, if you don't follow this list but still cover the points this is okay, too.
  
   * Who are you? Just to make interaction easier provide some basic facts like where you live and study. Please also provide details how we are able to contact you to ask further details if needed.   * Who are you? Just to make interaction easier provide some basic facts like where you live and study. Please also provide details how we are able to contact you to ask further details if needed.
Line 67: Line 71:
 ^Year ^Student ^Project ^Mentor ^Result ^1 year later ^ ^Year ^Student ^Project ^Mentor ^Result ^1 year later ^
 |2011 |[[https://​github.com/​akate|Kate]] ​         |Media revisions ​  | Andi |merged into 2011 release "​Augua"​| | |2011 |[[https://​github.com/​akate|Kate]] ​         |Media revisions ​  | Andi |merged into 2011 release "​Augua"​| |
-|2011 |[[https://​github.com/​piyushmishra|Piyush]] |Extension manager | Håkan|released as separate plugin| |+|2011 |[[https://​github.com/​ofpiyush|Piyush]] |Extension manager | Håkan|released as separate plugin| |
  
 ^Year ^Applications ^Students ^Succeed ^Mentors ^ ^Year ^Applications ^Students ^Succeed ^Mentors ^
 |2011 |   ​50 ​       |  2      |  2     | 4 Andi/​Håkan/​Anika/​Michitux(GSoC admin) | |2011 |   ​50 ​       |  2      |  2     | 4 Andi/​Håkan/​Anika/​Michitux(GSoC admin) |
devel/gsoc.1330979415.txt.gz · Last modified: 2012-03-05 21:30 by ach