Following my my previous mail "Attention developers" in which I made wrong
assumptions. Let's do some discussion first.
So, before I go further I'm trying to get a sense of what is currently
going on. And hopefully the problems and gaps will uncover themselves as we
go.
I wrote a page on mw.org with an overview of topics, audiences, example
cases
and a column for how we handle those.
Check out http://www.mediawiki.org/wiki/User:Krinkle/Communication and feel
free to fill in, correct, etc. as you see fit.
Thanks,
-- Krinkle
It's been a hectic few weeks for many of you who subscribe to this list,
preparing for and then carrying out the 1.18 upgrade, with all its last
minute patches and after-the-fact patches. It is easy for those of us
uninvolved in the process to play armchair quarterback, and to decry that
the upgrade failed to be seamless. I recognize that there was beta testing
going on at some of the smaller projects over the last little while, but
many of the things that were noticed once the "big" wikis were upgraded may
never have been triggered (or were considered unimportant) in the smaller
projects; software features that become indispensible on more mature
projects might be rarely used in those who are still in their infancy.
This has been the first upgrade that I've really paid a lot of attention to,
and I was really impressed with the response of the Ops team, in particular
Mark Hershberger's work at the English Wikipedia Village Pump (Technical).
Having an experienced Ops team member calmly addressing issues identified
on-project, and making sure that there was a matching bugzilla, was a major
factor in keeping the level of community distress at a minimum during the
immediate aftermath of the upgrade.
I know there's still much to do, both in resolving issues from this upgrade
and in addressing other issues for the next upgrade. But I thought the tech
team might appreciate knowing that it went pretty smoothly from this
non-techie's point of view.
Best,
Risker
(Administrator, English Wikipedia)
When we go to special:search/blah now, if [[foo]] exists the search
page will redirect us to [[foo]].
Is it possible for the special:search logic to take us to
[[category:foo]] if [[foo]] doesnt exist and [[category:foo]] does?
This could be useful on Commons where there is often have a well
maintained category structure with better results than the search
results, and gallery pages ([[foo]]) are not as well maintained.
--
John Vandenberg
This week I've been watching [[WP:VPT]] and copying relevant issues into
bug reports on Bugzilla. You can see the reports here:
https://bugzilla.wikimedia.org/29876
I would like to make these bug reports more profitable, though.
As Brion has said (http://en.wikipedia.org/w/index.php?diff=454166570),
we don't really have good acceptance tests to ensure that we produce
consistent behavior with each release.
To begin to solve this, please help me tag relevant bugs "need-unittest"
or "need-parsertest" and then look for that tag and help write tests.
If we do this right, the 1.19 release will be a *lot* smoother.
Mark.
On 5 October, 2011, we held a bug triage for open fundraising-related issues
in Bugzilla. We specifically selected low-hanging fruit to keep the barrier
to participation low.
During the triage, we made it through 9 of the 12 selected bugs. You can
view the full list of bugs in Bugzilla: http://bit.ly/qSGKn4
We closed a couple of them, but we are still looking for help in closing the
remaining issues - please take a stab at closing one or some of these issues
and be in touch!
== i18n-related bugs ==
* https://bugzilla.wikimedia.org/19895 * **Fold identical messages, or state
that they should or could be different.*
This component (FundraiserPortal), is no longer in use, so this bug was
closed, marked RESOLVED WONTFIX.
== ContributionReporting bugs ==
* http://bugzilla.wikimedia.org/23599 *Add support for date range in
ContributionTrackingStatistics*
The idea here is to be able to specify a particular date range and get
corresponding fundraising-related stats back. This is a relatively
straightforward new feature that would greatly increase the usability of
this page. Performance is something to keep in mind while implementing this
feature, and could be a nice introduction for someone learning how to deal
with caching and concurrency issues on the WMF cluster.
The special page in question can be viewed at
http://wikimediafoundation.org/wiki/Special:ContributionStatistics
* http://bugzilla.wikimedia.org/25430 *Fundraising-related Special pages
need header and footer messages*
This is a really easy bug to knock out - great for a quick fix by a vet or a
really gentle introduction to MediaWiki hacking. It simply requires adding
some i18n messages (which could be empty) that get loaded in
the appropriate place on the page, which can then be overridden on-wiki.
* http://bugzilla.wikimedia.org/25608 *MediaWiki:Fundraiserstats-tab-ytd
should not contain (USD)*
The feature in reference was introduced here:
http://www.mediawiki.org/wiki/Special:Code/MediaWiki/60222. The messaging
could either be modified on-wiki or could be changed in-code.
* http://bugzilla.wikimedia.org/26387 *Add better key to Fundraiser stats
page*
A fun and straightforward feature enhancement for one of the key
community-facing stats pages of the fundraiser (
http://wikimediafoundation.org/wiki/Special:FundraiserStatistics). There may
have been some work done on this already in trunk - if there is, it is
likely incomplete. All that this entails is adding a key or legend to the
stats graph.
* http://bugzilla.wikimedia.org/30820 *Special:FundraisingStatistics graph
spills out of main content area*
We did not have time to address this issue during the triage.
* http://bugzilla.wikimedia.org/30818 *Special:FundraisingStatistics should
display selected years and localizable by timezone*
We did not have time to address this issue during the triage.
== CentralNotice bug ==
* http://bugzilla.wikimedia.org/28903 *Make banner translations get deleted
when banners are removed automatically*
This issue might become easier to resolve with the impending implementation
of the Translage extension on meta.wikimedia.org
== CiviCRM-related bug ==
* http://bugzilla.wikimedia.org/24830 *International addresses not
displaying and/or saving correctly*
This one is a little hairy and very annoying. Abbreviations for 'states' for
47 non-US countries are numerical digits in the CiviCRM database. Mark
Hershberger said he would open a bug in CiviCRM to deal with this issue.
aude_ suggested that data could be taken from
naturalearthdata.com<http://natualearthdata.com/>.
If anyone wants to tackle this, efforts should be coordinated with the
CiviCRM community (see #civicrm on irc.freenode.net).
--
Arthur Richards
Software Engineer
Fundraising/Features/Offline/Mobile
[[User:Awjrichards]]
IRC: awjr
+1-415-839-6885 x6687
Ive done some quick research but cant seem to find if there are any mobile
skins/plugins/etc that make bug viewing and commenting easy on a mobile.
Sure there are apps but id rather see a mobile web compatible view.
Has anyone seen one? And if not are you interested in building one ?
--tomasz
I'm sorry for the slow response to the commit access request queue
recently - the 1.18 deploy and some slowness on my end are the cause.
* Tim Weyer (cervidae) - GlobalUserGroups extension
* Smoke 003723 (smoke3723) - Sternograph extension
* Sumana Harihareswara (sumanah) - community management
Please welcome them/us. :-)
--
Sumana Harihareswara
Volunteer Development Coordinator
Wikimedia Foundation
The Swedish Wikisource community has decided not to file any
bug report for the fact that LiquidThreads has again crashed
after the upgrade to MediaWiki 1.18. Instead, the local
village pump and other discussions will return to the old
plain wiki text format with colon indentation. We don't see
how LiquidThreads could ever become a reliable system, so
we will just pretend it never existed.
I'm personally very sorry and wish to apologize if my early
enthusiasm for LT gave anybody else the false impression that
this could be a working solution.
--
Lars Aronsson (lars(a)aronsson.se)
Aronsson Datateknik - http://aronsson.se