Changeset View
Changeset View
Standalone View
Standalone View
documentation/content/en/articles/building-products/_index.adoc
Show First 20 Lines • Show All 217 Lines • ▼ Show 20 Lines | |||||
The best projects to collaborate with are the ones that are __live__; i.e., with an active community, clear goals and a transparent working style. | The best projects to collaborate with are the ones that are __live__; i.e., with an active community, clear goals and a transparent working style. | ||||
* FreeBSD has an active developer community around it. At the time of writing there are many thousands of contributors from every populated continent in the world and over 300 individuals with write access to the project's source repositories. | * FreeBSD has an active developer community around it. At the time of writing there are many thousands of contributors from every populated continent in the world and over 300 individuals with write access to the project's source repositories. | ||||
* The goals of the FreeBSD project are <<Hub1994>>: | * The goals of the FreeBSD project are <<Hub1994>>: | ||||
** To develop a high-quality operating system for popular computer hardware, and, | ** To develop a high-quality operating system for popular computer hardware, and, | ||||
** To make our work available to all under a liberal license. | ** To make our work available to all under a liberal license. | ||||
* FreeBSD enjoys an open and transparent working culture. Nearly all discussion in the project happens by email, on https://lists.freebsd.org/mailman/listinfo[public mailing lists] that are also archived for posterity. The project's policies are link:https://www.FreeBSD.org/internal/policies/[documented] and maintained under revision control. Participation in the project is open to all. | * FreeBSD enjoys an open and transparent working culture. Nearly all discussion in the project happens by email, on link:https://lists.freebsd.org/[public mailing lists] that are also archived for posterity. The project's policies are link:https://www.FreeBSD.org/internal/policies/[documented] and maintained under revision control. Participation in the project is open to all. | ||||
[[freebsd-org]] | [[freebsd-org]] | ||||
=== Understanding FreeBSD culture | === Understanding FreeBSD culture | ||||
To be able to work effectively with the FreeBSD project, you need to understand the project's culture. | To be able to work effectively with the FreeBSD project, you need to understand the project's culture. | ||||
Volunteer driven projects operate under different rules than for-profit corporates. | Volunteer driven projects operate under different rules than for-profit corporates. | ||||
A common mistake that companies make when venturing into the open-source world is that of underplaying these differences. | A common mistake that companies make when venturing into the open-source world is that of underplaying these differences. | ||||
▲ Show 20 Lines • Show All 85 Lines • ▼ Show 20 Lines | |||||
This in turn leads to more bugs and security vulnerabilities being flushed out and performance anomalies being identified and fixed. | This in turn leads to more bugs and security vulnerabilities being flushed out and performance anomalies being identified and fixed. | ||||
Get support effectively:: | Get support effectively:: | ||||
For products with tight deadlines, it is recommended that you hire or enter into a consulting agreement with a developer or firm with FreeBSD experience. | For products with tight deadlines, it is recommended that you hire or enter into a consulting agreement with a developer or firm with FreeBSD experience. | ||||
The {freebsd-jobs} is a useful communication channel to find talent. | The {freebsd-jobs} is a useful communication channel to find talent. | ||||
The FreeBSD project maintains a link:https://www.FreeBSD.org/commercial/consult_bycat/[gallery of consultants and consulting firms] undertaking FreeBSD work. | The FreeBSD project maintains a link:https://www.FreeBSD.org/commercial/consult_bycat/[gallery of consultants and consulting firms] undertaking FreeBSD work. | ||||
The http://www.bsdcertification.org/[BSD Certification Group] offers certification for all the major BSD derived OSes. | The http://www.bsdcertification.org/[BSD Certification Group] offers certification for all the major BSD derived OSes. | ||||
+ | + | ||||
For less critical needs, you can ask for help on the http://lists.FreeBSD.org/mailman/listinfo[project mailing lists]. | For less critical needs, you can ask for help on the link:https://lists.freebsd.org/[project mailing lists]. | ||||
A useful guide to follow when asking for help is given in <<Ray2004>>. | A useful guide to follow when asking for help is given in <<Ray2004>>. | ||||
Publicize your involvement:: | Publicize your involvement:: | ||||
You are not required to publicize your use of FreeBSD, but doing so helps both your effort as well as that of the project. | You are not required to publicize your use of FreeBSD, but doing so helps both your effort as well as that of the project. | ||||
+ | + | ||||
Letting the FreeBSD community know that your company uses FreeBSD helps improve your chances of attracting high quality talent. | Letting the FreeBSD community know that your company uses FreeBSD helps improve your chances of attracting high quality talent. | ||||
A large roster of support for FreeBSD also means more mind share for it among developers. | A large roster of support for FreeBSD also means more mind share for it among developers. | ||||
This in turn yields a healthier foundation for your future. | This in turn yields a healthier foundation for your future. | ||||
Support FreeBSD developers:: | Support FreeBSD developers:: | ||||
▲ Show 20 Lines • Show All 46 Lines • Show Last 20 Lines |