-
Notifications
You must be signed in to change notification settings - Fork 67
Home
Please see README.md for a quick overview on our git workflow.
Join us in #nyccamp on IRC to chat about NYC Camp. Please join and stay awhile -- there's a lot of important notifications and communications happening in the channel :)
- rule32
- Druplicon
- githubbot - joins/leaves the channel to post notifications on commits and pull requests.
Issues are tracked on GitHub at http://github.com/NYC-Camp/website/issues.
We also use a PM tool called Trello. For 2014, this is: https://trello.com/b/ddrb1mw7/website-development. If you wish to get more involved beyond the github issue queue, then you can request access to Trello by contacting @mirie (mai on IRC).
There are already a lot of good resources online documentation agile open source distributed development converging on best practices. Although you may find local development hasn’t necessarily gained universal traction, it has generally helped to bring about more agreement over best practices.
If there’s one underlying principle here it’s good communication and good code should go hand in hand. A good rule of thumb for developers to follow is, whatever project you are working on, be logged into its respective channel when you are working on it. So don't be shy, join the #nyccamp channel :D
Another more specific example of this would be: When you add a pull request, check in the channel or watch for comment notifications from Github and/or the channel. Also, be sure to include in your issue or pull request any names (you can use '@' + github handle, example: @mirie) of people you would like to specifically involve in the discussion/feedback.
We also have an email for the team: team@nyccamp.org
Please see the wiki pages.
If you are just getting setup, then you'll probably want to checkout Setting up your Local Dev Environment.
If you are already setup, please review our git workflow.
Please also checkout our 2014 roadmap post-camp.