Resolutions from Wednesday's meeting
Here are the things we decided by majority vote at the weekly meeting yesterday.
We'll still support IE6 for the 1.8 release. Change the release
notes to say that some DojoX projects (like the new Calendar planner,
if/when that gets put into the release) don't support it.
Everyone seemed to be in favor of dropping IE6 and IE7 for 2.0
although we didn't actually vote on it.
(1) use git repos [instead of SVN]
(2) divide [dojo toolkit] into projects (ex: dojo-core, dijit,
charting, mobile, gfx), no mega projects (ex: dojox)
(3) github dojo org (https://github.com/dojo/) account
The github account https://github.com/dojo/ an opt-in area, meaning
that repositories (ex: dijit, charting) can live in this group
account, but they aren't required to. A project could still be part
of the cpm, website, etc. while existing under a different github
Projects in the group dojo account exist as separate repositories.
Projects are accepted under the dojo org account by a vote of
contributors or maybe by foundation board of directors (or
contributors vote and board can veto). ?As written above, the project
owner must want it to be added.
Affiliation prerequisites for a project:
1. requires CLA
2. uses same licensing (as current dojo toolkit)
3. has some % of code coverage with tests (75%? 80%?)
4. has a project manager and support guarantee
5. uses the same docs and testing system
6. valid package.json
We should discuss these at next week's meeting.
- Bug database (use one bug database, or separate ones per project,
or half-and-half). I guess we could also discuss splitting/not
splitting documentation, website, etc.
- Tarballs aka releases (going forward, which of the packages get
bundled up as part of the "dojo release", i.e. what today is known as
dojo 1.6, dojo 1.7, etc.)
- 1.8 contents and timing
Note: The line between dojo toolkit and dojo foundation has become
blurry. We could discuss "what is dojotoolkit?" at next week's