Comments (8)
If this isn't too detailed -- in your commits, always use the email appropriate to the context. That is, if you're making a contribution as part of your job at company xyz, you should be signing it using [email protected]. I go into more detail: https://www.juliaferraioli.com/blog/2022/your-git-email-matters/
from todogroup.org.
Some of the things that I think we should reflect here:
- Be open about your affiliation: We kind of touched this on the first principle, but this should be also present here.
- Share level of commitment for the project: is it a "one off", is it a long or mid level commitment?
- Purpose of the collaboration: what is the the work you are willing/allowed to take? Is the purpose to help the community taking tasks that affect all the community? Or only the intersection between community and their company's interest?
- Be straightforward: you shall not have any hidden agenda or trying to "secretly" steer the project in certain direction
from todogroup.org.
I think we should totally add this @juliaferraioli :)
from todogroup.org.
An attempt to convert the bullet points to text:
Your work on the projects should be transparent. Transparency has many different aspects an dimensions that we will try to showcase here.
You should be transparent with the rest on the community about your level of commitment with this project: from working only on issues that overlap with your company's interests, to help out in anything the project needs, or anything in between. All the options are valid and there is not right or wrong answer.
It is important to be transparent about the reason why you are working on the tasks you pick. Sharing as much context as you can is useful for the rest of the community to better gauge the importance of the work and why it should be included in the project. This is not about revealing company strategies, but sharing and explaining why is this paritcular piece of work needed and interesting.
We have multiple hats when interacting with communities: our company's or our own. It is important to differentiate and be explicit about which virtual persona you are in each moment. For example, when committing changes or writing emails, use the corporate or the personal email accordingly.
from todogroup.org.
An attempt to convert the bullet points to text:
You should be transparent with the rest on the community about your level of commitment with this project: from working only on issues that overlap with your company's interests, to help out in anything the project needs, or anything in between. All the options are valid and there is not right or wrong answer.
I'm curious what this would look like in practice. Any examples? I often see people stating when they'll be out of pocket as long-time contributors but less so people giving levels of commitment up-front.
from todogroup.org.
For example at Aiven we have people whose purpose is to contribute to specific Open Source projects, so people can have a long commitment to the projects. Making this known to the communities helps in planning, sharing responsibilities, and helps building trust.
I would guess sporadic collaborations are the default.
Other companies might say, we want this set of features on this project and we want to help make it happen and they dedicate some people on such endeavors, when finished, people focus on other projects.
Is this what you were looking for?
from todogroup.org.
See #384 for a draft for the guide based on the input of the issues.
from todogroup.org.
Closing as all additional input has been received.
from todogroup.org.
Related Issues (20)
- Principle 0: Don't be a Jerk ;) HOT 4
- pt-PT translation effort HOT 3
- Missing link to Slack HOT 3
- Change current todogorup.org navbar as a dropdown navbar HOT 5
- Verify Todo Group GitHub profile HOT 2
- Suitable Place for Corporate Covenant HOT 4
- Conspicuously link to the CoC in the header or footer of the website
- Broken picture links on Outbound OSS guide HOT 2
- Request to translate TODO Group slides into Chinese on about page HOT 5
- Request to upgrade the Hugo version of the website
- add OSPO Survey 2023 Chinese link HOT 4
- TODO redesign branch content review HOT 4
- Apply card view for content HOT 3
- Presentation shortcode height too big on mobile HOT 1
- Web page shows wrong copyright information HOT 6
- TODO RSS bug HOT 1
- Some of the error links are in the OPEN SOURCE GUIDES of LF website HOT 3
- broken link of Using open source code Page
- [Translation-zh-cn] Website translation task trace HOT 2
- Include Newsletter page to archive OSPONews past issues and new form link HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from todogroup.org.