Notice: We have migrated to GitLab launching 2024-05-01 see here: https://gitlab.rtems.org/

Changes between Version 40 and Version 41 of RTEMSMailingLists


Ignore:
Timestamp:
07/05/17 00:39:45 (7 years ago)
Author:
Chris Johns
Comment:

Clean up the page.

Legend:

Unmodified
Added
Removed
Modified

  • RTEMSMailingLists

    v40 v41  
    1 = RTEMSMailingLists =
     1= RTEMS Mailing Lists =
    22
    3 
    4 
    5 [[TOC(TBR/Website/RTEMSMailingLists, depth=2)]]
     3[[TOC(RTEMSMailingLists, depth=2)]]
    64
    75
    86The RTEMS Project has a number of public mailing lists whose archives are fully searchable. This lists are divided into active user based lists and results and monitoring lists for archiving.  All lists are public and a complete record of all postings is maintained.
    9 = Primary RTEMS Mailing Lists =
    107
    11  *  RTEMS Users ([mailto:users@rtems.org users@rtems.org]) is the source of assistance about using RTEMS. ([http://lists.rtems.org/mailman/listinfo/users subscribe]) ([http://lists.rtems.org/pipermail/users archives])
    12   * The RTEMS Users list is for users of RTEMS. Post questions about using and setting up tools, configuring RTEMS, BSP options and configuration or supported BSPs, questions about using the APIs, and any issues you may be having. RTEMS is a technical package so traffic on this list ranges from those who are new to embedded systems, real-time software or open source projects to technial users with many years of experience. The technical content level can vary. If you are a new user and want to ask a general question please ask on this list. If you are not sure which list to post please ask.
    13  *  RTEMS Developers ([mailto:devel@rtems.org devel@rtems.org]) is about the development of RTEMS. Send patches here. ([http://lists.rtems.org/mailman/listinfo/devel subscribe]) ([http://lists.rtems.org/mailman/listinfo/devel archives])
    14   *  The RTEMS Developers list is about developing RTEMS. It is about the implementation of RTEMS and covers a wide range of technical issues as well as directional issues relating to the way the project develops, maintains and releases RTEMS. This lists covers the maintenance of the tools RTEMS uses, new Board Support Packages, new features, and technical implementation details for third party packages bundled with RTEMS. It is technical. The list also accepts patches to RTEMS. If you have patches please send them to this list. It is the main point of view. Any responses to posts to the Version Control (rtems-vc@rtems.org) or Bugs (rtems-bugs@rtems.org) lists should be posted to this list as those lists are blocked to posting.
    15 = Policies =
     8== Primary RTEMS Mailing Lists ==
    169
     10*  RTEMS Users ([mailto:users@rtems.org users@rtems.org]) is the source of assistance about using RTEMS. ([http://lists.rtems.org/mailman/listinfo/users subscribe]) ([http://lists.rtems.org/pipermail/users archives])
    1711
    18  *  When posting messages, please try to avoid cross posting a message to several lists. 
     12* The RTEMS Users list is for users of RTEMS. Post questions about using and setting up tools, configuring RTEMS, BSP options and configuration or supported BSPs, questions about using the APIs, and any issues you may be having. RTEMS is a technical package so traffic on this list ranges from those who are new to embedded systems, real-time software or open source projects to technial users with many years of experience. The technical content level can vary. If you are a new user and want to ask a general question please ask on this list. If you are not sure which list to post please ask.
    1913
    20  *  Please refrain from sending messages in HTML, RTF or similar formats.
     14* RTEMS Developers ([mailto:devel@rtems.org devel@rtems.org]) is about the development of RTEMS. Send patches here. ([http://lists.rtems.org/mailman/listinfo/devel subscribe]) ([http://lists.rtems.org/mailman/listinfo/devel archives])
    2115
    22  *  Please avoid using a mail client that automatically appends content to your messages, such as sponsored advertisements, disclaimers, etc.
     16* The RTEMS Developers list is about developing RTEMS. It is about the implementation of RTEMS and covers a wide range of technical issues as well as directional issues relating to the way the project develops, maintains and releases RTEMS. This lists covers the maintenance of the tools RTEMS uses, new Board Support Packages, new features, and technical implementation details for third party packages bundled with RTEMS. It is technical. The list also accepts patches to RTEMS. If you have patches please send them to this list. It is the main point of view. Any responses to posts to the Version Control (rtems-vc@rtems.org) or Bugs (rtems-bugs@rtems.org) lists should be posted to this list as those lists are blocked to posting.
    2317
    24  *  These are public lists and have a varied range of users. Please be polite, constructive and respecting of other members of the list.
     18== Policies ==
    2519
    26  *  Please do not include or reference confidentiality notices, like:
     20*  When posting messages, please try to avoid cross posting a message to several lists. 
    2721
     22*  Please refrain from sending messages in HTML, RTF or similar formats.
     23
     24*  Please avoid using a mail client that automatically appends content to your messages, such as sponsored advertisements, disclaimers, etc.
     25
     26*  These are public lists and have a varied range of users. Please be polite, constructive and respecting of other members of the list.
     27
     28*  Please do not include or reference confidentiality notices, like:
    2829
    2930{{{
    30 The referring document contains privileged and confidential information. If you are not the intended recipient you must not disseminate, copy or take any action in reliance on it, and we request that you notify company_name immediately.
     31The referring document contains privileged and confidential information.
     32If you are not the intended recipient you must not disseminate, copy or take
     33any action in reliance on it, and we request that you notify 'company_name'
     34immediately.
    3135}}}
    32 
    3336
    3437Such disclaimers are inappropriate for mail sent to public lists. You have knowingly submitted your post to a public list which is sent to hundreds or thousands or users and archived on multiple servers around the world.  You have assumed that your unsolicited request should be honored by people who did not agree to it explicitly.  Worst of all, you expect someone to answer your supposedly confidential request.  Overall, it is quite absurd for the paragraph to even be put on email. 
    3538
    36 If your company automatically adds something like this to outgoing mail, and you can't convince them to stop, you might consider using a free web-based e-mail account.
    37 
    38  *  Notices like this:
     39If your company automatically adds something like this to outgoing mail, and you can't convince them to stop, you might consider using a free web-based e-mail account. Notices like this:
    3940
    4041{{{
    41 Any views expressed in this message are those of the individual sender, except where they are specifically stated to be the views of companyname.
     42Any views expressed in this message are those of the individual sender,
     43except where they are specifically stated to be the views of 'company_name'.
    4244}}}
    4345
     46are acceptable, although they are redundant; unless explicitly stated, it's assumed that no-one on these lists means to speak for their company.
    4447
    45 are acceptable, although they are redundant; unless explicitly stated, it's assumed that no-one on these lists means to speak for their company.
    46 = Posting from multiple accounts =
     48== Posting from multiple accounts ==
    4749
    4850If you like to post to a mailing list from more than one account, but only want to receive email to one account, you can subscribe to the list then send an email to:
    4951
    50 users-request@rtems.org with the body 'set delivery off'. (Or similarly for devel-request@rtems.org)
     52users-request@rtems.org with the body `set delivery off`. (Or similarly for devel-request@rtems.org)
    5153
    52 This will keep you subscribed so you can post but disable mail delivery. You can do 'set delivery on' to re-enable.
     54This will keep you subscribed so you can post but disable mail delivery. You can do `set delivery on` to re-enable.
    5355
    54 Alternatively you can subscribe, log into the mailman console at lists.rtems.org and set 'Mail Delivery' to 'Disabled'.
    55 = Other RTEMS Mailing Lists =
     56Alternatively you can subscribe, log into the mailman console at lists.rtems.org and set `Mail Delivery` to `Disabled`.
    5657
     58== Other RTEMS Mailing Lists ==
    5759
    58  *  [http://lists.rtems.org/mailman/listinfo/announce RTEMS Announce] is a read-only low volume list where we post announcements about releases or other important events.
    59   *  Mail List Archive: http://lists.rtems.org/pipermail/announce
    60   *  Subscription Page: http://lists.rtems.org/mailman/listinfo/announce
     60*  [http://lists.rtems.org/mailman/listinfo/announce RTEMS Announce] is a read-only low volume list where we post announcements about releases or other important events.
     61*  Mail List Archive: http://lists.rtems.org/pipermail/announce
     62*  Subscription Page: http://lists.rtems.org/mailman/listinfo/announce
    6163
    62  *  [http://lists.rtems.org/mailman/listinfo/bugs RTEMS Bugs] is a read-only list of all bug database changes posted. Discussion about a bug takes place within the bug tool or on the developers list.
    63   *  Mail List Archive: http://lists.rtems.org/pipermail/bugs
    64   *  Subscription Page: http://lists.rtems.org/mailman/listinfo/bugs
     64*  [http://lists.rtems.org/mailman/listinfo/bugs RTEMS Bugs] is a read-only list of all bug database changes posted. Discussion about a bug takes place within the bug tool or on the developers list.
     65*  Mail List Archive: http://lists.rtems.org/pipermail/bugs
     66*  Subscription Page: http://lists.rtems.org/mailman/listinfo/bugs
    6567
    66  *  [http://lists.rtems.org/mailman/listinfo/build RTEMS Build Logs] is a list where RTEMS build logs are posted.  This feature is not active yet, but hopefully is coming soon.
    67   *  Mail List Archive: http://lists.rtems.org/pipermail/build
    68   *  Subscription Page: http://lists.rtems.org/mailman/listinfo/build
     68*  [http://lists.rtems.org/mailman/listinfo/build RTEMS Build Logs] is a list where RTEMS build logs are posted.  This feature is not active yet, but hopefully is coming soon.
     69*  Mail List Archive: http://lists.rtems.org/pipermail/build
     70*  Subscription Page: http://lists.rtems.org/mailman/listinfo/build
    6971
    70  *  [http://lists.rtems.org/mailman/listinfo/vc RTEMS Version Control] is a read-only list and has all changes to the RTEMS Version Control system posted. Discussion about changes takes place on the developers list.
    71   *  Mail List Archive: http://lists.rtems.org/pipermail/vc
    72   *  Subscription Page: http://lists.rtems.org/mailman/listinfo/vc
     72*  [http://lists.rtems.org/mailman/listinfo/vc RTEMS Version Control] is a read-only list and has all changes to the RTEMS Version Control system posted. Discussion about changes takes place on the developers list.
     73*  Mail List Archive: http://lists.rtems.org/pipermail/vc
     74*  Subscription Page: http://lists.rtems.org/mailman/listinfo/vc