-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compile a list of lessons learned #224
Comments
Good idea! Something about the need for provenance, based on recent issues - @tony-johnson you had an idea for helping with that, you were going to issue it? Also this relates to this Computing Infrastructure issue - so if we can get some ideas about the pathfinder side of things going here, maybe we can prepare to report to the CI group? |
I have created #228 which I think is somewhat related to this issue. |
Cool. Passing to @SimonKrughoff to get the ball rolling. Post a lesson learned, and pass the assignment on! |
Tag @rbiswas4. We are passing the ball around adding some lessons learned. When you have added one to the page linked in the initial message in this issue, re-assign to someone else. |
I just added a few lessons learned to our "Lessons Learned" page. Please start each one with a single sentence summary in bold, to aid readability! I also split the document into Runs 1 and 1.1, and Run 2, also to keep it readable. Let's all please contribute to this document today, so we can make sure to have good coverage in our talks. Click on this link and edit in your thoughts! Thanks, everyone. cc. @DarkEnergyScienceCollaboration/twinkles |
I put in a few. Will add more if I can think of them. |
Thanks Rahul! @tony-johnson I put one in with your name on it! You'd better On Fri, Jul 8, 2016 at 12:27 AM, rbiswas4 notifications@github.com wrote:
|
Thanks for all your contributions to the "Lessons Learned" list - hopefully this'll be useful in formulating conclusions to our LSST DESC Notes series #284. We'll want to check back to this list when we are finishing those off, to make sure we don't miss anything. In the end, though, the record will be in the Notes, and this temporary list will be able to be retired. |
We are learning things as we go along and I'd like to see if we can capture that. My current thinking is just to keep a running list of things here.
The text was updated successfully, but these errors were encountered: