I would add that I am of course open to reorganization and would happily
discuss why any given decision was made ... be it trade offs with other
ways of doing things or lack of time to do it differently / better.
I also add that not all the legacy support and metavid based code has
been factored out. (for example for a while I supported the form based
upload but now that the upload api is in place I should remove that old
code) Other things like timed text support are barely supported because
of lack of time. But I would want to keep the skeleton of timed text in
there so once we do get around to adding timed text for video we have a
basis to move forward from.
I suggest for a timely release that you strip the js2 folder and make a
note that the configuration variable can not be turned on in this
release. And help me identify any issues that need to be addressed for
inclusion the next release?
And finally, the basic direction and feature set was proposed on this
list quite some time ago and ~some~ feedback was given at the time.
I would also would echo Trevor's call for more discussion with affected
parties if your proposing significant changes.
peace,
--michael
Trevor Parscal wrote:
On 9/22/09 6:19 PM, Tim Starling wrote:
Siebrand Mazeland wrote:
Hola,
I just created
https://bugzilla.wikimedia.org/show_bug.cgi?id=20768 ("Branch
1.16") and Brion was quick to respond that some issues with js2 and the
new-upload stuff need to be ironed out; valid concerns, of course.
I proposed to make bug 20768 a tracking bug, so that it can be made visible
what issues are to/could be considered blocking something we can make a 1.16
out of.
Let the dependency tagging begin. Users of MediaWiki trunk are encouraged to
report each and every issue, so that what is known can also be resolved
(eventually).
I'm calling on all volunteer coders to keep an eye on this issue and to help
out fixing issues that are mentioned here.
I've been working on a rewrite of the script loader and a
reorganisation of the JS2 stuff. I'd like to delay 1.16 until that's
in and tested. Brion has said that he doesn't want Michael Dale's
branch merge reverted, so as far as I can see, a schedule delay is the
only other way to maintain an appropriate quality.
-- Tim Starling
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
If you are really doing a JS2 rewrite/reorganization, would it be
possible for some of us (especially those of us who deal almost
exclusively with JavaScript these days) to get a chance to ask
questions/give feedback/help in general?
While I think a rewrite/reorganization could be really awesome if done
right, and also that getting it right will be easier if we can get some
interested parties informed/consulted.
I know that Michael Dale's work was more or less done outside of the
general MediaWiki branch for the majority of it's development, and afaik
it has been a work in progress for some time, so I feel that such a
golden opportunity has never really come up before.
Aside from my own desire to be involved at some level, it seems fitting
to have some sort of discussion at times like these so we can make sure
we are making the best decisions about software before it's deployed -
as making changes to deployed software is seems to often be much more
difficult.
Perhaps there's a MediaWiki page, or a time on IRC, or even just
continuing on this list...?
My first question is: "What are you changing and how, and what are you
moving and where?"
- Trevor
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l