WRT FOSDEM Beer Event

Lots of comments on my last blog entry. Let me make some points clear before you all turn the flamewar to full force.

FIRST I am NOT proposing you turn the beer event into a political demonstration. I do strongly encourage you to go there to have FUN. That’s what I will do. I will be there. Wearing my Fedora. So if you want to flame me for what I say, let’s do it face to face.

SECOND The fact that the developers working on the Android kernel parts seemingly (as pointed out by Greg Kroah-Hartman) have problems with upstreaming their patches is an alarming signal for the Linux community. I hope that Google shows us that I am wrong and they are willing to upstream their changes.

THIRD My call for saying “No, Thanks” to the beer is a pun directing to RMS famous quotes on comparing free beer and free speech.

So in closing: Geez, peeps! FOSDEM is about having fun *and* exchanging opinions. We should have both.

The unique opportunity that a lot of Open Source and Free Software minded people meet at FOSDEM could be a strong signal towards Google that we are there to *help* making things better.

So grab your beer, have fun and flame me if needed. If you want to throw your frustration and anger on me – fine. But I would prefer if you use that energy to get more Android patches upstream.

Deal?

UPDATE

This mail shows you that Google wants to get stuff upstream but ATM (that was in october last year) is limited in doing so..

We (Google) definitely want to get back in sync with mainline (as I’ve mentioned earlier in this or a related thread), and we’re planning on snapping up our kernel trees to 2.6.32+ once we get past various deadlines in the near future.

CC BY 4.0 This work is licensed under a Creative Commons Attribution 4.0 International License.

6 thoughts on “WRT FOSDEM Beer Event”

    1. @ade I come to the beer event for a fun evening. So just chatting and having good civilised conversation is absolutely required 😉

  1. I’m confused about this “[are] they are willing to upstream their changes” point. Of course we are! We’d love to get our code upstream.

    If the upstream response is “we don’t want that, throw it out and use this other thing” (which it is in some cases), we might not just jump at doing that, especially if it requires a huge effort across the entire Android stack to replace something that already works great for us with something somebody else would prefer we use instead.

    We’ve got a lot of work to do and devices to ship and a very small team to do this all with. If mainline says “your code sucks, we don’t want it”, that’s certainly their right, but I then am puzzled about how we become the bad guys here. We’re not refusing to give anybody the code. It’s freely available under GPLv2.

    We have no illusion that things can get upstream without some change and some compromise, but from my perspective this has to be a two way street. If nobody wants to even attempt to meet us halfway, we’re looking at far far more work to rewrite code that mainline doesn’t like than to just keep rebasing our patchsets every other kernel version or so (as we have been since 2.6.14).

Comments are closed.