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 FreeBSD.org 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
Nokia announced the release of Qt 4.5.3 today. It is a bug release version leading up to 4.6.0.
I updated area51 branches/qt-4.5 to 4.5.3. It is not quite ready for general use at this time. Contributors are welcome to check it out and provide patches as needed to make it build.
On a related note, KDE 4.3.2 will be tagged soon, so we need to decide what version of Qt to run with, feedback to [email protected] is appreciated
The FreeBSD KDE team is pleased to announce the first public call to test Qt-4.6.0-tp1. It can downloaded from the area51 repo with the following command
svn co http://area51.pcbsd.org/branches/qt-4.6tp/
Our initial testing has yielded a binary compatibility between 4.6.0 and 4.5.2. Please be aware that this needs more testing.
One other warning, the py-qt* bindings are still a work in progress. Dima Panov, aka fluffy@, is currently working on it.
Please send feedback to [email protected]
This branch was made possible by the hard work of Alberto Villa and other contributors.
The FreeBSD KDE team is pleased to report that Raphael Kubo da Costa has joined the team. He is a KDE contributor, maintaining the ark tool, and a recent convert to FreeBSD
More recently Raphael has been our man in the middle, getting the FreeBSD Qt patches merged upstream to Nokia via Gitorious.
Congratulations and welcome aboard!
Virtually every port *will* require some tender loving care. We are looking to you, our contributors, to hack it and provide the fixes to make it build.
Here are some instructions for testing and preparing patches for
inclusion to the area51 repository.
svn co http://area51.pcbsd.org/branches/qt-4.6tp ./area51
Overlay this area51 directory with your ports tree. I will leave
that as an exercise for you the reader. **HINT** checkout
Now do this
See what breaks, or won’t compile and fix it. It is as easy as that
You can do some recreational reading at
http://doc.qt.nokia.com/4.6-snapshot/installation.html to get some pointers on building the package.
For instance, through initial testing I noticed the plist was wrong
for misc/qt4-doc, so I fixed it and prepared a diff
svn diff pkg-plist > ~/qt4-doc-4.6.0.patch
Mail the patch as an attachment to [email protected], and await
one of our developers to test and include into the repo.
Please note that we have not tested KDE4 builds with Qt 4.6 yet,
so the usual disclaimer applies, “Beware, here be dragons”.
I am pleased to announce the addtion of Alberto Villa to the FreeBSD KDE team. Alberto has been an active contributor on the mailing lists, and now he will be directly contributing to the area51 repository.
Congratulations, and welcome aboard, Alberto!