I am trying to work on https://ta.wikisource.org with python API.
This tamil wikisource has custom html option buttons to mention the edit status.
See a screenshot here.
https://snag.gy/f3aTBn.jpg
How to enable these custom option buttons via API?
Thanks.
--
Regards,
T.Shrinivasan
My Life with GNU/Linux : http://goinggnu.wordpress.com
Free E-Magazine on Free Open Source Software in Tamil : http://kaniyam.com
Get Free Tamil Ebooks for Android, iOS, Kindle, Computer :
http://FreeTamilEbooks.com
FYI
---------- Forwarded message ----------
From: Quim Gil <qgil(a)wikimedia.org>
Date: Thu, Apr 28, 2016 at 9:37 AM
Subject: Developer metrics workshop next to OSCON
To: "A mailing list for the Analytics Team at WMF and everybody who has an
interest in Wikipedia and analytics." <analytics(a)lists.wikimedia.org>,
Manrique Lopez <jsmanrique(a)bitergia.com>
Hi, is there anybody in this list planning to attend OSCON (Austin, May
16-19)?
http://conferences.oreilly.com/oscon/open-source-us
Next to that event there will be a workshop about Software Development
Analytics and the new Grimoire toolkit platform, on May 16th (10am - 1pm CDT
):
https://www.eventbrite.com/e/software-development-analytics-workshop-ticket…
The registration is not free, but the organizers (Bitergia, the developers
of http://korma.wmflabs.org/ ) are offering us a couple of invitations.
Andre and I are not attending OSCON (we have participated in the FOSDEM
edition of this workshop). If you or someone you know is interested,
contact me.
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
FYI, the new models (BREAKING CHANGE) are now deployed.
On Sun, Apr 3, 2016 at 5:38 AM, Aaron Halfaker <aaron.halfaker(a)gmail.com>
wrote:
> Hey folks, we have a couple of announcements for you today. First is that
> ORES has a large set of new functionality that you might like to take
> advantage of. We'll also want to talk about a *BREAKING CHANGE on April
> 7th.*
>
> Don't know what ORES is? See
> http://blog.wikimedia.org/2015/11/30/artificial-intelligence-x-ray-specs/
>
> *New functionality*
>
> *Scoring UI*
> Sometimes you just want to score a few revisions in ORES and remembering
> the URL structure is hard. So, we've build a simple scoring user-interface
> <https://ores.wmflabs.org/ui/> that will allow you to more easily score a
> set of edits.
>
> *New API version*
> We've been consistently getting requests to include more information in
> ORES' responses. In order to make space for this new information, we needed
> to change the structure of responses. But we wanted to do this without
> breaking the tools that are already using ORES. So, we've developed a
> versioning scheme that will allow you to take advantage of new
> functionality when you are ready. The same old API will continue to be
> available at https://ores.wmflabs.org/scores/, but we've added two
> additional paths on top of this.
>
> - https://ores.wmflabs.org/v1/scores/ is a mirror of the old scoring
> API which will henceforth be referred to as "v1"
> - https://ores.wmflabs.org/v2/scores/ implements a new response format
> that is consistent between all sub-paths and adds some new functionality
>
> *Swagger documentation*
> Curious about the new functionality available in "v2" or maybe what the
> change was from "v1"? We've implemented a structured description of both
> versions of the scoring API using swagger -- which is becoming a defacto
> stanard for this sort of thing. Visit https://ores.wmflabs.org/v1/ or
> https://ores.wmflabs.org/v2/ to see the Swagger user-interface.
> Visithttps://ores.wmflabs.org/v1/spec/ or
> https://ores.wmflabs.org/v2/spec/ to get the specification in a
> machine-readable format.
>
> *Feature values & injection*
> Have you wondered what ORES uses to make it's predictions? You can now ask
> ORES to show you the list of "feature" statistics it uses to score
> revisions. For example,
> https://ores.wmflabs.org/v2/scores/enwiki/wp10/34567892/?features will
> return the score with a mapping of feature values used by the "wp10"
> article quality model in English Wikipedia to score oldid=34567892
> <https://en.wikipedia.org/wiki/Special:Diff/34567892>. You can also
> "inject" features into the scoring process to see how that affects the
> prediction. E.g.,
> https://ores.wmflabs.org/v2/scores/enwiki/wp10/34567892?features&feature.wi…
>
> *Breaking change -- new models*
> We've been experimenting with new learning algorithms to make ORES work
> better and we've found that we get better results with gradient boosting
> <https://en.wikipedia.org/wiki/Gradient_boosting> and random forest
> <https://en.wikipedia.org/wiki/Random_forest> strategies than we do with
> the current linear svc
> <https://en.wikipedia.org/wiki/Support_vector_machine> models. We'd like
> to get these new, better models deployed as soon as possible, but with the
> new algorithm comes a change in the range of probabilities returned by the
> model. So, when we deploy this change, any tools that uses hard-coded
> thresholds on ORES' prediction probabilities will suddenly start behaving
> strangely. Regretfully, we haven't found a way around this problem, so
> we're announcing the change now and we plan to deploy this *BREAKING
> CHANGE on April 7th*. Please subscribe to the AI mailinglist
> <https://lists.wikimedia.org/mailman/listinfo/ai> or watch our project
> page [[:m:ORES <https://meta.wikimedia.org/wiki/ORES>]] to catch
> announcements of future changes and new functionality.
>
> In order to make sure we don't end up in the same situation the next time
> we want to change an algorithm, we've included a suite of evaluation
> statistics with each model. The filter_rate_at_recall(0.9),
> filter_rate_at_recall(0.75), and recall_at_fpr(0.1) thresholds represent
> three critical thresholds (should review, needs review, and definitely
> damaging -- respectively) that can be used to automatically configure your
> wiki tool. You can find out these thresholds for your model of choice by
> adding the ?model_info parameter to requests. So, come breaking change,
> we strongly recommend basing your thresholds on these statistics in the
> future. We'll be working to submit patches to tools that use ORES in the
> next week to implement this flexibility. Hopefully, all you'll need to do
> is worth with us on those.
>
> -halfak & The Revision Scoring team
> <https://meta.wikimedia.org/wiki/Research:Revision_scoring_as_a_service>
>
Hello everyone,
The reading team's interaction consultation
<https://www.mediawiki.org/wiki/User_Interaction_Consultation> has been
wrapped up. Thanks for those who created new accounts in order to
participate and thanks to those who spent time writing proposals and adding
ideas. All in all we have 26 ideas. Some ideas are more relevant to the
topic of interaction than others, and some seemed more feasible than
others, so with these two parameters in mind, relevance and feasibility,
we have put together a shortlist, and added them as potential ideas for
brainstorming for Q1
https://www.mediawiki.org/wiki/Reading/Quarterly_planning/Q1. The
conversation can continue on the talk pages for each proposal or on the
talk page of Q1 planning. We added ideas to Q1 planning, which is the
earliest planning stage at the momet, however, ideas that don't get a
chance for further research or implementation in Q1, will be still be
considered for Q2, and other future plans, this is not the end of it :-).
This has been an interesting experiment, with lots of learning that
extended beyond the topic of interactivity, starting from how to avoid
jargon language on mailing lists, all the way, to how we really need to
enhance our mobile experiment to better serve our community engagement
through mobile.
Thanks to Wikimedia Foundation's communication team for their help with
promoting the consultation through our different non-wiki venues, and once
again thanks to all volunteers and staff who spent time in adding or
discussing ideas.
We are looking forward to the second phase of discussion, and to
possibilities of having proposals implemented starting Q1 or a distant
future to follow.
All the best,
Moushira
On Thu, Mar 17, 2016 at 2:12 AM, Derek V.Giroulle <
derekvgiroulle(a)wikimedia.be> wrote:
> Hello Moushira,
>
> Iḿ sorry i didn't say this explicitely , i was n persoanlly attacking you
> i was as you point out focussing the critic at jargon use in the WMF
>
> thanks
> derek
>
>
> On 16-03-16 17:58, Richard Symonds wrote:
>
>> Thanks Moushira :-)
>> On 16 Mar 2016 16:55, "Moushira Elamrawy" <melamrawy(a)wikimedia.org>
>> wrote:
>>
>> Hello again,
>>>
>>> I see that we have an interesting input here.
>>>
>>> Let me add further context, not to give any excuses but to put things in
>>> their perspective. This has nothing do to with corporate or jargon
>>> Silicon
>>> Valley culture, as I simply don't live in the US, and I don't have any
>>> corporate background :). I come from a design background, and while I am
>>> not a native English speaker, I didn't encounter any previous
>>> misunderstanding with using this word, in context, in the last decade,
>>> even
>>> with other non-native speakers.
>>>
>>> I now see the relevance of psychology in the use of the word "ideation"
>>> (where regardless of the article quality, we have the word used in both
>>> context
>>> <
>>>
>>> https://en.wikipedia.org/w/index.php?title=Special:WhatLinksHere/Ideation_%…
>>>
>>>> still)
>>>>
>>> . Given my non-medical background, and my previous use of the word,
>>> without
>>> failing to deliver what I needed to express at any point earlier, I,
>>> therefore, made a choice to include it in my email, which I wrote by
>>> myself
>>> without peer review.
>>>
>>> I see the point around the Foundation's seemingly repeated pattern of
>>> using
>>> words (or abbreviation) that aren't widely understood outside their
>>> context, or by a broader audience. While this is a valid concern, I just
>>> wanted to point out that our case here, is a matter of me failing to
>>> choose
>>> a term that isn't apparently jargon, because sometimes it is tricky to
>>> decide.
>>>
>>> Again, this is a good lesson on the importance of simplifying and
>>> globalizing my choice of words (oh, globalize could be jargon..no, not
>>> again ;).
>>>
>>> Point taken, thanks again everyone.
>>>
>>> Moushira
>>>
>>>
>>> On Wed, Mar 16, 2016 at 4:41 PM, Oliver Keyes <ironholds(a)gmail.com>
>>> wrote:
>>>
>>> While I agree with people that it's an uncommon and exclusionary
>>>> phrase (and a confusing one!) it seems like Moushira fully
>>>> acknowledges this and is going to work harder on this sort of problem
>>>> in the future, for which I laud her.
>>>>
>>>> If we want to have a general conversation about language choice at the
>>>> WMF, broadly-construed, it seems like it would be best to kick off a
>>>> new thread to avoid the appearance of a pileon.
>>>>
>>>> On Wed, Mar 16, 2016 at 9:13 AM, Derek V.Giroulle
>>>> <derekvgiroulle(a)wikimedia.be> wrote:
>>>>
>>>>> Hello everyone ,
>>>>>
>>>>> I agree with Fae and Craig,
>>>>> It's foreign jargon especially in this context , and on top of that
>>>>>
>>>> jargon
>>>>
>>>>> form a professional background where the term has been misused (imho)
>>>>> It has in my jargon the connotation of obsessively recurring idea ,
>>>>>
>>>> like
>>>
>>>> a
>>>>
>>>>> depressed patient
>>>>> always coming back to ideas of suicide : the suicidal ideation
>>>>> It would be the only place where i would allow fosuch reductive jargon
>>>>> because it has precise meaning
>>>>> i wouls never associate it with idea generation or brainstorming what
>>>>>
>>>> is
>>>
>>>> wrong with using those words
>>>>> as craig indicated : cringe worthy (business) jargon
>>>>> the mere fact that product design (business ing general) is stealing a
>>>>>
>>>> word
>>>>
>>>>> form other jargon
>>>>> show a lack of creativity of innovation
>>>>>
>>>>> I would like to call on the communications dept to start - and i can
>>>>>
>>>> just
>>>>
>>>>> picture someone for that task - a campaign
>>>>> at WMF to ban jargon "simply says it better"
>>>>>
>>>>>
>>>>> derek
>>>>>
>>>>>
>>>>>
>>>>> On 16-03-16 04:39, Craig Franklin wrote:
>>>>>
>>>>>> Hi Moushira,
>>>>>>
>>>>>> The problem when you use jargon like "ideation" in this context is
>>>>>>
>>>>> that
>>>
>>>> you're essentially excluding anyone who isn't familiar with the
>>>>>>
>>>>> particular
>>>>
>>>>> terminology used in the field. Especially so when there are plenty of
>>>>>> plain-English alternatives that can be used in its place. Note that
>>>>>>
>>>>> there
>>>>
>>>>> is a whole bunch of thought from experts that that word in particular
>>>>>>
>>>>> is a
>>>>
>>>>> particularly obnoxious piece of jargon:
>>>>>>
>>>>>> * http://money.cnn.com/2014/10/26/pf/corporate-jargon/
>>>>>> * https://hbr.org/2008/08/why-jargon-feeds-on-lazy-minds.html
>>>>>> *
>>>>>>
>>>>>>
>>>>>>
>>> http://www.lifed.com/10-cringeworthy-business-jargon-examples-that-should-b…
>>>
>>>> It's hardly the worst example I've seen out of the WMF, but while
>>>>>>
>>>>> we're
>>>
>>>> on
>>>>
>>>>> the topic it should be pointed out. Just because it's used elsewhere,
>>>>>>
>>>>> it
>>>>
>>>>> doesn't mean that the WMF has to fall into the same trap.
>>>>>>
>>>>>> Cheers,
>>>>>> Craig
>>>>>>
>>>>>> On 16 March 2016 at 10:07, Moushira Elamrawy <melamrawy(a)wikimedia.org
>>>>>> wrote:
>>>>>>
>>>>>> Hello Fae,
>>>>>>>
>>>>>>> Ideation phase [0], is a term widely used in product and design
>>>>>>>
>>>>>> context.
>>>>
>>>>> Now, I see your point around how volunteers who are not related to
>>>>>>>
>>>>>> these
>>>>
>>>>> fields, might not be familiar with it. Possibly something like, idea
>>>>>>> generation, or brainstorming could have replaced it.
>>>>>>>
>>>>>>> I am not sure though if the factors that you have listed are
>>>>>>>
>>>>>> relevant;
>>>
>>>> I
>>>>
>>>>> think it is a matter of using a word in a certain context where it
>>>>>>> actually
>>>>>>> fits, without realizing how a broader audience would perceive it.
>>>>>>>
>>>>>>> In any case, thanks for the note :-)
>>>>>>>
>>>>>>> [0] https://en.wikipedia.org/wiki/Ideation_%28creative_process%29
>>>>>>>
>>>>>>> Moushira
>>>>>>>
>>>>>>> On Wed, Mar 16, 2016 at 1:51 AM, Fæ <faewik(a)gmail.com> wrote:
>>>>>>>
>>>>>>> On 15 March 2016 at 22:33, Moushira Elamrawy <
>>>>>>>>
>>>>>>> melamrawy(a)wikimedia.org
>>>
>>>> wrote:
>>>>>>>> ...
>>>>>>>>
>>>>>>>>> The reading team is launching an experiment that supports early
>>>>>>>>>
>>>>>>>> engagement
>>>>>>>>
>>>>>>>>> in ideation phase, with a wide variety of users.
>>>>>>>>>
>>>>>>>> ...
>>>>>>>>
>>>>>>>> Hi, sorry to target your email with a more general observation,
>>>>>>>> however there seems to be a lot of odd jargon in Wikimedia
>>>>>>>> announcements over the last few months. It would be great to see
>>>>>>>>
>>>>>>> more
>>>
>>>> 'official' emails aimed at volunteers, written in plain and
>>>>>>>> grammatically complete English. Phrases like "ideation phase" may be
>>>>>>>> frequently used during meetings at the Wikimedia Foundation offices,
>>>>>>>> but are unlikely to be heard in real life by volunteer contributors,
>>>>>>>> and are unlikely to be easily understood outside of corporate
>>>>>>>>
>>>>>>> America,
>>>
>>>> especially by those without English as their first language.
>>>>>>>>
>>>>>>>> Sorry again about picking at your announcement rather than any
>>>>>>>>
>>>>>>> other,
>>>
>>>> it just stood out today.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Fae
>>>>>>>> --
>>>>>>>> faewik(a)gmail.com https://commons.wikimedia.org/wiki/User:Fae
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Wikimedia-l mailing list, guidelines at:
>>>>>>>> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
>>>>>>>> New messages to: Wikimedia-l(a)lists.wikimedia.org
>>>>>>>> Unsubscribe:
>>>>>>>>
>>>>>>> https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
>>>
>>>> ,
>>>>
>>>>> <mailto:wikimedia-l-request@lists.wikimedia.org
>>>>>>>>
>>>>>>> ?subject=unsubscribe>
>>>
>>>> _______________________________________________
>>>>>>> Wikimedia-l mailing list, guidelines at:
>>>>>>> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
>>>>>>> New messages to: Wikimedia-l(a)lists.wikimedia.org
>>>>>>> Unsubscribe:
>>>>>>>
>>>>>> https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
>>>
>>>> <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>> Wikimedia-l mailing list, guidelines at:
>>>>>> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
>>>>>> New messages to: Wikimedia-l(a)lists.wikimedia.org
>>>>>> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
>>>>>>
>>>>> ,
>>>
>>>> <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
>>>>>>
>>>>>
>>>>> --
>>>>> Kind regards,
>>>>> *Derek V. Giroulle*
>>>>> Wikimedia Belgium vzw.
>>>>> Treasurer
>>>>> Troonstraat 51 Rue du Trône, BE-1050 Brussels
>>>>> M: derekvgiroulle(a)wikimedia.be
>>>>> T: +32 494 134134
>>>>> F: +32 3666 2700
>>>>>
>>>>> _______________________________________________
>>>>> Wikimedia-l mailing list, guidelines at:
>>>>> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
>>>>> New messages to: Wikimedia-l(a)lists.wikimedia.org
>>>>> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
>>>>> <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
>>>>>
>>>> _______________________________________________
>>>> Wikimedia-l mailing list, guidelines at:
>>>> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
>>>> New messages to: Wikimedia-l(a)lists.wikimedia.org
>>>> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
>>>> <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
>>>>
>>>> _______________________________________________
>>> Wikimedia-l mailing list, guidelines at:
>>> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
>>> New messages to: Wikimedia-l(a)lists.wikimedia.org
>>> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
>>> <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
>>>
>> _______________________________________________
>> Wikimedia-l mailing list, guidelines at:
>> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
>> New messages to: Wikimedia-l(a)lists.wikimedia.org
>> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
>> <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
>>
>
> --
> Kind regards,
> *Derek V. Giroulle*
> Wikimedia Belgium vzw.
> Treasurer
> Troonstraat 51 Rue du Trône, BE-1050 Brussels
> M: derekvgiroulle(a)wikimedia.be
> T: +32 494 134134
> F: +32 3666 2700
> _______________________________________________
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> New messages to: Wikimedia-l(a)lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
>
Howdy,
A few updates on the work of the Discovery team this week. Thanks to those
who sent something in, and thank you for reading.
* David, Erik, and Trey had a discussion with JustinO about improving
recall and improving search in general. Semi-readable notes are in an
etherpad <https://etherpad.wikimedia.org/p/Recall>. Additional thoughts and
comments are welcome.
* Deb and Moiz had discussions with Abbey, Daisy and Edward about upcoming
surveys planned for the Wikipedia portal; awaiting Legal approval.
* The updated Perl version of TextCat is now available on GitHub
<https://github.com/Trey314159/TextCat>. Reminder: the PHP version
<https://github.com/wikimedia/wikimedia-textcat> has been available for a
while.
* Analysis has been completed
<https://www.mediawiki.org/wiki/User:TJones_(WMF)/Notes/TextCat_Optimization…>
on low-performing [search] queries (< 3 results) on French, Spanish, and
Italian Wikipedias, to optimize performance on language identification with
TextCat on those wikis. German is coming up next.
* Analysis is complete on recent Wikipedia.org portal page A/B test: Wikipedia
Portal Test of Language Detection and Primary Link Resorting
<https://commons.wikimedia.org/wiki/File:Wikipedia_Portal_Test_of_Language_D…>
* Maps servers now have 16 varnish servers instead of 2 in 4 different data
centers instead of 1.
* A new Wikipedia portal A/B test will be released next week - it will add
in descriptive text to the sister project links at the bottom of the page.
* Search for a new analyst (Oliver's replacement) is going along well. We
got 169 applicants and some of them have done or are scheduled to do the
take-home analysis task.
----
Feedback and suggestions on this weekly update are welcome.
The full update, and archive of past updates, can be found on Mediawiki.org:
https://www.mediawiki.org/wiki/Discovery/Status_updates
--
Yours,
Chris Koerner
Community Liaison - Discovery
Wikimedia Foundation
Hi Community Metrics team,
This is your automatic monthly Phabricator statistics mail.
Accounts created in (2016-03): 307
Active users (any activity) in (2016-03): 923
Task authors in (2016-03): 501
Users who have closed tasks in (2016-03): 280
Projects which had at least one task moved from one column to another on
their workboard in (2016-03): 0
Tasks created in (2016-03): 2997
Tasks closed in (2016-03): 2543
Open and stalled tasks in total: 29603
Median age in days of open tasks by priority:
Unbreak now: 56
Needs Triage: 159
High: 258
Normal: 413
Low: 732
Lowest: 544
(How long tasks have been open, not how long they have had that priority)
TODO: Numbers which refer to closed tasks might not be correct, as
described in https://phabricator.wikimedia.org/T1003 .
Yours sincerely,
Fab Rick Aytor
(via community_metrics.sh on iridium at Fri Apr 29 19:45:44 UTC 2016)
Hi all,
I would like to introduce to the Wikimedia community WikiToLearn, a FOSS
project of which I am a participant and which is lately getting a lot of
contributions and momentum.
It is a KDE project sponsored (among the others) by Wikimedia Italy and
recently joined by institutions such as HEP Software Foundation (CERN,
Fermilab, Princeton...) or Universities such as University of Pisa and Milano-
Bicocca. These institutions are already populating the website with content.
We aim to provide a platform where learners and teachers can complete, refine
and re-assemble lecture notes in order to create free, collaborative and
accessible textbooks, tailored precisely to their needs.
Although the project is quite young (only a few months old), it is already
growing in allure at an unexpected rate. Thanks to this we are now counting on
nearly 40 developers, and growing (including content developers).
We are different from Wikipedia and other WMF projects in several ways, and in
a sense, complementary. Our focus is on creating complete textbooks (and not
encyclopedic articles), drawing from a professor’s or a student’s own notes,
either existing or that have to be written down.
We also have a strong focus on offline use: all the content of WikiToLearn
should be easily printable by any student for offline use and serious
studying.
Besides a good team for content development, we can count on a small but
motivated team of developers, and we would like to improve communication with
upstream (a.k.a. you ;-) ), because we found ourselves developing a few
features which could probably be made available to the general public, with
some generalization and polishing. ;-)
Is this a right place to start such a discussion?
We would like to help as much as we can, but we might need some mentoring in
how to best approach MediaWiki development, as many of us are relatively new
to OSS/Web development.
Bye,
-Riccardo
Due to popular demand I've put my Gerrit extension in the Chrome web
store. It makes a few subtle improvements to the Gerrit UI to make it
easier to navigate. Feel free to try it out and if it gets popular
I'll commit to getting these changes upstreamed to Gerrit ;-)
https://chrome.google.com/webstore/detail/gerrit-be-nice-to-me/oafiggfcmbke…
There seems to be extremely little documentation on Wikimedia's GitHub
project https://github.com/wikimedia ... I can only find
https://www.mediawiki.org/wiki/Gerrit/GitHub which mostly says we mirror a
bunch of stuff from gerrit. And I know we have continuous integration of
some kind set up for some projects, but it doesn't seem to be well
documented in a place I could find.
There are also some repos that are mirrors of gerrit, and other repos that
are primary repos, and it's a bit unclear what's what. More importantly,
when folks have repos that they've been running on GitHub already and want
to move into the wikimedia project (rather than switch to gerrit), what's
the procedure? I'm an admin/owner so I can manually import people's repos
but I'm not sure whether I'm supposed to... :)
We also have a lot of admins, which I wonder is necessary:
https://github.com/orgs/wikimedia/people?utf8=✓&query=role%3Aowner+
<https://github.com/orgs/wikimedia/people?utf8=%E2%9C%93&query=role%3Aowner+>
Do we do any security review / removal of old accounts, or have a procedure
for adding new admins?
-- brion
Below there is an excerpt from one of the organizers of Texas Linux Fest.
They are explicitly interested in Wikimedia participants / speakers. If you
have a proposal for a session, please consider submitting it. Also remember
that we have https://meta.wikimedia.org/wiki/Grants:TPS for sponsoring
travel costs in this type of situations. All the better if you are already
in North America. :)
---------- Forwarded message ----------
Nate Willis here; amongst my other project pastimes, I'm one of the
organizers
of Texas Linux Fest, which is the leading community Linux-and-FOSS
conference for Texas and the surrounding region.
Our event is July 8th and 9th this year, in downtown Austin, TX. We'd
really love it if folks from the WikiMedia project & surrounding community
can be
there—be they local or from out of town.
I especially wanted to draw your attention to our call for
participation. We're intent on attracting a wide variety of speakers
representing open source and free software, both users and developers,
from all corners. The details are here:
http://2016.texaslinuxfest.org/call-for-papers
and the deadline is approaching.
Please consider submitting a talk proposal yourself, and we would doubly
love it if
you could help us spread the word by sharing the CFP with others in the
community!
If you have any questions, or if you want to know more about Texas
Linux Fest this year or in general, please get in touch!
Thanks, from me and on behalf of the entire TXLF 2016 team,
Nate
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
