Create email.md #42
Open
Create email.md #42
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chicoxyzzy
reviewed
Nov 7, 2017
email.md
Outdated
| - Explain ways that companies that support open source and why that is a positive perk that we are going to be looking out for | ||
| - Donations to projects that are used (instead of just saying "we use Babel, JSX, ES6, etc", wouldn't it be amazing to see "we have been sponsoring Babel with $10k/month for the last year because we care about supporting projects that we fundamentally rely on" | ||
| - Developer time: "We contribute to open source" vs. "we allow our developers to: spend 20% time, or 1 day a week, or weekly hackathons, or employ a maintainer of Babel" | ||
| - Monthyl donation stipend: "we allow our developers to distribute $50 a month to the open source project of their liking" |
|
Additionally:
|
|
50% is probably a percentage that may be too high for most companies to afford, but I think that 1 day a week for solid companies and 1 day every 2 weeks for emerging companies should become the minimum standard for companies using open source heavily in their business. My 2 cents. |
xtuc
reviewed
Nov 8, 2017
|
|
||
| ## Email Response | ||
|
|
||
| Thanks for reaching out! I'd be more interested in a company that supports the open source community more: whether it be donating to important projects that the company uses (like on opencollective.com), contributing developer time during work hours to fix bugs, report issues, even maintain a project, or even doing a matching donation similar to a non-profit (maybe give $50 a month to employees for them to choose). If you have any questions about that I'd be happy to explain. |
There was a problem hiding this comment.
That sounds like you could still be interested in the offer. What if the recruiter says yes?
|
@nemesisdesign I don't think I had the number 50% in this PR anywhere but I included 50% in my personal email because that's what I have now (unrelated to making a generic email here) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
So I was thinking about how I never respond to recruiter emails, and how their way of try to appeal to me is a bit lacking:
work on some framework, create a new framework, be a senior dev/cto, etc. Personally I was just thinking a bit about how companies can change to better support open source, so why not respond back with some suggestions/help?
Can suggest:
Maybe we can come up with a better-edited response that a lot of us can use when we aren't interested but would like to provide feedback about supporting open source?
Not really should how it should go, so making a PR so people can leave comments/suggestions/etc? I don't know 馃槄, figured it's worth a shot