Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add roadmap #43

Merged
merged 1 commit into from
Oct 9, 2021
Merged

Add roadmap #43

merged 1 commit into from
Oct 9, 2021

Conversation

zacharlie
Copy link
Collaborator

I have created a basic roadmap document. I think some of the issues highlighted need to be fleshed out and/ or formalized a bit so that community platform users are able to follow along with the development process and plan accordingly for when breaking changes are introduced

@timlinux
Copy link
Contributor

timlinux commented Oct 9, 2021

Thanks so much for this @zacharlie

As a general strategy, lets add new docs in the sphinx tree rather and then if we want to leave some breadcrumbs the md files in the top level dir can just have pointers over into the sphinc docs. I will do that for this PR

@timlinux timlinux merged commit 42205e8 into kartoza:main Oct 9, 2021
@zacharlie
Copy link
Collaborator Author

I would expect high level docs like roadmap and contributing guidelines to be in the root of the repo myself. But if we rely on the docs for this then I think we just need to add links to the relevant docs in the readme.

I think for developer-centric elements, especially those that affect deployment, are critical to have in the readme.

zacharlie added a commit that referenced this pull request Oct 10, 2021
address issue raised in #43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants