Roadmap page for the Overview section

[benjagm]

This is part of the Release 3 of the #158 . It will be great to create a page with the JSON Schema Roadmap.

Published roadmap: https://github.com/orgs/json-schema-org/discussions/427

The idea is create a page similar to this one : https://docs.dapr.io/contributing/roadmap/

But embedding the Roadmap github board : https://github.com/orgs/json-schema-org/projects/14/views/13

Other references: https://pantos.io/en/roadmap

[praveen-rikhari]

@benjagm since nobody is assigned to this can i work on this??

[benjagm]

can i work on this??

Please go ahead. The idea is create a page similar to this one : https://docs.dapr.io/contributing/roadmap/

But embedding the Roadmap github board : https://github.com/orgs/json-schema-org/projects/14/views/13

[benjagm]

@praveen-rikhari let me know if you need help with this. Maybe you can work this issue with somebody else.

[benjagm]

Hi @praveen-rikhari, I am going to leave this issue free for other contributors. If you finally prefer to continue working on it let me know.

[praveen-rikhari]

Hey @benjagm I hope you got my message on slack. Right now I am working on this issue. So, please reassign this task to me again.

[deveshidwivedi]

Hi, if this is available, I'd like to work on it.

[Sk05062003]

Hi @benjagm, I would like to work on this issue right away, if it is available. Please assign it to me.

[benjagm]

Can you please change the target branch to https://github.com/json-schema-org/website/tree/web-release-3?

Reference docs: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request

[VivekJaiswal18]

are you still working on this issue @praveen-rikhari. Do you need any help?

[benjagm]

I am leaving this issue available for other contributors as it has no activity for the last month.

[Akshaybagai52]

Hey @benjagm Can I work on this issue ?

[benjagm]

Thanks Akshaybagai52 . Go ahead!

[Akshaybagai52]

Hello @benjagm can you check this PR https://github.com/json-schema-org/website/pull/674

[benjagm]

Hi everyone working on this issue. I'd like to share here relevant requirements:

The roadmap es available on Github in this project: https://github.com/orgs/json-schema-org/projects/14

To access the information of each item you will need to use the Github API method created for it and documented here: https://docs.github.com/en/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects#finding-information-about-items-in-a-project

I tested it and it works perfectly. You will need to create your own api token for testing purposes with the read:project scope.

The GraphQL query needed for the POST API call to this url https://api.github.com/graphql is:

 query{
    node(id: "PVT_kwDOAMaoXc4ARJVm") {
        ... on ProjectV2 {
          items(first: 20) {
            nodes{
              id
              fieldValues(first: 8) {
                nodes{                
                  ... on ProjectV2ItemFieldTextValue {
                    text
                    field {
                      ... on ProjectV2FieldCommon {
                        name
                      }
                    }
                  }
                  ... on ProjectV2ItemFieldDateValue {
                    date
                    field {
                      ... on ProjectV2FieldCommon {
                        name
                      }
                    }
                  }
                  ... on ProjectV2ItemFieldSingleSelectValue {
                    name
                    field {
                      ... on ProjectV2FieldCommon {
                        name
                      }
                    }
                  }
                }              
              }
              content{              
                ... on DraftIssue {
                  title
                  body
                }
                ...on Issue {
                  title
                  assignees(first: 10) {
                    nodes{
                      login
                    }
                  }
                }
                ...on PullRequest {
                  title
                  assignees(first: 10) {
                    nodes{
                      login
                    }
                  }
                }
              }
            }
          }
        }
      }
    }

[benjagm]

This issue is now available for other contributors due to inactivity.

[github-actions[bot]]

Hello! :wave:

This issue has been automatically marked as stale due to inactivity :sleeping:

It will be closed in 180 days if no further activity occurs. To keep it active, please add a comment with more details.

There can be many reasons why a specific issue has no activity. The most probable cause is a lack of time, not a lack of interest.

Let us figure out together how to push this issue forward. Connect with us through our slack channel : https://json-schema.org/slack

Thank you for your patience :heart:

[rishabhknowss]

hey , i am working on this issue !!! can you please assign me as well :)

[benjagm]

There are some changes you need to consider for this issue: There is no need to call the api because the data is available in the "/data/roadmap.json" file because the data is being downloaded weekly by the sync-project-roadmap.yml action.

https://github.com/json-schema-org/website/blob/main/data/roadmap.json

This will avoid unnecessary API Calls and risk if hitting the rate limit.

[rishabhknowss]

okay !! on it

[rishabhknowss]

hi ! a quick question , is this design okay or i should make it more simple and clean

[benjagm]

Looks promising. I'll suggest do something with impact and effort values like creating labels with different colors, instead of just plain text.

[rishabhknowss]

okayy