Creating a roadmap

#1

I think a clearer roadmap with ways to contribute and information about the platforms objective would be a good idea. I usually like to take inspiration from Gitlabs Handbook when organising open source projects: https://about.gitlab.com/handbook/ - I think a clear roadmap with regular releases would instil confidence in the platform to continue the development for years to come. https://about.gitlab.com/direction/

It does seem like most of the responsibility has fallen to @flovilmart for the last 3+ years, and that burden needs to be shared.

5 Likes
Open Collective budget / finding new contributors / strategy
Open Collective budget / finding new contributors / strategy
#2

Sounds like a good plan, I think it would be a good idea to have a road map on the parse platform website because what with all the different repos in the project I think it would make sense to have a centralised source so its easy to find etc.

1 Like
#3

This is a great idea. Giving a roadmap gives some focus and confidence to those looking to use the platform. I see the setup of testing and I’m personally put off as I think it’s above my skillset - given direction and friendly support I would be one of those who would certainly invest some time in driving things forwards!

#4

Right let’s aim for a directions page https://about.gitlab.com/direction/

We need to group the tasks into milestones, does GitHub do milestones?
Then somehow need to pull this into a static page. I’m not too verse in GitHub as I’m a gitlabber, But I can try to take a look…

W

#5

does GitHub do milestones?

Yep, you can create version milestones and then assign issues and pull requests to them, e.g. milestones for parse server.

#6

Great - so lets set up. Presuming we have monthly releases…

3.1.0
3.2.0
3.3.0
3-6 Months
6-12 Months
Moonshots

Depending on the timeframe you want to make releases, we can modify this. Can you cross link issues? So we get the SDK issues pulled in?

W

#7

At the end of each release - we create a new milestone and pick issues from the 3-6 month list. When that list is dwindling - we promote the 6-12 months issues and so on.

1 Like
#8

For anyone helping with this it may be worth checking out the old roadmaps created by @dplewis:



#9

I would like to point out that Stalebot closed out a bunch of PRs. https://github.com/parse-community/parse-server/pulls?q=is%3Apr+label%3Awontfix+is%3Aclosed

If anyone is interested review, rebase or give them a good spit shine.