Transcript

Log070117

Agenda

1.0 Roadmap

See the roadmap

Splitting up source tree

Dustin's proposed a plan for splitting dojo into dojo-core, widgets-core and dojox.  It had these points of contention:

1. are widgets released at the same time as core?
Resolution: yes

2. separate repositories or just separate directories?  (Alex)
Resolution: Separate directories.

2a. core/trunk or trunk/core?
Resolution: most people seemed to like core/trunk better

2b. utils as separate project?
Resolution: no, it stays in core, linker goes to dojox/utils.

3. widgets are in a separate directory/project, but should they be in dojo module or in dojow module? (Bill)
Resolution: none.  doubt about why widgets/core are separate projects, and why widgets need to be released at the same time as core, discussion about overlaying widgets on top of core

4. I think it makes sense (and Alex is open to the idea but not sold either way) to have a separate list of committers on "core" and on "dojox".  All "core" committers automatically get "dojox" committer rights, but not vise versa. (Owen)
Resolution: core committers being a subset of dojox committers.   dojox committors get equal voting at foundation.  but we need a strangle-hold on what goes into core

5. What will be the policy for accepting things into the "dojox" project?  Sponsorship by a "core committer"?  (Owen)
Resolution: quorum to decide what gets in w/a light hand?

6. Can modules in "dojox" decorate objects in the "core" dojo?  (can dojox.date add stuff to dojo.date?) (Owen)
Resolution:  Not resolved.  no in general, except for special cases.  Also idea for dojo/ext directory that contains all the external stuff. 

7. widget project: templates at top level, parallel to source?   what about images? (Bill)

8. can core contain experimental modules?

9. src/dojo/module  vs. ROOT/module (Adam)

Release 0.4.2:

Bugs scheduled

http://dojo.jot.com/Release0Point42

James' list:

Three things I would like to include:

1) I would also like to include this bug:
http://trac.dojotoolkit.org/ticket/2119. It was a simple fix and
something that was just plain broken (using an undefined variable).

2) I would like to include this changeset (it only affects the
XhrIframeProxy code):
http://trac.dojotoolkit.org/changeset/7034

3) I am willing to port over the changes I did to get a cross-domain
build to work without needing a local copy of Dojo. Most of the fixes
are in the build process, but there is one that touches a few source
files and introduces dojo.uri.cache:

http://trac.dojotoolkit.org/changeset/6973

I may not have web building fully working for the 0.4.2 release, but
if I can get the changeset above merged in as well as the changesets
mentioned below, it would give us an opportunity to release a web
build system for the 0.4.2 code after the 0.4.2 launch.

Other changesets related to xdomain builds:
http://trac.dojotoolkit.org/changeset/6929
http://trac.dojotoolkit.org/changeset/6952
http://trac.dojotoolkit.org/changeset/6967
http://trac.dojotoolkit.org/changeset/6974
http://trac.dojotoolkit.org/changeset/6975
http://trac.dojotoolkit.org/changeset/6981
http://trac.dojotoolkit.org/changeset/6990
http://trac.dojotoolkit.org/changeset/7003

James

Resolution: go ahead, check in the stuff above, except for #2.  But NO FEATURE CREEP (people kept worrying about this).  James plans to have it done over the weekend.