RTEMS developers list (rtems-devel)

[Thomas Doerfler (nt)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

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.

wkr,

Thomas.



Am 06.11.2011 21:29, schrieb Chris Johns:
> Hello,
> 
> 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
> accepted.
> 
> 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 
> thread.
> 
> 6. rtems-test: RTEMS test results.
> 
> 7. #rtems: The IRC channel.
> 
> Comments.
> 
> Chris _______________________________________________ rtems-users
> mailing list rtems-users at rtems.org 
> http://www.rtems.org/mailman/listinfo/rtems-users


- -- 
- --------------------------------------------
IMD Ingenieurbuero fuer Microcomputertechnik
Thomas Doerfler           Herbststrasse 8
D-82178 Puchheim          Germany
email:    Thomas.Doerfler at imd-systems.de
PGP public key available at:
     http://www.imd-systems.de/pgpkey_en.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk62/TsACgkQwHyg4bDtfjRVFACfYq/ZbuBXzn/V+4rdFylZJjFk
Ma0AniIqjI3Ju93EalPY8Ajy1fxjD696
=THJ8
-----END PGP SIGNATURE-----