OSE Principles of Open Culture: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
OSE Principles of Open Culture build upon the [[Shuttleworth Foundation Principles of Open Culture]]. Further, from an operational standpoint, I observe: | OSE Principles of Open Culture build upon the [[Shuttleworth Foundation Principles of Open Culture]]. Further, from an operational standpoint, I observe: | ||
#There are two types of people: those with Open Culture and those in the old guard. I have seen a number of well-meaning people who are the most friendly and progressive, yet who are missing the basic concept that publishing information in the unfinished/development/process stage is useful to promote collaboration. | #There are two types of people: those with Open Culture and those in the old guard. I have seen a number of well-meaning people who are the most friendly and progressive, yet who are missing the basic concept that publishing information in the unfinished/development/process stage is useful to promote collaboration. I have seen examples where an individual was presenting technical information for my eyes only, and I requested that if they are not willing to share the document in question openly, then I am not interested in looking at it myself. My reason is that my team is the world. I share documents openly in general - as that allows me to obtain wide and immediate review - and not only from our core team, but from random contributors all over the world. If I am not able to share information openly, I am not able | ||
Revision as of 14:43, 4 October 2012
by Marcin
OSE Principles of Open Culture build upon the Shuttleworth Foundation Principles of Open Culture. Further, from an operational standpoint, I observe:
- There are two types of people: those with Open Culture and those in the old guard. I have seen a number of well-meaning people who are the most friendly and progressive, yet who are missing the basic concept that publishing information in the unfinished/development/process stage is useful to promote collaboration. I have seen examples where an individual was presenting technical information for my eyes only, and I requested that if they are not willing to share the document in question openly, then I am not interested in looking at it myself. My reason is that my team is the world. I share documents openly in general - as that allows me to obtain wide and immediate review - and not only from our core team, but from random contributors all over the world. If I am not able to share information openly, I am not able