Changes

From SME Server
Jump to navigationJump to search
1,290 bytes added ,  21:59, 15 February 2013
no edit summary
Line 1: Line 1:  
{{Languages}}
 
{{Languages}}
 +
 
===Why do we need volunteers?===
 
===Why do we need volunteers?===
 
For all kind of things! For one SME Server is a product made and maintained by people dedicating spare time and resources to create a secure and robust Small Enterprise server.  
 
For all kind of things! For one SME Server is a product made and maintained by people dedicating spare time and resources to create a secure and robust Small Enterprise server.  
    
===Skills===
 
===Skills===
Any skill is useful for the SME Server project.  
+
Any skill are useful for the SME Server project.  
    
If you are a developer of any kind, we will find something for you to do.  
 
If you are a developer of any kind, we will find something for you to do.  
Even if you think that you have no Linux skills you can still help. You can tell us if and how you understand the wiki pages, or more precisely, we would like to know what pages you don't understand. Thanks to the insights of new users we can continuously enhance readability of the wiki. Please add remark to the discussion tabs of the page.
+
Even if you think that you have no Linux skills you can still help. You can tell us if and how you understand the wiki pages, or more precisely, we would like to know what pages you don't understand. Thanks to the insights of new users we can continuously enhance readability of the wiki. Please add remarks to the discussion tabs of the page you are concerned with.
   −
If, on a top of that, you can write, you are invaluable. We need a lot of articles. There are thousands of Linux programs around, and more are released every day. In addition, new versions of existing applications are released. There is need for a lot of hands to write about them and to keep reviews current.  
+
If, on top of that, you can write, you are invaluable. We need a lot of articles. There are thousands of Linux programs around, and more are released every day. In addition, new versions of existing applications are released. There is a need for a lot of hands to write about them and to keep reviews current.
    
===Documentation===
 
===Documentation===
Line 16: Line 17:  
The current developers have continued to improve the SME Server software and to reflect these improvements the Documentation has to develop too. These wiki-based manuals have been put in place to allow anyone to update or add new sections where they see fit.
 
The current developers have continued to improve the SME Server software and to reflect these improvements the Documentation has to develop too. These wiki-based manuals have been put in place to allow anyone to update or add new sections where they see fit.
   −
The core manuals have been protected for stability, but anyone can request access to add and update howto and contrib pages to the wiki. If you've got instructions, solutions to common problems, neat tips and tricks, or just a good way to explain something, we'd love to hear from you.  
+
The core manuals have been protected for stability, but anyone can request access to add and update howto and contrib pages to the wiki. If you've got instructions, solutions to common problems, neat tips and tricks, or just a good way to explain something, we'd love to hear from you.
 +
You may want to join our [http://lists.contribs.org/mailman/listinfo/docteam Document mailing lists] to discuss your plans and coordinate with other Docteam members.
    
===Wiki Team===
 
===Wiki Team===
Line 31: Line 33:     
Our [http://bugs.contribs.org bug tracking system], [http://ww.bugzilla.org Bugzilla], is used for all SME Server Linux products. If you have never written a bug report, please refer to [[Bugzilla Help]] to learn what kinds of information make the report most useful.  
 
Our [http://bugs.contribs.org bug tracking system], [http://ww.bugzilla.org Bugzilla], is used for all SME Server Linux products. If you have never written a bug report, please refer to [[Bugzilla Help]] to learn what kinds of information make the report most useful.  
   
Your role in that is to report possible bugs only via the bug tracker, and to encourage others to do the same. Refer again to [[Bugzilla Help]] for helping with bug fixing and verification, the best way to learn is to fix other peoples' problems.
 
Your role in that is to report possible bugs only via the bug tracker, and to encourage others to do the same. Refer again to [[Bugzilla Help]] for helping with bug fixing and verification, the best way to learn is to fix other peoples' problems.
{{tip box|For an easier way to see new bug or new activity you can look at [[Bugzilla_Reports]] }}
+
{{tip box|For an easier way to see new bug or new activity you can look at [[Bugzilla_Reports]]  
 +
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....}}
    
===Programming===
 
===Programming===
The most obvious way, for programmers, to participate in the development of SME Server is to post a patch as a suggested solution to an existing bug in Bugzilla. Each package has a maintainer, who will contact you to discuss your proposed solution. You may want to join our development mailing lists before you start coding in order to discuss your plans and coordinate with other developers.  
+
The most obvious way, for programmers, to participate in the development of SME Server is to post a patch as a suggested solution to an existing bug in Bugzilla. Each package has a maintainer, who will contact you to discuss your proposed solution. You may want to join our [http://lists.contribs.org/mailman/listinfo/devinfo development mailing lists] before you start coding in order to discuss your plans and coordinate with other developers.  
    
For more information about getting source code and building your own packages, read the [[SME Server:Documentation:Developers Manual]].  
 
For more information about getting source code and building your own packages, read the [[SME Server:Documentation:Developers Manual]].  
 +
{{tip box|If you would like to '''help or to learn''' about SME Server 9 you should look at [[SME_Server_9.0_Development]] or the [http://wiki.contribs.org/Category:SME9-Development Category:SME9-Development]
 +
An overview of available roles is visible on [[SME_Server_Development_Framework]]}}
   −
If you would like to build your own applications on SME Server, read the [[SME Server:Documentation:Developers Manual]] to learn how to package your own software.
+
===Mailing Lists===
 +
The communication among different teams go through a software called Mailman for which you choose the relevant list that interest you.
 +
All messages will be received in your email box, you will only respond to the email address of the mailling (ie devinfo@contribs.org for example) that your mail is sent to all registered users on the list .
 +
you can choose your [http://lists.contribs.org/mailman/listinfo/ Mailing Lists]
    
===Languages===
 
===Languages===
 
A new system translation interface has been installed to facilitate translations of SME Server core packages as well as SME Server contribs, for more information have a look at the [[Translations]] page.
 
A new system translation interface has been installed to facilitate translations of SME Server core packages as well as SME Server contribs, for more information have a look at the [[Translations]] page.
The translation framework is located at http://translate.contribs.org.
+
The translation framework is located at http://translate.contribs.org. You may want to join our [http://lists.contribs.org/mailman/listinfo/translations Translation mailing lists] before you start your work and coordinate with other people.
    
===Donations===
 
===Donations===

Navigation menu