From d524fce4036859324b7fb024c1bdd2c704a55c21 Mon Sep 17 00:00:00 2001 From: ajstrongdev Date: Mon, 24 Jun 2024 22:41:52 +0100 Subject: [PATCH 1/3] upd(news-14): Structure news --- news-13.html | 2 +- news-14.html | 96 ++++++++++++++++++++++++++++++++++++++++++++++++++++ news.html | 15 +++++++- 3 files changed, 111 insertions(+), 2 deletions(-) create mode 100644 news-14.html diff --git a/news-13.html b/news-13.html index c803b21..c63b790 100644 --- a/news-13.html +++ b/news-13.html @@ -65,7 +65,7 @@

Development Update

- Before we get into information about this release, we have a brief update about our organizational structure. As we mentioned a while ago, developer burnout hit a breaking point for some us, and in consequence devlepment has somewhat stagnated. We have begun discussions about how we wish to structure Rhino Linux going forward, and are happy to announce that we have currently drafted a working Rhino Linux constitution, with a hard focus on community involvement. These structural changes will begin to come into effect shortly after this release, so stay tuned for the full announcement! + Before we get into information about this release, we have a brief update about our organizational structure. As we mentioned a while ago, developer burnout hit a breaking point for some us, and in consequence development has somewhat stagnated. We have begun discussions about how we wish to structure Rhino Linux going forward, and are happy to announce that we have currently drafted a working Rhino Linux constitution, with a hard focus on community involvement. These structural changes will begin to come into effect shortly after this release, so stay tuned for the full announcement!

If you wish to be a part of our upcoming community-led initiative, then consider joining us on our Discord. diff --git a/news-14.html b/news-14.html new file mode 100644 index 0000000..bd9f79c --- /dev/null +++ b/news-14.html @@ -0,0 +1,96 @@ + + + + + + + Rhino Linux | News + + + + + + +

+ +
+
+ +
+

+ ☰ +

+
+

+ News Feed +

+

+ Find news relating to Rhino Linux & its development +

+
+
+
+ +
+

+ An update on Rhino Linux's development goals and structure +

+

+ After a lot of discussions with the Rhino Linux team, we are finally ready to announce changes to the way we develop. We have decided to focus on the following areas:
+ • Providing a strong contributor's code of conduct
+ • Focusing effort on strong development and user documentation
+ • Rewriting our website in React, which will provide us with better tools for Documentation.
+ • Streamlining development channels.
+

+

+ With our contributor's code of conduct, we aim to provide a safe and welcoming environment for all contributors. We want to ensure that everyone feels welcome and that their contributions are valued. We believe that this will help us to attract more contributors and improve the quality of our software. Our newly written contributor's code of conduct can be found here. +

+

+ Our decision to rewrite our website in React is going to provide us with significantly better tools when it comes to managing our documentation, publishing blog posts and ensuring long-term maintainability. We plan to write development documentation while we undertake this website redesign. This development documentation will be made publicly available to all users and contributors. By documenting our development process, we aim to provide a clear, transparent view to how Rhino Linux is maintained, and help new contributors get up to speed quickly. +

+

+ We currently do not have any plans to move development discussions away from Discord at the moment. Discord has been useful as a small team to collaborate on development and communicate effectively. We plan to now utilise a public-facing Discord forum to allow for users and contributors to discuss and organise development around specific feature requests and bug reports. +

+

+ We are excited about these changes, and believe that this will help us to build the foundations for a stronger, more vibrant Rhino Linux community, where any user feels empowered to contribute to the project. +

+

+ Many thanks,
+ The Rhino Linux Team +

+ +
+ + +
+ +

+ Source Code | Contact & Social | Donate | Branding | Unicorn | Bug tracker +

+ + + + diff --git a/news.html b/news.html index 52d0639..34b9c93 100644 --- a/news.html +++ b/news.html @@ -59,7 +59,20 @@

News

-
+
+ +
+

+ An update on Rhino Linux's development goals and structure +

+

+ After a lot of discussions with the Rhino Linux team, we are finally ready to announce changes to the way we develop. We have decided to focus on the following areas... +

+

+ June 24th, 2024 +

+ +

From 561c9f065442a0a99f0eac6ec725fb53a139ad1d Mon Sep 17 00:00:00 2001 From: ajstrongdev Date: Sat, 29 Jun 2024 14:38:03 +0100 Subject: [PATCH 2/3] upd: add COC to website --- coc.html | 155 +++++++++++++++++++++++++++++++++++++++++++++++++ news-14.html | 10 ++-- src/output.css | 6 +- 3 files changed, 165 insertions(+), 6 deletions(-) create mode 100644 coc.html diff --git a/coc.html b/coc.html new file mode 100644 index 0000000..b0a1884 --- /dev/null +++ b/coc.html @@ -0,0 +1,155 @@ + + + + + + + Rhino Linux | Code of Conduct + + + + + + + + +
+
+ +
+

+ ☰ +

+
+

+ Rhino Linux +

+

+ Contributor's Code of Conduct +

+
+
+
+ +
+

+ Rhino Linux Contributor's Code of Conduct +

+

+ Last Edited: June 29th 2024. +

+

+ • This document should serve as a framework for the standards that we hold contributors and those on the Rhino Linux team. This document is intended to be continually updated and edited as Rhino Linux grows as an organisation. +

+

+ At Rhino Linux, we are committed to fostering an inclusive and welcoming community which seeks to thrive on mutual respect and honesty. We wholeheartedly believe that every member of our community should be treated with dignity and respect, regardless of race, sexuality, gender identity, disability or any other protected characteristic. To uphold these values, we expect all contributors to adhere to the following code of conduct: +

+

+ Expected behaviours: +

+

+ Expected behaviours are to be followed by all contributors to the Rhino Linux project in all environments. Contributors represent the project and should follow the expected behaviours in all official channels including (but not limited to): The Rhino Linux Discord server and GitHub. +

+

+ Examples of behaviour that contribute to fostering a positive environment includes: +

    +
  • • Showing respect towards different viewpoints and experiences
    • +
  • • Accepting constructive criticism
    • +
  • • Focusing on what is best for the community
    • +
  • • Expressing empathy towards other community members
    • +
  • • Treating all contributors with empathy, kindness and fairness
    • +
  • • Embracing diversity and inclusivity within the organisation
    • +
+

+

+ Examples of any unacceptable behaviour by contributors includes: +

    +
  • • The use of sexualised language or imagery.
    • +
  • • Insulting or derogatory comments, including any personal or political attacks.
    • +
  • • Discrimination, harassment or exclusion based on any protected characteristic.
    • +
  • • Public or private harassment
    • +
  • • Publishing others' private information, such as physical address, without explicit permission.
    • +
  • • Any other conduct which could reasonably be considered inappropriate in a professional setting.
    • +
+

+

+ Honesty and Transparency +

+

+ Honesty and transparency are paramount to the survival of any project. Please ensure that you adhere to these guidelines when contributing to Rhino Linux: +

    +
  • • Openly and honestly communicate with fellow contributors
    • +
  • • If required, disclose, to the team, any conflicts of interest or biases that could potentially affect your contributions.
    • +
  • • Respect the intellectual property rights of other projects, and ensure that you provide proper credit to others for their work, when required.
    • +
+

+

+ Seek help, offer support +

+

+ We recognise the fact that Rhino Linux maintenance is largely built on the basis of volunteer work. As such some maintainers may be busier at times than others, or there will be periods of their lives where they may not be able to contribute as much. +

    +
  • • Do not hesitate to ask for help when needed, whether it is technical assistance, guidance, clarification or to reduce your workload.
    • +
  • • Offer your support and assistance to other contributors whenever, and wherever possible. Please ensure that this is done in a constructive and respectful manner.
    • +
  • • Foster a culture of collaboration and mentorship by sharing knowledge and resources with others.
    • +
+

+

+ Ensuring maintainability +

+

+ It is important to ensure that our code is up to standard. This means that proper programming conventions should be followed at all times. Rhino Linux is used by people globally, and as such needs to be maintained by multiple people. By contributing your code to Rhino Linux you agree to adhere to these guidelines: +

    +
  • • All code submitted to the Rhino Linux project must be properly commented and documented.
    • +
  • • Developer documentation for all repositories must be created with instructions on maintainance and development
    • +
  • • Any and all AI-generated code submitted to the Rhino Linux project must be disclosed, and precautions must be in place to ensure that the code generated has the same quality and maintainability as any piece of code submitted by a maintainer.
    • +
  • • As a team we will conduct regular code reviews, as well as refactorings, to address technical debt, improve code quality and ensure long-term maintainability. These code reviews will be conducted at the team's discretion.
    • +
+

+

+ Accountability +

+

+ We recognise that contributors will have differing levels of capacity and availability. We ask that contributors inform other contributors within working groups of their capacity. This will allow for everyone to see who is able to take on certain tasks. If you are struggling, ask for help. We recognise things happen, and we would rather you ask for help, rather than going dark and abandoning what was being worked on for the project. As we have outlined in this document, community and collaboration is what makes Rhino Linux roll. +

+

+ Breaking any of our expected behaviours has the potential to result in removal from the Rhino Linux team or the ability to contribute to the project. +

+

+ By participating in the Rhino Linux community, you agree to abide by this code of conduct and contribute to creating a positive and inclusive environment for all members. Together, let's uphold the values of honesty, fairness, respect, and mutual support that define our community. +

+ +
+ + +
+ +

+ Source Code | Contact & Social | Donate | Branding | Unicorn | Bug tracker +

+ + + \ No newline at end of file diff --git a/news-14.html b/news-14.html index bd9f79c..a310b04 100644 --- a/news-14.html +++ b/news-14.html @@ -60,26 +60,26 @@

After a lot of discussions with the Rhino Linux team, we are finally ready to announce changes to the way we develop. We have decided to focus on the following areas:
- • Providing a strong contributor's code of conduct
- • Focusing effort on strong development and user documentation
+ • Providing a strong Contributor's Code of Conduct.
+ • Focusing effort on strong development and user documentation.
• Rewriting our website in React, which will provide us with better tools for Documentation.
• Streamlining development channels.

- With our contributor's code of conduct, we aim to provide a safe and welcoming environment for all contributors. We want to ensure that everyone feels welcome and that their contributions are valued. We believe that this will help us to attract more contributors and improve the quality of our software. Our newly written contributor's code of conduct can be found here. + With our contributor's code of conduct, we aim to provide a safe and welcoming environment for all contributors. We want to ensure that everyone feels welcome and that their contributions are valued. We believe that this will help us to attract more contributors and improve the quality of our software. Our newly written contributor's code of conduct can be found here.

Our decision to rewrite our website in React is going to provide us with significantly better tools when it comes to managing our documentation, publishing blog posts and ensuring long-term maintainability. We plan to write development documentation while we undertake this website redesign. This development documentation will be made publicly available to all users and contributors. By documenting our development process, we aim to provide a clear, transparent view to how Rhino Linux is maintained, and help new contributors get up to speed quickly.

- We currently do not have any plans to move development discussions away from Discord at the moment. Discord has been useful as a small team to collaborate on development and communicate effectively. We plan to now utilise a public-facing Discord forum to allow for users and contributors to discuss and organise development around specific feature requests and bug reports. + We currently have long-term plans to move development discussions away from Discord and onto a public-facing forum, which should allow for more structured discussions, better organisation of development tasks and a more centralised location for development discussions. Until then, we will continue to utilise Discord as our primary development channel. Updates on the development of this forum will come soon.

We are excited about these changes, and believe that this will help us to build the foundations for a stronger, more vibrant Rhino Linux community, where any user feels empowered to contribute to the project.

Many thanks,
- The Rhino Linux Team + The Rhino Linux Team.

diff --git a/src/output.css b/src/output.css index dda2f7a..60ba6bc 100644 --- a/src/output.css +++ b/src/output.css @@ -1,5 +1,5 @@ /* -! tailwindcss v3.4.3 | MIT License | https://tailwindcss.com +! tailwindcss v3.4.4 | MIT License | https://tailwindcss.com */ /* @@ -726,6 +726,10 @@ video { flex: 1 1 auto; } +.list-disc { + list-style-type: disc; +} + .appearance-none { -webkit-appearance: none; -moz-appearance: none; From ed7585c10364d363d56b73547e2e3da523c6c879 Mon Sep 17 00:00:00 2001 From: ajstrongdev Date: Sat, 29 Jun 2024 23:08:44 +0100 Subject: [PATCH 3/3] add: mission statement --- news-14.html | 8 +++-- news.html | 2 +- src/output.css | 4 --- statement.html | 84 ++++++++++++++++++++++++++++++++++++++++++++++++++ 4 files changed, 91 insertions(+), 7 deletions(-) create mode 100644 statement.html diff --git a/news-14.html b/news-14.html index a310b04..9797c4c 100644 --- a/news-14.html +++ b/news-14.html @@ -60,7 +60,8 @@

After a lot of discussions with the Rhino Linux team, we are finally ready to announce changes to the way we develop. We have decided to focus on the following areas:
- • Providing a strong Contributor's Code of Conduct.
+ • Providing a strong Contributor's Code of Conduct
+ • Outlining our goals as an organisation through our Mission Statement. • Focusing effort on strong development and user documentation.
• Rewriting our website in React, which will provide us with better tools for Documentation.
• Streamlining development channels.
@@ -71,6 +72,9 @@

Our decision to rewrite our website in React is going to provide us with significantly better tools when it comes to managing our documentation, publishing blog posts and ensuring long-term maintainability. We plan to write development documentation while we undertake this website redesign. This development documentation will be made publicly available to all users and contributors. By documenting our development process, we aim to provide a clear, transparent view to how Rhino Linux is maintained, and help new contributors get up to speed quickly.

+

+ We have outlined our goals as an organisation through our Mission Statement. Our mission statement serves as a guide for the Rhino Linux team, and outlines our goals as an organisation as well as allowing you to understand our vision for Rhino Linux, and why we are building it. +

We currently have long-term plans to move development discussions away from Discord and onto a public-facing forum, which should allow for more structured discussions, better organisation of development tasks and a more centralised location for development discussions. Until then, we will continue to utilise Discord as our primary development channel. Updates on the development of this forum will come soon.

@@ -79,7 +83,7 @@

Many thanks,
- The Rhino Linux Team. + The Rhino Linux Team.

diff --git a/news.html b/news.html index 34b9c93..17fdc51 100644 --- a/news.html +++ b/news.html @@ -69,7 +69,7 @@

After a lot of discussions with the Rhino Linux team, we are finally ready to announce changes to the way we develop. We have decided to focus on the following areas...

- June 24th, 2024 + June 29th, 2024

diff --git a/src/output.css b/src/output.css index 60ba6bc..6e555ad 100644 --- a/src/output.css +++ b/src/output.css @@ -726,10 +726,6 @@ video { flex: 1 1 auto; } -.list-disc { - list-style-type: disc; -} - .appearance-none { -webkit-appearance: none; -moz-appearance: none; diff --git a/statement.html b/statement.html new file mode 100644 index 0000000..c9fd580 --- /dev/null +++ b/statement.html @@ -0,0 +1,84 @@ + + + + + + + Rhino Linux | Code of Conduct + + + + + + + + +
+
+ +
+

+ ☰ +

+
+

+ Rhino Linux +

+

+ Mission Statement +

+
+
+
+ +
+

+ Our Mission: Creating the go-to, Debian-derived counterpart for Arch. +

+

+ The Rhino Linux organisation is a collection of individuals with the same goal, creating a Linux distribution that intends to parallel Arch Linux. +

+

+ Just as Pacstall aims to be the AUR for Ubuntu, Rhino Linux aims to be the go-to, Debian-derived counterpart for Arch. A rolling release distribution with community-based package management central to our philosophy. Creation of a single package can take as little as a single file. These packages are often built in real time, right on the system before installation, giving the user immense levels of control of their own system; similarly, user choice will always be at the forefront of decision making. +

+

+ Rhino Linux is usable and mutable, and while we have defaults, we provide efficient ways to shape the distribution to tailor your needs. In addition to ease of management for the systems using our distribution, Rhino Linux and Pacstall aim to make it incredibly simple to package for multiple targets, and even test on them in containers. +

+

+ Sincerely,
the Rhino Linux team. +

+ +
+ + +
+ +

+ Source Code | Contact & Social | Donate | Branding | Unicorn | Bug tracker +

+ + + \ No newline at end of file