docs, spec

part of #41

README.md

@@ -57,3 +57,12 @@ LuaRocks is a natural choice as the Nvim plugin manager, but defining a "federat
 ## Release
 
 TBD
+
+## TODO
+
+- [x] specify packspec (above)
+- [ ] specify ecosystem-agnostic client behavior (report conflicts, fetch things into `pack/` dir, update existing dir, ...)
+- [ ] specify what is undefined (i.e. owned by the per-ecosystem "engine", for example vim/nvim packages are fetched into 'packpath')
+- [ ] TODO: support other kinds of artifacts, like zip archives or binaries.
+- [ ] nested packages in workspace (`foo/pkg.json`, `foo/bar/pkg.json`)
+- [ ] Nvim: client can support conflicting dependencies by using git worktree.

docs/README.md

@@ -43,7 +43,6 @@ The initial use-case is for Vim and Emacs plugins (which can be downloaded from
 
 - No client spec (yet): only the format is specified, not client behavior.
 - No official client (yet)
-- TODO: support conflicting dependencies using git worktree.
 
 # Package requirements
 

docs/spec.md

@@ -123,14 +123,3 @@ This may be relaxed in the future.
    .local/share/nvim/site/pack/github.com/start/
    .local/share/nvim/site/pack/sr.ht/start/
    ```
-
-
-# Strategy
-
-- [x] specify packspec (above)
-- [ ] specify ecosystem-agnostic client behavior (report conflicts, fetch things into `pack/` dir, update existing dir, ...)
-- [ ] specify what is undefined (i.e. owned by the per-ecosystem "engine", for example vim/nvim packages are fetched into 'packpath')
-
-# TODO (future)
-
-- nested packages in workspace (`foo/pkg.json`, `foo/bar/pkg.json`)