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

Guidelines around technical initiative social media #259

Open
mlieberman85 opened this issue Feb 7, 2024 · 9 comments
Open

Guidelines around technical initiative social media #259

mlieberman85 opened this issue Feb 7, 2024 · 9 comments
Assignees
Labels
documentation Improvements or additions to documentation question Further information is requested

Comments

@mlieberman85
Copy link
Contributor

Some projects and working groups within the OSSF have expressed the desire to have social media handles that represent their project or group, e.g. X handles, LinkedIn, Mastodon, etc. We currently don't have guidelines or governance around this and I think it is worthwhile for us to allow the use of social media as long as some (hopefully) simple guidelines are met.

There's some pretty clear MUST NOTs like:

  • No endorsements of products
  • Any posts that would violate CoC

I think there's some reasonable things we can put in place like if a TI owns a social media account there should be guidelines within the TI on its use. Maybe some mechanism for having the account change hands, especially if there are issues with CoC violations or bad actors.

Thoughts? If this is a good idea, I'll also draft up a document on this as well.

@jennbly
Copy link

jennbly commented Feb 8, 2024

I am in favor of this! We do have the start of some guidelines within our larger Content Policy, (see the last section, Technical Initiative Websites and Social Media) but they could certainly be more robust. Ideas on what to add or break out into its own document are more than welcome. Agreed the MUST NOTs should be a key feature.

@SecurityCRob SecurityCRob added documentation Improvements or additions to documentation question Further information is requested labels Feb 23, 2024
@sevansdell
Copy link
Contributor

+1 @mlieberman85 in favor. Can MAC or DevRel help support drafting the documentation with you?

@SecurityCRob
Copy link
Contributor

has there been any progress on this? can we close this out if it is complete?

@sevansdell
Copy link
Contributor

@afmarcum can you please help drive getting this to the right action owner please?

@sevansdell
Copy link
Contributor

sevansdell commented Oct 28, 2024

status update please? @afmarcum are you the right Point of contact for this?

@afmarcum
Copy link
Contributor

afmarcum commented Oct 30, 2024

Apologies for the delay on this one. @aliu1020 can provide staff support on this effort and can provide existing guidelines as a start.

@aliu1020
Copy link

aliu1020 commented Oct 30, 2024

Hi all! Please find OpenSSF content policy here. https://docs.google.com/document/d/1m7zfFhAKAFGndifoip-BE2WhfQ6_p8CTnp0Na5UtIl8/edit?tab=t.0

These are relatively high-level guidelines developed last year. Let me know if it would be helpful to create one specifically tailored to Projects or SIGs.

@david-a-wheeler
Copy link
Contributor

@aliu1020 - awesome! I made a few suggestions on the content policy, let me know if they make sense. I think a few high-level guidelines is better, it's confusing if everything is tailored.

@aliu1020
Copy link

Thanks David! Since this is primarily for internal use within the community, I suggest uploading this policy to GitHub. Let me know if we also prefer to have it on our website! @afmarcum

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation question Further information is requested
Projects
None yet
Development

No branches or pull requests

7 participants