Dear Osmocom community,

This topic has been past due for way too many years by now:
A re-organization of our major mailing lists.

I would like to propose the following changes.  Pleas let me know if you
have any comments or feedback.  I'm aware that renaming will mean people
have to update their mail filter rules, but I think we're long past the
point where the names of some of our lists started to confuse users.

== [email protected] ==

* openbsc doesn't exist anymore since OsmoNITB, which is also obsolete
* does already cover anything "Osmocom CNI" related
* Proposed new name: [email protected]


== [email protected] ==

This date back to when GPRS was a highly experimental add-on to our GSM
code base.  This list should simply be merged with openbsc@ as 
[email protected]


== [email protected] ==

Historically was created to cover only the simtrace project.

We should rename this to [email protected] or something
along those lines.  

I would like to suggest it covers

* SIMtrace / SIMtrace2  hardware + firmware
* pySim and related tools for working with SIM/USIM/UICC cards
* any other information / discussion related to SIM/USIM/UICC cards,
  like OTA, ARA-M, ...


== [email protected] ==

This has been a private list for people attending OsmoDevCon

I would like to open up list membership to the general public, and ensure
it also covers the new OsmoDevCall.  We could then have discussions regarding
feedback, topics, scheduling, etc. on that list.

Maybe rename it to [email protected] instead?

To differentiate: [email protected] should remain a
private list related to organizational / administrative topics of those
involved with organizing future events.


== [email protected] ==

Should have been renamed to [email protected] quite some time
ago, I simply forgot about it. My apologies.

-- 
- Harald Welte <[email protected]>            http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)

Reply via email to