GroupsMigration

From Yocto Project
Revision as of 16:09, 18 July 2019 by MichaelHalstead (talk | contribs) (Created page with "he Yocto Project is moving from self-managed Mailman to Groups.io, which provides mailing list services in a simple but modern interface. Groups.io offers all of the capabilit...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

he Yocto Project is moving from self-managed Mailman to Groups.io, which provides mailing list services in a simple but modern interface. Groups.io offers all of the capabilities of our existing Mailman mailing service plus additional community tools that make it an exceptional service solution.


We are planning to migrate your existing mailing list archives and user lists to Groups.io soon. Exact time to be determined.


The migration will include details on subscriber preferences and owner or moderator privileges.


Owners and Moderators: Please be aware pending memberships or posts (and similar pending moderation actions) in Mailman will not be preserved in this migration. We recommend re-checking for any such pending decisions and taking action on them within Mailman one hour prior to the start of the migration window.


During the migration window you will still be able to access the archives, however the delivery of messages sent to the mailing lists during this window will be delayed until after the migration of the archives and list members are complete. We will turn off new list signups during the migration window, then this functionality will be restored once it is complete.


FAQs


What are the key differences between Mailman and Groups.io?


  • Groups.io has a modern interface, robust user security model, and interactive, searchable archives
  • Groups.io provides advanced features including muting threads and integrations with modern tools like GitHub, Slack, and Trello
  • Groups.io also has optional extras like a shared calendar, polling, chat, a wiki, and more
  • Groups.io uses a concept of subgroups, where members first join the project “group” (a master list, normally called "main", in our case called "yocto"), then they choose the specific “subgroup” lists they want to subscribe to


How is the experience different for me as a list moderator or participant?


In many ways, it is very much the same. You will still find the main group at your existing URL and sub-groups equate to the more focused mailing lists based on the community’s needs. The most important change is the domain. We are moving from yoctoproject.org to lists.yoctoproject.org for all list addresses. Here is an example of main group and sub-group URL patterns, and their respective emails:


https://lists.yoctoproject.org/g/yocto


https://lists.yoctoproject.org/g/meta-xilinx


yocto@lists.yoctoproject.org


meta-xilinx@lists.yoctoproject.org


‘’’What if I e-mail the yocto@yoctoproject.org after the migration?’’’


We are adding rules to redirect the e-mail to the new address so it should still be delivered. There will be a delay introduced so we recommend updating your addressbook right away.


Where do I find the settings and owner/moderator tools?


To change settings while in a group or subgroup, left click “Admin” from the side menu.


Then from “Admin” you can select:


“Settings” to change overall settings for a group, including privacy and message policy settings.


“Members” to manage people within a group, including adjusting their role and privileges


“Pending” to view messages pending moderation


If you’d like to learn more about using Groups.io , please reference their help documentation.


Will the migration also impact mailing lists on openembedded.org?


No, at this time , only lists from yoctoproject.org are moved to Groups.io and openembedded.org mailing lists will be moved at a later time.


Who can help in case of issue?


If you are facing any issue or have any questions related to the Groups.io migration, please contact Michael Halstead or Nicolas Dechesne.