[mylar-dev] RE: preparing for the Mylar Google Summer of Code

["Mik Kersten" <beatmik@xxxxxxx>]

The coding phase of the Summer of Code has begun!  Please update your bug
reports with your current status and bug reports that you are going to start
working on.  Balazs, you do not need to do this since you've already got
patches underway.  

Also, please plan to attend next Tuesday's conference call since we will be
discussing plans.  If you have any questions on getting started please email
me.  

Mik 

> -----Original Message-----
> From: Mik Kersten [mailto:beatmik@xxxxxxx]
> Sent: Tuesday, May 01, 2007 9:28 PM
> To: 'jevgeni.holodkov@xxxxxxxxx'; 'xiaoyang.guan@xxxxxxxxx';
> 'balazs.brinkus@xxxxxxxxx'
> Cc: 'Mylar developer discussions'
> Subject: preparing for the Mylar Google Summer of Code
> 
> We are now in the "interim period" where Google suggests that summer of
> code students learn more about their user communities before the
> official May 28th coding start.  Here is how to start getting involved
> with the Mylar community:
> 
> * We use Bugzilla for most of our collaboration, so get a Bugzilla
> account from: https://bugs.eclipse.org/bugs
> 
> * Subscribe to the mylar-dev mailing list:
> https://dev.eclipse.org/mailman/listinfo/mylar-dev
> 
> * Add a Watch for yourself to the Meetings page and Mylar wiki pages
> that interest you: http://wiki.eclipse.org/index.php/Mylar
> 
> * Get a workspace set up for Mylar development:
> http://wiki.eclipse.org/index.php/Mylar_Contributor_Reference
> 
> * Create a bug called "manage <title> GSOC project" and assign it to
> yourself.  Email me when you've done that so that I can add a query for
> your Bugzilla email address.
> 
> * In your Task List set up a query for all bugs assigned to you and all
> that you're CC'd on:
> http://wiki.eclipse.org/index.php/Mylar_User_Guide#Query_setup
> 
> After that, start looking through the list of our open bugs for key
> bugs of interest to your project and add yourself to the CC.  Here's a
> start:
> 
> Balazs:
> * I've tagged a bunch of bugs "[new eux]" which stands for New User
> Experience, so that's a start.
> 
> Jevgeni:
> * 178883: Provide ability to export/import individual task content via
> File->Export/Import menu
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=178883
> * 157546: allow task, repository, and context to dragged in and out of
> the workbench
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=157546
> * 111218: [discussion] sharing and awareness of task context
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=111218
> 
> Xiaoyang
> * 184904: provide wiki editing facilities in task editor
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=184904
> 
> Looking over the existing Mylar bugs will help you position your
> projects and deliverables to meet the user communities' needs.  During
> last year's summer of code we saw with Steffen Pingel and Jeff Pound's
> work what a significant impact a focused summer of code project can
> have on improving Mylar.  I look forward to working with you this
> summer,
> 
> Mik
> 
> --
> Mik Kersten
> President & CTO, http://tasktop.com
> Project Lead, http://eclipse.org/mylar
>