Skip to content

Include material on the utility of project roadmaps #235

Description

@semioticrobotic

The guide doesn't currently contain any explanation of or guidance on setting and maintaining project roadmaps—though by my count its authors reference the importance of establishing project roadmaps at least 15 times. Because this is a tool most open source projects use (and occasionally misuse), I think the guidebook should include something about it.

I tend to like @funnelfiasco's advice on the topic. With any luck, we may be able to convince him to contribute some of his recent writing for a new chapter or section.

Activity

  1. funnelfiasco commented on May 15, 2024

    @funnelfiasco

    Hey, I know that guy. I'm sure I could talk him into writing that content given a general shape of what you want and how it fits in.

  2. semioticrobotic commented on May 20, 2024

    @semioticrobotic
    MemberAuthor

    Nice! A huge boon for the project.

    We've been discussing the prospect of a new release. While we don't have any firm dates yet, I'll be sure to keep you posted.

    Meanwhile, I would say that we'd likely place something about roadmaps in the "Guiding Participants" section. I think your pre-existing writing already has an appropriate scope. A next step might be to clone the chapter template and begin noodling.

  3. semioticrobotic commented on May 23, 2025

    @semioticrobotic
    MemberAuthor

    At long last, @funnelfiasco, I am able to return to this. Would you still be interested in working on it for the next release of the guidebook? Pleading commenced.

  4. funnelfiasco commented on May 23, 2025

    @funnelfiasco

    I can do that. Do you have a roadmap for the next release so that I may give myself an appropriate deadline?

  5. semioticrobotic commented on May 23, 2025

    @semioticrobotic
    MemberAuthor

    That's great, @funnelfiasco! Many thanks.

    At the moment I'm attempting to engage authors to see who responds and is amenable. From there, I plan to work backwards to set some deadlines and plan the release milestone. So, truly, the date can be what you'd like it to be. But if you're looking for guidance that might add creative pressure: say, a month?

  6. semioticrobotic commented on Aug 4, 2025

    @semioticrobotic
    MemberAuthor

    How's this going, @funnelfiasco? If you're amenable to it, would you consider a "chapter swap" for peer review and editorial comment as you wrap up? @dneary and I are re-writing the chapter on open source strategy and I think you'd be a great editor and subject matter expert there. We'll read yours if you read ours.

  7. funnelfiasco commented on Aug 4, 2025

    @funnelfiasco

    To quote one of my favorite musicals:

    John Adams: Do you mean to say that it is not yet finished?
    Thomas Jefferson: No, sir. I mean to say that it's not yet begun.

    I am very much hoping that with the end of summer, I'll have more time to focus on these sorts of projects in my backlog. I'd be glad to review your chapter once I'm done with the two I've committed to write, but given where I am in the process, please don't block on my review.

  8. semioticrobotic commented on Aug 4, 2025

    @semioticrobotic
    MemberAuthor

    Fair enough. Thanks for considering. And good luck!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions