README.md: add Community section
authorPhilippe Proulx <eeppeliteloop@gmail.com>
Wed, 23 Mar 2016 16:40:29 +0000 (12:40 -0400)
committerPhilippe Proulx <eeppeliteloop@gmail.com>
Wed, 23 Mar 2016 16:40:29 +0000 (12:40 -0400)
Signed-off-by: Philippe Proulx <eeppeliteloop@gmail.com>
README.md

index 16142ebfbe644972d902ff34e60a73295a93f957..29d07a90ed8fd2d16945890baefda5e5e8d29d6a 100644 (file)
--- a/README.md
+++ b/README.md
@@ -165,3 +165,20 @@ You can specify [Bats](https://github.com/sstephenson/bats) options to
 output.
 
 You can exit the virtual environment by running `deactivate`.
+
+
+## Community
+
+Since the barectf community is small, it's sharing the communication
+channels of the [LTTng](http://lttng.org/) project,
+as [EfficiOS](http://www.efficios.com/) is the main sponsor of both
+projects. It goes like this:
+
+| Item | Location | Notes |
+| --- | --- | --- |
+| Mailing list | [lttng-dev](https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev) (`lttng-dev@lists.lttng.org`) | Preferably, use the `[barectf]` subject prefix |
+| IRC | [`#lttng`](irc://irc.oftc.net/lttng) on the OFTC network | More specifically, query `eepp` (barectf's maintainer) on this network or on freenode |
+| Code contribution | Create a new GitHub [pull request](https://github.com/efficios/barectf/pulls) | |
+| Bug reporting | Create a new GitHub [issue](https://github.com/efficios/barectf/issues/new) | |
+| Continuous integration | [barectf item on LTTng's CI](https://ci.lttng.org/job/barectf/) | |
+| Blog | The [LTTng blog](http://lttng.org/blog/) contains many posts about barectf | |
This page took 0.024763 seconds and 4 git commands to generate.