Difference between revisions of "SME Server Development Framework"
m (→Developer) |
|||
| (10 intermediate revisions by 3 users not shown) | |||
| Line 26: | Line 26: | ||
* Enthusiasm | * Enthusiasm | ||
| + | Backlog | ||
| + | * [[Triage_Queue|Triage Queue]] shows the list to work on. | ||
| + | * [[Verification_Queue|Verification Queue]] show the list of corrected bugs that you should test. | ||
==== Patch Author ==== | ==== Patch Author ==== | ||
| Line 45: | Line 48: | ||
* Perl / Python / Bash | * Perl / Python / Bash | ||
* Regular expressions | * Regular expressions | ||
| + | |||
==== Committer ==== | ==== Committer ==== | ||
| Line 54: | Line 58: | ||
==== Builder ==== | ==== Builder ==== | ||
| − | Someone who has access to the SME Server Build System. | + | Someone who has access to the SME Server Build System. This includes running 'make tag build' on behalf of the committers. |
Skills | Skills | ||
* SME Server Build System | * SME Server Build System | ||
| − | |||
==== Contrib Owner ==== | ==== Contrib Owner ==== | ||
| − | Someone who maintains or develops one of the contrib | + | Someone who maintains or develops one of the contrib packages. |
Skills | Skills | ||
| − | * | + | |
| + | * Linux knowledge | ||
| + | * CVS: able to retrieve the latest source code. | ||
| + | * Patch creation | ||
| + | * Working build system (official or their own) | ||
| + | * Perl / Python / Bash | ||
| + | * Regular expressions | ||
== Development tools == | == Development tools == | ||
| Line 92: | Line 101: | ||
[[Category:SME9-Development]] | [[Category:SME9-Development]] | ||
| + | [[Category:SME Server Development Framework]] | ||
| + | [[Category:Developer]] | ||
| + | [[Category:Howto]] | ||
Latest revision as of 13:03, 1 February 2014
SME Server Development
Welcome to the development of SME Server!
To provide SME Server a consistent and a sustainable future the contribs.org community is formalising the future development of SME Server. Not just the next release, but all future releases. You're most welcome to join and contribute in whatever way you can for all skills are welcomed. Not just programmers, but also enthusiasts that can help out.
Have fun!
Current development cycle
- Current: SME Server 9.0
- Next: SME Server 9.1
Development roles
Documentation writers
Skills
- Ability to write user documentation
- Ability to write technical documentation
- Ability to write administration manuals
Troubleshooter
There's a lot that non-coders can do to help in the bug tracker to improve bug report quality. We need help in making sure that bug reports are clear, that observations are fully collected, are separated from speculation and attempted workarounds, relevant log files are checked, etc, etc.
Skills
- Enthusiasm
Backlog
- Triage Queue shows the list to work on.
- Verification Queue show the list of corrected bugs that you should test.
Patch Author
Someone who has a fix that they want to contribute, but currently does not want to get involved with CVS and a build system
Skills
- Linux knowledge
Developer
Someone who is able to retrieve our source code from Sourceforge and make local builds to test out their fix. Note: The actual build system will not be mandated, and several options will be given.
Skills
- Linux knowledge
- CVS: able to retrieve the latest source code.
- Patch creation
- Working build system
- Perl / Python / Bash
- Regular expressions
Committer
Someone who has write access to our CVS on Sourceforge.
Skills
- CVS: able to retrieve, update, and commit a source code change.
Builder
Someone who has access to the SME Server Build System. This includes running 'make tag build' on behalf of the committers.
Skills
- SME Server Build System
Contrib Owner
Someone who maintains or develops one of the contrib packages.
Skills
- Linux knowledge
- CVS: able to retrieve the latest source code.
- Patch creation
- Working build system (official or their own)
- Perl / Python / Bash
- Regular expressions
Development tools
Wiki
Bugzilla
CVS
Patching
RPM building
Development process
- Set goals for the release
- Get organised
- Create a roadmap such as SME9.0_Roadmap
- Start a step by step plan such as this one.
- Stick to the roadmap