Hi Some of suggestions are as follows:
> > One part of the application is a link to our tasks page. One thing that > has confused me about this program is how tasks should be sized. How many > hours would we expect a task to take? As far as I know the tasks are categorized as per the level of difficulty (easy, medium and hard). Certain points are associated with each level of difficulty. Each task also has a pre-fixed amount of time to complete the task which is decided by the mentor for the task. Student do not necessarily work on the tasks only for one organization. They are free to switch between the organizations as soon as they complete the task. > Do we have an old list from when we participated in GCI to get an idea? > Also what kind of infrastructure do we want for our task list, just Jira > labels or something else? > Not very sure of the intricacies of Jira infrastructure or policies from our side, but gci-2011 for the tasks would be good to manage the tasks on Apache's side. On google's side, melange provides an interface to manage the completed tasks on there end as well. discussion between students and mentor usually happens there but as we already have a established infrastructure like Jira so encouraging the prospective students to use it would be a good bet. :) If I remember correctly, google requires the students to upload the patch/documentation or anything produced for the task on melange as well with each completed task. > > It seems before we submit our application we should get the list of tasks > started and have a primary admin volunteer. I wish I could admin but am > too time constrained right now. I could work on adding some tasks for > Derby once I understand the sizing. > Yes, this year google requires the organization to have a good number of tasks before applying (I am not sure but probably on a wiki page) It would be good to have a list of probably roles and responsibility that an admin needs to perform. Thanks > > Thanks > > Kathey > > > > -- Regards Siddharth Srivastava
