-
Notifications
You must be signed in to change notification settings - Fork 2
Contacting Sinatra maintainers? #5
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
Comments
+1, Eric. That's a pretty good idea. |
@ericgj I think it's a fantastic idea. Actually when I thought of setting up this group I thought if it took off we could eventually reach out to the maintainers just like you said. I think in most cases they would be happy at the thought of something encouraging users to read the source before asking questions. Im sure other @codereading/readers think this is a great idea so please go ahead! |
The code reading project seems like an awesome idea. I just started watching the repo. I will be on a major conference trip until the end of June, so I won't follow everything in here closely. Feel free to mention me if you think I should join a particular discussion. |
A very common question is how one goes about splitting up routes into multiple files rather than having them all in the one |
Good question @davesag. Do you want to open a new issue so we can discuss it? |
I had in mind to drop a note on the Sinatra mailing list that we are doing this code reading, anyone is welcome to join in, and ask the maintainers if there are particular questions that newcomers to Sinatra often ask about or issues they run into. With the idea that we could maybe have a focus on those areas - "common stumbling blocks" etc. What do you think?
Eric
The text was updated successfully, but these errors were encountered: