What's wrong with your open source project
We all know how good and commendable to take part in the development of open source projects.
In addition, you can then measure the number of commits in rails and ask for more wages.
And what if you decide to write your open source project?
')
It's a little different here. But it would seem that in this bad?
I wrote a library or application, flooded it with a githab and great.
And it's really great if this is a simple library with a couple of bugs and hundreds of users.
Once a month I wrote to issues, once a year I updated the version - everyone is happy.
And if the project is complex and even became popular? Here everything is bad.
Who does not know me - I am the author of the open source project GitLab .
In fact, this is a web application for hosting git-repositories inside a closed infrastructure.
For information, you can read this post .
It is in the Popular Starred Repositories github on the first page so it’s an example for this.
So given:
Project: GitLab
Number of githubs per day: 30-40
Installations: 40k +
1. Time
Time is a resource extremely limited in the life of the developer.
What is your open source project in terms of your time?
* This is a time to read the wishes, bug reports
* this is the time to develop and maintain the code
* This is the time to review pull ricks or patches
* This is the time for revision and fixes after these patches.
* this is the time for discussion and support
Total you are sitting at 11 pm for a laptop at home and your wife looks at you angrily
2. Fun
Great feeling to write an open source project. You choose the technologies that suit you, write without haste, beautifully and gracefully. You give this world a project of high quality and openness.
Then people start using your project. You are excited and surely your pride is dancing with delight.
And then there are bugs - you need to fix it. The more people the more feedback and certainly more bugs.
Fixing bugs is not so fun. Especially if they are difficult to reproducible or require ugly solutions from you.
This is far from fun.
You receive a large number of letters. To rake a bug report and to manage the issue tracker this is sad.
Patches come. Review is cool when you send good code. Or an interesting solution. But often it will be so-so. Or very bad. And then code review is longing.
Support for an open source project is not fun. It's hard and boring
3. Pull Requests or Patches
Everyone loves open source for community input. I can definitely say that a definite plus.
It would seem good when people send you pull ricksta.
But pull ricksta:
* often bad. And not always because the developer is bad. He just might not completely figure out your project.
* there are such
* require review, testing and still end up missing something. And then correct and swear.
* eat your time
* This is the code that you will then have to support.
As a result, you do not even want to open a tab with Pull Requests.
4. Community
We love open source because it's a community of developers like us.
You can divide the community into adequate people and not very much.
And the latter will have to deal more often.
“Make me this feature. Otherwise I will use another project. ”
"Without this functionality, this project is useless"
“You do everything wrong. Give us the project otherwise you'll ruin it. ”
"Your code sucks, we will write everything much better"
“I did not do everything according to the instructions. Why does nothing work for me? I hate you"
"You must...."
"I demand...."
And you are sitting like that - “wtf?”
It seems to be doing a good job, but here you owe someone already.
Total this turns into a job. But for which you do not pay.
Therefore, when you meet a bug or govnokod in an open source project - treat the authors with politeness and understanding.
They are already suffering.
In addition, you can then measure the number of commits in rails and ask for more wages.
And what if you decide to write your open source project?
')
It's a little different here. But it would seem that in this bad?
I wrote a library or application, flooded it with a githab and great.
And it's really great if this is a simple library with a couple of bugs and hundreds of users.
Once a month I wrote to issues, once a year I updated the version - everyone is happy.
And if the project is complex and even became popular? Here everything is bad.
Who does not know me - I am the author of the open source project GitLab .
In fact, this is a web application for hosting git-repositories inside a closed infrastructure.
For information, you can read this post .
It is in the Popular Starred Repositories github on the first page so it’s an example for this.
So given:
Project: GitLab
Number of githubs per day: 30-40
Installations: 40k +
1. Time
Time is a resource extremely limited in the life of the developer.
What is your open source project in terms of your time?
* This is a time to read the wishes, bug reports
* this is the time to develop and maintain the code
* This is the time to review pull ricks or patches
* This is the time for revision and fixes after these patches.
* this is the time for discussion and support
Total you are sitting at 11 pm for a laptop at home and your wife looks at you angrily
2. Fun
Great feeling to write an open source project. You choose the technologies that suit you, write without haste, beautifully and gracefully. You give this world a project of high quality and openness.
Then people start using your project. You are excited and surely your pride is dancing with delight.
And then there are bugs - you need to fix it. The more people the more feedback and certainly more bugs.
Fixing bugs is not so fun. Especially if they are difficult to reproducible or require ugly solutions from you.
This is far from fun.
You receive a large number of letters. To rake a bug report and to manage the issue tracker this is sad.
Patches come. Review is cool when you send good code. Or an interesting solution. But often it will be so-so. Or very bad. And then code review is longing.
Support for an open source project is not fun. It's hard and boring
3. Pull Requests or Patches
Everyone loves open source for community input. I can definitely say that a definite plus.
It would seem good when people send you pull ricksta.
But pull ricksta:
* often bad. And not always because the developer is bad. He just might not completely figure out your project.
* there are such
* require review, testing and still end up missing something. And then correct and swear.
* eat your time
* This is the code that you will then have to support.
As a result, you do not even want to open a tab with Pull Requests.
4. Community
We love open source because it's a community of developers like us.
You can divide the community into adequate people and not very much.
And the latter will have to deal more often.
“Make me this feature. Otherwise I will use another project. ”
"Without this functionality, this project is useless"
“You do everything wrong. Give us the project otherwise you'll ruin it. ”
"Your code sucks, we will write everything much better"
“I did not do everything according to the instructions. Why does nothing work for me? I hate you"
"You must...."
"I demand...."
And you are sitting like that - “wtf?”
It seems to be doing a good job, but here you owe someone already.
Total this turns into a job. But for which you do not pay.
Therefore, when you meet a bug or govnokod in an open source project - treat the authors with politeness and understanding.
They are already suffering.
Source: https://habr.com/ru/post/169339/
All Articles