Sonntag, 6 Mrz 2011

FreeBSD needs fresh Blood!

Oh well, it’s time to write some nice job offer, of course it’s all
for free, and you can’t earn any money out of it, but you’ll get a
big thanks, hugs and love from the community. Ask your self, how
long have you been using FreeBSD. Months? Years? Decades? And you
love using it because of whatever reason but at the same time
you’re feeling a bit guilty to use it all for free without giving
anything back? Well now you’ll have the chance to change that.
We at FreeBSD are always in need of new people who are willing
to spare some of their time and effort into FreeBSD development.

Let me share a bit of my experience. I have (re)built a lot of
teams in the past, such as gecko@, kde@, python@, and I was
involved in the creation of FreeBSD vbox@ team. I have always
managed to get assistance from a lot of people, but recently more
and more people have started to complain about the slowness,
broken commits and requested for more Call for Testing. And that
is actually a big problem. I am the kind of person who like to
call for test, but I am also the kind of person who easily gets
disapointed when I’m not getting much feedbacks. The best example
here is ATI, Xorg and Xfce update. I did a call for testing because
Xorg and Driver updates is always a big issue because there are so
many different hardware involved with various configurations. From
the call for testing, we managed to get a total of 19 mails of
positive feedback and after 2 weeks I’ve committed the update.
What happened after that was I received a lot of complains for
not conducting much testing, yadda, yadda. Well I say it ain’t
my fault for not testing much, but it is also your fault for not
helping us. It is always easy to blame instead of helping. Ask
yourself why have you not helped us in testing properly and give
us feedbacks. Complaining is fine when it is done in the right
way, with the right tone.

While I’m talking about Xorg, the FreeBSD Xorg Team is currently
a one man show effort, supported by kwm@ and fluffy@. Xorg alone
is too big to get worked on. Plus you should not think that it is
affecting the ports only, but it affects the kernel as well, which
we are having the most problems at the moment. And of course I
would like to call for help on that as well. Based on my last call
for help, it is funny to see how many people wanted to offer some
help, but after knowing the amount of work involved, I have stopped
hearing from these guys. I understand that to update Xorg is always
a crappy job but I love doing it, because it is nice to get more and
more experience in understanding how things work, and it helps to
improve my skills a lot.

Lets a talk a bit about our FreeBSD KDE Team. KDE is nice, but it
really is a fat project. It needs a lot of love, and maintenance
time. Currently it’s a 4 people project, namely makc@, fluffy@ and
avilla@. While for support Raphael Kubo da Costa is handling it
actively. The thing is, KDE involves more than just KDE packages.
It includes Qt, PY-Qt, KOffice and Cmake as well. It is a big
project too and it would be nice to find more people to contribute
in the development.

And now lets talk about gecko@. gecko@ includes all Mozilla Project,
namely Firefox, Thunderbird and Seamonkey. It is currently maintained
by beat@ and decke@, and supported by flo@ and andreas. So again,
I’d like to see some fresh faces for this project as well. If you are willing
to help, do ping us via mail :p.

As for FreeBSD Gnome Team, well I can’t say much about gnome but
whenever I see the cvs commits in marcuscome tree, it seems like
most work for the upcoming gnome3 is done by kwm@, and supported
by marcus@, mezz@ and avl@. Gnome includes not only Gnome things
but it also include gtk and cairo, the one that always cause
problems in a major update. I think the team would love to have
some fresh blood in the team.

Okay, all of these need an understanding of programming and
scripting. If you think that you can’t do any of that, testing would
also help much. FreeBSD is one of the best documented open source
project, so that’s another area that could use some help too. Check
if is available in your language, or start helping to
improve the FreeBSD documents in your language. It would be very
helpful and the community will thank you for that. So if you would
like to offer some help, ping me in irc/jabber/mail 🙂

– Martin

62 Responses to “FreeBSD needs fresh Blood!”

  1. FreeBSD needs fresh blood | FreeBSD News Says:

    […] to use it all for free without giving anything back? Well now you’ll have the chance to change that. We at FreeBSD are always in need of new people who are willing to spare some of their time and […]

  2. Rhyous » Blog Archive » Project ideas for FreeBSD Says:

    […] I just read this post and I am quite in agreement with it: FreeBSD needs fresh Blood! […]

  3. El proyecto FreeBSD necesita sangre nueva Says:

    […] Wilke en su blog (el cual juega un papel importante en el proyecto FreeBSD) en el cual menciona que el proyecto necesita “sangre nueva” y que todos los usuarios podemos aportar para que esto […]

  4. Adam Says:


    FreeBSD needs improvement with their ACPI support, I have very hit or miss luck on laptops for suspend. Hopefully dynamic ticks will be ready soon, too. This could potentially increase my battery life.

  5. Rhyous » Blog Archive » What is the FreeBSD plan? Says:

    […] I don’t know what the FreeBSD plan is. Unfortunately, I feel that if there is one, it is not a very well-rounded on. Maybe it only focuses on development and might not have a big focus on also important tasks like advertising and marketing, documentation, and acquiring new committers.  All of which is important because I am not the only that thinks that FreeBSD needs fresh Blood! […]

  6. Andrew Says:

    Yeah, i really like freebsd cause of community and ideology behind written code. And i really got thoughts to contribute some „usefulness“. Hope i will join soon.

  7. mgp Says:

    I also think projects like Xorg, KDE, Gnome, firefox, etc… need to be more aware of the other operating systems, not only Linux. After all it’s not the operating systems‘ responsibility to support e.g. KDE it is/should be the other way round! This is the root cause of all problems related to running these projects on platforms other than Linux.
    If, for example, the KDE guys cared as much for FreeBSD as they do for Linux this post wouldn’t exist, right?

    And still the job that FreeBSD developers do is nothing short of fantastic!

  8. kkchn Says:

    Hi Martin,

    I am using FreeBSD since version 6.0, for our hosting purposes in our data centre. I know C and python programming. I am interested with kernel modules and kernel fix and patches. Do you think is there a space for me in the FreeBSD kernel development program, as a volunteer. I would like to hear from you.

  9. FreeBSD needs fresh Blood! | Linux Info Says:

    […] FreeBSD needs fresh Blood! Posted in freebsd ati | Tags: gecko, job offer, money, python […]

  10. EmailisBest Says:

    please never use git or hg … just use fossil-scm … soooo easy for devs to have their own testing/patching/repos and then exchange patches.

    BSD licensed too. All it needs is some integration into the mailing lists and documentation building and voila perfection.

  11. Chris Telting Says:

    Some ideas.

    I think Freebsd needs to restructure it’s recruitment effort and it’s fan-base. And much as I hate to even bring it up I think it needs to embrace social media. Associate faces to names. Break down the barriers between kernel and user space so to speak.

    Start with a public server open to all with forums, blogs, and wiki’s all dedicated to Freebsd. Follow in the footsteps of the „Freebsd Diary“. People write blog entries for their own benefit. They can write about their hiccups and solutions with Freebsd. Maybe have an option to let it be private for the shy.

    Have people tag the apps they are most interested in. Then have tag based forums and transition to them form the traditional bloated mailing lists. When you click on a persons name your taken to a picture of them and their blog.

    Do stupid stuff like merit and skill badges that people can earn for their profile to show and prove their support. Complete a task on a VPS and you earn the badge to prove your knowledge/ability/qualifications and for certain skills you have to retest every so often. It’s turns the whole thing into a game.

    Stick to beta testing for six months, get a merit badge. A persons Freebsd profile could actually serve as proof of competence and as a reference for job applications. Hire people that have a know track record beta testing the applications you need to keep running.

    So in your situation you would start off by testing/train to download/compile a couple example builds and submit bug reports. There is a big difference between being able to do a thing and having already done it. Take the mystery away and they can learn it in a couple days at their leisure and then when it comes time for testing it will only take a couple hours on a Sunday morning.

    Just some food for thought.

  12. FreeBSD einmal zur Sicherheit: pfSense | Seraphyn Blog Says:

    […] Fehler zu suchen und zu melden, kann sich auf alle Fälle an FreeBSD wenden, denn jene suchen im Moment frische Blut. Und wer der Meinung ist, dass BSD ein wenig Linux im Desktop nachzieht und nichts kann sei doch […]

Leave a Reply