No description
Go to file
Mert Gör bb72cbbe53
Copyright (C) 2024 QB Networks
Copyright (C)  2017-2024  Masscollabs Services

Copyright (C)  2017-2024  procyberian and contributors

Copyright (C)  2017-2024  amassivus and contributors

Copyright (C)  2017-2024  Mass Collaboration Labs and contributors

Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3
or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
A copy of the license is included in the section entitled "GNU
Free Documentation License".

* This code of conduct file is licensed under the terms of GFDLv1.3 or any later.
* This Code of Conduct applies to Masscollabs Services or in other words [Masscollabs](https://github.com/masscollabs/), [procyberian](https://github.com/procyberian), [Mass Collaboration Labs](https://github.com/masscollaborationlabs) and [amassivus](https://www.github.com/amassivus) organizations.

* We are building a free, open and collaborative "core community" in other words a community for communities and a company for companies.
* We need to tell ourselves in a clear way which lets outsiders understand what we are doing easily.
* We know what is Free Software and Open Source and "other" software ideas or paradigms. Let's get started with licenses.

* We decide three layers for each organization amassivus, Mass Collaboration Labs, procyberian and Masscollabs Services. For in-house purposes and for our partners which we have a very close contact, like in person, we prefer Copyleft licenses. Mostly we prefer AGPLv3 or later because we are focused on Internet technologies. But for other software GPLv3 or later, for documentation GFDLv1.3 or later, for artworks CC BY-SA 4.0 or later licenses are what we prefer for our own works.
* For outsiders and who are **not** in our community instances, maybe other companies, individuals or state organizations we'll offer BSD 3-Clause license. The reason is easy to understand, we are the authors so we can easily write anything from scratch anytime.
* All code base will be written by our Core Team but contributions is needed and since we are building a free organization it is very important for us to listen other authors' ideas. But our approach is not to rely on any technology so we are trying to be a free and an independent organization, and an open system. Open system does **not** mean Open Source but we mean that we are trying to develop things for every operating system and hardware platform.

* We have taken our organization model from FreeBSD and OpenBSD, but we are following OpenBSD model for software development, especially the approach to the software security issues.
* Therefore we have three layers in every organization, core team, committers and contributors. So lets get started writing their roles and why we want that organization model.

* As we understand from software, it should be done in a short time and it should be done well and simple, maybe in 5 minutes or 30 minutes. Core Team is responsible from maintaining all information database in the domain and subdomains (amassivus, Mass Collaboration Labs, and procyberian). So Core Team can delete any harmful information such as malware code/binary or any kind of information that includes a hate speech, racism and sexism. It is very important for us to learn from other organizations. So we are curious to learn other Free Software and Open Source code of conduct standards written before us.

* Committers are mid-level or experienced developers in domain and subdomains (amassivus, Mass Collaboration Labs, and procyberian) or any information/content authors which has the right to add/commit information to our information database. We are a freely, open and collaborative company so we believe in free speech/freedom of speech and we are happy to get feedback and contributions from committers within our domain, subdomains or the people who is **not** working with us directly.

* Contributors are newcomers to our domain and subdomains so we want to take care of their skills and abilities, such as how they do useful things for **public**. We want to encourage committers and contributors to make their own services, communities and companies for the same reason to serve to the **public**.

* We wanted to be careful and make a better service rather than publishing any content that is not production ready. Thus we are letting people to use our information database easy for their **real-world** needs both without any cost or paid options. You can sell our information database or use them in your **own** organization freely under the terms of the licenses mentioned above.

* You **don't have to follow** our Core Team policies within the domain or subdomains so you may easily adapt our information database for your needs. If you don't like Copyleft versions you may ask for BSD 3-Clause information database. We think that it'll be better to make our organization free, open and collaborative.

* freedom of speech
* openness
* collaborative working
* privacy of community members and customers
* and also [Four Freedoms written by Free Software Foundation](https://www.gnu.org/philosophy/free-sw.en.html)

* **devel-x branches**: We plan to make daily updates for new features and security fixes in 5 minutes to 30 minutes.
* **master-x/main-x branches**: We plan to make monthly updates for new features and security fixes in one month, three months and six months. This is the main branch for communites, end users, companies and other organizations such as foundations, associations and state organizations.
* **stable-x branches**: We plan to make yearly updates for new features in one year, three years and five years. This is the Long Term Support branch. Stable and more focused on software and hardware security.
* **oldstable-x branches**: We plan not to limit ourselves to serve in a five year time period so on this branch the support lifetime is ten years.
* **legacy-x branches**: On this branch we have the information database which is archived and the information that is not supported by us directly.

* To be a free, open and collaborative organization we hope that this Code of Conduct file will help to the **public**. If you have any questions feel free to e-mail us with this format "[ REASON ] [ Message Topic ] and Message ". For example "[ Technical Support ] [ I can't get updates for my application] I can't get updates after a fresh installation with my new Operating System."

* Hacker is someone who is exploring limits of the related activity such as a Jazz improvisation with any instrument, or practicing martial arts in a clever way by following the martial arts culture, so the hacker culture itself and martial arts culture or Jazz culture are very similar thus we can say for all of them in short "hacker". They are all hackers. To be honest there are different approaches in hacker culture and this pluralism is what we need and like, and we encourage hackers to make their own practices and follow their own methodologies to do good and useful things for the **public**.

* freedom is good
* openness is good
* collaboration is good
* privacy is good
* we demand to do good and useful things for the *public* and do **not** want to rely on any technology so we are authors and we can make something better replacing existing information and technology.
2024-05-15 08:59:52 +03:00
README_assets MKA 2024-05-15 08:50:42 +03:00
README.md Copyright (C) 2024 QB Networks 2024-05-15 08:59:52 +03:00

Welcome to the Masscollabs Services

Mustafa Kemal Atatürk

License for documentation

Copyright (C) 2024 QB Networks

Copyright (C) 2017-2024 Masscollabs Services

Copyright (C) 2017-2024 procyberian and contributors

Copyright (C) 2017-2024 amassivus and contributors

Copyright (C) 2017-2024 Mass Collaboration Labs and contributors

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License".

Masscollabs Services Code of Conduct

Why we are writing a Code of Conduct and why it is so important

  • We are building a free, open and collaborative "core community" in other words a community for communities and a company for companies.
  • We need to tell ourselves in a clear way which lets outsiders understand what we are doing easily.
  • We know what is Free Software and Open Source and "other" software ideas or paradigms. Let's get started with licenses.

Domains and licenses

  • We decide three layers for each organization amassivus, Mass Collaboration Labs, procyberian and Masscollabs Services. For in-house purposes and for our partners which we have a very close contact, like in person, we prefer Copyleft licenses. Mostly we prefer AGPLv3 or later because we are focused on Internet technologies. But for other software GPLv3 or later, for documentation GFDLv1.3 or later, for artworks CC BY-SA 4.0 or later licenses are what we prefer for our own works.
  • For outsiders and who are not in our community instances, maybe other companies, individuals or state organizations we'll offer BSD 3-Clause license. The reason is easy to understand, we are the authors so we can easily write anything from scratch anytime.
  • All code base will be written by our Core Team but contributions is needed and since we are building a free organization it is very important for us to listen other authors' ideas. But our approach is not to rely on any technology so we are trying to be a free and an independent organization, and an open system. Open system does not mean Open Source but we mean that we are trying to develop things for every operating system and hardware platform.

Domains and their structures

  • We have taken our organization model from FreeBSD and OpenBSD, but we are following OpenBSD model for software development, especially the approach to the software security issues.
  • Therefore we have three layers in every organization, core team, committers and contributors. So lets get started writing their roles and why we want that organization model.

Core Team

  • As we understand from software, it should be done in a short time and it should be done well and simple, maybe in 5 minutes or 30 minutes. Core Team is responsible from maintaining all information database in the domain and subdomains (amassivus, Mass Collaboration Labs, and procyberian). So Core Team can delete any harmful information such as malware code/binary or any kind of information that includes a hate speech, racism and sexism. It is very important for us to learn from other organizations. So we are curious to learn other Free Software and Open Source code of conduct standards written before us.

Committers

  • Committers are mid-level or experienced developers in domain and subdomains (amassivus, Mass Collaboration Labs, and procyberian) or any information/content authors which has the right to add/commit information to our information database. We are a freely, open and collaborative company so we believe in free speech/freedom of speech and we are happy to get feedback and contributions from committers within our domain, subdomains or the people who is not working with us directly.

Contributors

  • Contributors are newcomers to our domain and subdomains so we want to take care of their skills and abilities, such as how they do useful things for public. We want to encourage committers and contributors to make their own services, communities and companies for the same reason to serve to the public.

Why three layers

  • We wanted to be careful and make a better service rather than publishing any content that is not production ready. Thus we are letting people to use our information database easy for their real-world needs both without any cost or paid options. You can sell our information database or use them in your own organization freely under the terms of the licenses mentioned above.

  • You don't have to follow our Core Team policies within the domain or subdomains so you may easily adapt our information database for your needs. If you don't like Copyleft versions you may ask for BSD 3-Clause information database. We think that it'll be better to make our organization free, open and collaborative.

Our Core Values

On Software Distribution and Support

  • devel-x branches: We plan to make daily updates for new features and security fixes in 5 minutes to 30 minutes.
  • master-x/main-x branches: We plan to make monthly updates for new features and security fixes in one month, three months and six months. This is the main branch for communites, end users, companies and other organizations such as foundations, associations and state organizations.
  • stable-x branches: We plan to make yearly updates for new features in one year, three years and five years. This is the Long Term Support branch. Stable and more focused on software and hardware security.
  • oldstable-x branches: We plan not to limit ourselves to serve in a five year time period so on this branch the support lifetime is ten years.
  • legacy-x branches: On this branch we have the information database which is archived and the information that is not supported by us directly.

Conclusion

  • To be a free, open and collaborative organization we hope that this Code of Conduct file will help to the public. If you have any questions feel free to e-mail us with this format "[ REASON ] [ Message Topic ] and Message ". For example "[ Technical Support ] [ I can't get updates for my application] I can't get updates after a fresh installation with my new Operating System."

Happy hacking!

  • Hacker is someone who is exploring limits of the related activity such as a Jazz improvisation with any instrument, or practicing martial arts in a clever way by following the martial arts culture, so the hacker culture itself and martial arts culture or Jazz culture are very similar thus we can say for all of them in short "hacker". They are all hackers. To be honest there are different approaches in hacker culture and this pluralism is what we need and like, and we encourage hackers to make their own practices and follow their own methodologies to do good and useful things for the public.

  • freedom is good

  • openness is good

  • collaboration is good

  • privacy is good

  • we demand to do good and useful things for the public and do not want to rely on any technology so we are authors and we can make something better replacing existing information and technology.