FFmpeg Code-In 2010 - Revision history

Compn: /* FTP Incoming cleanup */

2010-11-03T15:06:28Z

FTP Incoming cleanup

← Older revision		Revision as of 08:06, 3 November 2010
Line 381:		Line 381:

	== FTP Incoming cleanup ==		== FTP Incoming cleanup ==
	We have a incoming directory on FTP where users upload small bits of files that ffmpeg fails with in some way. This directory has over the years become filled with all kinds of things noone knows what they are or why they are there. The tasks below each contain about 50 files that you should figure out where they belong to (that involves searching for matching .txt files on ftp, searching with google, searching IRC logs, searching mailing list archives).		We have a incoming directory on FTP where users upload small bits of files that ffmpeg fails with in some way. This directory has over the years become filled with all kinds of things noone knows what they are or why they are there. The tasks below each contain about 50 files that you should figure out where they belong to (that involves searching for matching .txt files on ftp, searching with google, searching IRC logs, searching mailing list archives, and searching roundup and bugzilla).

	=== Incoming1 ===		=== Incoming1 ===

Stefanosa: Remove pointless "Initial draft page" text.

2010-10-31T15:26:33Z

Remove pointless "Initial draft page" text.

← Older revision		Revision as of 08:26, 31 October 2010
Line 1:		Line 1:
	~~Initial draft page~~



	== Coding Proposals ==		== Coding Proposals ==
	FFmpeg has always been all about code and code quality, we have plenty of [[Interesting Patches]] waiting to be cleaned and committed and lots of [[Small FFmpeg Tasks]] waiting for someone willing to pick them up.		FFmpeg has always been all about code and code quality, we have plenty of [[Interesting Patches]] waiting to be cleaned and committed and lots of [[Small FFmpeg Tasks]] waiting for someone willing to pick them up.

Stefanosa: Add a FFserver documentation task.

2010-10-31T15:24:13Z

Add a FFserver documentation task.

← Older revision		Revision as of 08:24, 31 October 2010
Line 361:		Line 361:

	=== Per-element documentation ===		=== Per-element documentation ===

	We need a separate section in the docs for codec, bitstream filters, formats, and one for the swscale options.		We need a separate section in the docs for codec, bitstream filters, formats, and one for the swscale options.

Line 373:		Line 372:

	Finally ffmpeg-doc.texi should be cleaned up once the per-element documentation has itw own place in a dedicated file.		Finally ffmpeg-doc.texi should be cleaned up once the per-element documentation has itw own place in a dedicated file.

			=== FFserver documentation ===
			FFserver documentation need a thorough cleanup, in particular it needs more complete documentation and all the options currently
			listed in ffserver.conf should be documented in ffserver-doc.texi.

	=== FFmpeg video tutorials ===		=== FFmpeg video tutorials ===

Stefanosa: Add per-element documentation task

2010-10-31T15:18:24Z

Add per-element documentation task

← Older revision		Revision as of 08:18, 31 October 2010
Line 359:		Line 359:

	FFmpeg needs better documentation and is next to unknown to the general public. This section should hold proposals on how to improve the overall perception and experience of non coding users.		FFmpeg needs better documentation and is next to unknown to the general public. This section should hold proposals on how to improve the overall perception and experience of non coding users.

			=== Per-element documentation ===

			We need a separate section in the docs for codec, bitstream filters, formats, and one for the swscale options.

			This should be done possibly following the model of protocols.texi/filters.texi.

			For what regards codecs and muxers/demuxers, there should be a general section explaining the meaning of the common options, and one section
			for each element when the meaning of the parameter is not immediate (e.g. for each encoder the meaning of "quality" may vary) and where there are
			per-codec specific options (as recently added).

			The section on swscale (swscale.texi?) should explain the libswscale options.

			Finally ffmpeg-doc.texi should be cleaned up once the per-element documentation has itw own place in a dedicated file.

	=== FFmpeg video tutorials ===		=== FFmpeg video tutorials ===

Merbanan: /* Developer documentation and tutorial videos */

2010-10-30T02:31:19Z

Developer documentation and tutorial videos

← Older revision		Revision as of 19:31, 29 October 2010
Line 349:		Line 349:
	'''IRC:''' #ffmpeg-devel on Freenode<br>		'''IRC:''' #ffmpeg-devel on Freenode<br>
	'''Mentor:''' Benjamin Larsson (IRC nick: merbanan alt merbzt)<br>		'''Mentor:''' Benjamin Larsson (IRC nick: merbanan alt merbzt)<br>

			* Create a video of how to use Eclipse with FFmpeg
			* Create a video of how to use KDevelop with FFMpeg
			* Create a video of how to add a decoder
			* Create a video of how to add a demuxer
			* Create a video of how to fix a segfault

	== Documentation and Outreach ==		== Documentation and Outreach ==

Michael: 2nd part of warning clarify

2010-10-29T22:53:05Z

2nd part of warning clarify

Show changes

Michael: Part 1 of 2 in fixing the which 10 warnings issue

2010-10-29T22:44:12Z

Part 1 of 2 in fixing the which 10 warnings issue

← Older revision		Revision as of 15:44, 29 October 2010
Line 29:		Line 29:
	=== Fix 10 compiler warnings ===		=== Fix 10 compiler warnings ===
	'''Area:''' coding<br>		'''Area:''' coding<br>
	'''Description:''' Fix 10 compiler warnings ~~generated by compiling ffmpeg with default options~~. Note the code must not become less readable nor slower.<br>		'''Description:''' Fix compiler warnings 1-10 from [http://www1.mplayerhq.hu/~michael/ffmpeg_warning_list1.txt]. Note the code must not become less readable nor slower.<br>
	'''Outcome:''' Post a patch to ffmpeg-dev that passes review<br>		'''Outcome:''' Post a patch to ffmpeg-dev that passes review<br>
	'''Difficulty:''' Depends on your C skillz<br>		'''Difficulty:''' Depends on your C skillz<br>

Multimedia Mike: /* Automated Testing */ promote to a higher section

2010-10-29T15:31:46Z

Automated Testing: promote to a higher section

← Older revision		Revision as of 08:31, 29 October 2010
Line 176:		Line 176:
	'''Mentor:''' To be determined<br>		'''Mentor:''' To be determined<br>

	=== Automated Testing ===		== Automated Testing ==
	'''Area:''' Automated Testing<br>		'''Area:''' Automated Testing<br>
	'''Description:''' FFmpeg uses an extensive, custom framework for automated testing. However, it does not yet cover all of FFmpeg's functionality.<br>		'''Description:''' FFmpeg uses an extensive, custom framework for automated testing. However, it does not yet cover all of FFmpeg's functionality.<br>

Multimedia Mike: /* Automated Testing */ formatting

2010-10-29T15:28:00Z

Automated Testing: formatting

← Older revision		Revision as of 08:28, 29 October 2010
Line 177:		Line 177:

	=== Automated Testing ===		=== Automated Testing ===
	'''Area:''' Automated Testing		'''Area:''' Automated Testing<br>
	'''Description:''' FFmpeg uses an extensive, custom framework for automated testing. However, it does not yet cover all of FFmpeg's functionality.		'''Description:''' FFmpeg uses an extensive, custom framework for automated testing. However, it does not yet cover all of FFmpeg's functionality.<br>
	'''Outcome:''' Use code coverage tools to identify which parts of the codebase are not yet covered by the automated testing system and write tests to cover those missing parts.		'''Outcome:''' Use code coverage tools to identify which parts of the codebase are not yet covered by the automated testing system and write tests to cover those missing parts.<br>
	'''Difficulty:''' easy<br>		'''Difficulty:''' easy<br>
	'''Time:''' a few days<br>		'''Time:''' a few days<br>
	'''IRC:''' #ffmpeg-devel on Freenode		'''IRC:''' #ffmpeg-devel on Freenode<br>
	'''Mailinglist:''' ffmpeg-soc@mplayerhq.hu		'''Mailinglist:''' ffmpeg-soc@mplayerhq.hu<br>
	'''Mentor:''' [[User:Multimedia Mike\|Mike Melanson]]		'''Mentor:''' [[User:Multimedia Mike\|Mike Melanson]]<br>

Multimedia Mike: /* Automated Testing */ description

2010-10-29T15:27:27Z

Automated Testing: description

← Older revision		Revision as of 08:27, 29 October 2010
Line 177:		Line 177:

	=== Automated Testing ===		=== Automated Testing ===
			'''Area:''' Automated Testing
			'''Description:''' FFmpeg uses an extensive, custom framework for automated testing. However, it does not yet cover all of FFmpeg's functionality.
			'''Outcome:''' Use code coverage tools to identify which parts of the codebase are not yet covered by the automated testing system and write tests to cover those missing parts.
			'''Difficulty:''' easy<br>
			'''Time:''' a few days<br>
			'''IRC:''' #ffmpeg-devel on Freenode
			'''Mailinglist:''' ffmpeg-soc@mplayerhq.hu
			'''Mentor:''' [[User:Multimedia Mike\|Mike Melanson]]