Wrong. While it’s not healthy for projects to spend forever arguing about philosophy or politics, community is important for a project to be successful, which is why of the following 2 statements, I prefer the Apache way.
Apache: “community is more important than code”
OpenJDK: “OpenJDK is all about code. Actual bits that do something. The opposite of politics.”
(note, I’m not endorsing any specific ‘politicization’ at OpenJDK, I have no idea who/what is going on there).
Great example. I talk about code. You make it appear I am defining policy for OpenJDK, and then use that policy to criticize OpenJDK. Nothing to do with furthering agendas of course.
I don’t know how to take that comment.
I genuinely don’t have an axe to grind with OpenJDK. Yes, I’m skeptical about it (specifically its governance, especially in the short term) but I have nothing personal to gain by its success or failure (well, actually, as someone who makes a living by writing Java code, I probably do have something to gain if it succeeds and lose if it fails).
I take your point about making it appear that you’re defining policy, but in some sense I hope/believe you are, that’s one of the things I believe open source is about – decisions made by the community, and you’re presenting yourself as part of the community.
More broadly though, it does reflect other statements I’ve seen from others talking about OpenJDK – that people shouldn’t worry about politics and governance because the important thing is that the code is there. If your post was the first thing I’d seen with that sentiment I wouldn’t have commented.
If you don’t think your views reflect the views of many in the OpenJDK community I’ll be happy to update the post to reflect that.