Difference between revisions of "Community"
Jump to navigation
Jump to search
(Add Mike) |
m (→Companies) |
||
| Line 10: | Line 10: | ||
* [https://canonical.com/ Canonical] employs {{Commits by|Tycho Andersen|tych0}} | * [https://canonical.com/ Canonical] employs {{Commits by|Tycho Andersen|tych0}} | ||
* [https://cloudlinux.com/ CloudLinux] employs {{Commits by|Ruslan Kuprieiev|efiop}} | * [https://cloudlinux.com/ CloudLinux] employs {{Commits by|Ruslan Kuprieiev|efiop}} | ||
| − | * [https://ibm.com/linux IBM] employs {{Commits by|Laurent Dufour|ldu4}} and Mike Rapoport | + | * [https://ibm.com/linux IBM] employs {{Commits by|Laurent Dufour|ldu4}} and {{Commits by|Mike Rapoport|rppt}} |
* [https://google.com/ Google] employs {{Commits by|Filipe Brandenburger|filbranden}} and {{Commits by|Saied Kazemi|SaiedKazemi}} | * [https://google.com/ Google] employs {{Commits by|Filipe Brandenburger|filbranden}} and {{Commits by|Saied Kazemi|SaiedKazemi}} | ||
* [https://codeaurora.com/ CodeAurora] employs Christopher Covington | * [https://codeaurora.com/ CodeAurora] employs Christopher Covington | ||
Revision as of 11:34, 3 August 2016
CRIU is a community-driven project. It started by Virtuozzo kernel engineers in 2011, but the project potential was soon recognized by other companies and individuals and so they became actively involved. This article summarizes the current state of project community.
Companies
This list includes companies and projects whose employees contributed at least 10 patches, and is loosely ordered by the company's contribution amount.
- Virtuozzo employs a number of key developers and provides most of the project infrastructure
- Canonical employs Tycho Andersen
- CloudLinux employs Ruslan Kuprieiev
- IBM employs Laurent Dufour and Mike Rapoport
- Google employs Filipe Brandenburger and Saied Kazemi
- CodeAurora employs Christopher Covington
- Red Hat employs Oleg Nesterov and Adrian Reber
- Samsung, Huawei and others employs minor contributors
- Acronis sponsors a few students working on the project
Get involved
Start with subscribing to the mailing list, where most of the fun is taking place (yes we're old school).
If you are ready to send some actual patches, please don't do so via github, see how to submit patches.
For other ways to be involved, see contacts.