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.

Sign up for GitHub

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

Jump to bottom

Communications excellence guidelines #316

Open
SecurityCRob opened this issue Apr 16, 2024 · 3 comments
Open

Communications excellence guidelines #316

SecurityCRob opened this issue Apr 16, 2024 · 3 comments
Assignees
@SecurityCRob
Labels
administration Content Updates/additions to TAC content/process. Must include a changelog entry. Needs 3 approvals. documentation Improvements or additions to documentation

Comments

@SecurityCRob
Copy link
Contributor

The TAC shall create simple, accessible guidelines to help empower our communities to understand what tools and channels are available, how best to communicate with distributed asynchronous communities, and where best to effectively share information with TIs and the broader community.
@SecurityCRob SecurityCRob added documentation Improvements or additions to documentation administration labels Apr 16, 2024
@SecurityCRob SecurityCRob self-assigned this Apr 16, 2024
@SecurityCRob SecurityCRob added the Content Updates/additions to TAC content/process. Must include a changelog entry. Needs 3 approvals. label May 15, 2024
@sevansdell
Copy link
Contributor

Seems related! #330

@sevansdell sevansdell mentioned this issue Jun 6, 2024
Open
@sevansdell
Copy link
Contributor

How should we continue to drive this issue? Do we have an example of another foundation who has something we can use as a starting point? Or is it a matter of proposing a V1 in a TAC process document in Github and starting a PR?

@sevansdell
Copy link
Contributor

This one has been opened a while with no action. @steiza How should we handle this? Can someone from the TAC be assigned as an action owner and we timebox the deliverable? Or do we close this one out for no activity, and reopen it when needed? Or something else?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SecurityCRob SecurityCRob

Labels
administration Content Updates/additions to TAC content/process. Must include a changelog entry. Needs 3 approvals. documentation Improvements or additions to documentation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@SecurityCRob @sevansdell