Le 9 mars 08 à 18:26, David Chisnall a écrit :

> Hi everyone,
>
> We (and, by we, I mean Quentin ;-) need to submit our SoC application
> in the next couple of days.  From the list of questions on the Google
> site I've come up with the following text for the application.  I'd
> appreciate any comments / suggestions / expansions of short parts:
>
> -Describe your organization.
>
> The Étoilé project aims to build a modern computing environment
> designed for the end of the desktop era and the start of the post-
> desktop era.  We focus heavily on network-based services and
> collaboration.
>
> What else do we want to say?

We could mention other things like composite document, project  
workflow, message-oriented persistency, live development etc. But I  
think the description is fine. May be the last sentence isn't really  
useful.

> -Why is your organization applying to participate in GSoC 2008? What
> do you hope to gain by participating?
>
> The Étoilé project was founded three years ago with some complex
> goals.  The core frameworks which will form the base for our
> environment are now nearing completion and so we are entering a stage
> when applications can be built relatively easily using these
> technologies.

A bit optimistic but ok :)
I suggest some minor rephrasing like the following one:
The core frameworks which will form the base for our
environment are now on the way to completion and so we are approaching  
a stage
when applications can be built relatively easily using these
technologies.

> -Did your organization participate in past GSoCs? If so, please
> summarize your involvement and the successes and challenges of your
> participation.
> -If your organization has not previously participated in GSoC, have
> you applied in the past? If so, for what year(s)?
>
> N/A

We never applied in the past.

> -Who will your organization administrator be? Please include Google
> Account information.
>
> Quentin?

ok

> -What license(s) does your project use?
>
> We favour the 3-clause BSD license, however code is accepted under
> other licenses for various reasons.  A copy of our licensing policy
> and rationale can be found here:
>
> http://staging.etoileos.com/etoile/0.3/overview/

ok

> -What is the URL for your ideas page?
>
> Currently in SVN.  We need to move it to the main site soon...

http://svn.gna.org/viewcvs/*checkout*/etoile/trunk/Etoile/Documentation/SoC

> What is the main development mailing list or forum for your
> organization?
>
> etoile-dev and etoile-discuss at gna.org.
>
> What is the main IRC channel for your organization?
>
> We do not use IRC, the SILC server silc.etoile-project.org hosts our
> online chat presence.  Developers can typically be found in the etoile
> room.

ok

> - Does your organization have an application template you would like
> to see students use? If so, please provide it now.
>
> We don't have one at the moment.  Should we?

We have a framework template available here: 
<http://svn.gna.org/viewcvs/etoile/trunk/Etoile/Developer/Templates/FrameworkTemplate/
 
 >
It can serves as a base for an app template too.
I think it helps to solve build issues and evolve the build  
infrastructure when all modules are based on a common template  
(GNUmakefiles and directory layout).
The template is mentionned in the HACKING document 
<http://svn.gna.org/viewcvs/*checkout*/etoile/trunk/Etoile/HACKING 
 >

> - Who will be your backup organization administrator? Please include
> Google Account information.
>
> Not sure who to use for this.  I could do it if you want?

Sure. Would be nice to you.

> - Who will your mentors be? Please include Google Account information.
>
> I can be one, other volunteers?

Well me too. Nicolas could you eventually mentor Camaelon work?

> - What criteria did you use to select these individuals as mentors?
> Please be as specific as possible.
>
> The mentors are drawn from the project's Core Team.  This is a group
> who maintains overall oversight of the project and who is responsible
> for the majority of the code.  All of the core team have experience
> assisting other developers working on the Étoilé code.

ok

> - What is your plan for dealing with disappearing students?
>
> No idea.  Suggestions?

I think we'll have to cancel the project the student was involved in.  
If some usable and well-written code has already been produced, the  
mentor in charge of the student work will take care to merge the code  
if needed and commit or update a TODO file explaining what remains to  
be done.
What do you think?

> - What is your plan for dealing with disappearing mentors?
>
> We don't anticipate this being a problem, since the mentors are drawn
> from the core team, who have shown a commitment to the project.  In
> the unlikely event that they should disappear, it is usually possible
> to find at least one of the core developers in the Étoilé SILC room.
> These are available to provide assistance to other developers whether
> or not they are taking part in the SoC and can take over the mentoring
> rôle should it be required.

ok.

> - What steps will you take to encourage students to interact with your
> project's community before, during and after the program?
>
> The best way of interacting with the Étoilé development community is
> via the SILC channel.  We will strongly encourage students to spend
> some time in there before submitting their applications.  This is
> where the goals and overall plan of the project are discussed, and is
> a great place to float ideas.

ok.

> - What will you do to ensure that your accepted students stick with
> the project after GSoC concludes?
>
> We intend to prioritise applications from students who have already
> submitted code to the project.  In addition, we have a small hackathon
> planned for the end of this month at Swansea University which will
> give us the opportunity to give presentations to the student body and
> hopefully garner some applicants.

ok.

Thanks a lot for writing the SoC application David :) I'll submit it  
either later today or tomorrow if there are no further modifications  
to do.

Cheers,
Quentin.


_______________________________________________
Etoile-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/etoile-discuss

Répondre à