Difference between revisions of "Developer.Guidelines"
(→Submitting Merge Requests: switch to github) |
(→Developer Guidelines: revised to be more current) |
||
| Line 1: | Line 1: | ||
==Developer Guidelines== | ==Developer Guidelines== | ||
BOARD18 is currently a '''very''' small project. | BOARD18 is currently a '''very''' small project. | ||
At the time of this writing | At the time of this writing around 10 people have contributed code, documentation or other work to BOARD18. <br>The testing community for BOARD18 consists of fewer than 20 people. | ||
Thus there is not yet much formal structure to the project. | Thus there is not yet much formal structure to the project. <br> | ||
The creator and main designer/coder of BOARD18 is Rich Price. And he could also be considered the informal project leader. <br>You can contact him by email at '''rich at gandalf.ws'''. | |||
The creator and main designer/coder of BOARD18 is Rich Price. And he could also be considered the informal project leader. <br>You can contact him | |||
===Communication with other Developers=== | ===Communication with other Developers=== | ||
The BOARD18 project has a | The BOARD18 project has a closed Google group called "BOARD18 Dev" that is used by developers to communicate about the project and about code development. <br>Anyone can request to join this group | ||
[https://groups.google.com/forum/?hl=en#!forum/board18-dev from here]. | |||
===Reporting Bugs=== | ===Reporting Bugs=== | ||
The BOARD18 project also has a BUGZILLA issue tracker at | The BOARD18 project also has a BUGZILLA issue tracker at | ||
[http://bugs.board18.org bugs.board18.org]. This tool should be used to track bugs, enhancement requests and other tasks. The bug list should be a good source of ideas for developers looking for something to do. | [http://bugs.board18.org bugs.board18.org]. This tool should be used to track bugs, enhancement requests and other tasks. | ||
<br>The bug list in this tracker should be a good source of ideas for developers looking for something to do. | |||
===Submitting Merge Requests=== | ===Submitting Merge Requests=== | ||
The BOARD18 project keeps its repositories at [https://github.com Github]. | The BOARD18 project keeps its repositories at [https://github.com Github]. | ||
'''Use [[How To Contribute Code|this How To document]] as a guide to using Github to code for the BOARD18 Project.''' | '''Use [[How To Contribute Code|this How To document]] as a guide to using Github to code for the BOARD18 Project.''' | ||
Revision as of 13:21, 23 March 2016
Developer Guidelines
BOARD18 is currently a very small project.
At the time of this writing around 10 people have contributed code, documentation or other work to BOARD18.
The testing community for BOARD18 consists of fewer than 20 people.
Thus there is not yet much formal structure to the project.
The creator and main designer/coder of BOARD18 is Rich Price. And he could also be considered the informal project leader.
You can contact him by email at rich at gandalf.ws.
Communication with other Developers
The BOARD18 project has a closed Google group called "BOARD18 Dev" that is used by developers to communicate about the project and about code development.
Anyone can request to join this group
from here.
Reporting Bugs
The BOARD18 project also has a BUGZILLA issue tracker at
bugs.board18.org. This tool should be used to track bugs, enhancement requests and other tasks.
The bug list in this tracker should be a good source of ideas for developers looking for something to do.
Submitting Merge Requests
The BOARD18 project keeps its repositories at Github. Use this How To document as a guide to using Github to code for the BOARD18 Project.