ontolog-invitation
[Top] [All Lists]

[ontolog-invitation] Ontolog-invitation Google Group - your action neede

To: ontolog-invitation@xxxxxxxxxxxxxxxx
Cc: ontolog-invitation@xxxxxxxxxxxxxxxx
From: Amanda Vizedom <amanda.vizedom@xxxxxxxxx>
Date: Sat, 26 Dec 2015 13:16:58 -0500
Message-id: <CAEmngXsDNnTTMkTfsHEQsFqyCPzsWmeFPO7M51LgQduoU=R5pw@xxxxxxxxxxxxxx>
Dear Colleague,

You are receiving this message because you are a current subscriber to the ontolog-invitation@xxxxxxxxxxxxxxxx. This list is moving from cim3 hosting to a Google Group, in light of Peter Yim's retirement and the cessation of cim3.net services. 

In order to continue receiving invitations and announcements from ontolog-invitation, without interruption, please go to https://groups.google.com/forum/#!forum/ontolog-invitation
and join the group. 

You will be subscribed immediately; no administrator approval is required. 

Should you wish to post to the group, now or in the future, contact the group administrators and request "contributor" status (posting permission). 

If you do not have web access to Google Groups, please reply to me off-list and I will add you directly. 

For those who have experienced the migration of other Ontolog lists and may be wondering about the differences, some explanation appears under the dashed line below.  

Thank you for your patience and cooperation.

Best Regards,
Amanda Vizedom
(on behalf of the Ontolog Board of Trustees and 
ontolog-invitation administrators)

----------------

Why ontolog-invitation migration differs from that of other Ontolog groups: 

Ontolog-invitation is intended to support dissemination of event invitations and announcements, not only to Ontolog's primary membership, but also to a broader community of interested parties. This purpose has been best served by limiting ontolog-invitation content to the sharing of such announcements (in contrast to other Ontolog groups, where discussion is encouraged). 

Correspondingly, ontolog-invitation has a substantially larger subscriber base than do other Ontolog community lists. Most subscribers use ontolog-invitation as a means of receiving announcements of interest. A small percentage of subscribers also post such messages. 

Posting permission needs some gatekeeping, in order to continue ontolog-invitation as a low-volume, spam-free group.  Since all of our content is public, no such control is needed over the receiving of messages. Thus, for ontolog-invitation, it makes sense to distinguish posting members from general members and to exercise some control over the former while opening the doors widely to the latter.

Finally, the size of Ontolog-invitation's subscriber base is such that it would take several months for group administrators to directly add all members, given the daily limit on such additions to free groups. Thus, it helps greatly if members can (and do) join the group themselves.

The above considerations lead to a different optimal configuration: 
- anyone may join, without the need for action by administrators
- only contributors (members who have "contributor" status) may post
- any member may request "contributor" status; a group administrator must approve and make the change
- subscribers to the old list are requested to add themselves to the new group

After some reasonable response period, we will resume direct-adding current subscribers who have not joined themselves. However, given the size of the subscriber base and the daily-add limits, messages are certain to be missed before any given member can be added in this way. Current subscribers are, therefore, strongly encouraged to take the initiative and add themselves to the group.  


_________________________________________________________________
Join this list: mailto:ontolog-invitation-join@xxxxxxxxxxxxxxxx
Leave this list: mailto:ontolog-invitation-leave@xxxxxxxxxxxxxxxx
Msg Archives: http://ontolog.cim3.net/forum/ontolog-invitation/  
Community Wiki: http://ontolog.cim3.net/wiki/ 
Community Portal: http://ontolog.cim3.net/     (01)
<Prev in Thread] Current Thread [Next in Thread>