| 3 Mar 2023 |
 evils | https://www.pine64.org/2023/03/01/february-update-things-are-taking-shape/ | 21:05:40 |
 jeremiahs | the road map does not have to have strict dates per say. just an overview of the state of up and comming things. | 21:06:08 |
| jeremiahs | a single page that is kept update date | 21:06:26 |
| jeremiahs | this would be in addition to monthly updates or something. | 21:06:44 |
| evils | my feeling is it's gonna be like pulling teeth to get an estimate out of an RFC shepherd
and most of the time those estimates are going to slip | 21:07:10 |
| evils | but i don't have evidence for that belief xD | 21:07:28 |
| evils | i wouldn't want to burden the people involved with being asked why they're past the date on the roadmap | 21:08:29 |
| jeremiahs | we can have the following states for up and coming changes:
- RFC
- PR
- REVIEW
- UNSTABLE
- RELEASED
| 21:09:05 |
| jeremiahs | in a central ui with a brief explanation of that it is doing. | 21:09:33 |
| jeremiahs | with a link to the full rfc / pr / testing branch | 21:09:54 |
| evils | yes, i'd love to read such a thing | 21:09:57 |
| evils | i guess the biggest difference between a monthly update and a roadmap is that the roadmap is a complete overview on every change | 21:10:26 |
| jeremiahs | right | 21:10:37 |
| jeremiahs | and if a rough deadline exists to state it. | 21:11:00 |
| evils | having watched the board panel thing earlier today
maintaining this kind of overview of the ecosystem seems like something they should take on | 21:11:18 |
| evils | (not to say they couldn't delegate it) | 21:11:39 |
| jeremiahs | board panel thing? | 21:13:18 |
| evils | https://youtu.be/yXPQdZh8o7c?t=534 | 21:13:47 |
| jeremiahs | i'll watch soon. | 21:14:57 |
| evils | ah, "public road map" was explicitly mentioned in the first question | 21:15:03 |
| evils | i don't think the roadmap part was addressed, but the first answer is very much an indication of "it's definitely progressing, but it'll be done when it's done" | 21:15:43 |
| evils | hmm, i think Rust has a similar attitude of "we'd rather get it right, than get it now"
they do do some road map like stuff
https://blog.rust-lang.org/inside-rust/2022/04/04/lang-roadmap-2024.html | 21:17:30 |
| evils | to get back to the "publishing stuff for users to look forward to" thing you said
i'm afraid of that turning into either "things you can have right now if you switch to unstable"
or annoyance at the feature a user wants still not being there | 21:19:09 |
| evils | * hmm, i think Rust has a similar attitude of "we'd rather get it right, than get it on schedule"
they do do some road map like stuff
https://blog.rust-lang.org/inside-rust/2022/04/04/lang-roadmap-2024.html | 21:20:37 |
| jeremiahs | "we'd rather get it right, than get it now"
but then how no means of knowing easily what they are getting on leaves you high and dry. you can have a project overview without deadlines??? | 21:25:15 |
| evils | hmm, i guess there's some fairly definite things to be said about which changes will come first just because they're dependencies of others | 21:28:15 |
| evils | but i quite like the sound of monthly updates that also update an overview | 21:29:13 |
| jeremiahs | monthly updates =/= overview. As a result to get all the info of all past months the user has to then go through every monthly update (not saying monthly updates should not exist) but it should be in addition to an overview / road map.
rust has a roadmap for note.
https://www.rust-lang.org/governance
https://github.com/rust-lang/rfcs/blob/master/text/3037-roadmap-2021.md | 21:34:50 |
| evils | i didn't suggest monthly updates are the overview
i mean that whoever finalizes the update, updates the overview/roadmap accordingly | 21:35:52 |
| evils | i've got a weird idea in my head now
git commits to change the roadmap have a large commit message that's a month's worth of updates | 21:38:06 |
