- Coordinate with core developer (TEAM.md), talk strategy with him/her. You'll get a clue on how to add.
- Look at the state of the Project, which are maintained by the core-developers. Make sure you import the issues here in the right project and that the card you are working on is in doing.. This means others will come to you if they want to contribute to the same problem!
- Bugs can be reported through Issues, you cannot set a label, a core developer will set a label, when your bug is accepted/reproduced.
- Don't link to external sources in issues to convey textual information.. Use Github.
- Please update your files when changes have been made - Create pull requests when ready
- Code Examples in Wiki, not in code (I violated this rule when making the project, it will be remedied)
- Send code examples to [email protected] !! (100x100 image, title, description, team!)
- Don't introduce dependencies (like JQuery), if a dependency is to be introduced, this needs extensive forethought and consultation with Hjalmar Snoep!
- We said English, but the translation is below..
--- translation in Dutch -> vertaling naar Holands.
- Overleg met de coordinatoren (zie TEAM.md)
- Zie de projecten die deze coordinatoren aanmaken. Zorg dat je kaartje op de goede plek staat.
- Bugs melden via Issues.
- Geen notes in issues, probeer het af te handelen met Github.
- Please update your files when changes have been made - Create pull requests when ready
- voorbeeld code graag in docs, niet in code
- Send code examples to [email protected] !! (100x100 image, title, description, team!)
- Geen dependencies introduceren (zoals JQuery), zeker niet zonder uitvoerig overleg!
- We hebben gezegd Engels.. Leek me duidelijker zo, maar....