17 ms·

Start your open-source career

364 points by vvoyer 9y ago

aphextron 9y ago
What are some useful, active web based projects to contribute to?
- deleted 9y ago
  [deleted]
- echolot 9y ago
  It's a valid question, but you may want to start by contributing to OSS projects that you actually use. The story in the article is about the author and his cofounder contributing to a library they used heavily. You already have a vested interest in things you use. The next step would be to visit the git repo and see how you can help.
  - watwut 9y ago
    Why? This answer is most common one and always puzzled me. Just because I like to use something does not mean it is good project for me to contribute to. They tend to be very different categories. Plus, the pool of people who have time to spare and want to do something is different then pool of people who have scratches all around the projects.
    - UncleEntity 9y ago
      > Why? This answer is most common one and always puzzled me. If you don't use it how do you know you're solving actual user problems? I used to contribute to an OSS project and there were a lot of times where the devs and users had differing opinions on how a feature should work.
      - figgis 9y ago
        > If you don't use it how do you know you're solving actual user problems? There are many (many) ways to contribute to a project that doesn't require you to be solving actual user problems. I'd suggest just finding new projects, review code, create pull requests for those small mistakes you see. Provide feedback if applicable. Etc.
      - watwut 9y ago
        > If you don't use it how do you know you're solving actual user problems? You can fix uncontroversial bug/feature request from issue tracker. Not everything us contested, most of it is not. Also, I would expect the project to welcome someone doing the work more then just another one that came to argue .
    - echolot 9y ago
      It puzzles me why anyone would go around fixing bugs in libraries they would never use themselves. If you don't like my answer, then go read Kierkegaard or Sartre and contemplate the essence of your existence, and then go do what fulfills you as an individual.
      - figgis 9y ago
        It puzzles why anyone would go around picking up trash from parks they never use themselves. If you don't like my answer, then go watch idiocracy and contemplate the essence of your existence, and then go and do what fulfills you as an individual. -- It puzzles me why anyone would go around in a santa suit cheering up kids they'll never see again. If you don't like my answer, then go read How the Grinch Stole Christmas and contemplate the essence of your existence, and then go do what fulfills you as an individual.
        echolot 9y ago
        Kierkegaard is smiling from the afterlife.
    - pm215 9y ago
      I think one reason is that if you already know a project as a user you're a long way up the learning curve for understanding it. You know roughly what its feature set is, you know how new features would fit in with the existing ones, you know how to do basic "does this thing work" testing of it. You probably have an idea of what changes are likely to be small tweaks to existing functionality and what are bigger and harder. Knowing the shape of the outside of something makes it easier to understand the inside of it. If you start out with a contribution to a project you don't use, you don't have that initial base to build on and so it's harder. Which isn't to say it's impossible, of course -- people getting new jobs working on proprietary software have to get up to speed with programs they probably never used before. It's just time consuming. The "what should I work on?" question implies that the asker has no preference, so answers optimising for what's easier to get started with make sense.
- deleted 9y ago
  [deleted]
- yorwba 9y ago
  Someone posted answer recommending the OpenEMR project, but now I can't see it anymore. Maybe they decided to delete it for some reason? Anyway, I think the project's aims are commendable: OpenEMR is the most popular open source electronic health records and medical practice management solution. ONC certified with international usage, OpenEMR's goal is a superior alternative to its proprietary counterparts. With passionate volunteers and contributors dedicated to guarding OpenEMR's status as a free, open source software solution for medical practices with a commitment to openness, kindness and cooperation. http://open-emr.org/ http://open-emr.org/
gilrain 9y ago
Rust is among the most welcoming of communities to start out in. If you're interested in the language, definitely check here for easy ways to get involved. https://www.rustaceans.org/findwork/starters https://www.rustaceans.org/findwork/starters
- waldir 9y ago
  It's worth noting that this newcomer friendliness is no accident: building and maintaining a welcoming FOSS community, and doing so at scale, can only be achieved with deliberate efforts. The video [Rust's Community Automation](https://www.youtube.com/watch?v=407nwX6__70 https://www.youtube.com/watch?v=407nwX6__70) offers an excellent summary of the strategies used in the Rust community to handle the social dynamics so that both contributors and maintainers are able to engage positively and productively, and continue doing so over extended periods of time. It's definitely something other projects should look at and replicate :)
jordigh 9y ago
Why do people want to have an "open-source" career at all? Why are people asking, "what should I contribute to?" I honestly don't understand this attitude at all, assuming the people who want to "do" open source are in earnest, and not because they want to pad their CV in order to get a job completely unrelated to free software. So, assuming you really do want to do free development, why do you need help being told where to start? The typical self-motivated reason to start is because you have found open and free software that doesn't do what you want it to do, so you go ahead, and by golly, you've had enough of these blighted bugs, and you're going to make the software work for yourself (or rarely, for someone close to you that you care about). Shopping around for something to work on without having a personal problem to solve seems like putting the cart before the horse. I assume that's not why people want to do it. They must already have a personal problem. So, what is it, what's the motivation to have a "career" in "open-source"?
- dominotw 9y ago
  > So, what is it, what's the motivation to have a "career" in "open-source"? Learn and work with people from all over the world, people who you never have a chance to work with in real life.
- watwut 9y ago
  It boils down either to "it us cool" or "I want to do something idealistic and helpfull for others". Nothing wrong with either.
  - connorelsea 9y ago
    A lot of communities are also full of great people. Makes it fun and enjoyable a lot of the time. It's also education, you learn from your work and get fairly real-world experience depending on what you're working on
- yorwba 9y ago
  Most of my problems tend to be pretty trivial, and those that aren't are at least easy to work around. While most of my open-source contributions are indeed bug fixes for things that affected me personally (which is how I noticed them), I find it much more satisfying to solve other people's problems. So having someone point out a thing they think needs improvement is a much better motivator than just scratching my own insignificant itches.
notyourday 9y ago
Thanks, but i like getting paid. That's why they call it "career".
- nrhk 9y ago
  Yea but I also like getting paid more and adding a feature to something like React or Node would pretty much put you in the upper echelon of JS developers most companies will hire. Also if you're switching to new frameworks and languages, doing open source will open up your career opportunities.
  - notyourday 9y ago
    That's what people who want you to program their frameworks or produce some other code for free would really want you to believe.
    - richardknop 9y ago
      I think it is actually true. Just ask some of the people who created and maintain some popular / high profile libraries or frameworks. That leads to a lot of job offers and more demand for your services means you can charge more. If you have companies reaching out to you with potential job offers frequently, you can use that when negotiating salary when applying for a new job or to negotiate a raise at your current job. It's the same principle as the guy who interviewed at Google, Facebook, Airbnb & dozen other companies and then used several offers he got to negotiate and he ended up with ridiculously good package for software engineer.
      - galaxyLogic 9y ago
        So shouldn't the article then have been "How to start your NON-open-source career by first doing open source?"
      - notyourday 9y ago
        a) that's survivorship bias - for every one who "worked" on those frameworks and got somewhere because of it, there are thousands who wasted their time. I would go as far as to say that those who worked on those frameworks and got hired would have been hired without that. > If you have companies reaching out to you with potential job offers frequently, you can use that when negotiating salary when applying for a new job or to negotiate a raise at your current job If you are one of those people who is a target of companies rather than recruiters outreach, then you do not care about frameworks. Hint: these are people who don't have interviews. They go for lunch. Or dinner. > It's the same principle as the guy who interviewed at Google, Facebook, Airbnb & dozen other companies and then used several offers he got to negotiate and he ended up with ridiculously good package for software engineer. That's an imaginary guy.
juicy-fruit 9y ago
Having a popular open source project is a pain in the ass. At some point the happiness from seeing people use your project turns to annoyance once you become the janitor and problem solver to people who won't take 1 minute to read the README. However, I honestly appreciate people who create open source software and answer all issues and questions. GitHub should have a Q/A section on repos so that frequently asked questions can be answered there instead of having someone open the same issue every few months.
- vvoyer 9y ago
  I did not mention it in the article, but it's also completely fine to abandon your own project if you state so and wait for anyone willing to maintain it. There's no shame in ignoring feedback in open-source if that's a struggle on your side, health before open-source :)
- ishbits 9y ago
  I’m a full time paid open source developer. About 40% of my time is reviewing pull requests these days. Most of these are meaningful contributions. And while it can be a pain in the ass it is community building.
- on_and_off 9y ago
  Indeed. I am on the watcher list of a project I use a lot and contribute to. I don't know how the main maintainer can answer so many stupid questions in a polite way. 99% of the answers are either in the ample doc of the project or a google search away. I am not even sure how to curb this.
  - VBprogrammer 9y ago
    Seems to me that this is an opportunity for someone who wants to contribute to a project but lacks the technical skills to do so.
- samschooler 9y ago
  I also maintained a relatively popular Bukkit (minecraft server) plugin a few years ago. I had to abandon it because it really does just become too much fielding the unnecessary repetitive support. On top of trying to keep up with API changes on bukkit while also trying to go to school. As I was writing this I realized I am describing running a business, with everything except payment.
thomastjeffery 9y ago
Maybe a better title would be "start working open-source into your career". The article is more geared toward those who think they don't fit into the open-source community. Rest assured, anyone is welcome; that is generally what free software is about.
- vvoyer 9y ago
  > The article is more geared toward those who think they don't fit into the open-source community. Exactly what I wanted to outline in the article. Too often I thought that open-source people where inside the NBA of developers, that's not true at all. It's just people that have code visible by everyone. It's just code.
drej 9y ago
I must say Github has been amazing in enabling this, at least the first steps bit. Ever since they introduced editing in the browser, I have committed to maybe half a dozen open source projects. All of these were trivial one-liners with very little added value, but still, given that I could do all that without even having git on that given machine, is amazing. That + integrated CI tools whose results are integrated within relevant pull requests... it's at a point when almost anyone can fix documentation or typos in code.
- vvoyer 9y ago
  True, and open-source projects can also have "Edit this page" links on every pages that directly goes to the edit mode of the file, example: https://community.algolia.com/react-instantsearch/guide/ https://community.algolia.com/react-instantsearch/guide/ We got many first time contributions with that.
orliesaurus 9y ago
Open source has a problem where a lot of people demand and request updates, fixes and all that without ever giving back. I am not talking about medium sized companies or even smaller ones, I am talking to a plethora of small one or two human teams that do consulting/freelance development and simply don't have the visibility in the world of open source that others like maybe you and me have. It feels a bit like the recycling problem, it's really easy to do yet only a percentage of the population does it correctly. In the uk, on the defra.gov.uk website, it states that only 16% of the picked up waste is recycling... Why ? How can wr change that?
- tzahola 9y ago
  >How can we change that? When someone demands an update for your open source project, ask them what they can give back in exchange?
  - nurettin 9y ago
    Even better: tell them what they give back in exchange. That is what patreon and the like is about.
deleted 9y ago
[deleted]
grewil2 9y ago
Different terms convey different ideas. Writers pick "open source" to signal that they find user freedom unimportant, and "free software" or "libre software" to signal that they find user freedom important. While the author's intentions are probably good, it's interesting that neither user freedom nor licenses are mentioned in this type of article. In the unlikely case anyone wonders what I mean: https://www.gnu.org/philosophy/open-source-misses-the-point.html https://www.gnu.org/philosophy/open-source-misses-the-point....
ardi93 9y ago
I've recently made a contribution to a well-known project (DBeaver, a database management software). It started with a feature request and somehow I was able to implement it myself. It sure makes you nervous when it's the first time contributing, especially because your code/issue will be read by many other people. But, once your PR is merged, you will feel you've accomplished something great and want to contribute more.
RomanPushkin 9y ago
I started my own project free libre open-source project. It become quite popular in a year. I even found a guy who wanted to "invest" XXXk (I said no), and I won a grant of 25k from one non-profit accelerator (but never able to receive it). Also, I already had couple of job opportunities I rejected, and already spoke with some legendary folks from Open Source world about the future of the project. So it is definitely interesting and worth doing. The only downside is you need to invest some time into it. So it's better to do something what's really interesting for you.
partycoder 9y ago
I value the altruism of open source. But I do not value people that piggyback on existing high profile projects for personal gain. If someone tells me they contribute to a project, I would usually check what was actually contributed. A couple of unit tests and docs are always helpful but do not give enough credit compare to the effort of building such projects.
- waldir 9y ago
  > A couple of unit tests and docs are always helpful but do not give enough credit compare to the effort of building such projects. You might want to take a look at https://github.com/kentcdodds/all-contributors https://github.com/kentcdodds/all-contributors :)
  - partycoder 9y ago
    If a contributor is responsible for significant part of the code coverage, funding or documentation, by all means kudos. But someone that donated $5 or wrote 2 test cases and a couple of comments to me is a casual contributor not a core contributor.

364 points by vvoyer 9y ago

aphextron 9y ago

What are some useful, active web based projects to contribute to?

deleted 9y ago
[deleted]
echolot 9y ago
It's a valid question, but you may want to start by contributing to OSS projects that you actually use. The story in the article is about the author and his cofounder contributing to a library they used heavily. You already have a vested interest in things you use. The next step would be to visit the git repo and see how you can help.
- watwut 9y ago
  Why? This answer is most common one and always puzzled me. Just because I like to use something does not mean it is good project for me to contribute to. They tend to be very different categories. Plus, the pool of people who have time to spare and want to do something is different then pool of people who have scratches all around the projects.
  - UncleEntity 9y ago
    > Why? This answer is most common one and always puzzled me. If you don't use it how do you know you're solving actual user problems? I used to contribute to an OSS project and there were a lot of times where the devs and users had differing opinions on how a feature should work.
    - figgis 9y ago
      > If you don't use it how do you know you're solving actual user problems? There are many (many) ways to contribute to a project that doesn't require you to be solving actual user problems. I'd suggest just finding new projects, review code, create pull requests for those small mistakes you see. Provide feedback if applicable. Etc.
    - watwut 9y ago
      > If you don't use it how do you know you're solving actual user problems? You can fix uncontroversial bug/feature request from issue tracker. Not everything us contested, most of it is not. Also, I would expect the project to welcome someone doing the work more then just another one that came to argue .
  - echolot 9y ago
    It puzzles me why anyone would go around fixing bugs in libraries they would never use themselves. If you don't like my answer, then go read Kierkegaard or Sartre and contemplate the essence of your existence, and then go do what fulfills you as an individual.
    - figgis 9y ago
      It puzzles why anyone would go around picking up trash from parks they never use themselves. If you don't like my answer, then go watch idiocracy and contemplate the essence of your existence, and then go and do what fulfills you as an individual. -- It puzzles me why anyone would go around in a santa suit cheering up kids they'll never see again. If you don't like my answer, then go read How the Grinch Stole Christmas and contemplate the essence of your existence, and then go do what fulfills you as an individual.
      - echolot 9y ago
        Kierkegaard is smiling from the afterlife.
  - pm215 9y ago
    I think one reason is that if you already know a project as a user you're a long way up the learning curve for understanding it. You know roughly what its feature set is, you know how new features would fit in with the existing ones, you know how to do basic "does this thing work" testing of it. You probably have an idea of what changes are likely to be small tweaks to existing functionality and what are bigger and harder. Knowing the shape of the outside of something makes it easier to understand the inside of it. If you start out with a contribution to a project you don't use, you don't have that initial base to build on and so it's harder. Which isn't to say it's impossible, of course -- people getting new jobs working on proprietary software have to get up to speed with programs they probably never used before. It's just time consuming. The "what should I work on?" question implies that the asker has no preference, so answers optimising for what's easier to get started with make sense.
deleted 9y ago
[deleted]
yorwba 9y ago
Someone posted answer recommending the OpenEMR project, but now I can't see it anymore. Maybe they decided to delete it for some reason? Anyway, I think the project's aims are commendable: OpenEMR is the most popular open source electronic health records and medical practice management solution. ONC certified with international usage, OpenEMR's goal is a superior alternative to its proprietary counterparts. With passionate volunteers and contributors dedicated to guarding OpenEMR's status as a free, open source software solution for medical practices with a commitment to openness, kindness and cooperation. http://open-emr.org/ http://open-emr.org/

gilrain 9y ago

Rust is among the most welcoming of communities to start out in. If you're interested in the language, definitely check here for easy ways to get involved. https://www.rustaceans.org/findwork/starters https://www.rustaceans.org/findwork/starters

waldir 9y ago
It's worth noting that this newcomer friendliness is no accident: building and maintaining a welcoming FOSS community, and doing so at scale, can only be achieved with deliberate efforts. The video [Rust's Community Automation](https://www.youtube.com/watch?v=407nwX6__70 https://www.youtube.com/watch?v=407nwX6__70) offers an excellent summary of the strategies used in the Rust community to handle the social dynamics so that both contributors and maintainers are able to engage positively and productively, and continue doing so over extended periods of time. It's definitely something other projects should look at and replicate :)

jordigh 9y ago

Why do people want to have an "open-source" career at all? Why are people asking, "what should I contribute to?" I honestly don't understand this attitude at all, assuming the people who want to "do" open source are in earnest, and not because they want to pad their CV in order to get a job completely unrelated to free software. So, assuming you really do want to do free development, why do you need help being told where to start? The typical self-motivated reason to start is because you have found open and free software that doesn't do what you want it to do, so you go ahead, and by golly, you've had enough of these blighted bugs, and you're going to make the software work for yourself (or rarely, for someone close to you that you care about). Shopping around for something to work on without having a personal problem to solve seems like putting the cart before the horse. I assume that's not why people want to do it. They must already have a personal problem. So, what is it, what's the motivation to have a "career" in "open-source"?

dominotw 9y ago
> So, what is it, what's the motivation to have a "career" in "open-source"? Learn and work with people from all over the world, people who you never have a chance to work with in real life.
watwut 9y ago
It boils down either to "it us cool" or "I want to do something idealistic and helpfull for others". Nothing wrong with either.
- connorelsea 9y ago
  A lot of communities are also full of great people. Makes it fun and enjoyable a lot of the time. It's also education, you learn from your work and get fairly real-world experience depending on what you're working on
yorwba 9y ago
Most of my problems tend to be pretty trivial, and those that aren't are at least easy to work around. While most of my open-source contributions are indeed bug fixes for things that affected me personally (which is how I noticed them), I find it much more satisfying to solve other people's problems. So having someone point out a thing they think needs improvement is a much better motivator than just scratching my own insignificant itches.

notyourday 9y ago

Thanks, but i like getting paid. That's why they call it "career".

nrhk 9y ago
Yea but I also like getting paid more and adding a feature to something like React or Node would pretty much put you in the upper echelon of JS developers most companies will hire. Also if you're switching to new frameworks and languages, doing open source will open up your career opportunities.
- notyourday 9y ago
  That's what people who want you to program their frameworks or produce some other code for free would really want you to believe.
  - richardknop 9y ago
    I think it is actually true. Just ask some of the people who created and maintain some popular / high profile libraries or frameworks. That leads to a lot of job offers and more demand for your services means you can charge more. If you have companies reaching out to you with potential job offers frequently, you can use that when negotiating salary when applying for a new job or to negotiate a raise at your current job. It's the same principle as the guy who interviewed at Google, Facebook, Airbnb & dozen other companies and then used several offers he got to negotiate and he ended up with ridiculously good package for software engineer.
    - galaxyLogic 9y ago
      So shouldn't the article then have been "How to start your NON-open-source career by first doing open source?"
    - notyourday 9y ago
      a) that's survivorship bias - for every one who "worked" on those frameworks and got somewhere because of it, there are thousands who wasted their time. I would go as far as to say that those who worked on those frameworks and got hired would have been hired without that. > If you have companies reaching out to you with potential job offers frequently, you can use that when negotiating salary when applying for a new job or to negotiate a raise at your current job If you are one of those people who is a target of companies rather than recruiters outreach, then you do not care about frameworks. Hint: these are people who don't have interviews. They go for lunch. Or dinner. > It's the same principle as the guy who interviewed at Google, Facebook, Airbnb & dozen other companies and then used several offers he got to negotiate and he ended up with ridiculously good package for software engineer. That's an imaginary guy.

juicy-fruit 9y ago

Having a popular open source project is a pain in the ass. At some point the happiness from seeing people use your project turns to annoyance once you become the janitor and problem solver to people who won't take 1 minute to read the README. However, I honestly appreciate people who create open source software and answer all issues and questions. GitHub should have a Q/A section on repos so that frequently asked questions can be answered there instead of having someone open the same issue every few months.

vvoyer 9y ago
I did not mention it in the article, but it's also completely fine to abandon your own project if you state so and wait for anyone willing to maintain it. There's no shame in ignoring feedback in open-source if that's a struggle on your side, health before open-source :)
ishbits 9y ago
I’m a full time paid open source developer. About 40% of my time is reviewing pull requests these days. Most of these are meaningful contributions. And while it can be a pain in the ass it is community building.
on_and_off 9y ago
Indeed. I am on the watcher list of a project I use a lot and contribute to. I don't know how the main maintainer can answer so many stupid questions in a polite way. 99% of the answers are either in the ample doc of the project or a google search away. I am not even sure how to curb this.
- VBprogrammer 9y ago
  Seems to me that this is an opportunity for someone who wants to contribute to a project but lacks the technical skills to do so.
samschooler 9y ago
I also maintained a relatively popular Bukkit (minecraft server) plugin a few years ago. I had to abandon it because it really does just become too much fielding the unnecessary repetitive support. On top of trying to keep up with API changes on bukkit while also trying to go to school. As I was writing this I realized I am describing running a business, with everything except payment.

thomastjeffery 9y ago

Maybe a better title would be "start working open-source into your career". The article is more geared toward those who think they don't fit into the open-source community. Rest assured, anyone is welcome; that is generally what free software is about.

vvoyer 9y ago
> The article is more geared toward those who think they don't fit into the open-source community. Exactly what I wanted to outline in the article. Too often I thought that open-source people where inside the NBA of developers, that's not true at all. It's just people that have code visible by everyone. It's just code.

drej 9y ago

I must say Github has been amazing in enabling this, at least the first steps bit. Ever since they introduced editing in the browser, I have committed to maybe half a dozen open source projects. All of these were trivial one-liners with very little added value, but still, given that I could do all that without even having git on that given machine, is amazing. That + integrated CI tools whose results are integrated within relevant pull requests... it's at a point when almost anyone can fix documentation or typos in code.

vvoyer 9y ago
True, and open-source projects can also have "Edit this page" links on every pages that directly goes to the edit mode of the file, example: https://community.algolia.com/react-instantsearch/guide/ https://community.algolia.com/react-instantsearch/guide/ We got many first time contributions with that.

orliesaurus 9y ago

Open source has a problem where a lot of people demand and request updates, fixes and all that without ever giving back. I am not talking about medium sized companies or even smaller ones, I am talking to a plethora of small one or two human teams that do consulting/freelance development and simply don't have the visibility in the world of open source that others like maybe you and me have. It feels a bit like the recycling problem, it's really easy to do yet only a percentage of the population does it correctly. In the uk, on the defra.gov.uk website, it states that only 16% of the picked up waste is recycling... Why ? How can wr change that?

tzahola 9y ago
>How can we change that? When someone demands an update for your open source project, ask them what they can give back in exchange?
- nurettin 9y ago
  Even better: tell them what they give back in exchange. That is what patreon and the like is about.

deleted 9y ago

[deleted]

grewil2 9y ago

Different terms convey different ideas. Writers pick "open source" to signal that they find user freedom unimportant, and "free software" or "libre software" to signal that they find user freedom important. While the author's intentions are probably good, it's interesting that neither user freedom nor licenses are mentioned in this type of article. In the unlikely case anyone wonders what I mean: https://www.gnu.org/philosophy/open-source-misses-the-point.html https://www.gnu.org/philosophy/open-source-misses-the-point....

ardi93 9y ago

I've recently made a contribution to a well-known project (DBeaver, a database management software). It started with a feature request and somehow I was able to implement it myself. It sure makes you nervous when it's the first time contributing, especially because your code/issue will be read by many other people. But, once your PR is merged, you will feel you've accomplished something great and want to contribute more.

RomanPushkin 9y ago

I started my own project free libre open-source project. It become quite popular in a year. I even found a guy who wanted to "invest" XXXk (I said no), and I won a grant of 25k from one non-profit accelerator (but never able to receive it). Also, I already had couple of job opportunities I rejected, and already spoke with some legendary folks from Open Source world about the future of the project. So it is definitely interesting and worth doing. The only downside is you need to invest some time into it. So it's better to do something what's really interesting for you.

partycoder 9y ago

I value the altruism of open source. But I do not value people that piggyback on existing high profile projects for personal gain. If someone tells me they contribute to a project, I would usually check what was actually contributed. A couple of unit tests and docs are always helpful but do not give enough credit compare to the effort of building such projects.

waldir 9y ago
> A couple of unit tests and docs are always helpful but do not give enough credit compare to the effort of building such projects. You might want to take a look at https://github.com/kentcdodds/all-contributors https://github.com/kentcdodds/all-contributors :)
- partycoder 9y ago
  If a contributor is responsible for significant part of the code coverage, funding or documentation, by all means kudos. But someone that donated $5 or wrote 2 test cases and a couple of comments to me is a casual contributor not a core contributor.