Ongoing and Future Work

[ralphtheninja]

This is a summary on what has been happening lately, what we're working on right now and what the future holds. If you want to see anything in particular done right now or cool things for the future, feel free to post suggestions and/or edit this message.

Ongoing

• Run tests in Sauce Labs using airtap where applicable
• Implement coverage across the board using coveralls.

Future

• Add canary tests (Canary system for most used dependents? abstract-leveldown#184)
• IDEA: Try to find good use cases for where we can make use of Property Based Testing. The idea is to try to build a test system that helps us find more bugs (see cryptpad with notes from PBT meetup)
• Fix up the homepage running at leveljs.org. We have really been slacking off here and we could do some really cool stuff with tutorials, write blog posts on the project as a whole (this issue could be a post)
• Bring back basho and lmdb into separate *downs (like rocksdb)? The easiest way is most likely to start from current state of leveldown and pull in the deps/ again from scratch.
• Write more benchmarks and run them continuously

Achieved

• Merge level(up) functionality into abstract-leveldown (Merge levelup into abstract-leveldown #58, abstract-level)
• Refactor (the dependencies of) subleveldown
• Implement manifests (Add manifest to levelup and abstract-leveldown implementations #83)
• Make sure we have a set of publishers for all modules (Add and remove npm owners #17)
• Increase transparency with a public backlog: https://github.com/orgs/Level/projects/2
• Homogenize and polish documentation (State of documentation #29)
• Port native modules to N-API (leveldown-hyper not yet done)
• Refactor the internals of leveldown and friends, fixing resource cleanup and segfaults along the way (leveldown-hyper not yet done)
• Complete and maintain level/awesome showing what's there and the status of related projects when it comes to dependencies etc
• Implement seek() in more abstract-leveldown implementations
• Drop key types other than strings and buffers from memdown and level-js (Decide on sort order memdown#186 (comment))
• Address security concerns from community (Address security concerns from community #43)

[vweevers]

I suggest adding: canary tests, seeking (and the things that it enables, like multi-get), manifests, fixing segfaults, benchmarks.

[vweevers]

Updated (see edit diff).

[vweevers]

Updated:

• Added Achieved section
• Merged Ongoing & Future into Ongoing
• Added Drop key types other than strings and buffers from memdown and level-js
• Moved benchmarks to Ongoing