Skip to content

Update JGIS meeting notes template to include project board review #89

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

mfisher87
Copy link
Member

@mfisher87 mfisher87 commented May 22, 2025


🔍 Preview: https://geojupyter--89.org.readthedocs.build/en/89/
Note: This Pull Request preview is provided by ReadTheDocs. Our production website, however, is currently deployed with GitHub Pages.

Copy link
Contributor

@brichet brichet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me

  • Are there things we can change about the project board to make it more useful? Add more information? Remove steps?

Answering this question here for the record, we should probably add milestone on issues/PRs to track it more easily in the project board, and be able to filter on it.

@mfisher87
Copy link
Member Author

Thanks, Nicolas! Can you clarify how you are suggesting we use milestones in more detail?

@brichet
Copy link
Contributor

brichet commented May 23, 2025

This is probably already one of the ideas behind the use of the project board, but I think that there is nothing currently in the board that can be used to filter the issues by priority.
For example, there is not milestone associated to the issues (AFAIK). We could add e.g. a v0.6.0 milestone and affect it on issues that we expect in version 0.6.0. That could help prioritizing the issues that should to be fixed before the next release.

@mfisher87
Copy link
Member Author

mfisher87 commented May 23, 2025

Thanks for clarifying! I agree with the need to prioritize, but it can be really hard to do that granularly. In my view, pinning issues to specific versions can delay us from releasing valuable features before all the issues assigned to that version are complete.

My thinking on this is that we can prioritize by limiting the number of issues on the project board to a small number, and treat it more as a "stream" than "milestone", and do releases on a more regular rolling basis.

By continuously revisiting the board, we could identify which issues may be languishing and agree to prioritize them, and also add stuff that we feel should be prioritized more highly. Perhaps we can also indicate priority by moving the highest priority items to the top? The approach I took for the first pass at this was to keep it as simple as possible so we can try it out, see how it works, and make changes to better serve our needs as we go!

How does that resonate with you? I'm interested in making sure this is actually valuable for everyone and incrementally improving :)

@brichet
Copy link
Contributor

brichet commented May 24, 2025

👍 Yes, it looks good too, to only add the prioritized issues to the board.
We can start with it and see later if we want more granularity.

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.

2 participants