Under a cat interesting poll
Perhaps, the heading of this article will seem to you not correct," As it is possible to write open-source a code? And what the code such is?" — you ask.
What open-source the code differs from "simply in - a code"? Open-source the project is responsibility for quality of a code, for a covering its tests, for documentation, for timely answers to questions and response to bug contango, for processing of pull-request. Your behavior and thoughts in a time of writing of open-source of a code which will see the world will be others, respectively and the code on an output turns out another.
Open-Source the project lives life — life of community which is formed around the project. Ideas, responses, bug contango, discussion and thanks from other associates influence you and the project directly, and stimulate writing of a code — clear, documentary and covered with tests.
Once, having laid out the code on GitHub, I any more not a smog will stop. The PHP-code intended for internalization on the basis of table MySQL was my first public repository. This repository did not collect stars and it is doubtful that by someone it was noticed. Not in stars business the matter is that your code is available to all. Your code is not hidden on the server, not minifitsirovan/aglifitsirovan in the browser and is not compiled on the hard drive of the user — it is exposed to all on demonstration. Understanding of this fact simply obliges you to write a code in the commonly accepted manner (on which according to that language you write), to observe indents, to add the description to methods and classes (at least to public), to name adequately variables, classes, methods and functions, to follow the rule do-not-repeat-yourself.
I am sure that the code published by me is useful to other developers exactly on as much, as well as me. Publishing a code, I not only impart experience with the world, but also I will be self-organized exactly on as much, as well as my code will be organized.
To write a public code is how to visit secular actions. You look, talk and conform to the highest IT industries standards, or at least aim at them. To write a public code is how to discuss functionality IT collective equal on scale to all IT community of the planet. Any of members of open-source of community can offer changes, report about bug'e and submit further development of the project for discussion.
Pleasant in open-source projects are emotions and the feelings felt from understanding that your project is useful. When the number of downloads grows up when you receive comments when people from all over the world join the project and you together do the project is better for the sake of what it is worth writing a code. At this moment simple writing of a code for a solution of objectives develops into a contribution to IT community.
About concerns of Studios and Companies:
Your company writes a code? You consider that the written code belongs only to you and to your clients who paid for it? If your answer — "yes", approach your developers and ask to consider how many code lines are written behind walls of your company the third party, GitHub is downloaded with SourceForge, it is set through NPM, apt-get, aptitude, and other sources of distribution of a code.
When it is about open-source, many heads (not all, but such is) consider that on GitHub the whole projects ready to use and earning money lie. When your employees suggest to be published on GitHub, they are going "to merge" all code for which developers got paid, and someone other (bad) will collect a clone of your product and will earn money. Or it is worse than that, will find an exploit and will secretly use it. It absolutely not so. First, nobody needs your project entirely except you and your client, secondly — it is not necessary to spread projects entirely. Small pieces, classes, methods, adapters, etc. of which your project consists can be useful not only to you. The IT community will answer your contribution with search and correction of errors and vulnerabilities, addition of functionality and improvement of performance. Perhaps, you will find the new employee on behalf of an active kontribyyutor.
Open-source project it:
- Live emotions, communication with people worldwide.
- Access to the accumulated knowledge and the previous saved-up experience.
- Maximum and exacting approach to writing of a code, documentation and tests.
- Collaboration over a task.
- Openness before ultimate users.
In the Universe where people did not learn to work in open-source community, there is no opportunity to make use of the previous saved-up experience of the IT industry and to accumulate it. In turn, the IT companies select the most part of the budget for paid software. And for the purpose of economy on purchase and subscriptions to software — write the solutions that causes growth of staff of developers in tens of times, ready to carry out tasks from writing of OS and frameworks to text editors in which this code is written. It is good that in our Universe of open-source the community actively develops and it does not threaten us.
Spread your code. Spread the code written in the company (from the agreement of all heads). Make a contribution to development of the IT industry. Read others code. Improve others code. Always write bug contango. Ask questions to owners of projects and do not forget to answer the questions asked you. Thanks.
The users only registered can participate in poll. Enter, please.
This article is a translation of the original post at habrahabr.ru/post/274791/
If you have any questions regarding the material covered in the article above, please, contact the original author of the post.
If you have any complaints about this article or you want this article to be deleted, please, drop an email here: email@example.com.
We believe that the knowledge, which is available at the most popular Russian IT blog habrahabr.ru, should be accessed by everyone, even though it is poorly translated.
Shared knowledge makes the world better.