Add a Roadmap to the project documentation

[DennisClark]

Per @mjherzog
Roadmap might be one item that should be a file on primary repo like README

Assigned to @DennisClark to investigate

[DennisClark]

From @mjherzog
I see that as a planning doc that probably needs to be updated separately from other doc. Keeping it on the wiki is also a possibility. In any case we need a standard across projects/repos

[mjherzog]

Overall, we need to set a standard for the few documents, like README, that need to be in the primary code tree versus the majority that belong under /docs. I think that ROADMAP should probably be in the main code tree because it is tied closely to Issues and Milestones, rather than HowTo etc.
Another option is to continue using the Wiki for the Roadmap, but it would be simpler to have all doc in the main code tree or /doc.

[steven-esser]

@AyanSinhaMahapatra Lets leave this issue open until we create new "Add roadmap" tickets to all of our OSS repos.

[inbuilt-aura]

@mjherzog, plzz assign me thios issue.Iwould love to contribute in this by makjing a roadmap as a readme file.

[pombredanne]

@inbuilt-aura we do not "assign" issues, you are just welcomed to work on one!
But here the roadmaps is not something you can likely take up as an issue anyway: this is rather a task for the core project contributors and maintainers as they are the only ones that can craft the right content for the ROADMAP.

[inbuilt-aura]

Thanks for you reply and guidance,i would love to add one asap!

…

On Fri, 10 Feb, 2023, 16:10 Philippe Ombredanne, ***@***.***> wrote: @inbuilt-aura <https://github.com/inbuilt-aura> we do not "assign" issues, you are just welcomed to work on one! But here the roadmaps is not something you can likely take up as an issue anyway: this is rather a task for the core project contributors and maintainers as they are the only ones that can craft the right content for the ROADMAP. — Reply to this email directly, view it on GitHub <#16 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARWZMCLPOQNJYS7DCZKZD23WWYLJFANCNFSM4HXBV4NA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[ashutosh887]

@pombredanne I would like to work on this if not already worked upon by some fellow contributor

[krishna9358]

@DennisClark I would love to give my hand in this task. With the right guidance, i think i can make the road map as README file.

[ashutosh887]

@pombredanne I would like to work on this if not already worked upon by some fellow contributor

cc: @DennisClark

[vHarshita15]

I WANT TO CONTRIBUTE ON THIS ISSUE

[pombredanne]

@vHarshita15 Thanks for you enthusiasm, but creating the roadmap is the privilege of the core contributors and maintainers of the project. The "documentation" part is the easy part, the content is the hard part.

[vHarshita15]

HELLO SIR ,, I WANT TO CONTRIBUTE, CAN U PLEASE TELL ME HOW WILL I START MY JOURNEY?

…

On Tue, 5 Nov 2024, 16:02 Philippe Ombredanne, ***@***.***> wrote: @vHarshita15 <https://github.com/vHarshita15> Thanks for you enthusiasm, but creating the roadmap is the privilege of the core contributors and maintainers of the project. The "documentation" part is the easy part, the content is the hard part. — Reply to this email directly, view it on GitHub <#16 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BGQ6MKS54TT32IXJZJHK5G3Z7CNFXAVCNFSM6AAAAABREROTVCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJWHAYDQOBYGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>