3 ms·
What's your suggestion? That they should have been more restrictive with the OOo community? Oracle screwed the pooch, not by "allowing" TDF to fork, but by dr
by redthrowaway 16y ago
What's your suggestion? That they should have been more restrictive with the OOo community? Oracle screwed the pooch, not by "allowing" TDF to fork, but by driving them to do so in the first place.
If there's a lesson to be learned here, it's that you need to consider community management a top priority if you're planning on relying on open source for a core business product. Sun managed to annoy the OOo community, but it took Oracle to drive them away.
- ahi 16y agoI think the suggestion was that if you're going to be restrictive with the OOo community, you better be ready to pick up the slack when they fork. By waving the white flag, Oracle demonstrated that their demands of the open source community are likely bluffs. Oracle needs the community more than the community needs them.
- redthrowaway 16y agoI think that's a fair reading of their post, and I agree with the sentiment. The "don't negotiate with terrorists" line is a pretty inflammatory one to use in this context, however.
- masklinn 16y ago> That they should have been more restrictive with the OOo community? That they should learn to engage and nurture their OSS projects/communities (or, alternatively, drop them outright/give them out early to their communities). Right now, they're fucking up on all front: they're creating enmity by locking down projects and behaving as if the project communities were their enemies, and they're still losing the projects to forks.
- theBobMcCormick 16y agoActually, I'd say community management needs to be a top priority for any business product, it's just that for open source the community is a bit broader.