RTEMS developers list (rtems-devel)
gedare at rtems.org
Mon Nov 7 17:48:00 UTC 2011
On Sun, Nov 6, 2011 at 4:33 PM, Thomas Doerfler (nt)
<Thomas.Doerfler at imd-systems.de> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> these are a lot of lists for the (relatively) low traffic ;-) But
> nevertheless splitting the "rtems-users" list into two may make sense,
> simply to allow sorting mail traffic into different categories.
> What should not happen is that the RTEMS community is split into
> "users" and "developers". In the past I have seen many people starting
> as "users" step by step became "developers" since they needed new
> functionality for their projects. So we should make sure to encourage
> new users also to register for the "rtems-devel" mailing list.
Great point, and ideally as users become developers they will
naturally migrate to the devel mailing list. As Chris said, anyone who
wants to join the devel list would be welcome to do so.
One point of the devel list is to foster centralized
development-oriented discussions. Right now these discussions happen
on IRC, on the rtems-vc list, within bugzilla, on rtems-users, or by
direct email. We should be having as many of these conversations in
front of as many eyes as possible: For users who are interested in
development discussions and the "bleeding edge" of RTEMS---but cannot
follow the bugzilla, vc list, or IRC---rtems-devel may actually
improve user-developer interactions.
The social ramifications are not entirely clear, but I think that
giving our overlapping communities (the users and developers) their
"own" primary communication path will lower the barrier to entry into
> Am 06.11.2011 21:29, schrieb Chris Johns:
>> Gedare Bloom attended a session on attracting new contributors at
>> the GSoC 2011 summit. One of the outcomes of this session, Gedare
>> and I discussed after, was the need to separate the technically
>> detailed posts from the new user and user posts on the mailing list
>> to help make RTEMS more approachable. A robust technical thread can
>> leave a new user with the perception the list and project is only
>> for those who are fully technically competent and may discourage
>> others from asking questions.
>> To better accommodate all users I would like to put forward the
>> splitting of technical developer email traffic away from the
>> 'rtems-user' list to a new 'rtems-devel' list.
>> Adding a rtems-devel list provides somewhere patches can be posted
>> and discussed before being committed. RTEMS is now adopting a
>> policy of "commit after review" and a developers list can provide a
>> suitable forum for these patches to be discussed, reviewed and
>> RTEMS will have the following:
>> 1. rtems-users: The user list for discussion about using RTEMS,
>> support of RTEMS, possible bugs, and advocacy.
>> 2. rtems-devel: Developers list for those developing RTEMS,
>> submitting patches, design and architectural issues, new projects
>> with in RTEMS.
>> 3. rtems-announce: Announcements related to RTEMS.
>> 4. rtems-vc: The version control commit list.
>> 5. rtems-bugs: A list of bugzilla changes. Bugs are not posted to
>> this list and discussion should be inside the specific bug's
>> 6. rtems-test: RTEMS test results.
>> 7. #rtems: The IRC channel.
>> Chris _______________________________________________ rtems-users
>> mailing list rtems-users at rtems.org
> - --
> - --------------------------------------------
> IMD Ingenieurbuero fuer Microcomputertechnik
> Thomas Doerfler Herbststrasse 8
> D-82178 Puchheim Germany
> email: Thomas.Doerfler at imd-systems.de
> PGP public key available at:
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.14 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> -----END PGP SIGNATURE-----
> rtems-users mailing list
> rtems-users at rtems.org
More information about the users