Difference between revisions of "SME Server Development Framework"

From SME Server
Jump to navigationJump to search
Line 20: Line 20:
  
  
==== Bughunters & Testers ====
+
==== 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
 
Skills
 +
* Enthusiasm
  
 +
==== 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
  
==== Junior Programmer ====
 
 
Skills
 
Skills
 
* Linux knowledge
 
* 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 mandates, and several options will be given.
  
==== Normal Programmer ====
 
 
Skills
 
Skills
* Experienced Linux knowledge
+
* Linux knowledge
 +
* CVS
 +
* Perl / Python / Bash
 +
* Regular expressions
  
 +
==== Committer ====
 +
Someone who has write access to our CVS on Sourceforge.
  
==== Senior Programmer ====
 
 
Skills
 
Skills
* Excellent Linux knowledge
+
* CVS
* Perl
+
 
* Bash
+
==== Builder ====
* Regular expressions
+
Someone who has access to the SME Server Build System.
 +
 
 +
Skills
 +
* SME Server Build System
 +
 
 +
==== Contrib Owner ====
 +
Someone who maintains or develops one of the contrib pacakges.
  
 +
Skills
 +
* ABC
  
 
== Development tools ==
 
== Development tools ==

Revision as of 05:59, 12 February 2013

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

Development roles

Various 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

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 mandates, and several options will be given.

Skills

  • Linux knowledge
  • CVS
  • Perl / Python / Bash
  • Regular expressions

Committer

Someone who has write access to our CVS on Sourceforge.

Skills

  • CVS

Builder

Someone who has access to the SME Server Build System.

Skills

  • SME Server Build System

Contrib Owner

Someone who maintains or develops one of the contrib pacakges.

Skills

  • ABC

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