blog.pkh.me
The FFmpeg/Libav situation
http://blog.pkh.me/p/13-the-ffmpeg-libav-situation.html
A small freedom area. Sat 30 Jun 2012. One year and a half ago, an important part of FFmpeg developers decided to change the way the project was managed. This led to some kind of takeover. Mainly to get rid of the old maintainer dictatorship, but also to change development methods, redefine objectives, etc. Then, for various reasons I will quickly explain, these people made a new project called Libav. How are MPlayer, FFmpeg, VLC, libav*, etc connected? And a few tools (. MPlayer is basically a GPL video...
hactrn.net
Rob Austein
https://www.hactrn.net/sra
Some folks say a program's the sum of its parts But that ain't so, and debugging's an art Debugging's an art to drive you crazy for good 'Cause your patch never does you thought it would You write 16K and what do you find? You're another day older and further behind Don't y'call me, Saint Peter, 'cause I can't go My code don't run and my compiler's too slow. It doesn't look like I'll ever have time to write a gee-whiz neato keen home page, so you'll just have to make do with this one. During which time I...
matt.sh
Programming Errors at Project Scale
https://matt.sh/programming-errors
Programming Errors at Project Scale. Programming Errors at Project Scale. Errors in Multi-Person Projects. Errors in multi-person projects involve typical programming errors. And, more annoyingly, interpersonal errors. This article is a quick overview of both technical and interpersonal errors we encounter when trying to develop software with more than one person. No literature was consulted. All thoughts are my own delusions. The Seven Errors (Y, Z, A, B, C, D, E). Your program doesn't compile or parse.
book.realworldhaskell.com
Red Bean Stuff
http://book.realworldhaskell.com/stuff.html
Here at Red Bean, we write software the old fashioned way: we steal. It When we can't get what we want from someone else, we write it and then steal it from ourselves. But anyway, it's all free software. So you're free to steal it from us, too. Most of our projects are kept in Subversion. For Subversion projects, obtain the project this way:. Svn checkout http:/ svn.red-bean.com/repos/PROJECTNAME. And for CVS projects, this way:. Our stuff is divided into two categories: serious stuff. An R5Rs scheme imp...
trac.bewelcome.org
DevMailingListRules – BW Rox
http://trac.bewelcome.org/wiki/DevMailingListRules
Apart from the obvious. Requirements, please consider the following before sending an email to the list to save everyone's time. Is your message really of interest for a majority of the 92 readers (December 2012)? Or can the issue be discussed in a smaller group and only the outcome be announced to the list? Get to the point quickly. Use the forum,. Or private messages for chatting. This is a working place. ;). OpenSUSE mailing list guidelines. To keep the mailing list archive small, please upload things...
bumgarner.com
Red Bean Stuff
http://www.bumgarner.com/stuff.html
Here at Red Bean, we write software the old fashioned way: we steal. It When we can't get what we want from someone else, we write it and then steal it from ourselves. But anyway, it's all free software. So you're free to steal it from us, too. Most of our projects are kept in Subversion. For Subversion projects, obtain the project this way:. Svn checkout http:/ svn.red-bean.com/repos/PROJECTNAME. And for CVS projects, this way:. Our stuff is divided into two categories: serious stuff. An R5Rs scheme imp...
gavinsharp.com
Gavin's blog | blog?
http://www.gavinsharp.com/blog
I started contributing to Mozilla nearly 11 years ago, in 2004, and joined as a full-time employee over 8 years ago. Suffice it to say, Mozilla has been a big part of my life in a lot of ways. I’ve dedicated essentially my entire career so far to Mozilla, and it introduced me to my wife. Just to name a couple. Mozilla’s in a great place now – still a tough challenge ahead, but plenty of great people willing and able to tackle it. Firefox has new leadership. I’m looking forward to what’s next! May 19, 2015.