Discourse migration - First draft of roadmap and user guide #45
Conversation
ChristianKuehnel
changed the title
|
@joker-eph That's a good question. @ChristianKuehnel We should add this to a TODO for the Discourse migration, what do you think is the best way to do this, a github issue? |
| [is not supported](https://meta.discourse.org/t/selecting-multiple-category/116827). | ||
|
|
||
| **TODO:** The documentation says tags can be used to achieve a similar outcome. | ||
| However they don't say how to do that. |
There was a problem hiding this comment.
There are other ways to emulate cross-posting. For example, you can have an 'announce' category or something that everyone is automatically subscribed too. I think the important thing about cross posting is that it reaches people who may be subscribe only to a single category. Where the archive of the discussion ends up is not all that important.
There was a problem hiding this comment.
I am not convinced that this is addressing "cross-posting" in general.
For example some technical discussion that starts on cfe-dev gets cross-posts to llvm-dev, but they aren't "announcements" neither they are suitable for a global category (irrelevant for lldb, lld, mlir, etc.).
discourse_migration/userguide.md
Outdated
|
|
||
| ### What is the reason for the migration? | ||
|
|
||
| see [this email](https://lists.llvm.org/pipermail/llvm-dev/2021-June/150823.html) |
There was a problem hiding this comment.
I think we should expand this section and list some of the features we get from using Discourse that we can't get from mailman.
There was a problem hiding this comment.
I agree, can you propose something in a PR? I merged this document to main branch.
|
I'm merging the current state of the document, so we can split up the discussions. Please do create PRs for the changes you would like to make. |
| * You can filter incoming emails in your email client by category using the | ||
| `List-ID` email header field. | ||
|
|
||
| ## Mapping of mailing lists to categories |
There was a problem hiding this comment.
It might be worth noting here that we have a lot more specific categories on Discourse than we previously had mailing lists for. Does it make sense to mention all the "new" categories that were previously discussed on the same mailing list? Or at least mention it in writing. In my opinion this is an organizational benefit of Discourse.
There was a problem hiding this comment.
Good point, can you propose something? I have to admit, I don't really have a good overview of the mapping.
I merged the file to the main branch, feel free to create a PR for that.
|
@sloppyjuicy , sorry, what did you want to tell me? |
roadmap
This should explain the steps for the migration. This is mostly for the people working on the migration.
user guide
This is intended for the community to answer the questions I would expect them to have.
This is related to #6 and #37.