gmane.comp.web.dojo.devel

Re: Let's start using Dote!

Kitson Kelly — 2013-05-22T20:01:08

By a request from a few, I have added a "timeline" view to dote.  It can
now be viewed (for those logged in) by going to
http://dote.kitsonkelly.com/timeline.  I will be adding an RSS feed of the
same information that will be "world readable" and point at the world
readable views of the topics.
_______________________________________________
dojo-contributors mailing list
dojo-contributors< at >mail.dojotoolkit.org
http://mail.dojotoolkit.org/mailman/listinfo/dojo-contributors

Re: GitHub transfer complete

Kitson Kelly — 2013-05-21T14:15:19

That was the original stub, but the one Bryan and I worked on and finally
got there and others reviewed was much more comprehensive and in markdown.
 The problem was keeping them in sync and accurate between a markdown
version and a reStructuredText.

I guess since the docs is the only official documentation at the moment, I
should just convert it to reStructuredText and put it in the reference
guide.



On 21 May 2013 14:49, Bill Keese <bill< at >dojotoolkit.org> wrote:

_______________________________________________
dojo-contributors mailing list
dojo-contributors< at >mail.dojotoolkit.org
http://mail.dojotoolkit.org/mailman/listinfo/dojo-contributors

Re: GitHub transfer complete

Bill Keese — 2013-05-21T13:49:21

It's already in the reference guide, at
https://github.com/dojo/docs/blob/master/developer/github.rst, right?

I can see why you'd want it in the wiki, but OTOH it makes sense for it to
be with the other documents in
https://github.com/dojo/docs/tree/master/developer.

On Tue, May 21, 2013 at 10:34 PM, Kitson Kelly <me< at >kitsonkelly.com> wrote:

_______________________________________________
dojo-contributors mailing list
dojo-contributors< at >mail.dojotoolkit.org
http://mail.dojotoolkit.org/mailman/listinfo/dojo-contributors

Re: GitHub transfer complete

Kitson Kelly — 2013-05-21T13:34:59

I was going to move it, but it appears that the wiki is shut off on the
new repository and I have been juggling issues with dote too much to figure
out how we wanted to sort it out.  We do need a place for the document.  I
could convert it back into reStructuredText and put it into the
reference-guide, but that doesn't seem the most logical place to put it
these days.


On 21 May 2013 12:51, Patrick Ruzand <pruzand< at >gmail.com> wrote:

_______________________________________________
dojo-contributors mailing list
dojo-contributors< at >mail.dojotoolkit.org
http://mail.dojotoolkit.org/mailman/listinfo/dojo-contributors

Re: GitHub transfer complete

Patrick Ruzand — 2013-05-21T11:51:55

Hi,

unless I missed something it seems the wiki of the
/dojo/dojo-oldmirror has not been migrated. It contains Kitson's dev
workflow document
(https://github.com/dojo/dojo-oldmirror/wiki/Dojo-Development-Workflow-on-GitHub)
that would still be usefull :)

Patrick

On Tue, May 21, 2013 at 5:45 AM, Colin Snover
<dojo-contributors< at >zetafleet.com> wrote:

Re: GitHub transfer complete

Colin Snover — 2013-05-21T03:45:09

At this point I'll just keep it around instead of trying to meddle with
history; even with the extra data, it's still far faster than checking
out from Subversion ever was. :)

For fetching old releases, I don't think there is really a preference,
just do whatever works best for you. Since you already have the old
release when you clone the repo from Git I would assume one would just
use Git for all of it.

On 2013-05-20 09:01, Adam L. Peller wrote:

Re: GitHub transfer complete

Adam L. Peller — 2013-05-20T14:01:25


The ant script does not require any resources on the network.  Thankfully,
the ant script will be going away in 2.0, but we'll still be consuming data
from the CLDR site.  Any solution which fetches them dynamically is fine
with me, as long as it's tied to a particular revision.

Do we plan to keep svn around indefinitely?  What would be the preferred
way to fetch old releases?  git or svn?  Not having the right version of
core.zip available somehow for old releases would be a problem.  If we
really had to, we could provide some sort of wiki page pointing to the data
for each release.

-Adam
_______________________________________________
dojo-contributors mailing list
dojo-contributors< at >mail.dojotoolkit.org
http://mail.dojotoolkit.org/mailman/listinfo/dojo-contributors

Re: Decisions

Kenneth G. Franqueiro — 2013-05-20T12:44:20

I'm pretty sure the thought was to implement a processor for
js-doc-parse that supports the jsdoc syntax, not actually use jsdoc -
while jsdoc3 supports more tags, it also has a hard dependency on not
only rhino, but a specific custom version of it.

I think we do need to decide exactly what set of jsdoc tags we would be
intending to support though.

--Ken

On 5/20/2013 6:19 AM, Bill Keese wrote:

Re: GitHub transfer complete

Ed Chatelain — 2013-05-20T11:39:11

In addition to those the todpApp is also missing in demos:
todoApp https://github.com/cjolif/dojo-todo-app/trunk

Thanks,
Ed


On Sun, May 19, 2013 at 7:04 PM, Bill Keese <bill< at >dojotoolkit.org> wrote:

Re: Decisions

Dylan Schiemann — 2013-05-20T11:01:41

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I was somewhat confused by that, as well as between what the difference
is between it, and
http://dote.kitsonkelly.com/topic/4beeb59b-1f87-4b8e-8d2c-0bb750c2aa08

Perhaps this topic can be cleaned up to talk through what's in heya/ctr?

I would like to have the following be made more explicit in the discussion:

* What's the difference between templating and code generation. The
original proposal description "Functional machinery is implemented by
heya-ctr and heya-pipe. The former contains simple template engines and
facilities for the code generation." isn't explicit enough to avoid
confusion.
* Is this a proposal for HTML templating support, or something else
* Is this syntax adopted from somewhere else, or is it a new grammar/syntax?
* Was something like peg.js considered?

Regards,
- -Dylan

on 5/20/13 3:47 AM (GMT-07:00) Bill Keese said the following:
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: Using GnuPG with Mozilla - http://en

Re: Decisions

Kitson Kelly — 2013-05-20T10:51:08

My opinion is that those are two separate questions.  The existing topic (
http://dote.kitsonkelly.com/topic/18472303-5835-4602-94a4-b0137a084cab)
needs to be clarified to meet question 1 and a second topic needs to
address option to.  I will manipulate those in the backend to accomplish
that goal.  I am still working on the feature to allow editing of this post
creation.
_______________________________________________
dojo-contributors mailing list
dojo-contributors< at >mail.dojotoolkit.org
http://mail.dojotoolkit.org/mailman/listinfo/dojo-contributors

Re: Decisions

Bill Keese — 2013-05-20T10:47:09

Ah I see.

I regret my wording to the topic
http://dote.kitsonkelly.com/topic/12ac19ca-9da1-43de-b172-80b564d6e808.
My goal was actually to review the functionality and API of heya/ctr, not
to have a meta-physical discussion about "what is core".   Too late now I
guess.

On Mon, May 20, 2013 at 7:38 PM, Dylan Schiemann <dylan< at >dojotoolkit.org>wrote:

_______________________________________________
dojo-contributors mailing list
dojo-contributors< at >mail.dojotoolkit.org
http://mail.dojotoolkit.org/mailman/listinfo/dojo-contributors

Re: Decisions

Dylan Schiemann — 2013-05-20T10:42:55

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

on 5/20/13 3:19 AM (GMT-07:00) Bill Keese said the following:

We had discussed the specifics of what this would mean during one of the
weekly IRC meetings, so hopefully someone (Colin maybe) can either
summarize the points, and/or grab a copy of the log, etc.

I don't know that I've said if we are maintaining our own parser, or
using a third party parser yet. I was under the assumption that we would
not need to add a lot of hints, as this was my original objection
against JSDoc vs. DojoDoc.

I think the main things that need to be decided:

1. API docs inline vs. external
2. If inline, JSDoc (which version, how will this look, etc.) vs. DojoDoc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlGZ/i8ACgkQ1E2HcBNypM7ZXQCeNlnEBoouqtg4UDWcvDqTqTCN
LlgAn2ObMVFIgO/7x8dvbu2F2IGQbm++
=AOQk
-----END PGP SIGNATURE-----

Re: Decisions

Dylan Schiemann — 2013-05-20T10:38:27

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

"Part of core" being the concept that was rejected (everything in core
being one package), vs. a "core package", the concept that was accepted,
where many packages will together constitute the Dojo 2 core.

on 5/20/13 2:50 AM (GMT-07:00) Bill Keese said the following:
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlGZ/SIACgkQ1E2HcBNypM7TdgCfXr0iFQODaAnWvbuoHVTXPMKs
3k8AnjdEvkLpqqkzgL2+/fULTpslQB84
=4AY9
-----END PGP SIGNATURE-----

Re: Decisions

Bill Keese — 2013-05-20T10:19:50

About this topic, it's unclear what's being proposed.   I was assuming that
js-doc-parse gets updated to parse JSDoc comments in addition to (or
instead of) dojodoc format comments.   In that case it's just a question of
converting our dojodoc format comments into JSDoc.

Others (like Dylan) are assuming that we actually use a 3rd party doc
parser, presumably https://github.com/jsdoc3/jsdoc.   In that case IIUC we
would need to add lots of hints (< at >augments, < at >borrows, < at >namespace?, etc.) to
our code, since JSDoc (see http://usejsdoc.org/) doesn't understand AMD or
dojo.declare().
_______________________________________________
dojo-contributors mailing list
dojo-contributors< at >mail.dojotoolkit.org
http://mail.dojotoolkit.org/mailman/listinfo/dojo-contributors

Re: Decisions

Bill Keese — 2013-05-20T09:50:46

What's the difference between a "core package" and "part of core"?

On Mon, May 20, 2013 at 6:43 PM, Dylan Schiemann <dylan< at >dojotoolkit.org>wrote:

_______________________________________________
dojo-contributors mailing list
dojo-contributors< at >mail.dojotoolkit.org
http://mail.dojotoolkit.org/mailman/listinfo/dojo-contributors

Re: Decisions

Dylan Schiemann — 2013-05-20T09:43:57

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

There is strong consensus that Core will likely be more than 1 package,
so I consider
http://dote.kitsonkelly.com/topic/ff0afc9b-cf6b-4d06-95f7-8455f16a3e4c
to be accepted and decided upon.

http://dote.kitsonkelly.com/topic/767c477f-cb74-4ac6-8a89-a531b26b9737
is still fairly divided, so I'm not ready to close that as resolved. I'm
not sure yet what the decision will be, but I'm going to leave this one
open until we have a chance to discuss.

Because of the decision that Core is more than one package, I think
topics like
http://dote.kitsonkelly.com/topic/c28dc5db-5d77-420d-86f7-ff29ce9e2a8d
(loader as part of core),
http://dote.kitsonkelly.com/topic/12ac19ca-9da1-43de-b172-80b564d6e808
(template system as part of core) should be review and updated/revoted
on, with the assumption of it being a core package, not necessarily part
of core. Please review your vote and update by Thursday.

Other decisions to decide by Thursday include:

Adopt Intern as the testing fr

Re: GitHub transfer complete

Eugene Lazutkin — 2013-05-20T04:49:58

I've disabled SVN => GIT mirroring scripts.


On 05/19/2013 05:20 PM, Colin Snover wrote:

Re: GitHub transfer complete

Colin Snover — 2013-05-20T01:36:27

This is my fault; I forgot to copy the attachments from the production
directory before performing the migration, so newer attachments didn't
exist. Everything should be working now.

On 2013-05-19 19:56, Bill Keese wrote:

Re: GitHub transfer complete

Colin Snover — 2013-05-20T01:15:16

For some reason, Edgewall decided to redo the way that attachments are
stored on the filesystem in Trac 1.0. They now use some sort of hashing
mechanism and distributed directory structure instead of just having a
simple file-to-file mapping. It seems some (but not all) of the
attachment filenames were not correctly migrated. I am looking into it.

On 2013-05-19 19:56, Bill Keese wrote:

Re: GitHub transfer complete

Bill Keese — 2013-05-20T00:56:53

PS: Oh, another problem is that I can't *download* the attachment on
https://bugs.dojotoolkit.org/ticket/17132.   I can view it, but not
download it.
_______________________________________________
dojo-contributors mailing list
dojo-contributors< at >mail.dojotoolkit.org
http://mail.dojotoolkit.org/mailman/listinfo/dojo-contributors