[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-dev] Welcome Google SoC Students

From: Mark Phippard <markphip_at_gmail.com>
Date: Wed, 23 Apr 2008 19:14:02 -0400

On Wed, Apr 23, 2008 at 5:57 PM, Eugene Kuleshov <eu_at_md.pp.ru> wrote:
>
> I would like to join Mark in welcoming SoC students and wish them to have
> great time in contributing to Subclipse project during this Summer.
>
> Now I would like to share few thought about the development process.
>
> First of all, we should create two issues in Subclipse IssueZilla for both
> projects and assign them to Alberto and Thaminda. Additional issues can be
> created ad added as "depends on" into those two umbrella issues.

Sure. Actually, there are existing issues for each of these.

http://subclipse.tigris.org/issues/show_bug.cgi?id=721

http://subclipse.tigris.org/issues/show_bug.cgi?id=513

We should get Alberto and Thaminda to create tigris accounts so we can
assign the issues to them and give them roles in the project.

> I think it would be extremely useful to have regular status report to
> discuss progress, architecture and any issues that may block or slow down
> students with their work, say every week or two. Because we all in different
> time zones, we could just do it over email, but if we can agree on time, it
> can be also done on irc or skype.

Yes, I agree. If there is a high amount of email regular email
traffic we could skip or cancel these, but we should definitely try
for something regular as a way of insuring we keep in contact.

> Not sure if it had been discussed already, but I think it is probably good
> idea to create branches at for each student's project and do a code review
> from time to time. http://subclipse.tigris.org/svn/subclipse/branches

Yes, I planned to do that when they get ready to code. No point in
doing it before then as it just creates more to merge. For Alberto, I
anticipate we will want one or more new plugins so that we can keep
all the new dependencies out of the core plugins.

> Also, students could use their own blogs to demonstrate their progress. We
> could probably link those blogs from Subclipse project page to help
> popularize this work. This practice been used last year by Eclipse SoC
> students and I think it worked really well. They even had an aggregated blog
> for this. See http://eclipse-soc.blogspot.com/
>
> What do you guys tink?

All sounds good to me.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: dev-help_at_subclipse.tigris.org
Received on 2008-04-24 01:14:08 CEST

This is an archived mail posted to the Subclipse Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.