<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi,<br>
<br>
On 07.09.2015 08:19, Ryan Li wrote:<br>
<blockquote cite="mid:SNT149-W138054C4A95733B173269FF6540@phx.gbl"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr">I think a documentation project sounds like a great
idea, except do you happen to have a place to start, in terms of
what hasn't been covered yet? Anything where I could contribute
to the hackers guide or modules docs?<br>
</div>
</blockquote>
<br>
Maybe a trivial suggestion, but have you already skimmed through the
Hacker Guide on the wiki?<br>
<br>
<a class="moz-txt-link-freetext" href="https://wiki.videolan.org/Hacker_Guide/">https://wiki.videolan.org/Hacker_Guide/</a><br>
<br>
There seem to be at least some some module types that have not been
documented yet, so that's one possible place to start.<br>
<br>
Another approach is to pick a feature you want to develop (or a bug
you want to fix), read what already exists on the wiki, study the
source, and then write any missing documentation as you go along. I
did this for video filters and the deinterlace module after
implementing IVTC and Phosphor some years ago. The people on this
list were very helpful.<br>
<br>
Also, the Developer's Corner on the wiki has more links to existing
documentation - you could see if you spot something that you think
should be documented but currently isn't.<br>
<br>
<a class="moz-txt-link-freetext" href="https://wiki.videolan.org/Developers_Corner/">https://wiki.videolan.org/Developers_Corner/</a><br>
<br>
<br>
-J<br>
<br>
</body>
</html>