How can Dask acknowledge developer contributions by companies?
- Dominant language
- No language data
- Stars
- 25
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Moving https://github.com/dask/dask/issues/5831 to here since this is a better fit.
Hi All,
I'd like to start a discussion on appropriate ways and criteria for the Dask community to acknowledge support by commercial companies. I've had a couple of these conversations offline with a couple of people and have some ideas but I wanted to raise it up for a larger discussion.
Currently the foot of the Dask website has a section called 'Supported By' that from my understanding lists organizations and companies that have supported Dask development through some sort of funding/grants etc. This is a very clear cut form of support.
Another form of support is through the funding of developers who directly work on Dask. At Quansight (where I work) we have clients who support a lot of Dask (and other open source) development and are looking for ways to be recognized as a good open source citizen.
My proposal is we develop some loose criteria on how to evaluate a company's contributions and whether they have been a good citizen and then either add their name/logo to the 'supported by' section of the website OR if we think we need to, add a new section to distinguish between direct monetary support and support through developers. I'd love to hear other ideas on how we could recognize these kind of contributions. We have done blog posts in the past but those are kinda ephemeral.
The advantages of this to the Dask community is to hopefully encourage more companies to contribute their resources and for the companies the recognition that they are open source friendly can help them in recruiting.
Contributor guide
Research direction
Start by reviewing the Dask website footer's existing “Supported By” section and the discussion moved from issue 5831. Define criteria for recognizing company support and decide whether to extend that section or create a separate one. Done means the community has agreed on a clear policy and recognition approach.
Written by the indexing model from the issue text.
Assessment
- Domain
- content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100