Re: [xwiki-devs] Welcoming our GSoC students

Hello Everyone.! At the outset i would like to thank XWiki. Congos my fellow GSocers. Glad to be part of the community. Am Arun Reddy (irc : arunreddy) going to work on Import Export from any other Wiki being mentored by Vincent Massol. The project is all about making a provision inside XWiki to import from various Wikis ( Confluence, MediaWiki, Tikiwiki etc.. ) using a Wizard based approach. My plan of action for this community bonding period : 1. Study Import and Export features of other wikis. 2. Fix some jira issues related to my project ( XWiki Rendering and Parsing ) 3. Coming up with ideas and use cases. 4. Research on best practices and design patterns related to my project. 5. Getting familiar with tools and XWiki culture. 6. Come up with a plan of action for the project with all necessary documentation on approach, architecture, implemenation which is appealing to the community. Once again thanks for accepting.I shall put in my sincere efforts to live up to your expectations. -- Best Regards, Arun Reddy On Wed, Apr 22, 2009 at 4:10 AM, Sergiu Dumitriu <sergiu(a)xwiki.com> wrote: during the selection period, and welcome in the XWiki development team. thank again all those who showed interest in XWiki for this Summer of Code. We had an impressive number of good applications this year, with professional approaches and interesting ideas, and it was very difficult to choose only 6. Unfortunately, some very good students, with great potential, were not accepted. So, to those interested in getting involved anyway, without Google's implication, I renew the invitation to put your ideas in practice under the guidance of the community. Even though the money will be missing, you can still take advantage of the other GSoC benefits: learning new things, gaining experience, earning recognition, etc [ http://www.catb.org/~esr/writings/cathedral-bazaar/homesteading/]. http://socghop.appspot.com/document/show/program/google/gsoc2009/timeline], the next month (April 20th - May 23rd) is to be used for community bonding. project on the dev list, so that everyone knows who you are and what to expect from you. and the developers. Please make sure you all read and understand the following - very useful - documents: officially in charge with your guidance, almost all interaction should be done 'in the open' as much as possible, on the IRC channel or on the mailing list. You should choose the communication medium according to the importance of the matters to be discussed: naturally, the less important issues are to be discussed on IRC, while the design decisions, important progress announcements and testing/feedback requests go on the list. This way, the community is informed on the evolution of your project, and other developers can come up anytime with useful ideas and suggestions. Moreover, if your mentor is hit by a bus (the bus factor [ http://en.wikipedia.org/wiki/Bus_factor]), another developer can take his place with little effort. a bad approach. However, please keep in mind that too much communication can also be harmful, as it distracts the others from their own work. You need to be able to communicate just right: decisions developer (or a student that fought the same problem) could quickly provide you an answer; however, do try to find the answer yourself at first. good? It doesn't work, help me!" building my project, and googling for a solution doesn't seem to help. Looking at the error, I think that there's a wrong setting for the assembly plugin, but nothing I tried works. Can someone please take a look?" monitoring the discussions. It is also recommended to subscribe to the users list, but not mandatory. The notifications list is a little too high volume and technical for the moment, but it is a great knowledge source. and log your progress: http://gsoc.myxwiki.org/ . Each student must register on this wiki, create and organize a space for the project, with a blog where the evolution will be described. Currently the wiki is pretty empty, but it will grow. documentation. [ http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/] http://en.wikipedia.org/wiki/Test-driven_development][http://www.amazon.com…] approach and to experience agile development [ http://www.amazon.com/dp/0596527675/]. After the first coding week, you must have some code that works. It won't do much, of course, but it will be the seed of your project. Every functionality will be validated by tests. The code must be properly tested and commented at the time of the writing (don't think you'll do that afterwards, because in most cases you won't). you to do __at least__ weekly commits (ideally, if you are well organized, you should be able to commit code that works daily, so try to aim at daily commits). This way, the code can be properly reviewed, and any problems can be detected before they grow into something too difficult to fix. One big code blob committed at the end, no matter how good it may seem, is a failure at several levels. prepare the maven build, which will give you the first unit test for the first class. master Maven, JUnit, Selenium, component driven development, ... your project__ -- This will help you get more familiar with the code your project needs to interact with. and write several use case scenarios. of the project, well documented on the wiki, you should have the build infrastructure ready, and you should be pretty familiar with the existing code you will need to interact with. And, of course, you should be familiar with the community and the way we communicate.