[RFC] Discourse structure

[adamgayoso]

Current proposal:

There are only two levels of topics, the main card, and tags within the card

- Help (one for each project e.g., Scanpy, Muon, ...)
    - Tags = project subpackage or relevant category (e.g., sc.preprocess in Scanpy help card, scvi-tools TOTALVI class)
- Assay (for general questions about analyzing this type of data)
    - RNA-seq
    - CITE-seq
    - ATAC-seq
    - ...
- Development
   - Tag for each package
- Community (discussion related to community initiatives, other miscellaneous topics)
- Governance (announcement related to governance, see Stan forums)
- Ecosystem
    -  Tag for each ecosystem project (ecosytem project head reaches out to us to be included)

Moderators have the ability to direct posts into the appropriate category if needed

[Zethson]

• Development
  • Tag for each package

I get why you have this here, but was wondering whether we should try to keep development discussions inside Github issues?

It might be easier for everyone to have user and meta questions/topics in the discourse and development issues in Github issues? Else, we might have development discussions happening in two places and it might get hard to keep track.

We could then also more easily point people to the appropriate place to post their bug or help request.

[adamgayoso]

I get why you have this here, but was wondering whether we should try to keep development discussions inside Github issues?

Yes, can probably remove this card. I was thinking like making a new model development with scvi-tools, which can have it's own subcategory in the help card.

[ivirshup]

I'm not sure I understand the purpose of the assays topic.

Are you trying to separate questions into "basic help" and "higher level questions"?

Would an "Ideas" topic make more sense? It seems like higher level questions wouldn't be limited just to assays. I would also suspect there would be overlap between "assays" and "help".

[adamgayoso]

We have packages with a lot of overlapping capabilities. Assays are for general questions about analyzing data - “how many HVG do I use” and not about how to use a particular function in any package.

On Wed, Mar 2, 2022 at 5:35 AM Isaac Virshup @.***> wrote:

I'm not sure I understand the purpose of the assays topic.

Are you trying to separate questions into "basic help" and "higher level questions"?

Would an "Ideas" topic make more sense? It seems like higher level questions wouldn't be limited just to assays. I would also suspect there would be overlap between "assays" and "help".

— Reply to this email directly, view it on GitHub https://github.com/scverse/governance/issues/25#issuecomment-1056938757, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACS3HMBJ5U2NT4WPB24KLQDU55VDLANCNFSM5OB4H3HQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>

[ivirshup]

I think the distinction makes sense.

I think the name "Assay" may end up drawing usage questions for particular assays which may fit better in "Help". I think "Help" may also attract some higher level questions.

What do you think about naming this something different? Like "Ideas", "Discussion", "Questions"?

[adamgayoso]

"Ideas" seems to broad to me because like they are questions not ideas. We could call it "general"?

Everything is generally ready except domain change. I made every core person who signed up a level 4 user (basically same as moderator, but we can only have 5 moderators). @ivirshup can we sync up to change the domain name?

https://discourse.scvi-tools.org/

[ivirshup]

I think "general" is good (but broader than "ideas", no?)