faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
|
Correct & suggest
by Jakob Petsovits on Thursday 12/Apr/2007, @06:14
|
Actually, there's also a project for Python support in KDevelop, which makes the KDevelop project count go up to five, not four.
Also, I believe that in "instant messanger", the messEnger is actually spelled with an "e", while messAging is spelled with an "a". Hope you don't mind me playing the nit-picker.
Other than that, I'm thrilled to see these projects getting implemented - 40 of them is _really much_, and even if only half of them would finish successfully, it means a tremendous advance for KDE.
Mentors and students, keep in mind that communication is everything. Students have to subscibe to their specific project's mailing list, and should hang out on IRC if possible. In order to finish the project successfully, students must be involved with the actual project, its team members, its conventions, and its current developments. Students who work independently from the "live" code base and plan to merge their improvements at the very end of the program are much more likely to fail than those who get their code into the project in small incremental commits.
Drupal (which also takes part in the Summer of Code) expects a weekly progress report from their students, so that communication is facilitated, progress is encouraged, and most importantly the students are made a genuine part of the community. I find one week a bit short (maybe two could still be enough), but on the whole I think this would be a splendid idea for KDE projects as well. Thiago, think about this.
Oh, and dannya, please don't quote me in the Commit Digest this time ;) |
|
|
![[KDE Dot News]](http://www.kde.org/dot/Images/kdedotnews.gif)
