## page was renamed from comma/Identity/Behavior . '''NOTA BENE - WORK IN PROGRESS''' - [[#Inputs_&_Thoughts|Your Inputs & Thoughts]] :-) . '''To CAcert.org [[Community]]''' - '''To CAcert.org [[comma#CAcert.org_Identity| Identity]]''' ---- == CAcert.org and CAcert Inc. Code of Conduct - Principles of the Community == . Description what is CAcert.org Code of Conduct. It is the unifying part of '''CAcert.org''' '''[[comma#CAcert.org_Identity| Identity]]''' . Today . '''Today's''' [[https://svn.cacert.org/CAcert/CAcert_Inc/Board/oss/oss_sabotage.html| CAcert.org Committee (CAcer Inc. Board)]] Behavior and Working Attitude - Website Version . '''Today's''' [[https://svn.cacert.org/CAcert/CAcert_Inc/Board/oss/OSS_Simple_Sabotage_Manual.pdf| Committee (CAcert Inc. Board) ]] Behavior and Working Attitude - Print Version .pdf Download . '''Today's''' [[https://svn.cacert.org/CAcert/principles.html|Principles]] for the Community might be seen as a prototype for this, cerca 2007. . '''Tomorrow's''' Behavior and Working Attitude should be like described in the CAcert.org Code of Conduct . more about [[http://en.wikipedia.org/wiki/Code_of_Conduct| Code of Conduct]] '' - source: en.wikipedia.org'' . more about [[http://en.wikipedia.org/wiki/Behavior| Behavior]] '' - source: en.wikipedia.org'' <
> == CAcert.org Code of Conduct == . Description / Purpose . Listing <
> ---- == Inputs & Thoughts == . 20090915-[[Iang]] . {{{ === Principles === .In 2007, we drafted the [[https://svn.cacert.org/CAcert/principles.html]] document as a start to clarifying what we thought of behaviour. In those terms, here are some snippets: * We do not discriminate. * We strive to open up as many of our processes as possible. We strive to present our decisions, products and services as transparent. We do not do secret deals. * We do not deceive. We disclose a fair and complete story. We commit to full disclosure of security breaches. We reveal our conflicts of interest, for the community to judge. * We train our users. We train our users to train other users. * If we accept someone in a role, we train, we test, and we support them. The training is provided for free. * When we take on a job, we do it, until we can't. When we cannot do a job, we say so. When we run out of time, we organise a replacement. . The rest of the principles are more about business & product, but are also interesting. Maybe it's time to update the principles? . maybe [[comma#comma_Arrangement| comma Arrangement]] would somehow apply as well... ;-) }}} ---- . 20090915-[[Iang]] . {{{ someone else in this wiki? }}} ---- . 20090915-[[Iang]] . {{{ There are many ways of developing a better working relationship with people. In order to improve personal productivity, I generally suggest a book like this one: ||''The only negotiating guide you'll ever need''||by Stark & Flaherty|| ||(101 ways to win every time in any situation)|| Aside from the awful title, it has the best/only framework which actually makes some sense. E.g., it explains why to follow this approach whereas most books just tell you the what, fluffed up by lots of marketing and blah blah. (Although I only say that this framework is good because it matches my framework :) ) }}} ---- . 20091012-[[Iang]] / UlrichSchroeter . {{{ === Principles AddOn === x. CAcert Assurer Reliable Statement (CARS) We may make a reliable statement to other members of the community, such as in an Assurance. This may be requested of us, and/or it may be appropriate to the circumstances. Where such a statement raises doubt, we readily submit ourselves and our statement to the Arbitrator. We intend that the statement is reliable. ======================== Status: Draft First introduced at Munich-20090517Minitop see https://svn.cacert.org/CAcert/Assurance/Minutes/20090517MiniTOP.html }}} . see also [[comma/Identity/Communications#CAcert_Assurer_Reliable_Statement|Communications, Section CARS]] . see also [[AssuranceHandbook2#CAcert_Assurer_Reliable_Statement|Assurance Handbook 2, Section CARS]] ---- . 20091119-[[hugi]] . {{{ moved from comma main wiki page, as is would make sense this arrangement would be part of Code of Conduct - Principles of the Community == comma Arrangement == . Is a basic agreement of comma teammates, how we will work together in order to execute comma Mission as efficient and as best possible. . '''Behavior''' . '''RESPECT''' your teammates - and your teammates will respect you . '''ACT''' than react . '''COOPERATE''' with your teammates - and your teammates will cooperate with you . '''SUPPORT''' your teammates - and your teammates will support you . '''Leadership''' . '''LEAD''' by example - and your teammates will follow you, if they like . '''PROPOSE''' your Ideas on CAcert.org wiki - than time consuming and confusing e-mail threads . '''Roles & Missions''' . Your role is according to the individual mission you proposed by action . Roles might be varying as your individual missions might be varying . You choose your individual missions, make sure you have at least one . A teammate without an individual mission being part of CAcert.org mission, is like a fish in the desert. . '''Titels''' . Propose one, if helps / supports CAcert.org . Propose one, if it motivates you . More '''background Information about Terms''' used in this comma Section: . more about [[http://en.wikipedia.org/wiki/Behavior| Behavior]] '' - source: en.wikipedia.org'' . more about [[http://en.wikipedia.org/wiki/Leadership| Leadership]] '' - source: en.wikipedia.org'' . more about [[http://en.wikipedia.org/wiki/Role| Roles]] ''- source: en.wikipedia.org '' <
> }}} ---- . YYYYMMDD-YourName . {{{ Text / Your Statements, thoughts and e-mail snippets, Please }}} ---- . YYYYMMDD-YourName . {{{ Text / Your Statements, thoughts and e-mail snippets, Please }}} ---- <
> '''Category''' or '''Categories'''<
> CategoryCommunity <
> CategoryPolicy