Difference between revisions of "User talk:Compn"

From MultimediaWiki
Jump to navigation Jump to search
Line 1: Line 1:
Did you end up getting the airbus stock you were after in early 2005? [[User:MovieMan|MovieMan]] 00:45, 14 March 2007 (EDT)
+
==Libav and ffmpeg situation==
 +
my view of the current libav vs ffmpeg situation. august 2014.
  
:No, I did not. I did learn that my stock broker is less than helpful. Maybe its a good thing? A few countries made Airbus orders then cancelled them. Boeing's stock is doing great... http://finance.google.com/finance?q=BA as well as BAE Systems (which used to or still owns a bunch of airbus) [http://finance.google.com/finance?q=LON%3ABA. http://finance.google.com/finance?q=LON%3ABA.] IMO, the stock market is just a big lottery scheme... --[[User:Compn|Compn]] 10:44, 14 March 2007 (EDT)
+
the problems in reuniting our projects are many including technical and personal reasons. here i will attempt to list the problems , maybe someone can solve them?
::The parent company of airbus is EADS http://finance.google.com/finance?q=EPA:EAD. I was simply curious whether you are the same Compn I have seen before elsewhere. [[User:MovieMan|MovieMan]] 16:30, 14 March 2007 (EDT)
+
 
:::i'm the one and only compn, just i didnt get to buy the stock i wanted. i think it was a split of EADS and BAE , or at least it was. maybe i have old information . [[User:Compn|Compn]] 17:16, 14 March 2007 (EDT)
+
this is just my idea of the problems in the projects. i could be 100% wrong. i am not speaking as represenative of anyone else but myself.
 +
 
 +
#some devs will not work together.
 +
##some of these devs have already left (mans, baptiste). more may leave if the projects are merged.
 +
#some devs will work together but not on any servers controlled by the other group.
 +
##has to be neutral 3rd party ground.
 +
##this also probably means that the admin with the final say in arguments has to be 3rd party as well.
 +
#libav and ffmpeg commit rights and developer rules differ.
 +
##in libav its maintainers who are able to commit and in ffmpeg its all contributors (of whom have figured out how to use git).
 +
 
 +
===ideas for reuniting projects===
 +
#corporate/sponsored (google/facebook etc) takeover of the project. with a group of developers committed to working on lav* full time.
 +
##with full time employees working on the project, they could take over a lot of administrative tasks, thus freeing developers up from being public relation, upstream / downstream packagers, bug testers etc.
 +
 
 +
or
 +
#a combined fork of ffmpeg and libav. combining the best parts of both projects. forcing developers from both projects to join the more successful project.
 +
##a combined unified codebase would entice software packages to use it for more stable api.
 +
 
 +
===things the projects are doing to help reunite===
 +
#ffmpeg has opened commit write access to all contributors and has offered any dev to work on #ffmpeg. no contributors or developers are banned.
 +
#libav has offered for any developer to work on libav, including michael nidermayer. michael is currently banned from the libav mailing list and irc channel, so libav is asking someone to submit patches from michael for inclusion into libav.
 +
 
 +
===things you can do to help reunite===
 +
#act as patch liason between the projects.
 +
##some developers in both projects have refused to even talk to each other. you will have to take git commits and test compile them against libav.
 +
##since ffmpeg is merging a lot of commits from libav, most of this job is going to be sending commit patches from ffmpeg to the libav mailing list.

Revision as of 20:00, 10 August 2014

Libav and ffmpeg situation

my view of the current libav vs ffmpeg situation. august 2014.

the problems in reuniting our projects are many including technical and personal reasons. here i will attempt to list the problems , maybe someone can solve them?

this is just my idea of the problems in the projects. i could be 100% wrong. i am not speaking as represenative of anyone else but myself.

  1. some devs will not work together.
    1. some of these devs have already left (mans, baptiste). more may leave if the projects are merged.
  2. some devs will work together but not on any servers controlled by the other group.
    1. has to be neutral 3rd party ground.
    2. this also probably means that the admin with the final say in arguments has to be 3rd party as well.
  3. libav and ffmpeg commit rights and developer rules differ.
    1. in libav its maintainers who are able to commit and in ffmpeg its all contributors (of whom have figured out how to use git).

ideas for reuniting projects

  1. corporate/sponsored (google/facebook etc) takeover of the project. with a group of developers committed to working on lav* full time.
    1. with full time employees working on the project, they could take over a lot of administrative tasks, thus freeing developers up from being public relation, upstream / downstream packagers, bug testers etc.

or

  1. a combined fork of ffmpeg and libav. combining the best parts of both projects. forcing developers from both projects to join the more successful project.
    1. a combined unified codebase would entice software packages to use it for more stable api.

things the projects are doing to help reunite

  1. ffmpeg has opened commit write access to all contributors and has offered any dev to work on #ffmpeg. no contributors or developers are banned.
  2. libav has offered for any developer to work on libav, including michael nidermayer. michael is currently banned from the libav mailing list and irc channel, so libav is asking someone to submit patches from michael for inclusion into libav.

things you can do to help reunite

  1. act as patch liason between the projects.
    1. some developers in both projects have refused to even talk to each other. you will have to take git commits and test compile them against libav.
    2. since ffmpeg is merging a lot of commits from libav, most of this job is going to be sending commit patches from ffmpeg to the libav mailing list.