Project Proposal #3692
Replies: 2 comments 1 reply
-
Hey, @AlannaBurke ! The project idea seems interesting. I've gone through the entire repository, including its docs, and I'm really interested in finding a way to facilitate transparent communication. Could you please guide me on where I can send my brief introduction? |
Beta Was this translation helpful? Give feedback.
1 reply
-
Update - our project was not selected, so i'll be closing this discussion and we'll try again net year! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Proposal Title
Overhaul Lagoon Technical Diagrams
About your organization
Lagoon is an open-source application delivery platform for Kubernetes. Lagoon allows developers to locally develop their code and their services with Docker and run the exact same system in production - the same container images, the same service configurations and the same code. Its primary focus is as a cloud-native tool for the deployment, management, security and operation of many applications. Lagoon greatly reduces the requirement on developers of those applications to have cloud-native experience or knowledge.
Lagoon was originally created and open sourced by the team at amazee.io in August 2017, and powers their global hosting platform.
Lagoon is largely maintained by the Lagoon team, who are employed by amazee.io, along with a handful of outside contributors. Our community has been slowly growing over the past few years, and we have seen increased adoption of Lagoon.
Your project's problem
As an open-source project, we aim to have the most comprehensive documentation possible for users, administrators, developers, and contributors. We have a variety of technical diagrams that are currently out of date and very difficult to update and publish. Having up-to-date and easy to update diagrams will make it much easier to understand the architecture of the Lagoon project, which is essential for many personas interacting with Lagoon. For example, a new contributor to the project benefits from being able to have a visual representation of all of Lagoon’s components and how they interact.
Your project's scope
This project will:
We have not yet identified potential technical writers for this project. The chosen technical writer will work with Alanna Burke, documentation writer for the Lagoon project, and Toby Bellwood, product owner.
Measuring your project's success
Lagoon is a complex project with a lot of moving parts, and it’s essential to the project to have an up-to-date technical diagram to give a visual explanation of how all of the various parts connect and interact.
Questions about Lagoon are fielded by the Lagoon team, mostly in the community Discord. Many questions could be answered or avoided altogether by having robust diagrams explaining how the system works and how the moving parts interact. Our goal in this project is to see a decrease in questions related to the overall functionality and architecture of the Lagoon project. We will track how many questions are asked per week, how many could be answered with updated technical diagrams, and continue to track after the diagrams are completed, published, and promoted to the community, ideally seeing a decrease in those questions.
Timeline
Project budget
Required skills
Creating, updating, and maintaining complex technical architecture and infrastructure diagrams in a system like Structurizr, mermaid.js, draw.io, etc. The first phase of this project will require analyzing potential solutions and presenting the best options for the project.
Beta Was this translation helpful? Give feedback.
All reactions