You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just talked to @dhuppenkothen about this and she suggested I leave an issue here about it.
For dotAstronomy and the AAS meeting hack days, I've implemented a "hacks collector" page/app: https://github.com/dotastro/hacks-collector and https://github.com/aasorg/hacks-collector . The basic idea is that it leverages a combination of git, Github pages, flask, and Heroku to make a system where people who do hacks can submit them to be included in a github repo as a long-term record of all the hacks at those events (either directly as hand-written PR's, or via a web form that automatically creates a PR). The whole things is pretty much automated at this point, so all the managers have to do is hit the merge button if a submission looks good.
It occurred to me that this might be useful for Astro Hack Week. If this seems like a good idea, I'm happy to adapt that machinery to Astro Hack Week's needs.
If by chance I'm at the next Astro Hack Week I could even do it as a hack... But either way it probably makes sense to do around the time of the hack week itself so as to get quick feedback to make sure it's all making sense.
The text was updated successfully, but these errors were encountered:
I'm happy to help to set this up (if you need any help at all). It would be great to have this up and running from early on so people will actually use during the week.
I just talked to @dhuppenkothen about this and she suggested I leave an issue here about it.
For dotAstronomy and the AAS meeting hack days, I've implemented a "hacks collector" page/app: https://github.com/dotastro/hacks-collector and https://github.com/aasorg/hacks-collector . The basic idea is that it leverages a combination of git, Github pages, flask, and Heroku to make a system where people who do hacks can submit them to be included in a github repo as a long-term record of all the hacks at those events (either directly as hand-written PR's, or via a web form that automatically creates a PR). The whole things is pretty much automated at this point, so all the managers have to do is hit the merge button if a submission looks good.
It occurred to me that this might be useful for Astro Hack Week. If this seems like a good idea, I'm happy to adapt that machinery to Astro Hack Week's needs.
If by chance I'm at the next Astro Hack Week I could even do it as a hack... But either way it probably makes sense to do around the time of the hack week itself so as to get quick feedback to make sure it's all making sense.
The text was updated successfully, but these errors were encountered: