Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upAdd roadmap summary to OrbitDB README #526
Comments
sirfumblestone
changed the title
|
The waffle board works across repositories, but I don't know that it has been updated especially in a while - I know that I haven't been using it, which isn't a good sign in general. A clearer way of seeing current issues would be good. Right now, the best way to do this is the jump on the call. @haadcode: you've mentioned the waffle board before as something you want to bring back. Am I right in thinking that? |
|
In the past we used Waffle (for Orbit Chat) to have display a) what's currently being worked on and b) what's on the roadmap. I think it was great and would love to start using it (as part of the "official process") for OrbitDB too. Waffle doesn't need manual updating in any way, it's always up to date. What it does need is properly configure the labels to match the board columns (which we never did for this repo, but have a tool to automate it across it org in https://github.com/haadcode/labels-and-milestones). That all said, the Waffle board right now is much more a real-time view to the roadmap as opposed "list of couple of main things". However, proper process/structuring of the issues in GH, can do that in Waffle too (eg. have an issue for each "main thing" and label them so that it's clear they're "bigger things" than individual PRs). All in all, I personally would want to automate it as much as possible in order to avoid manually updating READMEs or other files to reflect the current status. |
We could also have an issue for each quarter, which refers to the other main issues we're working on. We could pin this issue to the top of the repo. That's fairly minimal in the work involved, and it could be used as a 'subscribe to updates' issue we could post to after each call. What do you think? |
|
waffle.io no longer exists |
|
You're right, and we've also turned it off. We'll post another issue about our long-term plans sometime in the fall; for now, we're focusing on the next release. See #585. Instead of adding this to the README, we've started pinning it as an issue (it's the top issue), so I am going to close this issue as no longer needed. Thanks for pinging, @MTonomy-Nchinda-Nchinda |
Today the roadmap information is "hidden" to Waffle and is only briefly mentioned in README's Contribution section. Also Waffle tends to be both busy and somewhat complex for an untrained eye.
I think it would be beneficial for both the existing community and especially to new people who come across orbit-db to see a simple list of what major features/fixes (e.g. dynamic access control) are under development right now.
Does this make sense?