Changes

This title can't be asked, it is obtained by a decision or proposal of a '''Jedi''' or '''Yoda''' who believes that you have submitted enough patch to be a serious '''Admiral'''.

This title can't be asked, it is obtained by a decision or proposal of a '''Jedi''' or '''Yoda''' who believes that you have submitted enough patch to be a serious '''Admiral'''.

An '''Admiral''' GIT access, however, must be used to commit translations or bug fixes reported on Savannah (BUG tracker http://savannah.nongnu.org/bugs/?group=dolibarr) or forum (such as personal fixes or fixes submitted by a '''Fighter''').

An '''Admiral''' GIT access, however, must be used to commit translations or bug fixes that are reported on bug tracker ({{TemplateURLBugs}}) or forum (such as personal fixes or fixes submitted by a '''Fighter''').

So all GIT commits you do must necessarily include in the description (the commit log field), the issue of Savannah bug corrected or the title of the forum message indicating the problem. Only a translation escapes this constraint (no restrictions for translations). Failure to observe this constraint may lead to downgrade to the rank of '''Fighter'''.

So all GIT commits you do must necessarily include in the description (the commit log field), the issue of Savannah bug corrected or the title of the forum message indicating the problem. Only a translation escapes this constraint (no restrictions for translations). Failure to observe this constraint may lead to downgrade to the rank of '''Fighter'''.

For submission of new features, an Admiral must necessarily proceed on the principle of patches sent to the ML.

For submission of new features, an Admiral must necessarily proceed on the principle of patches sent to the ML.