Difference between revisions of "SME Server Development Framework"

From SME Server
Jump to navigationJump to search
 
(24 intermediate revisions by 3 users not shown)
Line 2: Line 2:
 
Welcome to the development of SME Server!
 
Welcome to the development of SME Server!
  
−
To provide SME Server a [[The_future_of_SME_Server|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 [[SME_Server_Development_Framework#Development_roles|skills]] are welcomed. Not just programmers, but also [[SME_Server:Volunteering|enthusiasts]] that can help out.
+
To provide SME Server a consistent and a [[The_future_of_SME_Server|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 [[SME_Server_Development_Framework#Development_roles|skills]] are welcomed. Not just programmers, but also [[SME_Server:Volunteering|enthusiasts]] that can help out.
  
 +
Have fun!
  
−
If you are not yet familiar with the SME Server Development we suggest to select the '''more detailed information link''' to the right. Or, If you are a regular visitor, you can jump straight to [[SME_9.0_Development|the current development cycle]]. Have fun!
+
== Current development cycle ==
−
<div class="mw-collapsible mw-collapsed" data-collapsetext="Collapse" data-expandtext="More detailed information">
+
* Current: '''[[SME_9.0_Development|SME Server 9.0]]'''  
 +
* Next:  [[SME_Server_9.1_Development|SME Server 9.1]]
  
 
== Development roles ==
 
== Development roles ==
−
Various roles
+
 
  
 
==== Documentation writers ====
 
==== Documentation writers ====
 +
Skills
 +
* Ability to write user documentation
 +
* Ability to write technical documentation
 +
* Ability to write administration manuals
  
  
−
==== Bughunters & Testers ====
+
==== Troubleshooter ====
−
===== Skils =====
+
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
  
−
==== Junior Programmer ====
+
Backlog
−
===== Skils =====
+
* [[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 ====
 +
Someone who has a fix that they want to contribute, but currently does not want to get involved with CVS and a build system
  
−
==== Normal Programmer ====
+
Skills
−
===== Skils =====
+
* Linux knowledge
  
  
−
==== Senior Programmer ====
+
==== Developer ====
−
===== Skils =====
+
Someone who is able to retrieve our source code from Sourceforge and make local builds to test out their fix.
−
* Perl
+
Note: The actual build system will not be mandated, and several options will be given.
−
* Bash
+
 
 +
Skills
 +
* Linux knowledge
 +
* CVS: able to retrieve the latest source code.
 +
* Patch creation
 +
* Working build system
 +
* Perl / Python / Bash
 
* Regular expressions
 
* Regular expressions
  
  
−
== Development tools ==
+
==== 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
  
−
==== Bugzilla ====
+
== Development tools ==
  
  
Line 42: Line 81:
  
  
−
==== CVS ====
+
==== Bugzilla ====
  
  
−
==== RPM building ====
+
==== CVS ====
  
  
−
==== RPM patching ====
+
==== Patching ====
  
−
== Development process ==
 
−
Generic explanation of the process
 
  
−
</div>
+
==== RPM building ====
  
−
== Current development cycle ==
 
−
Currently '''[[SME_9.0_Development|SME Server 9.0]]''' is under development.
 
  
 +
== 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 [[SME_on_CentOS_6| this one]].
 +
* Stick to the roadmap
  
 
[[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

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

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
Retrieved from "https://wiki.koozali.org/index.php?title=SME_Server_Development_Framework&oldid=23515"