Skip to content

Add roadmap with development plans in website - #396

Open
florence-bockting wants to merge 5 commits into
masterfrom
roadmap
Open

florence-bockting wants to merge 5 commits into
masterfrom
roadmap

Conversation

@florence-bockting

@florence-bockting florence-bockting commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

Description

This PR adds a roadmap with information about current and planned development plans (wrt loo).
The roadmap shall appear on the loo website and be accessible for the community.

ToDos

  • update the PR number in NEWS.md
  • remove the roadmap.html file currently included for easier review.

@codecov-commenter

codecov-commenter commented Sep 17, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.50%. Comparing base (7991145) to head (16527cd).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #396   +/-   ##
=======================================
  Coverage   92.50%   92.50%           
=======================================
  Files          31       31           
  Lines        3107     3107           
=======================================
  Hits         2874     2874           
  Misses        233      233           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@florence-bockting

florence-bockting commented Sep 17, 2026

Copy link
Copy Markdown
Contributor Author

Hi, I worked on a roadmap for the loo package.
What do you think about it @jgabry, @avehtari, @VisruthSK? Any ideas for topics to change, remove, add?

The following link uses githack and will open the .html (without the Stan style website) for easier review.
When you click the link the first time, it will ask you whether you trust the source.

preview of roadmap

On the website it could then look as follows (here just the upper part of the document is shown):

image

@florence-bockting
florence-bockting marked this pull request as ready for review September 17, 2026 10:30
@github-actions

github-actions Bot commented Sep 17, 2026

Copy link
Copy Markdown

This is how benchmark results would change (along with a 95% confidence interval in relative change) if 16527cd is merged into master:

  • ✔️loo_function: 1.36s -> 1.36s [-1.18%, +1.67%]
  • ✔️loo_matrix: 1.49s -> 1.49s [-1.39%, +0.94%]
    Further explanation regarding interpretation and methodology can be found in the documentation.

@VisruthSK

VisruthSK commented Sep 17, 2026

Copy link
Copy Markdown
Member

This is very cool!

I think it might be nice to link to the milestones so people could see all the PRs/issues associated with each? Similarly for open issues/PRs.

My one concern is that this page won't be maintained as we move things from In Progress to Planned--maybe we only highlight completed topics?

@florence-bockting

Copy link
Copy Markdown
Contributor Author

To link it with milestones in the PR/Issues is a good idea. That's nice.

Regarding the labeling "In Progress" and "Planned": I agree that it might be a bit annoying to actually keep track of this nuance. We could remove the "status" information, then we don't need to worry about that.

@jgabry

jgabry commented Sep 18, 2026

Copy link
Copy Markdown
Member

Yeah I think this is really great as long as it's easily maintainable without having to constantly remember to update it. We used to have a roadmap for the entire Stan project that was public but it was hard to keep it up to date. If this is just pulling from GitHub milestones and things that like then that's better, but any prose about any of the plans will have to be updated manually.

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.

4 participants