Dear Sergio, I have been composing the project proposal draft these days. I find some GSoC proposal examples, most of which contain the "time table" parts. I'd like to include the project schedule as well in my proposal.
Basically GSoC 2014 goes in this way: ---- Begin coding: 19 May Mid-term evaluation: 27 June End coding: 11 August ---- However I find that the due date of MARMOTTA-444 in Jira is 30 June. Does it mean that I'm supposed to complete the work before the mid-term of GSoC 2014? If so, how about the second part of the summer in July and August? I believe the Marmotta community has its plan of developing the Linked Data Platform implementations. I don't want to delay your original plan because of the GSoC program. Could you please tell me about the desired schedule? Best, Qihong Lin On Tue, Mar 4, 2014 at 3:40 PM, Sergio Fernández <[email protected]> wrote: > Hi, > > > On 04/03/14 05:03, Qihong Lin wrote: > > > I'll focus on implementing the LdpSrvice interface using SPARQL. >> The implementation can be developed incrementally during the GSoC 2014 >> summer, if anything would be changed for LdpService. I can also promise to >> maintain the implementation after the GSoC program. As a student, it's >> great to get involved into an open source community with long time >> contributions. I believe I can learn a lot from the project experience. >> > > Your contributions would be welcomed. And don't be self-conscious because > your inexperience. That's normal, it happened to everybody at some point, > it's a natural learning process. And GSoC is an excellent program for that. > > > According to your replies, the testing work contains 2 parts: 1) unit >> tests >> (junit) of the SPARQL implementation itself; 2) RESTful service tests >> (rest-assured). It seems the later one is service oriented, not for the >> concrete implementations. Shall we test the RESTful services for different >> LdpService implementations (i.e. different test cases/suits >> for different implementations)? >> > > Besides the unit tests, the REST test should behavior exactly the same > when plugin your implementation instead of the default one. In principle > we're going to provide a sufficient test suite (this is related to > MARMOTTA-438 by the way), but we could also expect contributions there for > improving the coverage of testing. > > > I'm clear about the project scopes now: the SPARQL implementation and the >> tests. The approaches are lucid in my mind as well. Anything else to be >> considered/discussed for the project scopes/approaches/etc? If not, I'd >> like to prepare a project proposal draft. >> > > Sure, I think you have enough information to prepare your proposal. > > > Cheers, > > -- > Sergio Fernández > Senior Researcher > Knowledge and Media Technologies > Salzburg Research Forschungsgesellschaft mbH > Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria > T: +43 662 2288 318 | M: +43 660 2747 925 > [email protected] > http://www.salzburgresearch.at >
