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
a67a96a0
Commit
a67a96a0
authored
Aug 07, 2006
by
Diego Biurrun
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
editorial changes
Originally committed as revision 5942 to
svn://svn.ffmpeg.org/ffmpeg/trunk
parent
4f9807d8
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
9 additions
and
9 deletions
+9
-9
soc.txt
doc/soc.txt
+9
-9
No files found.
doc/soc.txt
View file @
a67a96a0
Google Summer of Code and similar project guidlines
Google Summer of Code and similar project guid
e
lines
Summer of
code is a project by g
oogle in which students are paid to implement
Summer of
Code is a project by G
oogle in which students are paid to implement
some nice new features for various participating open source projects ...
This text is a collection of things to take care of
f
for the next soc as
it
s a little late for this years soc (2006)
This text is a collection of things to take care of for the next soc as
it
's a little late for this year's soc (2006).
The Goal:
Our goal in respect to soc is and must be of course exactly one thing and
that is to improve FFmpeg, to reach this goal, code must
* conform to the svn policy and patch submission guidlines
* must improve
ff
mpeg somehow (faster, smaller, "better",
* conform to the svn policy and patch submission guid
e
lines
* must improve
FF
mpeg somehow (faster, smaller, "better",
more codecs supported, fewer bugs, cleaner, ...)
for mentors and other developers to help students to reach that goal it is
essential that changes to their codebase are public
ally vis
sible, clean and
essential that changes to their codebase are public
ly vi
sible, clean and
easy reviewable that again leads us to:
* use of a revision control system like svn
* sep
eration of cosmetic from non cosmetic changes (this is almost entir
ly
* sep
aration of cosmetic from non-cosmetic changes (this is almost entire
ly
ignored by mentors and students in soc 2006 which might lead to a suprise
when the code will be reviewed at the end before a possible inclusion in
ffmpeg, individual changes where generally not reviewable due to cosmetics)
FFmpeg, individual changes were generally not reviewable due to cosmetics).
* frequent commits, so that comments can be provided early
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