Menu
▾
▴
sahana-maindev
|
From: Michael H. <mi...@sa...> - 2012-11-09 01:33:04
|
Hello All,
Our next community call will be on next week on Tuesday 13th November:
* 0200 UTC
(https://tacops.webex.com/tacops/j.php?ED=187625942&UID=1398154882&PW=NMGM2M2E3NDM0&RT=MiMyMQ%3D%3D
or Dial 1-408-792-6300 or toll-free 1-877-668-4490 Access code: 718
492 034)
* 2000 UTC
(https://tacops.webex.com/tacops/j.php?ED=187625752&UID=1398154167&PW=NMDlmN2I1Mzc4&RT=MiMyMQ%3D%3D
or Dial 1-408-792-6300 or toll-free 1-877-668-4490 Access code: 712
625 251 )
(More detailed instructions below)
It's been a busy time for the Sahana Software Foundation and on the call
you'll have a just to hear more about our responses to Hurricane Sandy
in the USA. By the time of the Community Call we will know if we're part
of Google Code In (fingers crossed!). We will also have announced our
Sahana Internship Program (watch this space!) - anyone who's interested
in this
Unfortunately we don't have any guest speaker this month, but I'm sure
there will be a lot to discuss with everything going on in the community.
The meeting document is up here, so feel free to add any updates or
notes to it:
https://docs.google.com/document/d/12i9KfZXXiMTfFI7vIGewMh3onTnA98O58J7l6Dtuosc/edit
Cheers
--
Michael Howden
skype: michael.howden
twitter:@michaelhowden
Managing Director, AidIQ
Director, Sahana Software Foundation
Sahana Eden Project Management Committee
Sahana Community Development Committee
Hello ,
Sahana Software Foundation invites you to attend this online meeting.
*
Date: Tuesday, November 13, 2012
Time: 2:00 am, GMT Time (London, GMT) *
Meeting Number: 718 492 034
Meeting Password: S4h4n4
-------------------------------------------------------
To join the online meeting (Now from mobile devices!)
-------------------------------------------------------
1. Go to
https://tacops.webex.com/tacops/j.php?ED=187625942&UID=1398154882&PW=NMGM2M2E3NDM0&RT=MiMyMQ%3D%3D
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: S4h4n4
4. Click "Join".
To view in other time zones or languages, please click the link:
https://tacops.webex.com/tacops/j.php?ED=187625942&UID=1398154882&PW=NMGM2M2E3NDM0&ORT=MiMyMQ%3D%3D
-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
To receive a call back, provide your phone number when you join the
meeting, or call the number below and enter the access code.
Call-in toll-free number (US/Canada): 1-877-668-4490
Call-in toll number (US/Canada): 1-408-792-6300
Global call-in numbers:
https://tacops.webex.com/tacops/globalcallin.php?serviceType=MC&ED=187625942&tollFree=1
Toll-free dialing restrictions:
http://www.webex.com/pdf/tollfree_restrictions.pdf
Access code:718 492 034
*Date: Tuesday, November 13, 2012
**Time: 8:00 pm, GMT Time (London, GMT) *
Meeting Number: 712 625 251
Meeting Password: S4h4n4
-------------------------------------------------------
To join the online meeting (Now from mobile devices!)
-------------------------------------------------------
1. Go to
https://tacops.webex.com/tacops/j.php?ED=187625752&UID=1398154167&PW=NMDlmN2I1Mzc4&RT=MiMyMQ%3D%3D
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: S4h4n4
4. Click "Join".
To view in other time zones or languages, please click the link:
https://tacops.webex.com/tacops/j.php?ED=187625752&UID=1398154167&PW=NMDlmN2I1Mzc4&ORT=MiMyMQ%3D%3D
-------------------------------------------------------
To join the audio conference only
-------------------------------------------------------
To receive a call back, provide your phone number when you join the
meeting, or call the number below and enter the access code.
Call-in toll-free number (US/Canada): 1-877-668-4490
Call-in toll number (US/Canada): 1-408-792-6300
Global call-in numbers:
https://tacops.webex.com/tacops/globalcallin.php?serviceType=MC&ED=187625752&tollFree=1
Toll-free dialing restrictions:
http://www.webex.com/pdf/tollfree_restrictions.pdf
Access code:712 625 251
-------------------------------------------------------
For assistance
-------------------------------------------------------
1. Go to https://tacops.webex.com/tacops/mc
2. On the left navigation bar, click "Support".
|
|
From: Michael H. <mi...@sa...> - 2012-11-12 21:00:08
|
Dear All,
I'm very please to announce that the Sahana Software Foundation has been
accepted into Google Code In this year. There's only 10 organisations
who have been selected this year, so this is a very high honour!
I'm like to thank Fran Boon, Ashwyn Sharma, Graeme Foster, Alfonso de la
Guarda, Mark Prutsalis, Ramindu Deshapriya, Nuwan Waidyanatha, Pat
Tressel, Vivek Hamirwasia, Robby O'Connor, Praneeth Bodduluri and Nitin
Agarwal who have volunteered to be mentors for GCI. We've got a great
team there and I'm sure that we'll have a great program. If you're
interested in mentoring, it's not too late to get involved!
Next steps:
* Please fill out the roster to indicate when you're able to be on
Duty [0]
* Could you also add you email addresses to [0]
* Please start adding any task you may have for GCI - ideally add
these directly to the "Tasks to Upload" tab [0]
o We need someone to migrate all of the tasks from
http://eden.sahanafoundation.org/wiki/Event/2012/GCI (and it's
sub-pages) to "Tasks to Upload".
o We need someone to review the tasks in the tracker
(http://eden.sahanafoundation.org/report/1) and put links to any
that are appropriate for GCI in the "Tasks to Upload" page.
* I think that it would be good to have a meeting to discuss and get
agreement on how we run our GCI program - especially for those of
you who haven't been involved before. Hopefully we can do this
during the Sahana Community Call today (details below) - if not I'll
send out a message to find a time next week.
Looking forward to a great GCI!
[0] Sahana Google Code-In Mentor Roster & Task List 2012-2013 -
https://docs.google.com/spreadsheet/ccc?key=0AuNG6ihli0CudFpIeWJqbjNIRGE5d1NuaGtfYWgxeEE
Cheers
--
Michael Howden
skype: michael.howden
twitter:@michaelhowden
Managing Director, AidIQ
Director, Sahana Software Foundation
Sahana Eden Project Management Committee
Sahana Community Development Committee
On 9/11/12 2:32 PM, Michael Howden wrote:
> Hello All,
>
> Our next community call will be on next week on Tuesday 13th November:
>
> * 0200 UTC
> (https://tacops.webex.com/tacops/j.php?ED=187625942&UID=1398154882&PW=NMGM2M2E3NDM0&RT=MiMyMQ%3D%3D
> or Dial 1-408-792-6300 or toll-free 1-877-668-4490 Access code:
> 718 492 034)
> * 2000 UTC
> (https://tacops.webex.com/tacops/j.php?ED=187625752&UID=1398154167&PW=NMDlmN2I1Mzc4&RT=MiMyMQ%3D%3D
> or Dial 1-408-792-6300 or toll-free 1-877-668-4490 Access code:
> 712 625 251 )
>
> (More detailed instructions below)
>
> It's been a busy time for the Sahana Software Foundation and on the
> call you'll have a just to hear more about our responses to Hurricane
> Sandy in the USA. By the time of the Community Call we will know if
> we're part of Google Code In (fingers crossed!). We will also have
> announced our Sahana Internship Program (watch this space!) - anyone
> who's interested in this
> Unfortunately we don't have any guest speaker this month, but I'm sure
> there will be a lot to discuss with everything going on in the community.
>
> The meeting document is up here, so feel free to add any updates or
> notes to it:
> https://docs.google.com/document/d/12i9KfZXXiMTfFI7vIGewMh3onTnA98O58J7l6Dtuosc/edit
>
>
> Cheers
> --
> Michael Howden
> skype: michael.howden
> twitter:@michaelhowden
> Managing Director, AidIQ
> Director, Sahana Software Foundation
> Sahana Eden Project Management Committee
> Sahana Community Development Committee
>
> Hello ,
>
> Sahana Software Foundation invites you to attend this online meeting.
> *
> Date: Tuesday, November 13, 2012
> Time: 2:00 am, GMT Time (London, GMT) *
> Meeting Number: 718 492 034
> Meeting Password: S4h4n4
>
>
> -------------------------------------------------------
> To join the online meeting (Now from mobile devices!)
> -------------------------------------------------------
> 1. Go to
> https://tacops.webex.com/tacops/j.php?ED=187625942&UID=1398154882&PW=NMGM2M2E3NDM0&RT=MiMyMQ%3D%3D
>
> 2. If requested, enter your name and email address.
> 3. If a password is required, enter the meeting password: S4h4n4
> 4. Click "Join".
>
> To view in other time zones or languages, please click the link:
> https://tacops.webex.com/tacops/j.php?ED=187625942&UID=1398154882&PW=NMGM2M2E3NDM0&ORT=MiMyMQ%3D%3D
>
>
> -------------------------------------------------------
> To join the audio conference only
> -------------------------------------------------------
> To receive a call back, provide your phone number when you join the
> meeting, or call the number below and enter the access code.
> Call-in toll-free number (US/Canada): 1-877-668-4490
> Call-in toll number (US/Canada): 1-408-792-6300
> Global call-in numbers:
> https://tacops.webex.com/tacops/globalcallin.php?serviceType=MC&ED=187625942&tollFree=1
>
> Toll-free dialing restrictions:
> http://www.webex.com/pdf/tollfree_restrictions.pdf
>
> Access code:718 492 034
>
>
> *Date: Tuesday, November 13, 2012
> **Time: 8:00 pm, GMT Time (London, GMT) *
> Meeting Number: 712 625 251
> Meeting Password: S4h4n4
>
>
> -------------------------------------------------------
> To join the online meeting (Now from mobile devices!)
> -------------------------------------------------------
> 1. Go to
> https://tacops.webex.com/tacops/j.php?ED=187625752&UID=1398154167&PW=NMDlmN2I1Mzc4&RT=MiMyMQ%3D%3D
>
> 2. If requested, enter your name and email address.
> 3. If a password is required, enter the meeting password: S4h4n4
> 4. Click "Join".
>
> To view in other time zones or languages, please click the link:
> https://tacops.webex.com/tacops/j.php?ED=187625752&UID=1398154167&PW=NMDlmN2I1Mzc4&ORT=MiMyMQ%3D%3D
>
>
> -------------------------------------------------------
> To join the audio conference only
> -------------------------------------------------------
> To receive a call back, provide your phone number when you join the
> meeting, or call the number below and enter the access code.
> Call-in toll-free number (US/Canada): 1-877-668-4490
> Call-in toll number (US/Canada): 1-408-792-6300
> Global call-in numbers:
> https://tacops.webex.com/tacops/globalcallin.php?serviceType=MC&ED=187625752&tollFree=1
>
> Toll-free dialing restrictions:
> http://www.webex.com/pdf/tollfree_restrictions.pdf
>
> Access code:712 625 251
> -------------------------------------------------------
> For assistance
> -------------------------------------------------------
> 1. Go to https://tacops.webex.com/tacops/mc
> 2. On the left navigation bar, click "Support".
|
|
From: Louiqa R. <lo...@um...> - 2012-11-12 21:33:11
|
On Tue, 13 Nov 2012, Michael Howden wrote: > Dear All, > > I'm very please to announce that the Sahana Software Foundation has been accepted into Google Code In this > year. There's only 10 organisations who have been selected this year, so this is a very high honour! > > I'm like to thank Fran Boon, Ashwyn Sharma, Graeme Foster, Alfonso de la Guarda, Mark Prutsalis, Ramindu > Deshapriya, Nuwan Waidyanatha, Pat Tressel, Vivek Hamirwasia, Robby O'Connor, Praneeth Bodduluri and Nitin > Agarwal who have volunteered to be mentors for GCI. We've got a great team there and I'm sure that we'll > have a great program. If you're interested in mentoring, it's not too late to get involved! FANTASTIC and thanks to the FIRST THIRTEEN mentors!!!!! Louiqa |
|
From: Avni K. <av...@gm...> - 2012-11-12 21:35:18
|
WOW - great news! Congratulations! Avni On Nov 12, 2012, at 4:33 PM, Louiqa Raschid wrote: > > > On Tue, 13 Nov 2012, Michael Howden wrote: > >> Dear All, >> I'm very please to announce that the Sahana Software Foundation has been accepted into Google Code In this >> year. There's only 10 organisations who have been selected this year, so this is a very high honour! >> I'm like to thank Fran Boon, Ashwyn Sharma, Graeme Foster, Alfonso de la Guarda, Mark Prutsalis, Ramindu >> Deshapriya, Nuwan Waidyanatha, Pat Tressel, Vivek Hamirwasia, Robby O'Connor, Praneeth Bodduluri and Nitin >> Agarwal who have volunteered to be mentors for GCI. We've got a great team there and I'm sure that we'll >> have a great program. If you're interested in mentoring, it's not too late to get involved! > > FANTASTIC and thanks to the FIRST THIRTEEN mentors!!!!! Louiqa > > -- > You received this message because you are subscribed to the Google Groups "Sahana-Eden" group. > To post to this group, send email to sah...@go.... > To unsubscribe from this group, send email to sah...@go.... > For more options, visit https://groups.google.com/groups/opt_out. > > |
|
From: Pat T. <ptr...@my...> - 2012-11-16 19:00:13
|
Apologies for spamming the lists -- this is aimed mainly at GCI mentors or others who'd like to help define GCI tasks and (more immediately) help get them onto the spreadsheet for upload. List of mentors from Michael's email: Fran Boon, Ashwyn Sharma, Graeme Foster, Alfonso de la Guarda, Mark > Prutsalis, Ramindu Deshapriya, Nuwan Waidyanatha, Pat Tressel, Vivek > Hamirwasia, Robby O'Connor, Praneeth Bodduluri and Nitin Agarwal > There are 5 task topics -- code, documentation, outreach, quality assurance, user interface -- and 5 lists of tasks to get onto the spreadsheet. I've finished code and am partway through documentation. Anyone want to have a go at outreach, QA, UI? They can be split up if lots of mentors want to help. ;-) There's one little ticky bit: The lists of tasks were on 5 pages linked from here: http://eden.sahanafoundation.org/wiki/Event/2012/GCI But most of those tasks were consolidated back onto the Eden wiki... http://eden.sahanafoundation.org/wiki/Contribute ...so they're no longer shown on the above GCI pages, they're mixed in with non-GCI work, and they've been updated since they were consolidated. So not everything on the "contribute" pages is a GCI task... So here's the trick: Go to the "event" wiki page for the topic you want to enter on the spreadsheet. Go to its history. Look at the version from a few days ago, where there was a list of tasks. That gives you the task titles (though the content may have been updated on the "contribute" pages). Back on the "contribute" pages (now that you know which are GCI tasks) for each GCI task do this: Look at the task -- is it way too time consuming? Should take an experienced developer on the order of 2-4 hours. If so, can it be split up? You can edit the wiki to subdivide tasks if needed. (Trac wiki hint: To get a link to a subdivided task that doesn't have its own link in the page table of contents, you can add an anchor like this: [=#NameOfAnchor] ) Also if the task is unclear, or will obviously need some hints or pointers to docs, please add them. Then mark the task as for GCI by adding [GCI] to its title (if the task has multiple pieces that don't have individual table of contents entries, you can put in [GCI, multiple tasks]), so it's easy to see in the table of contents. Since you're about to add it to the spreadsheet, add this right under the title: ''Added to GCI spreadsheet'' Add the task to the spreadsheet of tasks to be uploaded to Melange: https://docs.google.com/spreadsheet/ccc?key=0AuNG6ihli0CudFpIeWJqbjNIRGE5d1NuaGtfYWgxeEE Ok! Did one? Cool!! It'll be easier the next time. Did a whole topic? Victory dance! \o/ So, who wants to do which topic (outreach, QA, UI)? Who has new task ideas? Thanks!!! -- Pat |
|
From: Pearson, G. (NIH/NLM/L. [C] <gpe...@ma...> - 2012-11-16 20:08:45
|
I've added 3 more mentors to the ImageStat task, besides myself: Vajda, Szilard <szi...@ni...> Kanduru, Ajay <aka...@ma...> "Chase" aka Bonifant, Michael <mic...@ni...> Szilard will be the primary mentor (he's responsible for the project's creation of annotations). Chase is an intern here at NLM who has used the tool for annotation. Ajay is the tool's programmer. I'll be editing the spreadsheet further to specify mentor coverage as it becomes known. BTW, we're dropping the conjectured "document ImageStat" task, since most of that has to be done in advance for the GCI students. Also, Greg is likely back and in touch next week from a family funeral in the mid-west. Glenn From: Pat Tressel [mailto:ptr...@my...] Sent: Friday, November 16, 2012 2:00 PM To: Michael Howden Cc: Sahana Discuss; Sahana Eden Subject: Re: [sahana-discuss] [Members] Sahana Software Foundation accepted in Google Code In! Apologies for spamming the lists -- this is aimed mainly at GCI mentors or others who'd like to help define GCI tasks and (more immediately) help get them onto the spreadsheet for upload. List of mentors from Michael's email: Fran Boon, Ashwyn Sharma, Graeme Foster, Alfonso de la Guarda, Mark Prutsalis, Ramindu Deshapriya, Nuwan Waidyanatha, Pat Tressel, Vivek Hamirwasia, Robby O'Connor, Praneeth Bodduluri and Nitin Agarwal There are 5 task topics -- code, documentation, outreach, quality assurance, user interface -- and 5 lists of tasks to get onto the spreadsheet. I've finished code and am partway through documentation. Anyone want to have a go at outreach, QA, UI? They can be split up if lots of mentors want to help. ;-) There's one little ticky bit: The lists of tasks were on 5 pages linked from here: http://eden.sahanafoundation.org/wiki/Event/2012/GCI But most of those tasks were consolidated back onto the Eden wiki... http://eden.sahanafoundation.org/wiki/Contribute ...so they're no longer shown on the above GCI pages, they're mixed in with non-GCI work, and they've been updated since they were consolidated. So not everything on the "contribute" pages is a GCI task... So here's the trick: Go to the "event" wiki page for the topic you want to enter on the spreadsheet. Go to its history. Look at the version from a few days ago, where there was a list of tasks. That gives you the task titles (though the content may have been updated on the "contribute" pages). Back on the "contribute" pages (now that you know which are GCI tasks) for each GCI task do this: Look at the task -- is it way too time consuming? Should take an experienced developer on the order of 2-4 hours. If so, can it be split up? You can edit the wiki to subdivide tasks if needed. (Trac wiki hint: To get a link to a subdivided task that doesn't have its own link in the page table of contents, you can add an anchor like this: [=#NameOfAnchor] ) Also if the task is unclear, or will obviously need some hints or pointers to docs, please add them. Then mark the task as for GCI by adding [GCI] to its title (if the task has multiple pieces that don't have individual table of contents entries, you can put in [GCI, multiple tasks]), so it's easy to see in the table of contents. Since you're about to add it to the spreadsheet, add this right under the title: ''Added to GCI spreadsheet'' Add the task to the spreadsheet of tasks to be uploaded to Melange: https://docs.google.com/spreadsheet/ccc?key=0AuNG6ihli0CudFpIeWJqbjNIRGE5d1NuaGtfYWgxeEE Ok! Did one? Cool!! It'll be easier the next time. Did a whole topic? Victory dance! \o/ So, who wants to do which topic (outreach, QA, UI)? Who has new task ideas? Thanks!!! -- Pat |
|
From: Pat T. <ptr...@my...> - 2012-11-16 22:49:50
|
(Questions for both MIchael and Glenn specifically are included below.) I’ve added 3 more mentors to the ImageStat task > So this brings multiple task instances. There are several tasks that might have multiple instances: Bug fixing The above ImageStat task Making schema diagrams for Eden modules Write / update user guidelines for an Eden module Michael -- Should several instances of these tasks be added now? For the Eden module tasks, I'd recommend that we pick out specific modules and specify the module in the Melange task. How many of each should be added at the outset? Glenn -- Do you want multiple instances of the ImageStat task, overall? how many at the outset? All -- Little Trac wiki markup correction... ''Added to GCI spreadsheet''[[BR]] Also, when you add [GCI] to the headings, the URL changes... -- Pat |
|
From: Pearson, G. (NIH/NLM/L. [C] <gpe...@ma...> - 2012-11-16 23:28:15
|
Pat - ImageStat shares some backend db structures with Vesuvius/PL, and so works in terms of "events" (like disaster events). Each 3-4 hour task for GCI would be a separate event, i.e., "GCI1", "GCI2", etc. We would set up each such event with PL admin, then copy over the corresponding batch of images (this is a zipfile import hack and a bit tedious; room for improvement here). Before all that, partitioning the image corpus into task-sized chunks for zipping can be done by a script, so shouldn't be too bad. The thinking is that we would start with 10 such tasks (maybe trickled out the first week until we get our sea legs) and anticipate adding 10 tasks per week, more or less as demand and our capabilities dictates. Besides the work in creating a task, there's the work of evaluating each completed task in a way that is fair, convincing, timely, and not onerous for us. The first week of this is likely to be demanding. Glenn - heading out the door. From: ptr...@uw... [mailto:ptr...@uw...] On Behalf Of Pat Tressel Sent: Friday, November 16, 2012 5:50 PM To: Michael Howden; Pearson, Glenn (NIH/NLM/LHC) [C] Cc: Sahana Eden; discuss Subject: Re: [sahana-discuss] [Members] Sahana Software Foundation accepted in Google Code In! (Questions for both MIchael and Glenn specifically are included below.) I've added 3 more mentors to the ImageStat task So this brings multiple task instances. There are several tasks that might have multiple instances: Bug fixing The above ImageStat task Making schema diagrams for Eden modules Write / update user guidelines for an Eden module Michael -- Should several instances of these tasks be added now? For the Eden module tasks, I'd recommend that we pick out specific modules and specify the module in the Melange task. How many of each should be added at the outset? Glenn -- Do you want multiple instances of the ImageStat task, overall? how many at the outset? All -- Little Trac wiki markup correction... ''Added to GCI spreadsheet''[[BR]] Also, when you add [GCI] to the headings, the URL changes... -- Pat |
|
From: Mark P. <glo...@gm...> - 2012-11-16 23:07:05
|
Tasks should be unique to the extent possible. No pointers to "fix a bug from this list" and a pointer to Trac - Google said specifically that they did not want this.... individual items on the tracker should be screened for appropriateness and a unique task entered on the spreadsheet with a link to the specific ticket on trac. For ImageStat - can these be broken down by a code or numbering system - i.e. complete batch 1-600; batch 601-1200; 1201-1800, etc.? ImageStat testing tasks at the outset should number no more than 10 to start as we can add more and adjust numbers if these prove too time consuming. Sorry it is extra work but it makes a difference to Google and to the participants in the contest. Thanks, Mark On Nov 16, 2012, at 5:49 PM, Pat Tressel wrote: > (Questions for both MIchael and Glenn specifically are included below.) > > I’ve added 3 more mentors to the ImageStat task > > > So this brings multiple task instances. There are several tasks that might have multiple instances: > > Bug fixing > The above ImageStat task > Making schema diagrams for Eden modules > Write / update user guidelines for an Eden module > > Michael -- > > Should several instances of these tasks be added now? > > For the Eden module tasks, I'd recommend that we pick out specific modules and specify the module in the Melange task. > > How many of each should be added at the outset? > > Glenn -- > > Do you want multiple instances of the ImageStat task, overall? how many at the outset? > > All -- > > Little Trac wiki markup correction... > > ''Added to GCI spreadsheet''[[BR]] > > Also, when you add [GCI] to the headings, the URL changes... > > -- Pat > > -- > You received this message because you are subscribed to the Google Groups "Sahana-Eden" group. > To post to this group, send email to sah...@go.... > To unsubscribe from this group, send email to sah...@go.... > For more options, visit https://groups.google.com/groups/opt_out. > > |
|
From: Pat T. <ptr...@my...> - 2012-11-16 23:32:24
|
> No pointers to "fix a bug from this list" and a pointer to Trac - Google > said specifically that they did not want this.... individual items on the > tracker should be screened for appropriateness and a unique task entered on > the spreadsheet with a link to the specific ticket on trac. > Sure, that's what I was thinking -- we need to go through the available bugs. I can do (some of) that later (but happy to have others look too). For the Eden module schema diagram and user guidelines tasks, people who know what's needed now should pick some out. Post them here, and I'll add them. Still need people to add the outreach, QA, UI tasks. -- Pat |
|
From: Pearson, G. (NIH/NLM/L. [C] <gpe...@ma...> - 2012-11-16 23:32:54
|
Mark - Emails crossed here, my prior one addresses most points. So the only question in my mind is, do we have to use the Melange list and continually add tasks "GCI1, GCI2, ..GCI99", or can we just have a single Melange entry, and ask the students to request the specific task number (e.g., by IRC or email)? From: Mark Prutsalis [mailto:glo...@gm...] Sent: Friday, November 16, 2012 6:07 PM To: sah...@go... Cc: Michael Howden; Pearson, Glenn (NIH/NLM/LHC) [C]; discuss Subject: Re: [SahanaEden] [sahana-discuss] [Members] Sahana Software Foundation accepted in Google Code In! Tasks should be unique to the extent possible. No pointers to "fix a bug from this list" and a pointer to Trac - Google said specifically that they did not want this.... individual items on the tracker should be screened for appropriateness and a unique task entered on the spreadsheet with a link to the specific ticket on trac. For ImageStat - can these be broken down by a code or numbering system - i.e. complete batch 1-600; batch 601-1200; 1201-1800, etc.? ImageStat testing tasks at the outset should number no more than 10 to start as we can add more and adjust numbers if these prove too time consuming. Sorry it is extra work but it makes a difference to Google and to the participants in the contest. Thanks, Mark On Nov 16, 2012, at 5:49 PM, Pat Tressel wrote: (Questions for both MIchael and Glenn specifically are included below.) I've added 3 more mentors to the ImageStat task So this brings multiple task instances. There are several tasks that might have multiple instances: Bug fixing The above ImageStat task Making schema diagrams for Eden modules Write / update user guidelines for an Eden module Michael -- Should several instances of these tasks be added now? For the Eden module tasks, I'd recommend that we pick out specific modules and specify the module in the Melange task. How many of each should be added at the outset? Glenn -- Do you want multiple instances of the ImageStat task, overall? how many at the outset? All -- Little Trac wiki markup correction... ''Added to GCI spreadsheet''[[BR]] Also, when you add [GCI] to the headings, the URL changes... -- Pat -- You received this message because you are subscribed to the Google Groups "Sahana-Eden" group. To post to this group, send email to sah...@go...<mailto:sah...@go...>. To unsubscribe from this group, send email to sah...@go...<mailto:sah...@go...>. For more options, visit https://groups.google.com/groups/opt_out. |
Thanks for helping keep SourceForge clean.
X