Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tagging task-force-specific discussions in email threads #44

Closed
Antoine-Zimmermann opened this issue Mar 23, 2023 · 3 comments
Closed
Labels
propose closing Proposed for closing

Comments

@Antoine-Zimmermann
Copy link
Contributor

I propose that we add a prefix of the form [NameOfTaskForce] to the topic of a new email thread when it is specific to the task force called NameOfTaskForce. This issue is to get a unique proposal of what prefixes to use for each task force and enforce their use by the WG, so as to simplify filtering those discussions or finding them in the future. Here is a proposal:

  • Use case task force: [UC] (clear, short, hardly possible to misspell it)
  • Semantics task force: [Sem] (rather clear, short and hard to misspell)
  • Editors task force: [ED] (somewhat clear, short and hardly possible to misspell)

Alternative:

  • Use case TF: [UC]
  • Semantics TF: [Semantics] (very clear but long and easy to misspell)
  • Editors TF: [Editors] (very clear but possible to misspell)
@hartig
Copy link
Contributor

hartig commented Mar 23, 2023

+1 to the first option (i.e., [UC], [Sem], and [ED]).

@pchampin
Copy link
Contributor

I don't think that this was ever adopted, but as we moved the largest part of the discussions to github issues, this does not really matter anymore.

@Antoine-Zimmermann any objection to close this issue?

@pchampin pchampin added the propose closing Proposed for closing label Feb 18, 2025
@Antoine-Zimmermann
Copy link
Contributor Author

Yes, do close it. Thanks.

@pfps pfps closed this as completed Mar 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
propose closing Proposed for closing
Projects
None yet
Development

No branches or pull requests

4 participants