[xwiki-devs] [GSoC] Reminder: midterm evaluation in less than 3 weeks
Hello GSoC students, Time flies fast when you're having fun: only 3 weeks left until the midterm evaluation. Don't forget that, by July 6th, you should all have a project with at least 30% of the functionalities proposed in your application, which will help us estimate whether you will be able to finish your work according to the plan or not. Also, don't forget about the (at least) weekly commits requirement, very important for getting proper feedback, and about updating the wiki when you have news. Note that we believe some of the projects are not really advancing as expected, but it's probably not too late to catch up. Please communicate with one of the mentors in case you get stuck. Hoping to see some nice code committed this week, -- Sergiu Dumitriu http://purl.org/net/sergiu/
On Wed, Jun 17, 2009 at 12:56 AM, Sergiu Dumitriu <[email protected]> wrote:
Hello GSoC students,
Time flies fast when you're having fun: only 3 weeks left until the midterm evaluation. Don't forget that, by July 6th, you should all have a project with at least 30% of the functionalities proposed in your application, which will help us estimate whether you will be able to finish your work according to the plan or not. Also, don't forget about the (at least) weekly commits requirement, very important for getting proper feedback, and about updating the wiki when you have news.
Note that we believe some of the projects are not really advancing as expected, but it's probably not too late to catch up. Please communicate with one of the mentors in case you get stuck.
Hoping to see some nice code committed this week,
I didn't see much gsoc projects related communication on the devs mailing list (may be they are communicating with the relevant mentors privately). Anyway, just wanted to mention that discussing matters on the devs list is one of the best ways to keep everybody informed about what you are doing and it lets developers help you more. I know for a fact that devs list helped me a lot for making my gsoc project(s) successfull :) Just my humble opinion. Thanks. - Asiri
I personally agree with you.I was interested in one the GSoc projects and I did not have a lot news about it. It would be great if there are more communication o the mailling list. Regards, Keerthan Muthurasa 2009/6/17 Asiri Rathnayake <[email protected]>
On Wed, Jun 17, 2009 at 12:56 AM, Sergiu Dumitriu <[email protected]> wrote:
Hello GSoC students,
Time flies fast when you're having fun: only 3 weeks left until the midterm evaluation. Don't forget that, by July 6th, you should all have a project with at least 30% of the functionalities proposed in your application, which will help us estimate whether you will be able to finish your work according to the plan or not. Also, don't forget about the (at least) weekly commits requirement, very important for getting proper feedback, and about updating the wiki when you have news.
Note that we believe some of the projects are not really advancing as expected, but it's probably not too late to catch up. Please communicate with one of the mentors in case you get stuck.
Hoping to see some nice code committed this week,
I didn't see much gsoc projects related communication on the devs mailing list (may be they are communicating with the relevant mentors privately). Anyway, just wanted to mention that discussing matters on the devs list is one of the best ways to keep everybody informed about what you are doing and it lets developers help you more. I know for a fact that devs list helped me a lot for making my gsoc project(s) successfull :)
Just my humble opinion.
Thanks.
- Asiri _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Hi, Asiri Rathnayake wrote:
On Wed, Jun 17, 2009 at 12:56 AM, Sergiu Dumitriu <[email protected]> wrote:
Hello GSoC students,
Time flies fast when you're having fun: only 3 weeks left until the midterm evaluation. Don't forget that, by July 6th, you should all have a project with at least 30% of the functionalities proposed in your application, which will help us estimate whether you will be able to finish your work according to the plan or not. Also, don't forget about the (at least) weekly commits requirement, very important for getting proper feedback, and about updating the wiki when you have news.
Note that we believe some of the projects are not really advancing as expected, but it's probably not too late to catch up. Please communicate with one of the mentors in case you get stuck.
Hoping to see some nice code committed this week,
I didn't see much gsoc projects related communication on the devs mailing list (may be they are communicating with the relevant mentors privately). Anyway, just wanted to mention that discussing matters on the devs list is one of the best ways to keep everybody informed about what you are doing and it lets developers help you more. +1 There should be more communication on the mailing lists.
I need to remind the students that they should report weekly progress(Eg: blog posts on http://gsoc.xwiki.org/ ). Students should also publish their binaries(where possible) at least twice a month so that more people can give a quick feedback. IMO, gsoc projects lack a tool like jira that makes it easier for the student to organize his tasks and for the others to monitor the progress. Thanks, Florin Ciubotaru
I know for a fact that devs list helped me a lot for making my gsoc project(s) successfull :)
Just my humble opinion.
Thanks.
- Asiri _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On Jun 17, 2009, at 12:52 PM, Florin Ciubotaru wrote:
Hi,
Asiri Rathnayake wrote:
On Wed, Jun 17, 2009 at 12:56 AM, Sergiu Dumitriu <[email protected]> wrote:
Hello GSoC students,
Time flies fast when you're having fun: only 3 weeks left until the midterm evaluation. Don't forget that, by July 6th, you should all have a project with at least 30% of the functionalities proposed in your application, which will help us estimate whether you will be able to finish your work according to the plan or not. Also, don't forget about the (at least) weekly commits requirement, very important for getting proper feedback, and about updating the wiki when you have news.
Note that we believe some of the projects are not really advancing as expected, but it's probably not too late to catch up. Please communicate with one of the mentors in case you get stuck.
Hoping to see some nice code committed this week,
I didn't see much gsoc projects related communication on the devs mailing list (may be they are communicating with the relevant mentors privately). Anyway, just wanted to mention that discussing matters on the devs list is one of the best ways to keep everybody informed about what you are doing and it lets developers help you more. +1 There should be more communication on the mailing lists.
I need to remind the students that they should report weekly progress(Eg: blog posts on http://gsoc.xwiki.org/ ).
Posting on this list is even better than blogging on gsoc.xwiki.org. You'll get a much wider audience and most people don't know or won't go to gsoc.xwiki.org I'd really prefer that GSOCers integrates with current xwiki dev practices rather than invent new ones.
Students should also publish their binaries(where possible) at least twice a month so that more people can give a quick feedback.
IMO, gsoc projects lack a tool like jira that makes it easier for the student to organize his tasks and for the others to monitor the progress.
They should use the exact same tools we use for development. JIRA is there for them too as for any project. Since GSOCers are supposed to use the Sandbox SVN they're also supposed to use the SandBox JIRA project. I think one pb is that GSOCers are quite isolated in their practices: - usage of gsoc.myxwiki.org - usage of IRC These 2 practices don't generate visibility to the rest of the xwiki community automatically (people have to voluntarily go there to learn and people don't do this). For ex no important decision should be taken on IRC. You can use IRC to discuss but any important decision MUST go through the mailing list for agreement or simply to let people know and have a chance to react. Thanks -Vincent
I know for a fact that devs list helped me a lot for making my gsoc project(s) successfull :)
Just my humble opinion.
Thanks.
- Asiri
participants (5)
-
Asiri Rathnayake -
Florin Ciubotaru -
Keerthan MUTHURASA -
Sergiu Dumitriu -
Vincent Massol