Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: pass (athena.apache.org: domain of runseb@gmail.com designates
 74.125.83.48 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [GSOC] Update to document
From: Sebastien Goasguen <runseb@gmail.com>
In-Reply-To: 
 <CAEJ3w4VmjANGFXCx16aSr6GKZNVQt=ArjEnSCHB8G91W3oH=WA@mail.gmail.com>
Date: Fri, 5 Jul 2013 10:39:25 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <729844AB-1616-4C61-A866-B0A72AD32253@gmail.com>
References: <E2D01F5D-B6D9-45CE-B162-B2F1942F0E36@gmail.com>
 <20130705132539.GB1341@cloud-2.local>
 <CAEJ3w4U1g8m2jRXoPZ8q_ARXKBsvz8_AN6tTH8BhbVCjOjgnZw@mail.gmail.com>
 <CAEJ3w4VmjANGFXCx16aSr6GKZNVQt=ArjEnSCHB8G91W3oH=WA@mail.gmail.com>
To: dev@cloudstack.apache.org


On Jul 5, 2013, at 10:35 AM, Ian Duffy <ian@ianduffy.ie> wrote:

> Sorry to create two emails in a row...
>=20
> Just in terms of the Google wants/needs deadline on the 29th, is there
> anything you guys, the cloudstack community specifically want to see?
>=20

I am going to check exactly what Google requires, the evaluation will be =
submitted by your mentor: Abhi :)

In general I think a prototype demo and seeing your code committed is =
really what we would like.

So don't be afraid to commit, if you don't want to break the existing =
setup we can created a feature branch for you. But we'd rather see lots =
of small commits than a large chunk at the end.


> I know Abhi mentioned the creation of a prototype for me in one of the
> gtalk conversations we had awhile back. So I'm hoping to have the
> plugin I detailed in the blog post completely cleaned up and ready for
> review by you guys with full end to end testing by that date. This
> would allow me to have the second half of the Google summer of code
> term to work on creating a UI to allow admins to easily provision
> users and extending the plugin where/if required. As mentioned to
> Sebastien during the skype interviews I would *ideally* like to have
> the project wrapped up by the end of August, based on the progress so
> far this seems possible.
>=20
> On 5 July 2013 15:25, Ian Duffy <ian@ianduffy.ie> wrote:
>> @Sebastien - Is it ok to just copy and paste over what I had in that
>> blog post? (Excluding the opening image and closing paragraph)
>>=20
>> On 5 July 2013 14:25, Prasanna Santhanam <tsp@apache.org> wrote:
>>> On Fri, Jul 05, 2013 at 09:18:10AM -0400, Sebastien Goasguen wrote:
>>>> Hi guys,
>>>>=20
>>>> I modified the format of our "report", I moved the proposals to a
>>>> chapter and started a new chapter called "updates".
>>>> Each of you should use a section to write a small report/updates on
>>>> your progress so far.
>>>>=20
>>>> You can see the doc at:
>>>> =
http://jenkins.cloudstack.org/job/docs-4.3-gsoc-guide/lastSuccessfulBuild/=
artifact/Apache_CloudStack-4.2.0-CloudStack_GSoC_Guide-en-US.pdf
>>>>=20
>>>> Your respective sections should be self-explanatory when you
>>>> checkout the code.
>>>>=20
>>>> We will use this for the mid-summer evaluation that Google
>>>> wants/needs.
>>>>=20
>>>> A good example of progress report is from Ian at:
>>>>=20
>>>> http://imduffy15.blogspot.co.uk
>>>>=20
>>>> You can include specific things about your project but also things
>>>> related to CloudStack itself, what you are learning (jira, git
>>>> etc..) and what you contributed so far outside your project (e.g
>>>> Meng gave us the quick install guide for 4.1 and Dharmesh is =
looking
>>>> at a significant update to the code with CLOUDSTACK-212)
>>>>=20
>>>=20
>>> Excellent work so far. Great work all!
>>>=20
>>> --
>>> Prasanna.,
>>>=20
>>> ------------------------
>>> Powered by BigRock.com
>>>=20