HyperWiki

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
en:project:teamwork [2024/03/06 22:16]
throgh 		en:project:teamwork [2024/04/16 02:39]
throgh [Working in a team with and for Hyperbola]
Line 8: Line 8:
   * an orientation towards the UNIX design philosophies of minimalism and technical emancipation   * an orientation towards the UNIX design philosophies of minimalism and technical emancipation
  
-The following points are intended to define both acceptable and unacceptable behaviors from contributors. These are based on general guidance for projects such as Hyperbola, as well as to address specific situations that have arisen throughout the history of the Hyperbola project. We would like to underline that those rules here are surely in further development, so if anyone feel uncomfortable with one or more rules please speak up open with us. But also note that we then would like to work on a counterproposal. Criticism without any proposal for alternative is not working.+The following points are intended to define both acceptable and unacceptable behaviors from contributors. These are based on general guidance for projects such as Hyperbola, as well as to address specific situations that have arisen throughout the history of the Hyperbola project. We would like to underline that those rules here are surely in further development, so if anyone feels uncomfortable with one or more rules please speak up open with us. But also note that we then would like to work on a counterproposal. Criticism without any proposal for alternative is not working.
  
  
-  - **Respectful for each other:** Every team-member can await to be treated fair, but also has the commitment to respect other members same way. When there is something to debate, we demand that people get in touch with each other and clear up issues and problems and don't search only to create scandals. This kind of dramatic staging is not tolerated here at Hyperbola and also not within the team as this is not respectful treatment.+  - **Respectful for each other:** Every team-member can await to be treated fair, but also has the commitment to respect other members same way. When there is something to debate, we demand that people get in touch with each other and clear up issues and problems and don't search only to create scandals. This kind of dramatic staging is not tolerated here at Hyperbola and also not within the team as this is not respectful treatment. Please also never use [[https://en.wikipedia.org/wiki/Sealioning|sealioning]] and [[https://en.wikipedia.org/wiki/Law_of_triviality|bikeshedding]] in your approach for argumentation. Direct, but friendly approaches, including respect and inclusion is the way Hyperbola is using. Not the opposite as //bikeshedding// for example means focusing on the minor details in a discussion rather than the issue at hand. We have no interest in useless debates and accusations.
   - **Stating open about difficulties:** Not everyone has the same knowledge about everything. So every team-member should talk direct and open when something is not clear. Problems are made transparent, but also with clear and straight facts and not with interpretations.   - **Stating open about difficulties:** Not everyone has the same knowledge about everything. So every team-member should talk direct and open when something is not clear. Problems are made transparent, but also with clear and straight facts and not with interpretations.
   - **Not awaiting any advantages:** Team-members should not await a better position. So being part of the team working on Hyperbola means also to work with and for Hyperbola. Being part of the team just to present this like a trophy elsewhere is nothing we want here.   - **Not awaiting any advantages:** Team-members should not await a better position. So being part of the team working on Hyperbola means also to work with and for Hyperbola. Being part of the team just to present this like a trophy elsewhere is nothing we want here.
Line 22: Line 22:
   - **Not your own dreamcastle:** Yes, Hyperbola is about acting with and for free, libre culture and software. But also no as Hyperbola is not about the fulfillment of any personal "dreamcastle"-buildout. If people want to start something with and / or on top of Hyperbola, they can always feel welcome. But this is inbound with doing, not only with some statements and empty promises. If you want to do, please do and approve your doing. Not just think that you can be part of a team and others carry out and realize your wishes.   - **Not your own dreamcastle:** Yes, Hyperbola is about acting with and for free, libre culture and software. But also no as Hyperbola is not about the fulfillment of any personal "dreamcastle"-buildout. If people want to start something with and / or on top of Hyperbola, they can always feel welcome. But this is inbound with doing, not only with some statements and empty promises. If you want to do, please do and approve your doing. Not just think that you can be part of a team and others carry out and realize your wishes.
  
-If you do not see some points here fitting for you or you want to make your own rules, we kind but straight ask you to stop asking for being a member of the team (and the community also) as this does not make any sense: Hyperbola is not meant as your personal playfield for your visions. The system is meant to enable you working with your hardware, but reasonable and not meant on behalf of irretational thoughts. Decisions, workfows and more were made out of reasoning. They are surely part of discussion in time and can be optimized together. But the keywords here are **working together**, **teamwork** and **decision making together**. This implies also to accept existing workflows. If you have proposals to change them? Sure thing, but demanding from everyone to follow only your perspective without any approval is not working for us.+If you do not see some points here fitting for you or you want to make your own rules, we kind but straight ask you to stop asking for being a member of the team (and the community also) as this does not make any sense: Hyperbola is not meant as your personal playfield for your visions, when you only want to talk, discuss and let others do work and realize your "ideas". The system is meant to enable you working with your hardware, but reasonable and not meant on behalf of irretational thoughts. Decisions, workfows and more were made out of reasoning. They are surely part of discussion in time and can be optimized together. But the keywords here are **working together**, **teamwork** and **decision making together**. This implies also to accept existing workflows. If you have proposals to change them? Sure thing, but demanding from everyone to follow only your perspective without any approval is not working for this project.
  
 ===== How to become part of the team? ===== ===== How to become part of the team? =====