A markdown based view of the Logos roadmap https://roadmap.logos.co
Go to file
Corey efa6049576 vac weekly 2023-08-21 15:29:22 -04:00
.github Initial commit 2022-08-11 16:01:26 -04:00
.vscode update to faq 2022-11-28 19:57:03 -05:00
assets added milestones, added mermaid diagrams 2023-08-07 13:11:18 -04:00
content vac weekly 2023-08-21 15:29:22 -04:00
data config update, fixed lastmod 2023-08-04 10:52:07 -04:00
layouts added milestones, added mermaid diagrams 2023-08-07 13:11:18 -04:00
static Update icon.png 2023-01-10 16:19:40 -05:00
.gitignore add Jenkinsfile for CI builds, extend Makefile 2022-09-07 21:19:55 +02:00
.hugo_build.lock Initial commit 2022-08-11 16:01:26 -04:00
.prettierrc Initial commit 2022-08-11 16:01:26 -04:00
CODE_OF_CONDUCT.md Initial commit 2022-08-11 16:01:26 -04:00
Jenkinsfile add Jenkinsfile for CI builds, extend Makefile 2022-09-07 21:19:55 +02:00
LICENSE.txt Initial commit 2022-08-11 16:01:26 -04:00
Makefile add Jenkinsfile for CI builds, extend Makefile 2022-09-07 21:19:55 +02:00
README.md changed index page, updated readme 2023-08-21 11:49:38 -04:00
config.toml updates to names and overviews 2022-11-29 15:20:11 -05:00
screenshot.png Initial commit 2022-08-11 16:01:26 -04:00

README.md

Logos Collective Project Roadmaps

Overview

This repository contains the aggregated technical roadmaps of projects under and associated with the Logos Collective. It is an attempt to provide easy access to what we're all actively working on, and how it's going.

In its current form, it is an implementation of a Quartz "mind-garden", which is a Hugo theme that allows for easy text and graph-based searching of markdown files. This repository is built and served to https://roadmap.logos.co

The content, today, contains the definition of work planned by various projects, broken up via:

Project --> Milestones --> Epics --> Issues

Each project is given as much autonomy as possible to work as they see fit, with a minimal reporting scheme that sits on top that allows for aggregation of information and project tracking.

In a nutshell, projects give a definitions of their roadmap up-front, which includes the mapping of issues to epics, and epics to milestones. They also provide perceived risks and dependencies associated with their work.

The projects then report a weekly "diff" associated with the work they did each week, which is ostensibly a stand-up. The Insights team can work from there to do what they need.

Contribution

The bulk of the content is added by the Insights team within the Logos Collective, which is a team that works to keep track of activity within the projects in order to provide analysis and insight based on that work to various stakeholders, including the projects themselves.

For now, this process is quite manual, purposely. In order to solidify the format that the content is delivered in, manual processing and iteration are required. Once this is more consistent and smooth, we plan to open the door to more contributors. Step one is transparency and consistency.

If you see a type or broken link, PRs are always welcome :)

If there is information you'd like to see included that isn't here, create and issue :)