Changes

{{Languages}}

{{Languages}}

 

===Skills===

===What skills are necessary?===

Any skills are useful for the SME Server project.  

Any skill is useful for the SMESERVER 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. Visit Communicate to learn how to contact us.  

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 -Review or Write Documentation, Manuals, and Articles===

===Documentation===

Documentation for SME Server was inherited from the prior distribution maintainers, e-smith and mitel. Their work gave SME a great base to work from.

Documentation for SME Server was inherited from the prior distribution maintainers, e-smith and mitel. Their work gave SME a great base to work from.

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.

===Bug and New Feature Verification===

===Wiki Team===

You can help improve SMESERVER by finding and reporting bugs. This helps us to make our software as reliable as possible.  

This page is built with MediaWiki. The concept of a Wiki is that anybody may add and modify content. On [[Help:Contents]], find a quick tutorial if you're unfamiliar with wikis.

Our bug tracking system, Bugzilla, is used for all SMESERVER Linux products. If you have never written a bug report, please refer to [[BugzillaHelp]] to learn what kinds of information make the report most useful.  

As long as you edit anything on the wiki you are de facto member of the Wiki Team.  

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 [[BugzillaHelp]] for helping with bug fixing and verification, the best way to learn is to fix other peoples' problems.

To make edits, you need to log in to the wiki. In order to do this, you will need to open an account. The information that SME Server requires for opening an account is very limited and easy to do and can be found [[Help:Contents|here]].

After you log in, you will see a toolbar at the top of the page that is always available. There is a link in the toolbar that is labeled with your username. This takes you to your "personal page". Use this page to introduce yourself and don't be shy. Write a word or two about your interests, especially those related to SME Server and Linux. If nothing else, tell us how you learned about SME Server.

The most obvious way, for programmers, to participate in the development of SMESERVER 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.  

===Bug and New Feature Verification===

 

You can help improve SME Server by finding and reporting bugs. This helps us to make our software as reliable as possible.  

 

===Maintaining existing Languages===

 

For a simple change add the original and the new text to a bug report.

 

 

Obtain an original file that you are going to modify, it will usually be a translation of a panel, eg.

 

make a directory and copy your file there as name.old

make a copy name.new and edit it to suit

from the command line create a patch

diff -u name.old name.new > name.patch

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 [[SME_Server:Documentation:QA:Verification]] for helping with bug fixing and verification, the best way to learn is to fix other peoples' problems.

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....}}

add this to the existing bug or create a new one in Translations

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. WIP: [[Coming on-board]]

To make edits, you need to log in to the wiki. In order to do this, you will need to open an account. The information that SMESERVER requires for opening an account is very limited and easy to do.

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]]}}

After you log in, you will see a toolbar at the top of the page that is always available. There is a link in the toolbar that is labeled with your username. This takes you to your "personal page". Use this page to introduce yourself and don't be shy. Write a word or two about your interests, especially those related to SMESERVER and Linux. If nothing else, tell us how you learned about SMESERVER.  

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]

===Help Other Users===

===Languages===

There is an active community in the forum that help all levels of SMESERVER users. Please have a look at the forum for an overview: http://forums.contribs.org

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. 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.

===Suggest New Features or Software===

===Contribute===

Visit the BUGTRACKER NEW FEATURE RELEASE (NFR) page and add your suggestion:  

There is an active community in the forum that help all levels of SME Server users. Please have a look at the forum for an overview at http://forums.contribs.org

http://bugs.contribs.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&product=SME+Server+Future

Visit the [http://bugs.contribs.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&product=SME+Server+Future New Feature Request (NFR) page in the bug tracker] and add your suggestion.

Only software with an OSI-compliant open-source license will be added to the SMESERVER project.

Only software with an OSI-compliant open-source license will be added to the SME Server project.

----

----

<noinclude>[[Category:Howto]]</noinclude>

<noinclude>[[Category:Howto]][[Category:SME Server]]</noinclude>