geonetwork/core-geonetwork

Change to "roadmap" project for proposals, "release" project for release planning

jodygarnett opened this issue · 4 comments

jodygarnett commented

Change to GitHub Project Board for change proposals.

Image

Proposal

Jeroen setup a new GeoNetwork roadmap project board as a replacement for the wiki proposals page. The issue detailing this can be found here.

The existing policy:

Proposals are developed on the WIKI so others can get a better understanding of what a developer wants to add to GeoNetwork opensource before it is accepted in the core. When writing a proposal, you should use the proposal-template as starting point. Add your proposal to the list below. When proposal is ready for vote, an issue should be opened and a pull request attached when available.

Replacement policy:

Proposals offer public review of changes GeoNetwork opensource policy or core codebase. Proposals are developed on the GeoNetwork roadmap project board as a draft item. When approved by the PSC the item is turned into an issue (and a pull request attached when available).

Why this is important

Offers a more interactive approach to proposal process with tool support for the resulting workflow.

This improves traceability without so much editing and linking by hand. It is also more efficient in PSC meetings.

Proposal Support

This is a community lead proposal without financial / fundraising component.

Voting

Voting established via geonetwork-devel email list, held open until May 22 2024, community response welcome.

PSC Support:

  • Jo Cook
  • Jose Garcia
  • Paul van Genuchten
  • Florent Gravin
  • Simon Pigot
  • Francois Prunayre
  • Jeroen Ticheler

Community support:

  • Jody Garnett (initial motion)

Reference

jodygarnett commented

Addressed by #7837 created under previous wiki policy.

New Workflow: Draft Item --> GeoNetwork Issue

jodygarnett commented

Feedback from PSC meeting:

  • Including PRs and proposals on the same board is resulting in too much complexity
  • PRs show up on board, but have not been voted on
  • PRs are blocked waiting for review - how to indicate that?

Approach:
2. release board:

  • for planning standard cabana board for PRs and Issues
  • columns: todo / progress / blocked / done
  1. roadmap board:
    • for PSC proposal process
    • columns: opportunity, proposal, approved, rejected
jodygarnett commented

Evaluating options for release planning:

  • Trying the standard GitHub "future release" board for release planning:

    Image

    Going with defaults is nice as people can find example and videos on how to use.

  • Trying a simple kanban board:

    Image

Both the the GitHub defaults provide "more" than a simple kanban board I was expecting.

  • While some of the view, like "in review" and "my items" are helpful. I am concerned that views like "roadmap" gant-chart presentation provide a misleading impression of timeline commitment to the public.

Decision:

  • Using the "future release" template as-is as it allows for milestones which follow our development cycle.

    See the public board here: release

jodygarnett commented

Okay the roadmap board is updated, see detailed process update for updated procedure.

To support release manager issues and pull-requests have been pulled out to their own release board.