Moving JWST to github about braindump HOT 6 CLOSED

Updated the original issue with suggested agenda for tomorrow's meeting.

from braindump.

May 19th, noon, S322

from braindump.

from braindump.

Yes, I'll post notes here.

from braindump.

Very interesting topic but unfortunately I cannot attend. Looking forward to the meeting notes.

Personally:

• 👎 on namespace. Realistically, what user will only ever need a single step? As a user, I'd rather get everything as a single package, which will not cause dependency mismatch problem.
• Both workflows are similar. But Astropy is a bit more complete, I think. I might be biased because I am used to Astropy already. Perhaps a compromise is to start with Joe's workflow, and then adopt Astropy's when everyone is familiar with git and GitHub?
• Where are the documents anyway? Please don't say Confluence or SOCCER.

from braindump.

I added notes from yesterday's meeting.

https://github.com/spacetelescope/braindump/blob/master/move_to_github_%234/notes-move-to-github.rst

Feel free to add, modify, agree or disagree.

If there's consensus, we may have a sprint next week to reorganize the code, write tests or just mess with github.

from braindump.