Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [soc-dev] Check in

Hi Wayne,

I am working on the project "Diagram Layout in eTrice with KIELER" ( proposal : [1] ). The progress of the project could be monitored on the project wiki [2], which will be shortly updated to show the most recent status and schedule of the project.

Though i intended to start the coding one week before the actual coding begin date, i realized that more in-depth understanding of the KIELER framework and other details is required. As such i delayed the coding by one week and stated it only by 21st (This will be updated on wiki). This delay would be compensated by the backup week in the schedule.
  
Currently i am working in the "Phase I" of the project and the first week milestone will be completed by day after tomorrow(a little behind schedule, for which i apologize)  

I have gone through a mammoth of documentation and wiki pages, tutorials, etc. and have learn to use the Gerrit Code review system.

As far the communication is concerned, I communicate with my mentors  Henrik Rentz-Reichert and  Miro Spoenemann through private emails only. As you have suggested, i would now augment them to the project development list as well. 

Kindly Regards,
Jayant Gupta

[1] http://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/jayant/1
[2] http://wiki.eclipse.org/ETrice/GSoC/2012/DiagramLayout_Kieler 


On Mon, May 28, 2012 at 6:47 AM, Wayne Beaton <wayne@xxxxxxxxxxx> wrote:
Can everybody who is working on an GSoC project please check in?

Students, can you please let us all know your status? Are you on schedule? Are you learning what you need to learn?

You should be well underway in your development. If you are in need of assistance, you should seek it soon.

Please let us all know where you are doing most of your communication. I do see some student activity project mailing lists, but I'm only seeing the work of a very small number of our students. I prefer that you work in an open and transparent manner; project dev lists are an ideal location for this sort of communication. Bugs are another good place. Some private email communication is normal and expected, but should augment public communication.

If students or mentors are missing in action, please let me know. Private email might be best for this sort of communication :-)

I look forward to hearing from you.

Wayne
--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse Projects

_______________________________________________
soc-dev mailing list
soc-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/soc-dev



Back to the top