Is anyone working on fixing the broken output from
http://en.wikipedia.org/wiki/Special:ValidationStatistics ?
I brought this up on IRC a week-ish ago and there was some speculation
as to the cause but it wasn't clear to me if anyone was working on
fixing it.
Roan Kattouw wrote, at 20:33:44 UTC on 2010-06-23:
> I think calling $j.collapsibleTabs.handleResize(); yourself should do it.
Unfortunately, that doesn't fix the problem at all; that function returns the same error, breaking the code into which it's inserted in the process, as then the error is local to that code (rather than occurring in the collapsibleTabs routine). :(
I seem to recall having tried that at some point, but it's been awhile since I've delved into the collapsibleTabs code to look for a solution. I don't think I understand the problem enough to solve it myself.
> Either way, this is a bug in CollapsibleTabs and should be fixed.
Is there an existing bug, or should I file a new one?
Thanks,
Nihiltres
This is a bugfix release related to the previous 1.2b release. The
following has changed:
* Fixed issue with single domains, and non-auto-authentication domains
being non-operational due to security fix in 1.2b
* Fixed another issue with mail me a password not working properly
To download this version, please use the extension distributor
(http://www.mediawiki.org/wiki/Special:ExtensionDistributor/LdapAuthenticati…),
select “Development version (trunk)”, and click “Continue”.
Respectfully,
Ryan Lane
Hi everyone,
Sorry for the email length here. Here's my quick summary:
* Trying to figure out how to do good project management on Bugzilla,
working with the Bugzilla community to juice it up
* Failing that, we'd like to migrate off of it. Leading candidate: Redmine
* Wiki page: http://www.mediawiki.org/wiki/Tracker/PM_tool
And now, the (much) longer version:
As you probably recall, Priyanka has been investigating our use of Bugzilla,
and investigating whether or not it makes sense to keep using it, or migrate
to something else. I'm helping her out with that evaluation now, and here's
where we're at.
We really want to have well-integrated issue management (both feature
requests and bugs) along with project management.
We've informally narrowed the choices down to 1) staying with Bugzilla, or
2) migrating to Redmine. I say "informally" because it's not as though
there's been any formal consensus gathering process of any sort, and we know
we need to really need to involve everyone in this process.
Staying on Bugzilla would obviously be the least disruptive choice, and we'd
prefer to stay with the devil we know rather than find out what Redmine or
some other tracker doesn't have after a migration.
However, looking at Bugzilla, as currently configured, from the point of
view of a project manager, it really doesn't work very well. It's very
difficult to provide a birds-eye view of how a project is progressing
without building a separate manually-maintained wiki page with a project
plan on it. While it seems possible to *cope* as a project manager with
Bugzilla, it doesn't seem like the kind of tool that a project manager could
grow to love, at least not how it exists now.
Redmine has time management built in, and is pretty clearly designed as a
project management tool generally. By way of example, here's the roadmap
for the Redmine project itself:
http://www.redmine.org/projects/redmine/roadmap
It seems to favor old-school time management (with Gantt charts having
better support than Burndown charts), but it looks like a versatile enough
tool to adapt to many different project management styles. Most
importantly, it has sensible defaults that we can count on others also
building upon.
Now, as I've alluded to, the problem may just be with our configuration of
Bugzilla, which is pretty narrowly focused on just tracking bugs. We
reached out to the Bugzilla developers on IRC, and I'm planning to follow up
on the Bugzilla newsgroup:
http://groups.google.com/group/mozilla.support.bugzilla/
As with pretty much any mature piece of infrastructure software, it is
possible to extend it. For example, Max Kanat-Alexander pointed out the new
extension interface in the latest version of Bugzilla, and believes it would
be reasonably simple now to create a roadmap plugin. That's not the only
thing Bugzilla is lacking to be a really good project management tool, so
we'll need a little more than "add roadmaps" to get us where we ultimately
want to be, but having that functionality is a good start.
In order for Bugzilla to be a viable option for project management, the
Bugzilla team would need to demonstrate that they're serious about creating
something competitive in this area. Redmine isn't the only competition that
appears to do better; JIRA is also better in this regard. While we may be
the ones asking most directly right now, I've gotta believe that many other
Bugzilla users are either hitting the same wall we are, or know something
that we don't.
Here's what we're planning to do:
1. Engage the Bugzilla community much more seriously about project
management. Engage the Firefox developers to find out how they're making it
work for them, as well as other large projects (e.g. perhaps GNOME).
2. Simultaneously engage the Redmine community and generally evaluate
Redmine. Make sure we understand a lot better the good and the bad with
it. For example, it appears on the surface that the query abilities aren't
as sophisticated. We'll need to understand if that's going to be a problem
for us.
3. If it looks like Bugzilla is on a rapid enough trajectory to becoming a
great project management tool (with or without our help), then we figure out
how to make that process go as quickly as possible.
4. If it looks like Bugzilla is not going to get there without an
all-too-heroic effort on our part, or it looks like one of the alternatives
is SO compelling that we really should make a switch, then we'll be floating
a migration plan with you all.
Here's the web page that discusses this:
http://www.mediawiki.org/wiki/Tracker/PM_tool
On that page, we get into some more detail about the pros and cons of each
of the tools.
I realize that most of the readers on this list probably are not project
management tool connoisseurs, and you're probably more interested in
Bugzilla for its bug tracking ability. That said, there's probably a
significant number of you that want to be more in-the-loop about what WMF
staff developers are up to. Having access to the tool we use for
scheduling/planning will give you more visibility.
So, here's what I'm hoping you all can help out with:
1. Take a really good look at Redmine, and see if you'd love/hate/be
indifferent to a migration to that tool
2. Help with the process of fleshing out requirements/nice-to-haves on the
wiki page above.
3. Help engage both the Bugzilla and Redmine communities if you've got an
interest in this topic.
Does this all seem reasonable to everyone? Let us know what you think.
Thanks!
Rob
Hey,
I'm giving a loose MediaWiki and SMW workshop the upcoming Sunday in Gent
(Belgium), at the local hackerspace, 0x20 [0]. It'll cover the basics you
need to know to manage a wiki's content and some common extensions. More
info and registration at [1].
[0] http://0x20.be/
[1] http://0x20.be/MediaWiki_workshop
--
Jeroen De Dauw
* http://blog.bn2vs.com
* http://wiki.bn2vs.com
Don't panic. Don't be evil. 50 72 6F 67 72 61 6D 6D 69 6E 67 20 34 20 6C 69
66 65!
--
I've been playing around with customizing Vector a bit. I'm particularly enjoying the inclusion of jQuery; as a newbie to JS it makes many things much easier than they might be otherwise. I've run into a problem that I'm not sure how to work around, and it seems a general enough problem that I figured I'd ask about it here; I hope it's on-topic enough. :P
If one adds a tab to the p-views tab bar, one gets a harmless but annoying "$settings is undefined" error from plugins.combined.min.js (specifically, the Collapsible Tabs code). If the window is resized in such a way that tabs should not collapse, and the new tab does not have the "collapsible" class, the error repeats. If the window is then resized such that one or more tabs are collapsed, nothing new happens; the new tab will be collapsed iff it has the "collapsible" class. If the window is further resized so as to allow the collapsed tabs to uncollapse, the error repeats indefinitely. This is very frustrating for people who want to customize Vector.
As far as I can tell (again, JS newbie), the collapsibleTabs JS assigns some sort of data to each element, settings data that lets the rest of the code put things back into place nicely when it's done. How can I (assuming I can) assign this data to tabs to be added to the p-views tab bar or otherwise avoid* this error? (*No, simply putting/leaving things in p-cactions defeats the purpose.)
Placing extra tabs in the tab bar can be very convenient—for example, one of my scripts moves the "delete" tab out if there's an element on the page which uses one of the classes used by enwiki's deletion templates—but the errors are quire undesirable. Thanks for any help you can provide, and I'll be sure to either write up my solution, or point others to existing documentation in future, if you can point out the gist of it for me.
Thanks,
Nihiltres
As we look more closely at some of the XML dumps being generating, we
are noticing bad revisions hanging around from various conversion bugs.
In particular, nlwiktionary has around 1500 revisions from the early
part of 2004 that are no longer recoverable.
Does anyone have (or know someone who might have) a full history dump of
nl wiktionary from October 2004 or earlier (but no earlier than June)?
If so we could pull the data from there.
Thanks,
Ariel Glenn
Software Developer / Systems Engineer
Wikimedia Foundation