Add ROADMAP
message: Add ROADMAP change_hash: AL5+4r6xZWUDcAUqKJmKWWP5FCTAtmJBxfmt+rYRPljq credentials: - type: pgp_signature pub_key_id: 95C46FA6A41148AC body: iQIzBAABAgAdFiEEJ6tQKp6olvZKJ0lwlcRvpqQRSKwFAl5azpwACgkQlcRvpqQRSKxDbg/9ET30ULbN0xq29o0WIC8x81j+J1oWluxTMitJTm31u+ZVDA7vpLpuBIg0HLVQYRtO1F/xjA0PTry+6bEwgw/mYZQ8G9DNtgEPaekmORs8EIMaIukXyZUOobBoJOTRB+rcFpbJW2b0trTRMGRDTWE0g+/HqB5Pgx7EJjlTCZCUWY3jiNXDRa97upp28s076+aJEYIYtwRi6G1W8jGyD297q4+VR0/TDUUVvVbJpPBGPD2acdEwwxvXf+nY3bXmbjyWuTocIIVH8hXvmdlLKRBUTuWyjMzv3llA3Nq42RlviS0TO4XXXaqgucgdpicXNfdG0E3cDhMM3/OG3cWh8fR4uRXNFZT5d6VHdtUWN/RGVf7Nxv7i16AL7iALqukxhXV6XFlW3szr9UhH404b8RTkWoQf+SsIcZUaWLeCjWr1ohyV2b2ptRnLi3D8nr8Fbh8GXC+mI0TAgvip20oYovs35tO80u7dLqUR+mTG7Z8AlYwBHD+abMbn4SUlreytaBZjeVLZD3UbDpm8VoJI4rb4eZTOgBcP56Hyh+R48epKPaTQ/DaJpLq2NOempQJFPucflFsOGLwA+JxbFvaJQwOVyBL6G3Hts0llM3KWkb38ai47kN3gK+xwjKA+v+qQKH52UtCGSIDlOPJ9X1PKTJHBFt3HUVbOj4TCvPidDAp2YkQ= account: mediocregopher
This commit is contained in:
parent
76309b51cb
commit
0af9c04e33
64
ROADMAP.md
Normal file
64
ROADMAP.md
Normal file
@ -0,0 +1,64 @@
|
||||
# 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.
|
||||
|
||||
## Milestone: Be able to add other developers to the project
|
||||
|
||||
* Thread commits (comments, signatures)
|
||||
* Coalesce command
|
||||
* Fast-forward perms on branches
|
||||
* README with a "Getting Started" section
|
||||
|
||||
## Milestone: Versions
|
||||
|
||||
* Tag commits
|
||||
* Add dehub version to the SPEC, make binary aware of it
|
||||
* Figure out a release system?
|
||||
|
||||
## Milestone: Enough polish to show off the project
|
||||
|
||||
* Possibly rename "trunk", it's kind of weird as being a kind of branch,
|
||||
especially when its corallary type is "thread" which has nothing to do with
|
||||
trees.
|
||||
|
||||
* Polish commands
|
||||
- New flag system, some kind of interactivity support (e.g. user doesn't
|
||||
specify required argument, give them a prompt on the CLI to input it
|
||||
rather than an error. This can be built into the flag system.
|
||||
|
||||
- Review flags, probably make some of them into positional arguments,
|
||||
document everything better.
|
||||
|
||||
- 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.
|
||||
|
||||
* HTTP docs
|
||||
- Some kind of addition to the docker server to auto-serve md files.
|
||||
- Reorganize all the md files under a `docs` directory, except the README.
|
||||
- Make sure linking between documents works.
|
||||
|
||||
* More/better tests?
|
||||
|
||||
## Milestone: IPFS support
|
||||
|
||||
* Big ol' question mark on this one.
|
||||
|
||||
## Milestone: Minimal plugin support
|
||||
|
||||
* SPEC and implement. Things which should be pluggable, initially:
|
||||
- Conditions
|
||||
- Signifiers
|
||||
|
||||
## 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.
|
||||
|
Loading…
Reference in New Issue
Block a user