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

TODO Guide Employee Open Source Engagement Guide #285

Open
jlprat opened this issue Feb 11, 2022 · 18 comments
Open

TODO Guide Employee Open Source Engagement Guide #285

jlprat opened this issue Feb 11, 2022 · 18 comments

Comments

@jlprat
Copy link
Member

jlprat commented Feb 11, 2022

As an outcome of the Touchpoint for 2022.02.11 I'm creating this issue, to collect people who would be willing to collaborate on writing a Guide on how OSPO teams can provide guidance around how to participate in OS communities.

🙋 Instructions for New Contributors

  1. Join TODO Slack
  2. Search for #guide-engaging-with-communities
  3. Introduce yourself to the group

If you can't access slack, either because of company or local restrictions, please let us know and we will find a better channel to sync for this guide 👍

@jlprat jlprat added the guide label Feb 11, 2022
@jlprat jlprat changed the title TODO Guide: How OSPO teams provide guidance around how employees should participate OS communities? TODO Guide: How OSPO teams provide guidance around how employees should participate in OS communities? Feb 11, 2022
@debbryant
Copy link

debbryant commented Feb 11, 2022 via email

@cm-howard
Copy link

More than happy to be a part of this @jlprat so looking forward to hearing more! 👍🏼

@gravax
Copy link

gravax commented Feb 14, 2022

Adding you both to the channel on Slack.

@gravax
Copy link

gravax commented Feb 14, 2022

And Deb too, if you want.

@gravax
Copy link

gravax commented Feb 14, 2022

Actually, Deb, you're not on the Slack, it seems.

@debbryant
Copy link

IRC? ;)

It’s true I’m not on Slack. But happy to otherwise contribute.

@Santhosh-LaB007
Copy link

Hi jlprat, I saw your message on LinkedIn. I would like to be part of this. Please add me to the loop in case there is any.

@jlprat
Copy link
Member Author

jlprat commented Feb 15, 2022

@Santhosh-LaB007 Thanks for your interest! We are trying to sort out how and where we should collaborate. But if you can, feel free to join the TODO Group slack space and join the #engaging-with-communities in the mean time.

In https://todogroup.org/ you'll find a widget to join the TODO Slack space.

@anajsana
Copy link
Member

@Santhosh-LaB007 here's the link to join please let us know if you can't access the Slack platform at all and we will try to find a better channel to sync 👍

@awright
Copy link

awright commented Feb 15, 2022

FWIW, we released our internal guidance as public document last public last year. The document was written as a collaboration between our OSPO and Legal. https://www.redhat.com/en/about/open-source/participation-guidelines Deb Bryant

this is really interesting deb. a question for you -- do you have/know of any guidelines -- which may be internal -- for how people should "behave" in open source spaces? and that's not like -- behave -- in prescriptive ways, but guidance and support so people can be positive contributors and not representatives of a corporate stakeholder. (i've often seen tension).

and also, what are the guidelines for when an employee is not their best self in an open source community? i feel like we have all seen difficult dynamics in the social parts of open source -- what are the guidelines when things go wrong?

@gyehuda
Copy link
Member

gyehuda commented Feb 15, 2022 via email

@awright
Copy link

awright commented Feb 15, 2022

thank you! helps so much @gyehuda -- no chance that internal document ever found the light of day, right?

@gyehuda
Copy link
Member

gyehuda commented Feb 15, 2022 via email

@awright
Copy link

awright commented Feb 15, 2022 via email

@awright
Copy link

awright commented Mar 1, 2022

Some resources as point of reference. All -- please continue to add to the list!

@winterrocks
Copy link
Member

Vicky's book is a good guide too: https://pragprog.com/titles/vbopens/forge-your-future-with-open-source/
It is a guide for those who want to start contributing for the first time.

@jlprat jlprat changed the title TODO Guide: How OSPO teams provide guidance around how employees should participate in OS communities? TODO Guide Employee Open Source Engagement Guide Mar 10, 2022
@perploug
Copy link

Great initiative, would also like to contribute here.

Previously I collaborated with HR at Zalando, to create a policy, on supporting employees engaging in open source on behalf of the company, this is kind of the other side of the coin, that we as organisations should have mechanisms in place to support our employees in case they are target of harassment due to their open source work.

The policy was released here:
https://opensource.zalando.com/docs/resources/harassment-policy/

@awright
Copy link

awright commented Mar 10, 2022 via email

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

No branches or pull requests

10 participants