Mailman to Discourse migration
ChristianKuehnel opened this issue · 12 comments
This epic will track the issues around the Mailman to Discourse migration:
- Agree and merge #45 First draft of roadmap and user guide
- #46 Can we preserve the links to the email archive?
- Share draft of the user guide with the community
- Document the new email archive
- #48 Find a solution for cross-posting to multiple categories
- Set up email addresses for creating new topics and redirect them to Discourse
- #94 Define long-term roadmap for mailing list archive
- update all documentation related to mailing lists
We should collect all the missing features so we can raise them directly to the Discourse team as we have conversations with them about the migration. They may be able to implement or give us a timeline for new features, like github did when we did that migration.
@tstellar please feel free to add tasks to the list on top of this issue.
@sloppyjuicy , sorry what are you trying to tell me?
notes from meeting on 2021-08-03:
- LLVM board wants to move forward with migration
- finalized category list and mailing list mapping
- Up next: getting quote from discourse
- hint: archives could be conserved with static html inside mailman
notes from meeting on 2021-08-17:
- completed category mapping
- waiting from quote from Discourse (the company)
- communication to the community in preparation by the board
stale effort, removing from out backlog
from meeting 2022-01-18:
@ChristianKuehnel reach to @tlattner to figure out if the IWG should help with the migration.
If not: close the issue.
@tlattner Is there anything the IWG can do to help with the Discourse migration?
If not I would close this issue.
Now that we have moved, there is lots of cleanup. Mostly documentation related. Anyone can help with that if they see places we need to update things. I'll be working my way through them as well.
@tlattner do you have a list of things to improve? You probably have a much deeper insight on what needs to be done.
not sure how the IWG can help at the moment --> closing the issue.