search

LSST-nonproject / sims_maf_contrib

Contributed code for MAF (sims_maf)
18 stars 46 forks source link

Projects need milestones #3

Closed drphilmarshall closed 10 years ago

drphilmarshall commented 10 years ago

Maybe the first one is the proceedings of the workshop that Knut mentioned? Or some sort of "launch" to prompt everyone to check in?

rhiannonlynne commented 10 years ago

I'm still getting used to issues, etc. In the project we use issues more specifically .. but I guess this is an issue to prompt communication? (so all the team members should be getting this email?) Can we check that everyone's getting the emails appropriately. I seem to be getting some sent to spam and only seeing replies.

drphilmarshall commented 10 years ago

I think I probably had to tag my github notifications as "always important" at some point, too. This issue really is about milestones though - if there's a date to get something done by we should make a milestone of it and associate issues with it. I think its what you would normally do in jira, no? I can't answer the question though, because I don't know what the MAF plan is - I just know that issues need to belong to milestones! :-)

On Mon, Aug 18, 2014 at 11:42 AM, Lynne Jones notifications@github.com wrote:

I'm still getting used to issues, etc. In the project we use issues more specifically .. but I guess this is an issue to prompt communication? (so all the team members should be getting this email?) Can we check that everyone's getting the emails appropriately. I seem to be getting some sent to spam and only seeing replies.

— Reply to this email directly or view it on GitHub https://github.com/LSST-nonproject/sims_maf_contrib/issues/3#issuecomment-52536208 .

rhiannonlynne commented 10 years ago

So - let's discuss what milestones there might be. From my point of view, the important milestones would be related to the opsim runs and being able to run the metrics that you all deem important on those runs (we will run the metrics on all released runs and make the results available on the web). This means that there should be some plan to start a discussion of the results of those metrics and what the results mean (and what new runs should be done as a result). Would it make sense to set up a quarterly schedule to review the available contributed metrics, decide which to add to the 'default set', run these on all available opsim runs? (added after close of issue...)

drphilmarshall commented 10 years ago

I like the regular review idea very much! A nice way to keep things rolling along - and to keep prompting for new metrics etc, with the carrot of seeing them run on the new opsim products.

On Thu, Sep 4, 2014 at 2:59 PM, Lynne Jones notifications@github.com wrote:

So - let's discuss what milestones there might be. From my point of view, the important milestones would be related to the opsim runs and being able to run the metrics that you all deem important on those runs (we will run the metrics on all released runs and make the results available on the web). This means that there should be some plan to start a discussion of the results of those metrics and what the results mean (and what new runs should be done as a result). Would it make sense to set up a quarterly schedule to review the available contributed metrics, decide which to add to the 'default set', run these on all available opsim runs? (added after close of issue...)

— Reply to this email directly or view it on GitHub https://github.com/LSST-nonproject/sims_maf_contrib/issues/3#issuecomment-54551603 .