Skip to content
This repository has been archived by the owner on Feb 8, 2023. It is now read-only.

Identify which Projects Need Roadmaps and Who Maintains those Roadmaps #135

Closed
flyingzumwalt opened this issue Aug 5, 2016 · 4 comments
Closed

Comments

@flyingzumwalt
Copy link
Contributor

flyingzumwalt commented Aug 5, 2016

Which projects go on the Organizational Roadmap (see description in #131)?

A quick list of projects I've seen mentioned:

  • IPFS (general)
  • go-ipfs
  • js-ipfs
  • orbit + orbit-db (aka "dynamic content"?)
  • IPLD
  • PubSub
  • libp2p
  • XTP
  • IPFS Cluster
  • Packet Management
  • Multiformats
  • Infrastructure
    etc..
@flyingzumwalt
Copy link
Contributor Author

We can write this list into the config file for @haadcode's roadmap-generator. That way we have a file in a git repo explicitly listing the repositories that we are watching. See PR #176

@RichardLitt
Copy link
Member

Has this issue changed?

Which projects go on the Organizational Roadmap (see description in #131)? Who is responsible for maintaining the roadmap of each project?

Is this you, now?

@haadcode
Copy link
Member

haadcode commented Sep 7, 2016

Which projects go on the Organizational Roadmap (see description in #131)? Who is responsible for maintaining the roadmap of each project?
Is this you, now?

I believe @flyingzumwalt is responsible for the organization's roadmap. Project leads are still responsible for individual project roadmaps.

@flyingzumwalt
Copy link
Contributor Author

Yep. What @haadcode said. I'll update the text so the ticket remains focused on the actual task at hand - identifying which projects need to be included on the org roadmap.

@ghost ghost removed the status/ready Ready to be worked label May 6, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants