[FFmpeg-devel] [PATCH] web/download: make wording of who has push/commit rights more precisse

Michael Niedermayer michaelni at gmx.at
Mon Jan 13 17:02:50 CET 2014


On Mon, Jan 13, 2014 at 07:34:34AM -0800, Timothy Gu wrote:
> On Jan 13, 2014 6:59 AM, "Michael Niedermayer" <michaelni at gmx.at> wrote:
> >
> > Signed-off-by: Michael Niedermayer <michaelni at gmx.at>
> > ---
> >  src/download |    4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/src/download b/src/download
> > index db43d18..e2f4b7b 100644
> > --- a/src/download
> > +++ b/src/download
> > @@ -123,7 +123,7 @@ developers and groups of developers are available.
> >      <td><a href="http://git.videolan.org/?p=ffmpeg.git">Browse</a></td>
> >      <td><a href="
> http://git.videolan.org/?p=ffmpeg.git;a=snapshot;h=HEAD;sf=tgz
> ">Snapshot</a></td>
> >      <td>Michael Niedermayer</td>
> 
> > -    <td>All FFmpeg developers</td>
> > +    <td>All FFmpeg developers who want to have direct access</td>
> 
> ... who want_s_
> 

> Also how is push access given? It's not documented anywhere. Does a person
> directly ask you for access or do a RFC on ML?

i think theres no formal and documented process
before git everyone got write access pretty much automatically because
with svn direct write access is pretty much neccessary to reasonably
work.
With git its the opposit, direct write access isnt neccessary,
people can just work in their own repository and ask for a merge.
And as a project gets larger more people having direct write access
tends to cause more problems. For example i dont think the linux kernel
would be possible if every linux developer would push directly.

To awnser your question, i think sending me a private mail was the
most common way by which ffmpeg maintainers/developers asked for
direct write access since we use git


> 
> >      <td>Main FFmpeg / libavcodec / libavformat / libavfilter / libavutil
> / libswscale / libswresample git repository, all work is merged in here,
> and it is the recommended repository for users and developers
> >          to use.</td>
> >  </tr>
> > @@ -132,7 +132,7 @@ developers and groups of developers are available.
> >      <td>-</td>
> >      <td>-</td>
> >      <td>Michael Niedermayer</td>
> > -    <td>All FFmpeg developers</td>
> > +    <td>All FFmpeg developers who want to have direct access</td>
> >      <td>Main ffmpeg.org website repository</td>
> >  </tr>
> >  <tr>
> > --
> > 1.7.9.5
> >
> > _______________________________________________
> > ffmpeg-devel mailing list
> > ffmpeg-devel at ffmpeg.org
> > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
> 

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Those who are best at talking, realize last or never when they are wrong.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20140113/a6de8da8/attachment.asc>


More information about the ffmpeg-devel mailing list