{"id":508,"date":"2015-09-10T02:51:42","date_gmt":"2015-09-10T02:51:42","guid":{"rendered":"http:\/\/blogs.gentoo.org\/lu_zero\/?p=508"},"modified":"2015-12-06T13:43:59","modified_gmt":"2015-12-06T13:43:59","slug":"libav-the-project","status":"publish","type":"post","link":"https:\/\/blogs.gentoo.org\/lu_zero\/2015\/09\/10\/libav-the-project\/","title":{"rendered":"Libav: The project"},"content":{"rendered":"

\n This is a tiny introduction to Libav, the organization.\n<\/p><\/blockquote>\n

Libav<\/h2>\n

The project aims to provide useful tools, written in portable code that is readable<\/strong>, trustworthy<\/strong> and performant<\/strong>.<\/p>\n

Libav<\/a> is an opensource organization focused on developing libraries and tools to decode, manipulate and encode multimedia<\/strong> content.<\/p>\n

Structure<\/h3>\n

The project tries to be as non-hierarchical<\/strong> as possible. Every contributor must abide by a well defined set of rules<\/strong>, no matter which role<\/strong>.<\/p>\n

For decisions we strive to reach near-unanimous consensus<\/a>. Discussions may happen on irc<\/a>, mailing-list<\/a> or in real life meetings<\/a>.<\/p>\n

If possible, conflicts<\/strong> should be avoided and otherwise resolved<\/a>.<\/p>\n

Join us!<\/h2>\n

We are always looking for enthusiastic new contributors and will help you get started. Below you can find a number of possible ways to contribute. Please contact<\/a> us.<\/p>\n

Roles<\/h2>\n

Even if the project is non-hierarchical, it is possible to define specific roles within it. Roles do not really give additional power<\/strong> but additional responsibilities<\/strong>.<\/p>\n

Contributor<\/h3>\n

\n Contributing to Libav makes you a Contributor!
\n Anybody who reviews<\/strong> patches, writes patches, helps triaging bugs, writes documentation, helps people solve their problems, or keeps our infrastructure running is considered a contributor.\n<\/p><\/blockquote>\n

It does not matter how little you contribute. Any help is welcome.<\/p>\n

On top of the standard<\/a> great feats of contributing to an opensource project, special chocolate<\/a> is always available during the events.<\/p>\n

Reviewer<\/h3>\n

\n Many eyes might not make every<\/strong> bug shallow, but probably a second and a third pair might prevent some silly mistakes.\n<\/p><\/blockquote>\n

A reviewer is supposed to read the new patches and prevent mistakes (silly, tiny or huge<\/strong>) to land in the master.<\/p>\n

Because of our workflow<\/a>, spending time reading other people patches is quite common.<\/p>\n

People with specific expertise might get nagged to give their opinion more often than others, but everybody might spot something that looks wrong and probably is.<\/p>\n

Bugwrangler<\/h3>\n

\n Checking that the bugs<\/a> are fixed and ask for better reports is important.\n<\/p><\/blockquote>\n

Bug wrangling<\/a> involves making sure reported issues have all the needed information to start fixing the problem and checking if old issues are still valid or had been fixed already.<\/p>\n

Committer<\/h3>\n

\n Nobody can push a patch to the master until it is reviewed, but somebody has to push it once it is.\n<\/p><\/blockquote>\n

Committers are the people who push code to the main repository after it has been reviewed.<\/p>\n

Being a committer requires you to take newly submitted patches, make sure they work as expected either locally or pushing them through our continuous integration system<\/a> and possibly fix minor issues like typos.<\/p>\n

Patches from a committer<\/strong> go through the normal review<\/strong> process as well.<\/p>\n

Infrastructure Administrator<\/h3>\n

The regression test system<\/a>. git<\/a> repository, the samples collection<\/a>, the website<\/a>, the patch<\/a> trackers<\/a>, the wiki<\/a> and the issue tracker<\/a> are all managed on dedicated hardware.<\/p>\n

This infrastructure needs constant maintaining and improving.<\/p>\n

Most of comes from people devoting their time and (beside few exceptions) their own hardware, definitely this role requires a huge amount of dedication<\/strong>.<\/p>\n

Rules<\/h2>\n

The project strives to provide a pleasant<\/strong> environment for everybody.<\/p>\n

Every contributor<\/strong> is considered a member of the team, regardless if they are a newcomer or a founder. Nobody has special<\/strong> rights or prerogatives.<\/p>\n

Well defined rules have been adopted since the founding of the project to ensure fairness.<\/p>\n

Code of Conduct<\/h3>\n

A quite simple code of conduct<\/a> is in place in our project.<\/p>\n

\n It boils down to respecting<\/strong> the other people and being pleasant to deal with.\n<\/p><\/blockquote>\n

It is commonly enforced<\/strong> with a friendly warning, followed by the request to leave if the person is unable to behave and, then, eventual removal if anything else fails.<\/p>\n

Contribution workflow<\/h2>\n

The project has a simple contribution workflow<\/a>:<\/p>\n