[xwiki-devs] Welcoming our GSoC students
Hello Google Summer of Code students, First of all, congratulations on your applications and your activity during the selection period, and welcome in the XWiki development team. Before guiding the accepted students to their next steps, we'd like to 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/]. If you would like to do that, please let us know by replying to this mail. For the accepted students, here are some getting started hints: Community bonding period According to the program timeline [http://socghop.appspot.com/document/show/program/google/gsoc2009/timeline], the next month (April 20th - May 23rd) is to be used for community bonding. The first thing to do, sometime this week, is to present yourself and your project on the dev list, so that everyone knows who you are and what to expect from you. Also, you should continue getting acquainted with the code, the practices and the developers. Please make sure you all read and understand the following - very useful - documents: - http://purl.org/xwiki/community/ - http://purl.org/xwiki/dev/ - http://platform.xwiki.org/xwiki/bin/view/Features/ Mentorship We prefer open mentorship. While your assigned mentor is the one 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. Communication Sitting alone in your room, working secretly on your project is definitely 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: - provide meaningful information about your progress, - ask the community's opinion on non-trivial design or implementation decisions - avoid waisting a lot of time on a problem, when a more experienced 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. Wrong: "Where do I start? What do I do now? And how do I do that? Is this good? It doesn't work, help me!" Right: "Since a couple of hours ago I get a strange exception when 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?" Subscribe to the devs list (if you didn't do this already), and start 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. We have set up a wiki on the community farm for you to organize your ideas 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. Development process The project's lifecycle is NOT design -> implementation -> testing -> documentation. [http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/] We invite you to adopt a test driven development [http://en.wikipedia.org/wiki/Test-driven_development][http://www.amazon.com/dp/0321146530][http://www.amazon.com/dp/0201485672/] 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). We will create the proper projects in the xwiki sandbox, and we encourage 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. A simple way of having something functional in the first week is to prepare the maven build, which will give you the first unit test for the first class. Next steps, in a nutshell - Get more familiar with the code and development process and try to master Maven, JUnit, Selenium, component driven development, ... - Continue fixing a few small issues, chosen so that they are __related to your project__ -- This will help you get more familiar with the code your project needs to interact with. - Refine and organize the ideas concerning your project (use the wiki), and write several use case scenarios. - Start writing the first piece of code for your project. At the end of the community bonding period, you should have a clear vision 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. Good luck, and may we all have a great Summer of Code! -- Sergiu Dumitriu http://purl.org/net/sergiu/
Hi I was interested in GSOC idea on XMPP integration with XWiki, I would like to contribute to this work even tough my idea was not selected, I would like to learn XWiki and contribute to this idea, while doing some part time work. I think my idea was not selected to GSOC for some other student. I would be rather happy to work on this idea, but I would not strictly able to meet the GSOC deadlines, any way for my experience I would like to work on this. Please let me know if this could be possible, I would be glad to contribute to this. Kind regards, -Tharindu
Hi everyone, i applied for the Anti Vandalism Filters project and i would like to work on it. The only problem is that i will not be able to respect the deadlines as i will only be able to get involved part time, is that ok? Have a great day, Ancuta Gheorghe
Ancuta Maria Gheorghe wrote:
Hi everyone,
i applied for the Anti Vandalism Filters project and i would like to work on it. The only problem is that i will not be able to respect the deadlines as i will only be able to get involved part time, is that ok?
Hi Ancuta, Sure you are welcome to work on it. I will be your main mentor (looks like I'll have lots of students to mentor this year). Using an agile, incremental approach, the longer timeline won't be a problem. This is more of a meta-project, with lots of submodules that can be solved individually. As Jerome said on IRC, you can start with making the existing JCaptcha integration easy to enable and use. -- Sergiu Dumitriu http://purl.org/net/sergiu/
Hi, On Wed, Apr 22, 2009 at 5:55 PM, Sergiu Dumitriu <[email protected]> wrote:
Ancuta Maria Gheorghe wrote:
Hi everyone,
i applied for the Anti Vandalism Filters project and i would like to work on it. The only problem is that i will not be able to respect the deadlines as i will only be able to get involved part time, is that ok?
Hi Ancuta,
Sure you are welcome to work on it. I will be your main mentor (looks like I'll have lots of students to mentor this year).
Sergiu, I can work as the mentor on XOO integration if want to free up some time. Guillaume
Using an agile, incremental approach, the longer timeline won't be a problem. This is more of a meta-project, with lots of submodules that can be solved individually. As Jerome said on IRC, you can start with making the existing JCaptcha integration easy to enable and use. -- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Guillaume Lerouge Product Manager - XWiki Skype ID : wikibc http://guillaumelerouge.com/
Guillaume Lerouge wrote:
Hi,
On Wed, Apr 22, 2009 at 5:55 PM, Sergiu Dumitriu <[email protected]> wrote:
Ancuta Maria Gheorghe wrote:
Hi everyone,
i applied for the Anti Vandalism Filters project and i would like to work on it. The only problem is that i will not be able to respect the deadlines as i will only be able to get involved part time, is that ok? Hi Ancuta,
Sure you are welcome to work on it. I will be your main mentor (looks like I'll have lots of students to mentor this year).
Sergiu, I can work as the mentor on XOO integration if want to free up some time. Guillaume
Well, since we're promoting open mentorship, we can both be mentors there. You'll be the product manager, I'll be the coach, OK? -- Sergiu Dumitriu http://purl.org/net/sergiu/
Hi, That is great news (from all those that replied so far: Tharindu, Ancuta, Keerthan, Chathura, Harsha). To get you started, everything that was suggested to the accepted students can apply to you, too: reading the useful documentation, getting more acquainted with our development process, creating your own spaces on the GSoC wiki. Of course, your time frame will basically be as flexible as you want it, since you are doing this voluntarily. It is great to meet such enthusiastic students. Tharindu Madushanka wrote:
Hi
I was interested in GSOC idea on XMPP integration with XWiki, I would like to contribute to this work even tough my idea was not selected, I would like to learn XWiki and contribute to this idea, while doing some part time work. I think my idea was not selected to GSOC for some other student. I would be rather happy to work on this idea, but I would not strictly able to meet the GSOC deadlines, any way for my experience I would like to work on this. Please let me know if this could be possible, I would be glad to contribute to this.
Yes, the XMPP integration project currently has no developer assigned, so you are welcome to work on it. For the XMPP part, I think that you are the one that knows the most about that, so we won't be able to help you much. For the rest, Asiri has offered to be the primary mentor. -- Sergiu Dumitriu http://purl.org/net/sergiu/
Hi all, congrats to all the other students who were accepted! I'm Alexandru Cismaru (Alex, alexmaru on the IRC) and I'll work on "XWiki widget and firefox extension" being mentored by Guillaume Lerouge, this project is about exposing wiki relevant information in a widget. Because I was a GSOC student last year I expect to perform very well and to exceed your expectations. Here is my plan of action: 1. Doing some research about the diferences between different widget platforms. 2. Discuss with the community about the architecture and user interface of the widget. 3. Develop a web widget (maybe for iGoogle). 4. Customize the web widget to work with other web platforms (NetVibes, Facebook, and others). 5. Develop a desktop widget (for Google Gadgets), it should be similar to the web widget . 6. Customise the desktop widget to work with other desktop widget platforms (Vista Sidebar, Dashboard, and others). 7. Develop the Firefox Extension (with the web widget functionalities), the user interface will be defined with XUL, but I think we will reuse much of the web widget Javascript code. 8. Develop a rich internet application with the functionalities of the widget, in Adobe AIR. Thank you for accepting me, you'll not be disappointed. Best Regards, Alex
Hello, I applied for the xwiki export import feature but unfortunately I was not accepted.However I will be glad to bring my litle contribution to xwiki and learn more from you guys.For the moment I am working on my Msc dissertation project and I would like to aquire better knowledge about xwiki API. I will start by having a look on the existing code and try to propose some patch.As soon I will finish my dissertation I will be back to work on xwiki. Regards, Keerthan Muthurasa 2009/4/22 Alexandru Cismaru <[email protected]>
Hi all, congrats to all the other students who were accepted!
I'm Alexandru Cismaru (Alex, alexmaru on the IRC) and I'll work on "XWiki widget and firefox extension" being mentored by Guillaume Lerouge, this project is about exposing wiki relevant information in a widget. Because I was a GSOC student last year I expect to perform very well and to exceed your expectations. Here is my plan of action:
1. Doing some research about the diferences between different widget platforms. 2. Discuss with the community about the architecture and user interface of the widget. 3. Develop a web widget (maybe for iGoogle). 4. Customize the web widget to work with other web platforms (NetVibes, Facebook, and others). 5. Develop a desktop widget (for Google Gadgets), it should be similar to the web widget . 6. Customise the desktop widget to work with other desktop widget platforms (Vista Sidebar, Dashboard, and others). 7. Develop the Firefox Extension (with the web widget functionalities), the user interface will be defined with XUL, but I think we will reuse much of the web widget Javascript code. 8. Develop a rich internet application with the functionalities of the widget, in Adobe AIR.
Thank you for accepting me, you'll not be disappointed.
Best Regards, Alex _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Keerthan MUTHURASA wrote:
Hello,
I applied for the xwiki export import feature but unfortunately I was not accepted.However I will be glad to bring my litle contribution to xwiki and learn more from you guys.For the moment I am working on my Msc dissertation project and I would like to aquire better knowledge about xwiki API. I will start by having a look on the existing code and try to propose some patch.As soon I will finish my dissertation I will be back to work on xwiki.
Hi Keerthan, This is great. However, as the import/export feature is quite important, we have given it to another student (if we had one more slot, you would have been accepted on it). Now, you have three options: - Work together with Arun on this project - Find another project you would like to work on - Don't take a whole project, but be active in the general development of XWiki, working on various aspects, much like I'm doing. Any estimate on when your dissertation will be ready? -- Sergiu Dumitriu http://purl.org/net/sergiu/
Hello Sergiu, 2009/4/22 Sergiu Dumitriu <[email protected]>
Keerthan MUTHURASA wrote:
Hello,
I applied for the xwiki export import feature but unfortunately I was not accepted.However I will be glad to bring my litle contribution to xwiki and learn more from you guys.For the moment I am working on my Msc dissertation project and I would like to aquire better knowledge about xwiki API. I will start by having a look on the existing code and try to propose some patch.As soon I will finish my dissertation I will be back to work on xwiki.
Hi Keerthan,
This is great. However, as the import/export feature is quite important, we have given it to another student (if we had one more slot, you would have been accepted on it). Now, you have three options:
- Work together with Arun on this project - Find another project you would like to work on - Don't take a whole project, but be active in the general development of XWiki, working on various aspects, much like I'm doing.
Any estimate on when your dissertation will be ready?
My dissertation will be ready by the end of Auguest but I will have time to work on other projects in the same time, Actually I expected to start my dissertation later if I was selected.I will be able to work on xwiki project I guess end of mai - start of june. I will start getting familiar with xwiki API as soon as I finish my exams. I guess I will start by proposing patches it's the best way to understand things. Thank you for your mail and see you soon. Regards, Keerthan Muthurasa
-- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Hi and Congratulations to all that were selected. It was a very tough process since we had really great applications and candidates and not that many slots. We are however highly greatful to Google for having XWiki a Summer of Code participant since the program started. We had many good proposals which did not make it in the short list and projects we would love to see in XWiki. For the students that have done such good like Anthony Rosequist, Ancuta gheorghe, Chathura Ganegoda, Keerthan Muthurasa, Karel Piwko, Tharindu Madushanka, Udai Gupta We would have loved to have you as students and transfer as much as we can about Open Source. Continue your involvement and passion and it will pay off. There is not surprise that Ancuta, Tharindu and Keerthan express interest in working on their project although it was not selected. It really shows that we had a great candidate list. We even considered financing some of the projects through XWiki SAS but unfortunately we don't have the possibility to do that at this point. I hope XWiki SAS will be able to run our own programs at one point. One a side note if some companies would like to finance some student projects that they would like to see in XWiki, please don't hesitate to talk with us. This is also my first year personnaly at not being a mentor. I enjoyed a lot last year working with Asiri and it was a great success with great results. The project list matched other mentors much better and my time is less permitting anyway. I will always be available if you need help on areas that I know well. Don't hesitate to get me in the conversation. I enjoy transmitting to students what I know and like about Open Source and development. Good luck for your projects. I'm eager to see the results in XWiki. Ludovic
Ludovic Dubost wrote:
Hi and Congratulations to all that were selected. It was a very tough process since we had really great applications and candidates and not that many slots. We are however highly greatful to Google for having XWiki a Summer of Code participant since the program started.
We had many good proposals which did not make it in the short list and projects we would love to see in XWiki. For the students that have done such good like
Anthony Rosequist, Ancuta gheorghe, Chathura Ganegoda, Keerthan Muthurasa, Karel Piwko, Tharindu Madushanka, Udai Gupta
And many others, these are not the only ones that we liked.
We would have loved to have you as students and transfer as much as we can about Open Source. Continue your involvement and passion and it will pay off. There is not surprise that Ancuta, Tharindu and Keerthan express interest in working on their project although it was not selected. It really shows that we had a great candidate list.
We even considered financing some of the projects through XWiki SAS but unfortunately we don't have the possibility to do that at this point. I hope XWiki SAS will be able to run our own programs at one point. One a side note if some companies would like to finance some student projects that they would like to see in XWiki, please don't hesitate to talk with us.
Google also offers some stuff for the students that work along the program, not much, but it matters.
This is also my first year personnaly at not being a mentor. I enjoyed a lot last year working with Asiri and it was a great success with great results. The project list matched other mentors much better and my time is less permitting anyway. I will always be available if you need help on areas that I know well. Don't hesitate to get me in the conversation. I enjoy transmitting to students what I know and like about Open Source and development.
Good luck for your projects. I'm eager to see the results in XWiki.
-- Sergiu Dumitriu http://purl.org/net/sergiu/
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 <[email protected]> wrote:
Hello Google Summer of Code students,
First of all, congratulations on your applications and your activity
during the selection period, and welcome in the XWiki development team.
Before guiding the accepted students to their next steps, we'd like to
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/].
If you would like to do that, please let us know by replying to this mail.
For the accepted students, here are some getting started hints:
Community bonding period
According to the program timeline [ http://socghop.appspot.com/document/show/program/google/gsoc2009/timeline], the next month (April 20th - May 23rd) is to be used for community bonding.
The first thing to do, sometime this week, is to present yourself and your project on the dev list, so that everyone knows who you are and what to expect from you.
Also, you should continue getting acquainted with the code, the practices and the developers. Please make sure you all read and understand the following - very useful - documents: - http://purl.org/xwiki/community/ - http://purl.org/xwiki/dev/ - http://platform.xwiki.org/xwiki/bin/view/Features/
Mentorship
We prefer open mentorship. While your assigned mentor is the one 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.
Communication
Sitting alone in your room, working secretly on your project is definitely 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: - provide meaningful information about your progress, - ask the community's opinion on non-trivial design or implementation decisions - avoid waisting a lot of time on a problem, when a more experienced 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.
Wrong: "Where do I start? What do I do now? And how do I do that? Is this good? It doesn't work, help me!" Right: "Since a couple of hours ago I get a strange exception when 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?"
Subscribe to the devs list (if you didn't do this already), and start 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.
We have set up a wiki on the community farm for you to organize your ideas 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.
Development process
The project's lifecycle is NOT design -> implementation -> testing -> documentation. [ http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/]
We invite you to adopt a test driven development [ http://en.wikipedia.org/wiki/Test-driven_development][http://www.amazon.com/dp/0321146530][http://www.amazon.com/dp/0201485672/] 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).
We will create the proper projects in the xwiki sandbox, and we encourage 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.
A simple way of having something functional in the first week is to prepare the maven build, which will give you the first unit test for the first class.
Next steps, in a nutshell
- Get more familiar with the code and development process and try to master Maven, JUnit, Selenium, component driven development, ... - Continue fixing a few small issues, chosen so that they are __related to your project__ -- This will help you get more familiar with the code your project needs to interact with. - Refine and organize the ideas concerning your project (use the wiki), and write several use case scenarios. - Start writing the first piece of code for your project.
At the end of the community bonding period, you should have a clear vision 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.
Good luck, and may we all have a great Summer of Code! -- Sergiu Dumitriu http://purl.org/net/sergiu/
Arun Reddy wrote:
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
Note that the GSoC page lists Arun as working on Google Docs integration. Given that Arun was one of the most active students, we considered that he deserves a slot, even though his project wasn't as important, so we proposed him a more interesting project, one that will benefit our users most. Unfortunately, this decision came after we found out about the very low number of slots, when the application was read-only.
being mentored by Vincent Massol.
Your secondary mentor is Thomas Mortagne.
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.
-- Sergiu Dumitriu http://purl.org/net/sergiu/
hi all I would be really thankful to all of u , i was busy with my final year project when i was stepping towards XWiki. So that's why i selected album application thinking it will be easy, but now i understood it is not that important in point of Xwiki and also it is not that difficult to implement. Anyway i would like to be with you in the future. I was interested in the Integration of Mozilla Bespin as a core Script editor in XWiki , and i asked of it.but unfortunately i got a reply late and could not submit a proposal. So i am thinking of this integration of Bespin as a core script editor , I would like know about the importance of this project in point of xwiki , otherwise propose me an another important project. I would like to contribute you as time permits me. Good Luck Xwiki ... Thanks Harsha
Harsha Halgaswatta wrote:
hi all
I would be really thankful to all of u , i was busy with my final year project when i was stepping towards XWiki. So that's why i selected album application thinking it will be easy, but now i understood it is not that important in point of Xwiki and also it is not that difficult to implement.
On the contrary, web applications are critical. We would really appreciate if you could also work on the photo album. There are lots of critical things that need to be done, and our workforce is not big enough. Indeed, the photo album is not that difficult to implement.
Anyway i would like to be with you in the future. I was interested in the Integration of Mozilla Bespin as a core Script editor in XWiki , and i asked of it.but unfortunately i got a reply late and could not submit a proposal.
So i am thinking of this integration of Bespin as a core script editor , I would like know about the importance of this project in point of xwiki , otherwise propose me an another important project. I would like to contribute you as time permits me.
The Bespin integration is more like an investment. Currently, Bespin is pretty young, so its features and functionality are not very good, so it will be a bit unsuccessful at first. I tried it, and it was terribly slow, and the usability was awful. The good thing is that Bespin has a lot of potential, so in a few months it could be great. It also depends on where does this project go. It can either be a developer tool (if it supports JS, CSS and HTML mainly), or it can be a user tool competing with the WYSIWYG editor (if it also supports wiki markup, velocity and the xwiki API). So, correctly estimating how important this project is at the moment is a difficult task. The good thing in Open Source is that you get to choose what you work on. I suggest that you evaluate both projects and decide for yourself which one you like most. A valid option is to work on both projects :) -- Sergiu Dumitriu http://purl.org/net/sergiu/
Hi Harsh, Sergiu, all, see below Sergiu Dumitriu wrote:
Harsha Halgaswatta wrote:
hi all
I would be really thankful to all of u , i was busy with my final year project when i was stepping towards XWiki. So that's why i selected album application thinking it will be easy, but now i understood it is not that important in point of Xwiki and also it is not that difficult to implement.
On the contrary, web applications are critical. We would really appreciate if you could also work on the photo album. There are lots of critical things that need to be done, and our workforce is not big enough. Indeed, the photo album is not that difficult to implement.
Anyway i would like to be with you in the future. I was interested in the Integration of Mozilla Bespin as a core Script editor in XWiki , and i asked of it.but unfortunately i got a reply late and could not submit a proposal.
So i am thinking of this integration of Bespin as a core script editor , I would like know about the importance of this project in point of xwiki , otherwise propose me an another important project. I would like to contribute you as time permits me.
The Bespin integration is more like an investment. Currently, Bespin is pretty young, so its features and functionality are not very good, so it will be a bit unsuccessful at first. I tried it, and it was terribly slow, and the usability was awful.
That's because you are on linux :) (which is not a good excuse to be slow, I admit ;)) Sergiu is right, bespin is still very young and not yet a mature project. On the other hand, it evolves very fast, and it's already pretty good, besides a couple of annoying bugs that should be fixed in the coming version 0.2 - Usability/VCS integration release (see https://wiki.mozilla.org/Labs/Bespin/Roadmap#Current_Focus). We are already several XWiki developers that use the skin editor application on a regular basis for front-end development, because besides its bugs it already brings value as a development tool. And I'm persuaded this number will grow as bespin and the XWiki integration of it will evolve. Now Sergiu is right again, this is a long-run project that will take time before showing positive results, but good side of this project is that it has the potential of a killer feature for XWiki as a development platform. I do not really agree with Sergiu on the fact that it could become a competitor for the WYSIWYG. For me it's a pure developer tools and it is more than likely that it will remain so ("Code in the cloud" is bespin motto). The objective of the integration is indeed that at some point bespin understands XWiki syntax and groovy/velocity/XWiki API. But honestly I don't think the WYSIWYG is meant for that, that's why I consider it a very different tool. It's more a competitor of XEclipse, though I think both can co-exist and have different purpose. All this to say that besides it's not a critical project for XWiki right now and that it's something long run, we will continue to work on this integration (at least, I personally will, as my free time allows), and if you are willing to help on this, I'll be more than happy to mentor you :) Jerome.
The good thing is that Bespin has a lot of potential, so in a few months it could be great. It also depends on where does this project go. It can either be a developer tool (if it supports JS, CSS and HTML mainly), or it can be a user tool competing with the WYSIWYG editor (if it also supports wiki markup, velocity and the xwiki API). So, correctly estimating how important this project is at the moment is a difficult task.
The good thing in Open Source is that you get to choose what you work on. I suggest that you evaluate both projects and decide for yourself which one you like most. A valid option is to work on both projects :)
Hi everyone, I'm Anamaria Stoica (on irc: anamarias) and I'll be working on Google Gadget and OpenSocial Integration<http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/GoogleGadgetsandOpenSocialIntegration>which will make XWiki more social. My main mentor is going to be Sergiu Dumitriu. The full integration of Google Gadgets and Open Social will involve the creation of a Gadgets Application (using Velocity macros) and backend support for the new gadgets API. The new gadgets run in containers (OpenSocial containers) which must support the OpenSocial API (compared to the original gadgets that run on any website). Moreover any OpenSocial Application will be able to be installed. Project comprises 2 parts: - Gadgets Application : iGoogle like Dashboard, Gadgets Directory, Add Gadget action etc. - Open Social integration : integration with Apache Shindig<http://incubator.apache.org/shindig/>, application for adding and removing apps, storing activities, adding and removing friends, canvas pages for OpenSocial applications, etc. I'll make sure to add a detailed project description, architecture and plan on the gsoc wiki and ask for your opinions and suggestions. I'm very happy to be here ! :) Thanks again, Anamaria On Wed, Apr 22, 2009 at 1:40 AM, Sergiu Dumitriu <[email protected]> wrote:
Hello Google Summer of Code students,
First of all, congratulations on your applications and your activity during the selection period, and welcome in the XWiki development team.
Before guiding the accepted students to their next steps, we'd like to 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://www.catb.org/%7Eesr/writings/cathedral-bazaar/homesteading/> ]. If you would like to do that, please let us know by replying to this mail.
For the accepted students, here are some getting started hints:
Community bonding period
According to the program timeline [ http://socghop.appspot.com/document/show/program/google/gsoc2009/timeline], the next month (April 20th - May 23rd) is to be used for community bonding.
The first thing to do, sometime this week, is to present yourself and your project on the dev list, so that everyone knows who you are and what to expect from you.
Also, you should continue getting acquainted with the code, the practices and the developers. Please make sure you all read and understand the following - very useful - documents: - http://purl.org/xwiki/community/ - http://purl.org/xwiki/dev/ - http://platform.xwiki.org/xwiki/bin/view/Features/
Mentorship
We prefer open mentorship. While your assigned mentor is the one 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]<http://en.wikipedia.org/wiki/Bus_factor%5D>), another developer can take his place with little effort.
Communication
Sitting alone in your room, working secretly on your project is definitely 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: - provide meaningful information about your progress, - ask the community's opinion on non-trivial design or implementation decisions - avoid waisting a lot of time on a problem, when a more experienced 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.
Wrong: "Where do I start? What do I do now? And how do I do that? Is this good? It doesn't work, help me!" Right: "Since a couple of hours ago I get a strange exception when 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?"
Subscribe to the devs list (if you didn't do this already), and start 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.
We have set up a wiki on the community farm for you to organize your ideas 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.
Development process
The project's lifecycle is NOT design -> implementation -> testing -> documentation. [ http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/<http://www.catb.org/%7Eesr/writings/cathedral-bazaar/cathedral-bazaar/> ]
We invite you to adopt a test driven development [ http://en.wikipedia.org/wiki/Test-driven_development][http://www.amazon.com/dp/0321146530][http://www.amazon.com/dp/0201485672/<http://en.wikipedia.org/wiki/Test-driven_development%5D%5Bhttp://www.amazon.com/dp/0321146530%5D%5Bhttp://www.amazon.com/dp/0201485672/>] 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).
We will create the proper projects in the xwiki sandbox, and we encourage 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.
A simple way of having something functional in the first week is to prepare the maven build, which will give you the first unit test for the first class.
Next steps, in a nutshell
- Get more familiar with the code and development process and try to master Maven, JUnit, Selenium, component driven development, ... - Continue fixing a few small issues, chosen so that they are __related to your project__ -- This will help you get more familiar with the code your project needs to interact with. - Refine and organize the ideas concerning your project (use the wiki), and write several use case scenarios. - Start writing the first piece of code for your project.
At the end of the community bonding period, you should have a clear vision 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.
Good luck, and may we all have a great Summer of Code! -- Sergiu Dumitriu http://purl.org/net/sergiu/
Anamaria Stoica wrote:
Hi everyone,
I'm Anamaria Stoica (on irc: anamarias) and I'll be working on Google Gadget and OpenSocial Integration<http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/GoogleGadgetsandOpenSocialIntegration>which will make XWiki more social. My main mentor is going to be Sergiu Dumitriu.
The co-mentor will be Jerome.
The full integration of Google Gadgets and Open Social will involve the creation of a Gadgets Application (using Velocity macros) and backend support for the new gadgets API. The new gadgets run in containers (OpenSocial containers) which must support the OpenSocial API (compared to the original gadgets that run on any website). Moreover any OpenSocial Application will be able to be installed.
Project comprises 2 parts: - Gadgets Application : iGoogle like Dashboard, Gadgets Directory, Add Gadget action etc. - Open Social integration : integration with Apache Shindig<http://incubator.apache.org/shindig/>, application for adding and removing apps, storing activities, adding and removing friends, canvas pages for OpenSocial applications, etc.
You should start by reading and following tutorials (from http://wiki.opensocial.org/index.php?title=Articles_%26_Tutorials), the API reference (from http://wiki.opensocial.org/index.php?title=JavaScript_API_Reference) and the specifications (from http://www.opensocial.org/page/specs-1). One important decision is what version of the API we should support. Please write an email for this, listing the advantages and disadvantages of 0.8.1 and 0.9.
I'll make sure to add a detailed project description, architecture and plan on the gsoc wiki and ask for your opinions and suggestions.
I'm very happy to be here ! :)
-- Sergiu Dumitriu http://purl.org/net/sergiu/
Hi! I'm Teofil Achirei (irc: tachirei) and I'll work on XWiki integration with MS Office, being mentored by Florin Ciubotaru. The project name is "Skin and template support for XOffice", but my contribution to XOffice during GSoC will consist of: - Adding style support to XOffice - Porting XOffice to MS Office 2003 You will find more on http://gsoc.myxwiki.org/xwiki/bin/view/Skin+and+template+support+for+XOffice... . This will contain links to http://teofilachirei.myxwiki.org/xwiki/bin/view/XOffice/ , since I plan to continue contributing to XOffice after GSoC also. On Wed, Apr 22, 2009 at 1:40 AM, Sergiu Dumitriu <[email protected]> wrote:
Hello Google Summer of Code students,
First of all, congratulations on your applications and your activity during the selection period, and welcome in the XWiki development team.
Before guiding the accepted students to their next steps, we'd like to 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/]. If you would like to do that, please let us know by replying to this mail.
For the accepted students, here are some getting started hints:
Community bonding period
According to the program timeline [http://socghop.appspot.com/document/show/program/google/gsoc2009/timeline], the next month (April 20th - May 23rd) is to be used for community bonding.
The first thing to do, sometime this week, is to present yourself and your project on the dev list, so that everyone knows who you are and what to expect from you.
Also, you should continue getting acquainted with the code, the practices and the developers. Please make sure you all read and understand the following - very useful - documents: - http://purl.org/xwiki/community/ - http://purl.org/xwiki/dev/ - http://platform.xwiki.org/xwiki/bin/view/Features/
Mentorship
We prefer open mentorship. While your assigned mentor is the one 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.
Communication
Sitting alone in your room, working secretly on your project is definitely 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: - provide meaningful information about your progress, - ask the community's opinion on non-trivial design or implementation decisions - avoid waisting a lot of time on a problem, when a more experienced 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.
Wrong: "Where do I start? What do I do now? And how do I do that? Is this good? It doesn't work, help me!" Right: "Since a couple of hours ago I get a strange exception when 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?"
Subscribe to the devs list (if you didn't do this already), and start 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.
We have set up a wiki on the community farm for you to organize your ideas 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.
Development process
The project's lifecycle is NOT design -> implementation -> testing -> documentation. [http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/]
We invite you to adopt a test driven development [http://en.wikipedia.org/wiki/Test-driven_development][http://www.amazon.com/dp/0321146530][http://www.amazon.com/dp/0201485672/] 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).
We will create the proper projects in the xwiki sandbox, and we encourage 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.
A simple way of having something functional in the first week is to prepare the maven build, which will give you the first unit test for the first class.
Next steps, in a nutshell
- Get more familiar with the code and development process and try to master Maven, JUnit, Selenium, component driven development, ... - Continue fixing a few small issues, chosen so that they are __related to your project__ -- This will help you get more familiar with the code your project needs to interact with. - Refine and organize the ideas concerning your project (use the wiki), and write several use case scenarios. - Start writing the first piece of code for your project.
At the end of the community bonding period, you should have a clear vision 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.
Good luck, and may we all have a great Summer of Code! -- Sergiu Dumitriu http://purl.org/net/sergiu/
-- Teofil Achirei
Hi Teofil, Great to have you on board. However I think it would be much better community wise if you publish your data on xoffice.xwiki.org. This would be much better community wise. You can of course keep a blog/wiki for yourself and your personal projects but in general it's much more engaging with the community to do it in a shared space than in the personal one. Ludovic Teofil Achirei a écrit :
Hi! I'm Teofil Achirei (irc: tachirei) and I'll work on XWiki integration with MS Office, being mentored by Florin Ciubotaru. The project name is "Skin and template support for XOffice", but my contribution to XOffice during GSoC will consist of: - Adding style support to XOffice - Porting XOffice to MS Office 2003 You will find more on http://gsoc.myxwiki.org/xwiki/bin/view/Skin+and+template+support+for+XOffice... . This will contain links to http://teofilachirei.myxwiki.org/xwiki/bin/view/XOffice/ , since I plan to continue contributing to XOffice after GSoC also.
On Wed, Apr 22, 2009 at 1:40 AM, Sergiu Dumitriu <[email protected]> wrote:
Hello Google Summer of Code students,
First of all, congratulations on your applications and your activity during the selection period, and welcome in the XWiki development team.
Before guiding the accepted students to their next steps, we'd like to 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/]. If you would like to do that, please let us know by replying to this mail.
For the accepted students, here are some getting started hints:
Community bonding period
According to the program timeline [http://socghop.appspot.com/document/show/program/google/gsoc2009/timeline], the next month (April 20th - May 23rd) is to be used for community bonding.
The first thing to do, sometime this week, is to present yourself and your project on the dev list, so that everyone knows who you are and what to expect from you.
Also, you should continue getting acquainted with the code, the practices and the developers. Please make sure you all read and understand the following - very useful - documents: - http://purl.org/xwiki/community/ - http://purl.org/xwiki/dev/ - http://platform.xwiki.org/xwiki/bin/view/Features/
Mentorship
We prefer open mentorship. While your assigned mentor is the one 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.
Communication
Sitting alone in your room, working secretly on your project is definitely 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: - provide meaningful information about your progress, - ask the community's opinion on non-trivial design or implementation decisions - avoid waisting a lot of time on a problem, when a more experienced 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.
Wrong: "Where do I start? What do I do now? And how do I do that? Is this good? It doesn't work, help me!" Right: "Since a couple of hours ago I get a strange exception when 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?"
Subscribe to the devs list (if you didn't do this already), and start 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.
We have set up a wiki on the community farm for you to organize your ideas 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.
Development process
The project's lifecycle is NOT design -> implementation -> testing -> documentation. [http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/]
We invite you to adopt a test driven development [http://en.wikipedia.org/wiki/Test-driven_development][http://www.amazon.com/dp/0321146530][http://www.amazon.com/dp/0201485672/] 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).
We will create the proper projects in the xwiki sandbox, and we encourage 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.
A simple way of having something functional in the first week is to prepare the maven build, which will give you the first unit test for the first class.
Next steps, in a nutshell
- Get more familiar with the code and development process and try to master Maven, JUnit, Selenium, component driven development, ... - Continue fixing a few small issues, chosen so that they are __related to your project__ -- This will help you get more familiar with the code your project needs to interact with. - Refine and organize the ideas concerning your project (use the wiki), and write several use case scenarios. - Start writing the first piece of code for your project.
At the end of the community bonding period, you should have a clear vision 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.
Good luck, and may we all have a great Summer of Code! -- Sergiu Dumitriu http://purl.org/net/sergiu/
-- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost
Teofil Achirei wrote:
Hi! I'm Teofil Achirei (irc: tachirei) and I'll work on XWiki integration with MS Office, being mentored by Florin Ciubotaru.
Hi Teo, Florin will be your main mentor, as the creator of XOffice, and Guillaume will be your secondary mentor, as a product manager and the guy who speaks for the clients.
The project name is "Skin and template support for XOffice", but my contribution to XOffice during GSoC will consist of: - Adding style support to XOffice - Porting XOffice to MS Office 2003
There was a controversy about accepting two office integration projects, given that XWiki is a web project, so we have high expectations for the two projects (XOffice and XOO).
You will find more on http://gsoc.myxwiki.org/xwiki/bin/view/Skin+and+template+support+for+XOffice... . This will contain links to http://teofilachirei.myxwiki.org/xwiki/bin/view/XOffice/ , since I plan to continue contributing to XOffice after GSoC also.
You could also work mainly on the GSoC wiki, and later move your data between the two wikis, once the SoC period is over. -- Sergiu Dumitriu http://purl.org/net/sergiu/
participants (13)
-
Alexandru Cismaru -
Anamaria Stoica -
Ancuta Maria Gheorghe -
Arun Reddy -
Guillaume Lerouge -
Harsha Halgaswatta -
Jerome Velociter -
Keerthan MUTHURASA -
Ludovic Dubost -
Ludovic Dubost -
Sergiu Dumitriu -
Teofil Achirei -
Tharindu Madushanka