I invite you to the yearly Berlin hackathon. It's 1-3 June and
registration is now open. If you need financial assistance or help with
hotel/hostel, just mention it in the registration form.
https://wmberlin.eventbrite.com/
This is the premier event for the MediaWiki and Wikimedia technical
community. We'll be hacking, designing, and socialising, primarily
talking about Gadgets, the switch to Lua, Wikidata, and Wikimedia Labs.
Our goals for the event are to bring 100-150 people together, with
lots of people who have not attended such events before. User
scripts, gadgets, API use, Toolserver, Wikimedia Labs, mobile,
structured data, templates -- if you are into any of these things, we
want you to come!
Details: https://www.mediawiki.org/wiki/Berlin_Hackathon_2012
Thanks to Wikimedia Germany for hosting and coordinating this event.
(Venue still to be determined.)
--
Sumana Harihareswara
Volunteer Development Coordinator
Wikimedia Foundation
> That documentation completely misses the point :(
> There's no list of what actions to use in the factory, or that a login
> action has setPassword method (as you're using the magic method __set(),
> those things aren't listed by phpDocumentor).
> It's that kind of things what I'd want to view (or an explanation on how
> to map the api documentation to dementia).
Like most generated documentation, the audience is more developers
than end users (I hope to do a better write-up soon for end users,
including what the core goals of the framework are, but I'm aware that
my progress is slow at the moment). All of the methods to use on an
Action or Query instance *are* listed, though; you can get variables,
set variables, and execute, and that's it.
The variables you can get or set depend on what action or query is
specified, but there is not a separate framework class for each action
or query. The variables are by necessity defined in the API
documentation (e.g. http://www.mediawiki.org/wiki/API:Allpages) and
not the framework documentation; while I could write up examples using
the framework for each type of action and query, I couldn't possibly
cover the sheer breadth of options that are available in the API.
The point at the moment is that the framework automagically handles
all prefixing of parameters, including generators' parameters, so the
end user's code is more readable; it also continues queries
automatically and selects an appropriate backend for actions and
queries (which is its primary purpose).
Does that make more sense?
-Madman
http://opensourcebridge.org/blog/2012/03/cfp-deadline-extended-until-march-…
You (yes you, no matter where you live or who you work/don't work for)
have less than a day to submit a talk about Wikimedia stuff to Open
Source Bridge, a great open source conference. If your talk gets
accepted, tell me, and WMF will partially or fully subsidize your flight
and hotel. Details and ideas:
http://lists.wikimedia.org/pipermail/wikitech-l/2012-March/058791.html
I'll be there (keynote speaker), and Roan, Alolita, RobLa, Trevor,
Ironholds, jorm, and Ward Cunningham have submitted talks. Join us!
--
Sumana Harihareswara
Volunteer Development Coordinator
Wikimedia Foundation
Hi all, I made a HTML file named "mgedawy.htm" in order to make my userpage
in the Toolserver webserver, And put the file inside the folder "*
public_html/*". The problem is that i find the page i created at:
http://toolserver.org/~mgedawy/mgedawy.htm instead of:
http://toolserver.org/~mgedawy/
How can i solve this please?
Hi.
Two questions:
What is nightshade's status? I read
<https://jira.toolserver.org/browse/MNT-1198> but the last activity from the
roots is from February 27, nearly a month ago.
Are the crontabs from nightshade gone? Some people still believe that when
nightshade returns that their cronjobs will return, but I'm fairly sure the
system was wiped and that the crontabs are gone. Can one of the roots please
answer this definitively so that I can cite the mailing list reply? :-)
Thank you!
MZMcBride
I note that MNT-1225, which was originally projected to take over 24 hours,
is now closing in on 72 hours and there doesn't seem to be any meaningful
way to project a completion time. Nothing we can do about that now, of
course.
But, I am wondering whether it was necessary to run these updates on *both*
replicas of s1 (s1-sql-rr and s1-sql-user) at the same time? This is really
a naive question, as I don't know enough about mysql administration to even
guess at the answer. Perhaps someone more knowledgeable can enlighten us.
(I do observe, however, that WMF seems to have managed to update all of its
database slaves in some kind of sequential fashion that didn't impact access
to enwiki.)
If, in fact, there is no technical requirement for updating both replicas at
the same time, I would suggest that the next time a situation like this
arises, it would make more sense to do the updates sequentially so that
users (both toolserver users and tool users) are not deprived of access to
this resource for such a long time.
Russ
I'm having some trouble with the database on the toolserver.
When I connect to my userdb (mysql -h enwiki-p.userdb.toolserver.orgu_grphack)
and run an INSERT command on a table, I get the following error:
ERROR 1290 (HY000): The MySQL server is running with the --read-only option
so it cannot execute this statement
Are others getting this error? Does this have to do with the changes to
mediawiki 1.19 (i.e. the inclusion of a text checksum field)? If so, when
can I expect to be able to write to tables in my userdb again?
In case this works better for the admins workflow, I've filed a bug here:
https://jira.toolserver.org/browse/TS-1334
Thanks,
-Aaron
On 12 March 2012 15:49, Hydriz Wikipedia <admin(a)alphacorp.tk> wrote:
> Tparis has the full source code of those tools, and looks like he has
> already brought them up on his own account. See
> https://toolserver.org/~tparis.
>
>
Could we (in general) *please* not do this? If someones tools are important
enough to be taken over by someone else, they are most certainly important
enough for a multi-maintainer project. In {one month, one year, five
years}, Tparis' account will also expire and we will have the same problem
all over again.
Best,
Merlijn
Hello all,
as you may noticed nightshade is not re-setup yet and also yarrow is not back
for use. That have a reason: We decided to get rid of Solaris on the userland-
server again, because no real solaris-expert is left in the root-group; but
there are 2 Debian-users in the group so we choose Debian as new operating
system.
The original plan was to use yarrow as a playground and when everything is fine
there to switch willow. For some unknown reason, nightshade lost its solaris-
installation shortly after or during the last colo-visit.
So the plan was changed in the following manner: We use yarrow as playground,
but try to speed up everything, and when we fine with it, we switch
*nightshade* over. I hope to make all changes to puppet (our server-managment-
system) during the next 7 days, but it may take few days longer.
If you are a Debian-user too, you can help me a little bit: Insert needed
packages at [1] and help other users to find packages for their needed
liberies.
Willow will keep Solaris for several more months (if nothing bad happens with
it), so there will be no problems with non-running tools. At first everything
will keep running on willow and when you are ready you can switch over your
tools to Debian (if you use SGE, that will be very easy because only 1 flag has
to set – more details later) – for most tools there should be no (big)
problems.
Just as a information for you what is going on at the moment.
Sincerley,
DaB.
[1] https://wiki.toolserver.org/view/User:Dab/Debian-Packages
--
Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885