Repository : ssh://git@open-mesh.org/doc
On branches: backup-redmine/2017-07-13,master
commit 19bc5bd73c7401d978e723f372bf68a0449c363b Author: Sven Eckelmann sven@narfation.org Date: Thu Mar 17 22:43:40 2011 +0000
doc: open-mesh/Contribute: Remove information regarding bmx
19bc5bd73c7401d978e723f372bf68a0449c363b open-mesh/Contribute.textile | 91 +++++++++++++++++++++++++------------------- 1 file changed, 52 insertions(+), 39 deletions(-)
diff --git a/open-mesh/Contribute.textile b/open-mesh/Contribute.textile index 0eb56988..ca8a0b5e 100644 --- a/open-mesh/Contribute.textile +++ b/open-mesh/Contribute.textile @@ -1,66 +1,79 @@ -= How to Contribute =
-{{{ -#!div style="width: 46em; text-align: justify" +h1. How to Contribute
-Thanks 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]. + +<pre> +<code class="div"> + +Thanks 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 [[MailingList|Mailing List] You can always contact us via [wikiIRC IRC]].
If you like this project and you want to take part and/or give something back, here is a short list of starting points:
-=== Reporting Bugs ===
-If you find a bug, please see if the problem is already known in the by [https://dev.open-mesh.org/batman/report Reading the Tickets]. [[BR]] -If not, please [https://dev.open-mesh.org/batman/newticket add a new Ticket]. +h3. Reporting Bugs + + +If you find a bug, please see if the problem is already known in the by "Reading the Tickets":https://dev.open-mesh.org/batman/report. + +If not, please "add a new Ticket":https://dev.open-mesh.org/batman/newticket.
Please add as much information as possible. In particular interesting are:
- * Which branch (batman, bmx, batman-advanced) - * Which version (0.X, SVN/git revision number) - * kernel version, distribution (and version) - * machine type (PC, Linksys WRT, Fon, NS2, ...) - * command line parameters used - * iptables/firewall rules - * [wiki:Coredump get a coredump] if you experience a segfault - * your guess what triggered the problem. ;) +* Which branch (batman, batctl, batman-adv) +* Which version (0.X, SVN/git revision number) +* kernel version, distribution (and version) +* machine type (PC, Linksys WRT, Fon, NS2, ...) +* command line parameters used +* iptables/firewall rules +* [[Coredump|get a coredump]] if you experience a segfault +* your guess what triggered the problem. ;) + + +h3. Documentation / Feedback
-=== Documentation / Feedback ===
Write 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: - * How did you find us ? - * How does you setup look like ? - * Where are you building your mesh ? - * What problems did you encounter ? - * How did you debug / solve them ? - * What did you like / not like ? - * How can B.A.T.M.A.N. improve ? +* How did you find us ? +* How does you setup look like ? +* Where are you building your mesh ? +* What problems did you encounter ? +* How did you debug / solve them ? +* What did you like / not like ? +* How can B.A.T.M.A.N. improve ?
There'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.
-=== Research === + +h3. Research +
B.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.
-=== Development ===
-You 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. +h3. Development + + +You 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 [[MailingList|mailing list]] to get integrated. We also hand out SVN/git access to people that want to get involved. + + +h3. Submitting patches
-=== Submitting patches ===
If you intend to send us patches, please consider the following guidelines:
- * Prefer small & digestible over long "all in one" patches. - * No MIME, no links, no compression, no attachments. Just plain text (patches are to be sent inline). - * Patches sent to the mailing list should include "PATCH" in the subject to make it easier to distinguish between patches and discussions. - * 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.org/timeline timeline] for more examples. - * Add a "Signed-off-by: Your Name !you@example.com" line to the patch message to make the ownership of the patch clear. - * 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). - * Patches must be against trunk and have an additional prefix before the actual project subdirectory. It must be possible to apply those patches on top of a checkout of the svn trunk directory using {{{patch -p1 -i $PATCH}}} - * Patches against the batman-adv master branch must be formated using -{{{ +* Prefer small & digestible over long "all in one" patches. +* No MIME, no links, no compression, no attachments. Just plain text (patches are to be sent inline). +* Patches sent to the mailing list should include "PATCH" in the subject to make it easier to distinguish between patches and discussions. +* 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 "timeline":http://www.open-mesh.org/timeline for more examples. +* Add a "Signed-off-by: Your Name !you@example.com" line to the patch message to make the ownership of the patch clear. +* 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). +<pre> +* Patches against the batman-adv master branch must be formated using +<pre> git format-patch -M --patience --src-prefix=a/batman-adv/ --dst-prefix=b/batman-adv/ $BASECOMMIT -}}} - * An exemplary good submission you may want to look at can be found here: https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2009-December/002033.html +</code></pre> +* An exemplary good submission you may want to look at can be found here: https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2009-December/002033.html
-}}} +</code></pre>