Difference between revisions of "Join Us!"

From ADempiere
Jump to: navigation, search
This Wiki is read-only for reference purposes to avoid broken links.
(Getting started with coding)
(Getting started with usability: Fix link)
 
(10 intermediate revisions by 5 users not shown)
Line 1: Line 1:
==Join the Developers==
+
==Join the Community==
  
There are a lot of ways to get involved in Adempeire development. For example, you could write code, write documentation, find bugs, fix bugs, design logos, draw icons, manage websites or do promotional work. The Adempiere project welcomes anyone who wants to help.
+
There are a lot of ways to get involved in ADempiere development. For example, you could write code, write documentation, find bugs, fix bugs, design logos, draw icons, manage websites or do promotional work. The ADempiere project welcomes anyone who wants to help.
  
If you aren't sure where to start, read below - it provides an overview of the different aspects of Adempeire development, and of the Adempiere development community.
+
If you are not sure where to start, read below, it provides an overview of the different aspects of ADempiere development, and of the ADempiere development community.
  
 
==News and Mail Sources==
 
==News and Mail Sources==
  
The general direction of the Adempiere project is determined by those who do the work - there is no single high level plan for what Adempiere will look like in the future. If you want to find out what is currently happening, then there are a number of sources you might like to consider:
+
The general direction of the ADempiere project is determined by those who do the work (there are no single high level plans for what ADempiere will look like in the future). If you want to find out what is currently happening, then there are a number of sources you might like to consider:
  
'''[[http://sourceforge.net/mail/?group_id=176962 Mailing Lists]]'''
+
'''[http://sourceforge.net/mail/?group_id=176962 Mailing Lists]'''
Probably the best way to find out what's going on in Adempiere development. Archives are available here.
+
Probably the best way to find out what's going on in ADempiere development. Archives are available here.
  
'''[[http://sourceforge.net/mailarchive/forum.php?forum_id=50275 CommitFilter]]'''
+
'''[http://sourceforge.net/mailarchive/forum.php?forum_id=50275 Commit Log]'''
 
Receive notification of SVN commits in areas that interest you.
 
Receive notification of SVN commits in areas that interest you.
 
'''[[Adempiere Commit-Digest]]'''
 
Weekly summary of SVN commits.
 
  
 
'''[[The Dot]]'''
 
'''[[The Dot]]'''
The Adempiere news site.
+
The ADempiere news site.
  
 
==Getting started with coding==
 
==Getting started with coding==
  
Getting started at coding in Adempiere is a matter of finding something to fix, and fixing it. You may want to consult the module overview to help find what you are looking for; once you have fixed something, you will want to send in a patch. If you do that a few times, you may want to apply for an SVN account so you can fix things directly.
+
Getting started at coding in ADempiere is a matter of finding something to fix, and fixing it. You may want to consult the [[Adempiere Developer Corner]] to help find what you are looking for; once you have fixed something, create a patch and upload it to the Adempiere Patch Tracker. If you do that a few times, the [[Commit_Committee]] will consider grant you Commit Access to the source repository.
 
+
*[[Module overview]]
+
*[[Sending patches]]
+
*[[Applying for a Adempiere SVN Account]]
+
*[[First steps with your new SVN account]]
+
 
+
 
+
A more detailed description of the steps above is available in our Programming Guide.
+
Getting started with documentation
+
 
+
Adempiere documentation work is very important, and can always use more developers to write new documentation, review and proofread current documentation, and to do translations and localization.
+
  
For more information on getting started, refer to the Joining the Adempiere Documentation Team reference. There is a wealth of information on the Adempiere Localization web site, including list of the Translation Teams.
+
ADempiere documentation work is very important, and can always use more developers to write new documentation, review and proofread current documentation, and to do translations and localization.
Getting started with usability
+
  
 +
==Getting started with usability==
  
There are a large number of applications within Adempiere, and not all of them have a maintainer dedicated to managing bugs and generally helping out with all the issues associated with turning some working code into a polished application.
+
There are a large number of modules within ADempiere, and not all of them have a maintainer dedicated to managing bugs and generally helping out with all the issues associated with turning some working code into a polished application.
  
If you are interested in helping out with Adempiere, but don't know where to start, becoming a member of the Adempiere Quality Team might appeal to you - see the Quality Team website for more information. Note that you do not need any programming skills to become involved.
+
If you are interested in helping out with ADempiere, but don't know where to start, becoming a member of the ADempiere Quality Team might appeal to you (see [[The QA Process]] for more information). Note that you do not need any programming skills to become involved.
  
Of course, you can become involved in bug hunting without being part of the Adempiere Quality Team - just create yourself an account on the Adempiere bug tracking system, and start searching / sorting through the bugs. Again, you don't have to have programming skills - it helps the programmers enormously just to have a procedure that allows a bug to be consistently reproduced.
+
Of course, you can become involved in bug hunting without being part of the ADempiere Quality Team (just create yourself an sourceforge user account and start searching / sorting through the bugs). Again, you don't have to have programming skills - it helps the programmers enormously just to have a scenario that allows a bug to be consistently reproduced.
Historical Sources
+
[[Category:Developer documentation]]
 +
[[Category:Community]]

Latest revision as of 20:10, 17 June 2010

Join the Community

There are a lot of ways to get involved in ADempiere development. For example, you could write code, write documentation, find bugs, fix bugs, design logos, draw icons, manage websites or do promotional work. The ADempiere project welcomes anyone who wants to help.

If you are not sure where to start, read below, it provides an overview of the different aspects of ADempiere development, and of the ADempiere development community.

News and Mail Sources

The general direction of the ADempiere project is determined by those who do the work (there are no single high level plans for what ADempiere will look like in the future). If you want to find out what is currently happening, then there are a number of sources you might like to consider:

Mailing Lists Probably the best way to find out what's going on in ADempiere development. Archives are available here.

Commit Log Receive notification of SVN commits in areas that interest you.

The Dot The ADempiere news site.

Getting started with coding

Getting started at coding in ADempiere is a matter of finding something to fix, and fixing it. You may want to consult the Adempiere Developer Corner to help find what you are looking for; once you have fixed something, create a patch and upload it to the Adempiere Patch Tracker. If you do that a few times, the Commit_Committee will consider grant you Commit Access to the source repository.

ADempiere documentation work is very important, and can always use more developers to write new documentation, review and proofread current documentation, and to do translations and localization.

Getting started with usability

There are a large number of modules within ADempiere, and not all of them have a maintainer dedicated to managing bugs and generally helping out with all the issues associated with turning some working code into a polished application.

If you are interested in helping out with ADempiere, but don't know where to start, becoming a member of the ADempiere Quality Team might appeal to you (see The QA Process for more information). Note that you do not need any programming skills to become involved.

Of course, you can become involved in bug hunting without being part of the ADempiere Quality Team (just create yourself an sourceforge user account and start searching / sorting through the bugs). Again, you don't have to have programming skills - it helps the programmers enormously just to have a scenario that allows a bug to be consistently reproduced.