github/meteor
1
1
Fork 0
mirror of https://github.com/meteor/meteor.git synced 2026-01-09 23:58:19 -05:00
Code Issues Packages Projects Releases Wiki Activity

First pass at an updated roadmap

Browse Source
This commit is contained in:
Zoltan Olah
2016-04-08 15:49:29 -07:00
parent 4afbabd0dc
commit 2cbba1bbaf
2 changed files with 27 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
Contributing.md
View File

@@ -70,8 +70,7 @@ Meteor is a big project with [many](https://www.meteor.com/projects)
doesn't have as many
[core developers (we're hiring!)](https://www.meteor.com/jobs/core-developer)
as subprojects, so we're not able to work on every single subproject every
month. We use our [roadmap](https://roadmap.meteor.com/) to communicate what
we're actually working on now, and what things we might be working on soon.
month. We use our [roadmap](Roadmap.md) to communicate the high level features we're prioritizing over the near and medium term.
Every additional feature adds a maintenance cost in addition to its value. This
cost starts with the work of writing the feature or reviewing a community pull
@@ -98,11 +97,6 @@ labels, so it's easier for a core developer to find all the feature requests for
a subproject and think of ways to holistically address multiple feature
requests.
(We will close feature requests that are entire new subprojects that are already on the
[roadmap](https://roadmap.meteor.com/); discuss them on the roadmap! Many of these projects can be
achieved (or at least prototyped) as non-core packages; the best way to influence the future of
Meteor core on these future projects is to build a package that implements it yourself.)
In general, if a feature can be implemented as an external Atmosphere package by
our community, that's better than building it in to core, since future changes
can be made directly by the community users who directly depend on the feature.

26
Roadmap.md Normal file
View File

@@ -0,0 +1,26 @@
Meteor Roadmap
==============
This document describes the high level features the project has decided to prioritize in the near to medium term future. A large fraction of the MDG core engineering team's time will be dedicated to working on the features described here.
Contributors are encouraged to focus their efforts on work that aligns with the roadmap as maintainers will prioritize their time around these contributions. This however does not mean that PR's against other features and bugs will be automatically rejected.
For the meantime, MDG won't be accepting PR's for changes to the roadmap. We hope to change this in the future as we figure out strategies to decentralize Meteor development.
# 1.3.x
## Mongo updates
The mongo driver that currently ships with Meteor is quite old and users are finding issues with connecting to MongoDB 3.2 databases (e.g [#6258](https://github.com/meteor/meteor/issues/6258)). We want to update to the latest driver [#5763](https://github.com/meteor/meteor/issues/5763).
In addition, we'd like to update the dev bundle to ship with the latest stable version of MongoDB (3.2) [#5809](https://github.com/meteor/meteor/issues/5809).
## Support for Node 4 and beyond
We want to be able to update the version of Node that ships with Meteor to 4 and eventually 6 when it is released [#5124](https://github.com/meteor/meteor/issues/5124). [#6537](https://github.com/meteor/meteor/issues/6537) lays the groundwork to overcome the main blocker for updating to Node 4, that is, needing to rebuild all existing Meteor packages that contain binary dependencies.
# 1.4+
## Full transition to npm
1.3 introduced `npm install` support along with ES2015 modules. With 1.4, we would like to transition the Meteor package ecosystem over entirely from Atmosphere to npm. We are still in the early conceptual design phase and expect to update the roadmap once we have a design in place that will underpin further development.