Linked by Thom Holwerda on Tue 14th Sep 2010 22:42 UTC
Thread beginning with comment 441277
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[10]: You obviously don't get open source
by Panajev on Fri 17th Sep 2010 09:11
in reply to "RE[9]: You obviously don't get open source"
"Doing stuff != collaborating. Collaborating requires code contributions, everything else is specific to Ubuntu; ads, forums, papercuts, blog posts, UI design, art-work, etc. All those benefit only Ubuntu.
"Collaborating requires code contributions"... So, no other kind of collaboration is actually collaboration, only the kind _you_ want? If I wrote a 500 page book for newcomers to Linux it wouldn't be beneficial to the community and I should rather just write code? That is a REALLY narrow way of seeing things.
"Collaborating requires code contributions"... So, no other kind of collaboration is actually collaboration, only the kind _you_ want? If I wrote a 500 page book for newcomers to Linux it wouldn't be beneficial to the community and I should rather just write code? That is a REALLY narrow way of seeing things.
A book is not collaboration [...] "
... sigh... If other "tasks" do not get equal respect to coding, it is bad for the whole OSS ecosystem. The concept of "a system made by coders for coders", taken to its extremes, is not helping...
RE[11]: You obviously don't get open source
by felipec on Sat 18th Sep 2010 02:28
in reply to "RE[10]: You obviously don't get open source"
... sigh... If other "tasks" do not get equal respect to coding, it is bad for the whole OSS ecosystem. The concept of "a system made by coders for coders", taken to its extremes, is not helping...
You can argue all you want, but that doesn't change the definition of the word collaboration:
1. The act of working together; united labor.
2. the act of willingly cooperating with an enemy, especially an enemy nation occupying one's own country.




Member since:
2007-09-25
"Collaborating requires code contributions"... So, no other kind of collaboration is actually collaboration, only the kind _you_ want? If I wrote a 500 page book for newcomers to Linux it wouldn't be beneficial to the community and I should rather just write code? That is a REALLY narrow way of seeing things.
A book is not collaboration, unless it's actually developed by many parties like a wiki, and it's a pretty small contribution, unless it's given away for free. Ubuntu hasn't done a book, BTW.
The thing you are not getting is that they do it for their own benefit, the fact that it might help others is a side-effect, it cannot be called a contribution if they never intended it that way.
For example, if a Fedora artist designs a wallpaper with two versions, one with a Fedora logo, and one without a logo, so other distributions can put their logo there, that can be called a contribution to the linux community, because he did it with other distributions in mind. When an Ubuntu artist designs a wallpaper specifically for Ubuntu, with only one version, that features a logo of Ubuntu, that cannot be called a contribution. Similarly, if he just happened to not put a logo, it can hardly be called a contribution.
Some Ubuntu people do make contributions, but not Canonical.