Brion Vibber wrote:
Magnus Manske wrote:
[snip]
Then, I think it was two weeks ago, you said
that, after seventeen month
of hot air, that the validation feature was unsalvagable. So I went
ahead and rewrote it as a feature, which was one of your wishes some
month ago. I have not heard anything about that from you either.
I haven't had a chance to go over that code yet; I've got to review
that and Erik's wikidata stuff still. But I do feel a lot better about
it being done as an extension, and I'd love to see it up and running
soon.
Great!
What *I* wish for is a process like this:
* Someone writes a major new function/extension to be used on the
Wikimedia sites
* Someone in charge of these sites (Tim, Brion, whoever) says either
** "OK, that's great, we'll use it right away" OR
** "No, we'll never use that, so don't waste your time" OR
** "We would use it if you fix THIS and change THAT"
Yes, we need to be better about that. I know the most frustrating
thing is waiting for a solid reaction, and I'm sorry I haven't been as
good about that as I should.
OK, no hard feelings.
Please call me on it if you see me being wishy-washy on things.
I will! :-)
So, to come back to the original topic, this is
*the* chance to answer a
few of my questions:
* Is /anyone/ actively working on a stable version feature?
Tim has been working on it for about a week, and is about to commit
into a branch.
* If so, is it already more advanced than the
code I put into CVS?
We'll see when he commits his code, which should be Very Soon Now.
OK. As I
said, I'm not trying to push my code here because /I wrote it/.
Tim likely knows the MediaWiki code better than I do, so we'll probably
end up using his solution. I have no problem with that at all, I'm just
glad things get done.
* Is there some other reason this can't be
done based on my code?
Who knows. :D
I'll be on the 22C3, so maybe we could
discuss these things in person.
Great, I'll see you there!
Looking forward to it.
A few things:
* Those of us who are mostly chatting on IRC, we should remember to
keep everybody posted on the mailing list when we start or finish
something major.
* If actively working on code, popping into IRC is strongly
recommended to get some immediate feedback. In particular, I'd like to
ask that anyone making commits to CVS be in #mediawiki at the time to
respond to questions or reactions that others may have.
Personally, I prefer mails;
IRC always strikes me as ... hectic. I'll
try to be there more often, though.
* Those of us working on code for more than a day or two without it
making it into CVS should show post work patches from time to time to
show our progress. A live demo site is particularly helpful.
This is probably
intended for Tim :-) as I have always tried to supply both.
I'd like to remark that a *central* demo site might be more helpful. We
do have the test site, but there should be an easy way to
* update it from live CVS
* turn extensions on and off, and alter the test database (add new
tables for extensions etc.), for CVS developers
Maybe I should write some code for that. Then again, maybe not ;-)
Magnus