-
Notifications
You must be signed in to change notification settings - Fork 0
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
Find a date #2
Comments
I'm planning to send out |
Also in August this year: Chaos Communication Camp. Last time that happened (4 years ago) we skipped RailsCamp in favor of a Ruby Village. :) |
Whoops. Never finished my last comment. What I plan to send out via the Railscamp Newsletter is the announcement that there won't be a "regular" Railscamp this year (2015) due to lack of core organizers, but that everybody is invited to come the the OpenCodeTown at the CCC camp (featuring Railscamp, Railsgirls, NodeSchool, Rust, etc.) If there would already be a potential Railscamp date for 2016, this news could also be communicated. |
I'm in for helping on whatever needs to be done. Is railscamp2k16 still a thing? |
great that you want to help :) but for it to become a real "thing" we will need a couple more people commited to helping out. I had talked to @Uepsilon whether it might be an idea to move away a little bit from the "Rails" theme and maybe try to join forces with the people that were formerly behind SIGINT and its successor (don't know the name right now) to create something like a "Chaos Communication Camp Mini Cologne". But that's just a very half-baked idea right now. |
Will there be a railscamp this year? |
Unfortunately not. I talked about it with @jhilden but we did not plan Next year on the other hand is not yet decided. If we could find more ConcurrentHashMap [email protected] schrieb am Fr., 3. Juni 2016,
|
I would definitively be interested, but don't know where I could assist exactly. |
These are the factors I would aim for:
My vote would be e.g. for the weekend 10-11th of September 2016
The text was updated successfully, but these errors were encountered: