Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Contribute to GitLab
Sign in / Register
Toggle navigation
F
ffmpeg.wasm-core
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Linshizhi
ffmpeg.wasm-core
Commits
743586ff
Commit
743586ff
authored
Aug 23, 2011
by
Michael Niedermayer
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
developer.texi: add Contributing section
Signed-off-by:
Michael Niedermayer
<
michaelni@gmx.at
>
parent
f3fb71f0
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
16 additions
and
0 deletions
+16
-0
developer.texi
doc/developer.texi
+16
-0
No files found.
doc/developer.texi
View file @
743586ff
...
...
@@ -34,6 +34,21 @@ You can use libavcodec or libavformat in your commercial program, but
@emph
{
any patch you make must be published
}
. The best way to proceed is
to send your patches to the FFmpeg mailing list.
@section Contributing
There are 3 ways by which code gets into ffmpeg.
@itemize @bullet
@item Submiting Patches to the main developer mailing list
see @ref
{
Submitting patches
}
for details.
@item Directly commiting changes to the main tree.
@item Commiting changes to a git clone, for example on github.com or
gitorious.org. And asking us to merge these changes.
@end itemize
Whichever way, changes should be reviewed by the maintainer of the code
before they are commited. And they should follow the @ref
{
Coding Rules
}
.
The developer making the commit and the author are responsible for their changes
and should try to fix issues their commit causes.
@anchor
{
Coding Rules
}
@section Coding Rules
...
...
@@ -241,6 +256,7 @@ We think our rules are not too hard. If you have comments, contact us.
Note, these rules are mostly borrowed from the MPlayer project.
@anchor
{
Submitting patches
}
@section Submitting patches
First, read the @ref
{
Coding Rules
}
above if you did not yet, in particular
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment