On Fri, 12 Sep 2014 15:27:00 -0800 Lou Logan <l...@lrcd.com> wrote: > Also slightly reorder mailing lists by "category" of development, user > help, then logs. > > Also link some phrases to relevant pages. > > Signed-off-by: Lou Logan <l...@lrcd.com> > --- > src/contact | 25 ++++++++++++------------- > 1 file changed, 12 insertions(+), 13 deletions(-) > > diff --git a/src/contact b/src/contact > index 640ae58..2d0d09e 100644 > --- a/src/contact > +++ b/src/contact > @@ -32,30 +32,29 @@ > </div> > <br> > <div class="list-group"> > + <a class="list-group-item" > href="https://lists.ffmpeg.org/mailman/listinfo/ffmpeg-devel/"> > + <strong>ffmpeg-devel</strong><br> > + For discussions involving development of FFmpeg. Patches for > FFmpeg should be submitted > + here. It is <strong>not</strong> for development of software that > use the FFmpeg libraries > + and <strong>not</strong> for <a href="bugreports.html">bug > reports</a>. > + </a>
I think inexperienced/new people would still get confused by this: what if they have found a bug, but also made a patch that fixes it? ffmpeg-devel says not to report bugs. TRAC says not to post patches. > <a class="list-group-item" > href="https://lists.ffmpeg.org/mailman/listinfo/ffmpeg-user/"> > <strong>ffmpeg-user</strong><br> > - This list is for regular user questions and discussions including > usage of > - <code>ffmpeg</code>, <code>ffplay</code>, <code>ffprobe</code>, and > - <code>ffserver</code> > + For general user questions and discussions involving the FFmpeg > cli tools: > + <code>ffmpeg</code>, <code>ffplay</code>, <code>ffprobe</code>, > and <code>ffserver</code>. > </a> > <a class="list-group-item" > href="https://lists.ffmpeg.org/mailman/listinfo/libav-user/"> > <strong>libav-user</strong><br> > - This list is for application developer questions about development > using the > - FFmpeg libraries > - </a> > - <a class="list-group-item" > href="https://lists.ffmpeg.org/mailman/listinfo/ffmpeg-devel/"> > - <strong>ffmpeg-devel</strong><br> > - This list is for development of FFmpeg itself. It is > <strong>not</strong> for > - development of software that use the FFmpeg libraries and > <strong>not</strong> > - for bug reports > + For questions about using the FFmpeg libraries and API. > </a> > <a class="list-group-item" > href="https://lists.ffmpeg.org/mailman/listinfo/ffmpeg-cvslog/"> > <strong>ffmpeg-cvslog</strong><br> > - This list gets all changes to the FFmpeg sources / main git > repository. > + A log of all changes and updates made to the FFmpeg source. > </a> > <a class="list-group-item" > href="https://lists.ffmpeg.org/mailman/listinfo/ffmpeg-trac/"> > <strong>ffmpeg-trac</strong><br> > - This list gets all changes to the FFmpeg Trac issue tracker. > + Receives all bug reports, comments, and status changes made on the > + <a href="https://trac.ffmpeg.org/">FFmpeg Bug Tracker</a>. > </a> > </div> <!-- list-group --> > </div> <!-- col --> _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel