2020-02-29 20:50:42 +00:00
|
|
|
# Roadmap
|
|
|
|
|
|
|
|
This document describes currently planned features and events related to the
|
|
|
|
dehub project. It's intention is to help prioritize work. There are no dates
|
|
|
|
set, only a sequence of milestones and the requirements to hit them.
|
|
|
|
|
2020-03-29 22:24:44 +00:00
|
|
|
## Milestone: Publicize project
|
|
|
|
|
|
|
|
Must be able to feel good about showing the project publicly, as well as be able
|
|
|
|
to accept help from people asking to help.
|
|
|
|
|
|
|
|
* Figure out commit range syntax, use that everywhere.
|
|
|
|
* Tutorials
|
|
|
|
* Maybe move external host?
|
2020-02-29 20:50:42 +00:00
|
|
|
|
2020-03-29 22:24:44 +00:00
|
|
|
## Milestone: IPFS support
|
|
|
|
|
|
|
|
* Big ol' question mark on this one.
|
2020-02-29 20:50:42 +00:00
|
|
|
|
|
|
|
## Milestone: Versions
|
|
|
|
|
|
|
|
* Tag commits
|
2020-04-26 20:23:03 +00:00
|
|
|
* Add dehub version to payloads, make binary aware of it
|
2020-02-29 20:50:42 +00:00
|
|
|
* Figure out a release system?
|
|
|
|
|
2020-04-26 20:23:03 +00:00
|
|
|
## Milestone: Prime commits
|
2020-04-05 18:28:32 +00:00
|
|
|
|
2020-04-26 20:23:03 +00:00
|
|
|
(Cloning/remote management is probably a pre-requisite of this, so it's a good
|
|
|
|
thing it comes after IPFS support)
|
|
|
|
|
|
|
|
* Ability to specify which commit is prime.
|
|
|
|
* The prime commit is essentially the identifier of the entire project; even
|
|
|
|
if two project instances share a commit tree, if they are using a
|
|
|
|
different prime commit then they are not the same project.
|
2020-04-05 18:28:32 +00:00
|
|
|
|
2020-03-29 22:24:44 +00:00
|
|
|
## Milestone: Minimal plugin support
|
|
|
|
|
|
|
|
* SPEC and implement. Things which should be pluggable, initially:
|
|
|
|
* Conditions
|
|
|
|
* Signifiers
|
|
|
|
* Filters
|
2020-04-26 20:23:03 +00:00
|
|
|
* Payloads???
|
2020-03-29 22:24:44 +00:00
|
|
|
|
|
|
|
## Milestone: Minimal notifications support
|
|
|
|
|
|
|
|
* Some way to store notification settings locally, and run a command which shows
|
|
|
|
a sequence of events since the last time you ran it.
|
|
|
|
* The command should keep a history of all of its outputs, and allow the
|
|
|
|
user to see that history (in case they run the command, then clear the
|
|
|
|
output by accident).
|
|
|
|
* The user should be able to specifically get notifications on threads
|
|
|
|
they're a part of, threads by branch name pattern, files by path pattern,
|
|
|
|
and keywords in commit messages.
|
|
|
|
|
|
|
|
# Misc Polish
|
|
|
|
|
|
|
|
These tasks aren't necessarily scheduled for any particular milestone, but they
|
|
|
|
are things that could use doing anyway.
|
2020-02-29 20:50:42 +00:00
|
|
|
|
2020-04-11 16:51:09 +00:00
|
|
|
* Config validation. Every interface used by the config should have a
|
|
|
|
`Validate() error` method, and Config itself should as well.
|
|
|
|
|
2020-03-04 23:34:02 +00:00
|
|
|
* Maybe coalesce the `accessctl`, `fs`, and `sigcred` packages back into the
|
|
|
|
root "dehub" package.
|
|
|
|
|
2020-02-29 20:50:42 +00:00
|
|
|
* Polish commands
|
2020-03-29 22:24:44 +00:00
|
|
|
* New flag system, some kind of interactivity support (e.g. user doesn't
|
2020-02-29 20:50:42 +00:00
|
|
|
specify required argument, give them a prompt on the CLI to input it
|
2020-03-14 00:06:35 +00:00
|
|
|
rather than an error). This is partially done, in that a new flag system
|
|
|
|
has been started. Needs further work.
|
2020-02-29 20:50:42 +00:00
|
|
|
|
2020-03-29 22:24:44 +00:00
|
|
|
* Review flags:
|
|
|
|
* probably make some of them into positional arguments
|
|
|
|
* add flag shortcuts
|
|
|
|
* document everything better.
|
2020-02-29 20:50:42 +00:00
|
|
|
|
2020-03-29 22:24:44 +00:00
|
|
|
* POSIX compatible-ish flags?
|
2020-02-29 20:50:42 +00:00
|
|
|
|
2020-03-29 22:24:44 +00:00
|
|
|
* Possibly save state locally in order to speed things along, such as
|
|
|
|
"account id" which probably isn't going to change often for a user.
|