Difference between revisions of "Guides/Contributing Code"
m |
|||
| Line 15: | Line 15: | ||
Externally facing apps need a bit more thought in terms of security, so use your common sense. Even if you know what you are doing hackers afterwards may not. | Externally facing apps need a bit more thought in terms of security, so use your common sense. Even if you know what you are doing hackers afterwards may not. | ||
| − | You can get an account on [[babbage]] by | + | You can get an account on [[babbage]] by asking on IRC. |
Revision as of 09:52, 6 December 2011
You want to add a bit to the hackspace infrastructure. We've built up a rough system of how things are done. So here are a few guidelines on how to do this so that other people can work on your code and everything is somewhat organised.
Languages
Python seems to be the lingua franca, but lots of us know a little bit of lots of languages. You are just likely to get more contributions to your code if it is python.
Github
We have a github group for shared code. It would be nice to have everything in one place if we can. Get access to this by asking on IRC or submitting a pull requests. If we're not familiar with your git skills, we may ask you to make a pull request first, just in case.
Internal Server
We currently have babbage as an internal server. This is to be preferred for internally facing apps, so that everyone can hack on them.
Externally facing apps need a bit more thought in terms of security, so use your common sense. Even if you know what you are doing hackers afterwards may not.
You can get an account on babbage by asking on IRC.