Changes between Version 12 and Version 13 of Contribute

Show
Ignore:
Timestamp:
06/21/10 12:24:35 (3 months ago)
Author:
marek (IP: 82.247.12.166)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Contribute

    v12 v13  
     1 
    12= How to Contribute = 
    2 Thanks for using B.A.T.M.A.N.! If you have suggestions, comments, want to tell us [[BR]] 
    3 about your experiences or discuss problems the best thing is always to use the [[BR]] 
    4 [wiki:MailingList Mailing List]. You can always contact us via [wiki:IRC IRC]. 
    53 
    6 If you like this project and you want to take part and/or give something back, [[BR]] 
    7 here is a short list of starting points: 
     4{{{ 
     5#!div style="width: 46em; text-align: justify" 
     6 
     7Thanks for using B.A.T.M.A.N.! If you have suggestions, comments, want to tell us about your experiences or discuss problems the best thing is always to use the [wiki:MailingList Mailing List]. You can always contact us via [wiki:IRC IRC]. 
     8 
     9If you like this project and you want to take part and/or give something back, here is a short list of starting points: 
    810 
    911 
    1012=== Reporting Bugs === 
     13 
    1114If you find a bug, please see if the problem is already known in the by [https://dev.open-mesh.net/batman/report Reading the Tickets]. [[BR]] 
    1215If not, please [https://dev.open-mesh.net/batman/newticket add a new Ticket]. 
    … …  
    1518 
    1619 * Which branch (batman, bmx, batman-advanced) 
    17  * Which version (0.X, SVN revision number) 
     20 * Which version (0.X, SVN/git revision number) 
    1821 * kernel version, distribution (and version) 
    1922 * machine type (PC, Linksys WRT, Fon, NS2, ...) 
    … …  
    2528=== Documentation / Feedback === 
    2629 
    27 Write an article about your experience with B.A.T.M.A.N. and have it published here or ask [[BR]] 
    28 us to link to your site: 
     30Write an article about your experience with B.A.T.M.A.N. and have it published here or ask us to link to your site: 
    2931 * How did you find us ? 
    3032 * How does you setup look like ? 
    … …  
    3537 * How can B.A.T.M.A.N. improve ? 
    3638 
    37 There's lots of people that want to know about B.A.T.M.A.N. - help us to spread the word! [[BR]] 
    38 We also hand out direct wiki access to those that are interested. Please ask on our  [[BR]] 
    39 [wiki:MailingList mailing list] for the accounts. 
     39There's lots of people that want to know about B.A.T.M.A.N. - help us to spread the word! You also can create a wiki account and improve the documentation. 
    4040 
    4141=== Research === 
    4242 
    43 B.A.T.M.A.N. gives much room for research, especially the layer 2 implementation in the [[BR]] 
    44 kernel. Get in touch with us to share your ideas. If you write papers we are happy to [[BR]] 
    45 publish them here or link to your page. If you are looking for the right topic or [[BR]] 
    46 mentorship feel free to contact us. We have more ideas than time to implement them. 
     43B.A.T.M.A.N. gives much room for research, especially the layer 2 implementation in the kernel. Get in touch with us to share your ideas. If you write papers we are happy to publish them here or link to your page. If you are looking for the right topic or mentorship feel free to contact us. We have more ideas than time to implement them. 
    4744 
    4845=== Development === 
    4946 
    50 You looked in the code ? Fixed bugs ? Added a cool new function ? Integrated B.A.T.M.A.N.[[BR]] 
    51 in a distribution ? Don't hesitate to let us and others know! We can avoid duplicated [[BR]] 
    52 work by publishing it here or linking to your page. Patches are always welcome and can [[BR]] 
    53 be posted on the [wiki:MailingList mailing list] to get integrated. We also hand out SVN [[BR]] 
    54 access to people that want to get involved. 
     47You looked in the code ? Fixed bugs ? Added a cool new function ? Integrated B.A.T.M.A.N. in a distribution ? Don't hesitate to let us and others know! We can avoid duplicated work by publishing it here or linking to your page. Patches are always welcome and can be posted on the [wiki:MailingList mailing list] to get integrated. We also hand out SVN/git access to people that want to get involved. 
    5548 
    5649=== Submitting patches === 
    … …  
    5952 
    6053 * Prefer small & digestible over long "all in one" patches. 
    61  * No MIME, no links, no compression, no attachments.  Just plain text. 
    62  * Patches sent to the mailing list should include "PATCH" in the subject to make[[BR]] 
    63    it easier to distinguish between patches and discussions. 
    64  * The mail's subject will become the first line in the commit message. The body [[BR]] 
    65    contains the longer patch description and the patch (unified format) itself. [[BR]] 
    66    Please also specify the target branch (e.g. batctl, batman-adv, etc) at the [[BR]] 
    67    beginning of the subject line. See the [http://www.open-mesh.net/timeline timeline] for more examples. 
    68  * Add a "Signed-off-by: Your Name <!you@example.com>" line to the patch [[BR]] 
    69    message to make the ownership of the patch clear. 
    70  * Patches for B.A.T.M.A.N. Advanced need to follow the linux kernel coding style[[BR]] 
    71    closely (use checkpatch.pl to verify your patch) as well as the linux "how to [[BR]] 
    72    submit patches" guidelines (search for the term !SubmitPatches to find thorough[[BR]] 
    73    documentation). 
    74  * An exemplary good submission you may want to look at can be found here:[[BR]] 
    75    https://lists.open-mesh.net/pipermail/b.a.t.m.a.n/2009-December/002033.html 
     54 * No MIME, no links, no compression, no attachments.  Just plain text (patches are to be sent inline). 
     55 * Patches sent to the mailing list should include "PATCH" in the subject to make it easier to distinguish between patches and discussions. 
     56 * The mail's subject will become the first line in the commit message. The body contains the longer patch description and the patch (unified format) itself. Please also specify the target branch (e.g. batctl, batman-adv, etc) at the beginning of the subject line. See the [http://www.open-mesh.net/timeline timeline] for more examples. 
     57 * Add a "Signed-off-by: Your Name <!you@example.com>" line to the patch message to make the ownership of the patch clear. 
     58 * Patches for B.A.T.M.A.N. Advanced need to follow the linux kernel coding style closely (use checkpatch.pl to verify your patch) as well as the linux "how to submit patches" guidelines (search for the term !SubmitPatches to find thorough documentation). 
     59 * An exemplary good submission you may want to look at can be found here: https://lists.open-mesh.net/pipermail/b.a.t.m.a.n/2009-December/002033.html 
    7660 
     61}}} 
     62