-
Notifications
You must be signed in to change notification settings - Fork 14
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
Repository Cleaning & Archiving #20
Comments
Is the web site repo our actual web site? If so, we should probably keep that. Do the guru session repos contain projects, or information? If the latter, maybe we can move that into the open repo. |
@ElDragonRojo Updated per your comments. Resetting clock to 1 week deadline. |
@spllr @mmeiborg @mattfeigal @matteom @pdarcey You guys cool with this? |
I am. |
Will have to check the website repo for sensitive info before opening it. But perhaps the code base of the current website should be in there and not old ruby code. @mmeiborg do we have the new code? Could you check with seb if he can push to our org page? |
Peter Mitchell is doing some work on the payment system. When done we’ll be in touch with Seb and I’ll ask. (Meanwhile the site is backup to Amazon every day.) On 31 Aug 2013, at 08:20, Klaas Speller wrote:
|
Hello everyone, never heard back on a final YES let's do this!!! More like a mumble mumble maybe if..... So I ask again @spllr @mmeiborg @mattfeigal @ElDragonRojo Shall we clean up some of the repos? |
Recommending a general cleanup of all projects/repositories.
Please take the next 7 days to review, discuss and generally backup what is needed/wanted.
Use/Keep
Use/Keep
Use/Keep
Move to Open Repo
Move to Open Repo
Move to Open Repo
Fork now or forever hold your piece! ;)
The text was updated successfully, but these errors were encountered: