From bef1082673c050eaa3a6b459d1a6d4e2711d859b Mon Sep 17 00:00:00 2001 From: Lorenzo Torres Date: Thu, 27 Mar 2025 19:45:11 +0100 Subject: base code --- content/development.md | 45 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 45 insertions(+) create mode 100644 content/development.md (limited to 'content/development.md') diff --git a/content/development.md b/content/development.md new file mode 100644 index 0000000..9b02f7b --- /dev/null +++ b/content/development.md @@ -0,0 +1,45 @@ + + +# Development + +Sideros development is email-driven, as contributions, discussions and logs all take place on specific automated mailing lists. + +## Mailing lists + +Mailing lists are automated, to subscribe just send an email to +``` +list-name at lists.sideros.org +``` +putting `subscribe` in the mail body. +Please note that some clients usually send emails with html by default, you should ensure to send plain-text emails instead, otherwise commands will not be parsed correctly. + + +Here is a list of the development related mailing lists: + + + + + + + + + + + + +
List nameDescription
patchSend git patch files, see Contributing for more info.
git(Read-only) commit logs are automatically sent here.
+ +## Contributing + +Documentation for contributors is available in the source tree, under the [`documentation/`](https://git.sideros.org/sideros/tree/documentation) directory. Once you got a modification you want to send, create a commit using git and generate a patch file with the following command: +``` +$ git format-patch -M origin/master +``` +and when you have the patch file send it to the `patch` mailing list, possibly using `git send-email` like this: +``` +$ git send-email *.patch +``` + +## Bugs + +We use [Bugzilla](https://bugs.sideros.org) to track issues and feature requests. You can create an account there and subscribe to specific bugs to get emails with updates. -- cgit v1.2.3