organize and document the work that is going to be done. Just create a
new entry for your feature and follow the remaining indications (make a
jira issue, send a mail to the community asking for feedback on your
documented plan of action, etc.).
Sorry for the confusion.
Thanks,
Eduard
P.S.: I have added a mention on the
) and have disabled user registration.
On Wed, May 2, 2012 at 8:31 PM, Thomas Mortagne
<thomas.mortagne(a)xwiki.com>wrote;wrote:
On Wed, May 2, 2012 at 7:13 PM, Vincent Massol
<vincent(a)massol.net> wrote:
On May 2, 2012, at 6:18 PM, Eduard Moraru wrote:
> Hi Paul, students,
>
> The best place for GSoC students to work in, when it comes to
architecture,
> design, documentation etc., is the
students' wiki:
http://gsoc.myxwiki.org
I don't quite agree. For me a GSOC student must be treated exactly like
any
contributor.
Thus for me the best place for architecture, design is
http://dev.xwiki.org/xwiki/bin/view/Design/WebHome
More generally they should use the exact same tools as all xwiki
developers/contributors are using so that we don't create silos: mailing
list, irc, design page, etc.
I agree with Vincent on this, I don't see the point in isolating GSOC
students on a special wiki when we have a place for this already.
Thanks
-Vincent
> The students' wiki needs a bit more maintaining, but it should be
usable.
> I`ve done some minor decorating for GSoC
2012.
>
> The students need to register a new user (the
xiwki.org user does not
work
> since it's a different farm). Besides
wiki pages, they can also use the
> Blog if they don`t already have one :).
>
> Thanks,
> Eduard
>
> On Thu, Apr 26, 2012 at 2:32 PM, Paul Libbrecht <paul(a)hoplahup.net>
wrote:
>
>> Sorry to answer myself, a few precisions:
>>
>> Le 26 avr. 2012 à 13:24, Paul Libbrecht a écrit :
>>> - one page about her Google Summer of Code work where, for example,
the
>> schedule she presented in her proposal is
presented to the public and,
>> where we shall elaborate it with milestones that are assessable
somehow.
>>
>> I would suggest it also includes the following which I'm happy to
>> complement:
>>
>> - detail the incorporation alternatives so that we know what kind of
>> versioning we base on (e.g.: very successful early: incorporation in
trunk;
>> successful at end: a simple pull request;
simple cases: a standalone
>> contribution with installation instructions, ...)
>>
>> - software availability at milestones (e.g. unit-tests, docs, can be
tried
>> by someone, ...)
>>
>> - describe the expected feedback of community and mentors at each phase
>>
>>> Eduard, someone, are there example for such pages?
>>> It would be possible to replace the project page:
>>>
>>
http://dev.xwiki.org/xwiki/bin/inline/GoogleSummerOfCode/SOLRsearchcomponent
>>> but I think this is more a
"proposal", or?
>>
>>
>>> - one design page about the SOLR component. There are many design
pages
so Savitha, go ahead and get inspired.
Maybe the page of Fabio is a start?
paul
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs