Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do we need a roadmap? #4198

Closed
nolanlawson opened this issue Aug 24, 2015 · 7 comments
Closed

Do we need a roadmap? #4198

nolanlawson opened this issue Aug 24, 2015 · 7 comments
Labels
enhancement Feature request

Comments

@nolanlawson
Copy link
Member

Hoodie has one (hoodiehq/discussion#38), and it makes me wonder if it affects our contributor numbers, that nobody knows what we plan to do. In fact I tend to act kind of randomly, working on whatever I find interesting in a given weekend, but maybe it would make more sense to try to organize our trajectory, at least for the near future.

Thoughts?

@NickColley
Copy link
Contributor

I think if we want to try and get more contributors (myself included) we can try to be more inclusive.

I think a roadmap would be good to be able to try and focus efforts with multiple people?

If people know what the long term goals are we could encourage them to help out or help them get to the point where they can.

Also hype.

@nolanlawson
Copy link
Member Author

My personal long-term goals:

  • crazy good perf
  • runs everywhere JS runs
  • easy to install, no more leveldown headaches

More practically:

  • finish pouchdb-find
  • make queries faster
  • make replication faster

@NickColley
Copy link
Contributor

Along side your runs everywhere JS runs I think we should update the website to reflect that pouchdb is universal(isomorphic) and move towards pushing pouchdb-server.

I'd also like to help moving pouchdb-finds documentation into the site making it a first class citizen if that's where we want to take it.

@nolanlawson
Copy link
Member Author

Yeah I agree with that direction for pouchdb-find, but I want to give it a bit more polish first (implement $in, $or, and $elemMatch). Also we should think about when/how we remove mapreduce and publish it as a separate plugin. I'd be happy to do that for a 5.0 or 6.0, since pouchdb-find is pretty close already.

@daleharvey daleharvey added the enhancement Feature request label Aug 28, 2015
@daleharvey
Copy link
Member

Yeh I have always been wary of roadmaps, I dont like contributors having expectations put on them but a general listing of what peoples focus's are would be helpful.

Personally my main priorities:

  • 0 bugs
  • faster replication
  • faster indexes
  • fix compaction story (auto_compact by default)
  • PouchDB playground / try pouchdb etc

@NickColley
Copy link
Contributor

Putting purge in here since it's pretty important. #802

@nolanlawson
Copy link
Member Author

Gonna close this for now; we have #4257 and we do tend to do a monthly "what's everyone working on" thing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Feature request
Projects
None yet
Development

No branches or pull requests

3 participants