Hi,
The use of jargon, acronyms and other abbreviations throughout the
Wikimedia movement is a major source of communication issues, and
barriers to comprehension and involvement.
The recent thread on this list about "What is Product?" is an example
of this, as are initialisms that have long been known to be a barrier
for Wikipedia newcomers.
A way to bridge people and communities with different vocabularies is
to write and maintain a glossary that explains jargon in plain English
terms. We've been lacking a good and up-to-date glossary for Wikimedia
"stuff" (Foundation, chapter, movement, technology, etc.).
Therefore, I've started to clean up and expand the outdated Glossary
on meta, but it's a lot of work, and I don't have all the answers
myself either. I'll continue to work on it, but I'd love to get some
help on this and to make it a collaborative effort.
If you have a few minutes to spare, please consider helping your
(current and future) fellow Wikimedians by writing a few definitions
if there are terms that you can explain in plain English. Additions of
new terms are much welcome as well:
https://meta.wikimedia.org/wiki/Glossary
Some caveats:
* As part of my work, I'm mostly interested in a glossary from a
technical perspective, so the list currently has a technical bias. I'm
hoping that by sending this message to a wider audience, people from
the whole movement will contribute to the glossary and balance it out.
* Also, I've started to clean up the glossary, but it still contains
dated terms and definitions from a few years ago (like the FundCom),
so boldly edit/remove obsolete content.
Thank you,
--
Guillaume Paumier
Technical Communications Manager — Wikimedia Foundation
https://donate.wikimedia.org
Hello everyone,
This is one of my major updates regarding my GSoC project (named
ConventionExtension), which I have been working on for about three months
now. This project has come a long way and it has reached a point where a
lot about it can be shared with others. Since I don't post that often in
this list I would like to make this post a long one, and talk about the
status of my extension and where its headed in the coming weeks. Some of
the features which were part of my timeline for GSoC but were not completed
are put under the section "Things yet to be done" along with the other
features that I would be working on in the upcoming weeks.
*1. Completed Features*
*
*
1. Dashboard Page (more features are likely to be added depending upon the
feedback I gather from the people who have set up conferences on their wiki
in the past)
2. Author Registration Page
3. Conference Setup Page
4. Backend (DB) for storing the conference details
5. The basic architecture of the extension:
5.a) Model classes - encapsulating the basic objects required for this
extension
5.b) Api Module -- for interacting with ajax calls from the client
5.c) Util classes
5.d) Templates -- classes exending QuickTemplate class, providing a basic
layout for Dashboard and Author Register pages
5.e) UI classes - classes extending SpecialPage class (Dashboard,
AuthorRegister and ConferenceSetup pages)
5.f) JS + CSS resource modules
6. Parser tags, Magic Words (Variables) and a parser function
parser tags --> <conference>, <page>, <account>,
<registration>,<passport>,<author>,<submission>,<event>,<organizer> and
<location>
variables --> {{CONFERENCENAME}}, {{CONFERENCEVENUE}},
{{CONFERENCECITY}}, {{CONFERENCEPLACE}}, {{CONFERENCECOUNTRY}},
{{CONFERENCECAPACITY}}, {{CONFERENCEDESCRIPTION}}
parser function --> {{#cvext-page-link}}
7. Sidebar modification (added some new portals for the conference)
8. Schedule Template System - which automates the process of creating a
schedule for the conference, as new locations and events are added to the
system.
9. Content Pages - these are the default set of pages that are created for
the conference by the extension (Note : these are just like any other wiki
pages whose content can be modified using the wiki interface)
*2. Things yet to be done !*
*
*
1. *DB rollback implementation in most of my model classes
2. *Account Setup Page (for registration of users)
3. *Modification of User pages for displaying content related to the
conference
3. Organizer management module (most part of it is already implemented in
the basic architecture, just some additions needed regarding the
permissions and rights for this group)
4. Payment Gateway
5. Support for languages other than English
6. Some more parser functions and variables which would help in editing the
content pages of the conference
* - These features were not completed during the GSoC period.
I really enjoyed my experience of working with such a vibrant community
over this summer, especially thankful to all the people who helped me out
in the IRC channel may it be regarding the setting up of labs, or helping
me out with the localisation issues, or even suggesting me come up with a
better feature than what I had already implemented. Other community fellows
who reviewed my big chunks of code, many issues which I very easily missed
were pointed out with a proper explanation of what needs to be done, have
helped me a great deal in improving it. And finally I would like to thank
Sumana and Greg for managing this program so well, and my mentor Jure
Kajzer for his unmatched support and guidance throughout the summer.
Some important links:
Proposal Page -
http://www.mediawiki.org/wiki/User:Chughakshay16/GSOCProposal(2012)
Gerrit changesets -
https://gerrit.wikimedia.org/r/#/q/ConventionExtension,n,z
Extension Page - http://www.mediawiki.org/wiki/Extension:ConventionExtension
Suggestions are always welcome !
--
Thanks,
Akshay Chugh
skype- chughakshay16
irc - chughakshay16(#mediawiki)
[[User:Chughakshay16]] on mediawiki.org
fyi
-------- Original Message --------
Subject: [Engineering] Report from Gerrit User Summit + Hackathon
Date: Mon, 19 Nov 2012 11:55:00 -0500
From: Chad Horohoe <chorohoe(a)wikimedia.org>
To: Development and Operations engineers (WMF only)
<engineering(a)lists.wikimedia.org>
Hi all,
Last week, I attended the Fall Gerrit Hackathon and User Summit.
All in all, it was a productive week, and I'd like to share some of
the highlights with you all:
- I fixed the "inherit external groups" issue that was introduced in
2.5 (and remains broken in master). It's pending review, but the
solution was agreed upon by myself and the other affected
parties[0].
- I re-skinned Gerrit similar to our light white/grey theme. This
means the default will no longer be puke green/yellow[1].
- I fixed GWT to no longer obfuscate CSS classes, so any
customizations we make will remain stable between releases and builds[2].
- Lots of aspects of the JSON-RPC API were turned to the new
public RESTful API, making the API in master much more
feature-complete.
- Dashboards can now be defined in refs/meta/config on a per-
project basis (and can be saved). They are all linked from the
project info pages.
-Topics can be edited from the UI[3] after committing (but before
merging, for cleanup), and the same is in progress for branches
and commit messages.
- Also in progress: carrying over approvals on trivial (whitespace-
only) rebases. Making it possible to exclude unchanged (other than
whitespace) files on a diff, easier for verifying rebases.
- Discussion began on: supporting README.md files for projects
that have them, how to properly "request" new projects and
branches (no code, but a very good outline[4]).
Gerrit now has a mascot: Diffy the Kung-Fu Review Cuckoo[5].
A very very cool presentation was given on some improvements
that were done to JGit (making their way into upstream currently).
If you like Git internals stuff, this is for you[6].
There's way too many nice things going on since 2.5 was cut, so
when we get the LDAP issue fixed I'll be deploying stable-2.6 +
our LDAP fix (so we're skipping 2.5). Hoping this can happen in
the next 2-3 weeks at the latest.
-Chad
[0] https://gerrit-review.googlesource.com/#/c/39140/
[1] https://gerrit-review.googlesource.com/#/c/39376/
[2] https://gerrit-review.googlesource.com/#/c/39251/
[3]
https://gerrit-review.googlesource.com/#/q/status:merged+project:gerrit+bra…
[4] https://code.google.com/p/gerrit/issues/detail?id=1433#c5
[5] https://code.google.com/p/gerrit/
[6]
https://docs.google.com/presentation/d/1t2qzSO4z5MbrN21Cz4RrLWz9IZ5ylJNwQas…
Welcome Juliusz, very excited to have you on board :D
On Tue, Nov 20, 2012 at 8:37 AM, Steph Thommen <sthommen(a)wikimedia.org>wrote:
> Many congratulations and welcome Julius!
>
>
> On 20 November 2012 05:20, Sumana Harihareswara <sumanah(a)wikimedia.org>wrote:
>
>> On 11/19/2012 04:59 PM, Tomasz Finc wrote:
>> > I am pleased to announce that Juliusz Gonera joins WMF this week as a
>> > Software Developer (Mobile team) today.
>> >
>> > Juliusz has worked at the University of Virginia, developing software
>> > for a laboratory that studies the macromolecular structure of
>> > proteins. Before that he created a system for sending bulk SMS
>> > messages for a Polish company. Juliusz is a proponent of open source
>> > and agile methodologies and apart from a few projects of his own [1]
>> > he contributes to open source software he uses. He has just moved to
>> > San Francisco and earlier lived in Virginia, Spain and Poland.
>> >
>> > The team would like to welcome him and wish him success.
>> >
>> > [1] - https://github.com/jgonera
>> >
>> > --tomasz
>>
>> Congrats and welcome, Juliusz. We are strange but friendly folk and we
>> hope you enjoy becoming part of our community. :-)
>>
>> --
>> Sumana Harihareswara
>> Engineering Community Manager
>> Wikimedia Foundation
>>
>> _______________________________________________
>> Wmfall mailing list
>> Wmfall(a)lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wmfall
>>
>
>
>
> --
> Steph Thommen
> Recruitment Manager
> Wikimedia Foundation
>
>
>
> _______________________________________________
> Wmfall mailing list
> Wmfall(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wmfall
>
>
--
Arthur Richards
Software Engineer, Mobile
[[User:Awjrichards]]
IRC: awjr
+1-415-839-6885 x6687
Hi,
In the Bangalore DevCamp I spoke a bit with Brion about a way to
measure various ways of editing MediaWiki pages. The original idea was
to measure how much the mobile editing, when it becomes widely
available, is actually used. A simplistic solution would be add a
boolean "rev_mobile" field to the revision table, but this can apply
to a lot of other things, for example:
* Visual Editor vs. the current wiki-syntax editor
* A usual browser vs. AutoWikiBrowser vs. direct API calls
* bots vs. non-bots
* for file uploads, Special:Upload vs. Special:UploadWizard
Things get even more complicated, because several such flags may apply
at once: for example, I can imagine a human editor using a mobile
editing interface with a bot flag, because he makes a lot of tiny
edits and the community doesn't want them to appear in RecentChanges.
And of course, there may be privacy and performance implications, too.
Nevertheless, some kind of metrics of the various contributions
channels would be useful. Any more ideas?
--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
“We're living in pieces,
I want to live in peace.” – T. Moore
A few weeks ago I upgraded a single SSL termination server to Ubuntu
Precise. I let it run for a while to ensure we wouldn't see memory leaks
and to give time for people to report errors. No issues were reported and
resource consumption was good, so today I upgraded all other nodes. This
upgrade eliminates our vulnerability to the CRIME attack and also allows us
to use HTTP 1.1 to the backends from nginx. Testing for HTTP 1.1 will
follow soonish.
If you notice any new HTTPS oddities, let me know.
- Ryan
Thanks a lot for the support! I will go through the page suggested! :)
On Tue, Nov 20, 2012 at 4:00 AM, <wikitech-l-request(a)lists.wikimedia.org>wrote:
> Send Wikitech-l mailing list submissions to
> wikitech-l(a)lists.wikimedia.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> or, via email, send a message with subject or body 'help' to
> wikitech-l-request(a)lists.wikimedia.org
>
> You can reach the person managing the list at
> wikitech-l-owner(a)lists.wikimedia.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Wikitech-l digest..."
>
>
> Today's Topics:
>
> 1. A Newbie! (Hasini Abeywickrama)
> 2. Re: A Newbie! (Amir E. Aharoni)
> 3. Re: MW 1.20 backwards compatibility in extensions (Krinkle)
> 4. Re: Please take this survey about new contributors (bawolff)
> 5. Re: Research on newcomer experience - do we want to take
> part? (Diederik van Liere)
> 6. Re: Please take this survey about new contributors (Quim Gil)
> 7. Welcome Juliusz Gonera as Software Developer to the Mobile
> Team! (Tomasz Finc)
> 8. Re: Wikimedia URL shortener (Mono)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 20 Nov 2012 00:43:26 +0530
> From: Hasini Abeywickrama <hvabey(a)gmail.com>
> To: Wikitech-l(a)lists.wikimedia.org
> Subject: [Wikitech-l] A Newbie!
> Message-ID:
> <
> CANYxRU8_-VAJ9A4wz5OfBnNdnQG7zEuT_66upkCaLqV6+QsXiw(a)mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi all!
>
> I am a new member to this mailing group & I am interested in taking part in
> the Outreach Programme for Women!
>
> I would like to make my contribution to Wikimedia. I read through the
> webpage but I have no clear idea on where do download the code & source
> files etc.
>
> Can someone out there please help?
>
> Thanks a lot in advance! :)
>
> Hasi
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 19 Nov 2012 22:09:19 +0200
> From: "Amir E. Aharoni" <amir.aharoni(a)mail.huji.ac.il>
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
> Subject: Re: [Wikitech-l] A Newbie!
> Message-ID:
> <
> CACtNa8skujbDZQFCATwW9ou1+HUaifOFfYup0NnM2E4CK7waQg(a)mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> 2012/11/19 Hasini Abeywickrama <hvabey(a)gmail.com>:
> > Hi all!
> >
> > I am a new member to this mailing group & I am interested in taking part
> in
> > the Outreach Programme for Women!
> >
> > I would like to make my contribution to Wikimedia. I read through the
> > webpage but I have no clear idea on where do download the code & source
> > files etc.
> >
> > Can someone out there please help?
>
> Hello, and welcome!
>
> Take a look at the following page:
> https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker
>
> --
> Amir Elisha Aharoni ? ?????? ????????? ??????????
> http://aharoni.wordpress.com
> ??We're living in pieces,
> I want to live in peace.? ? T. Moore?
>
>
>
> ------------------------------
>
> Message: 3
> Date: Mon, 19 Nov 2012 21:15:27 +0100
> From: Krinkle <krinklemail(a)gmail.com>
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
> Subject: Re: [Wikitech-l] MW 1.20 backwards compatibility in
> extensions
> Message-ID: <AEE2F6EF-6A69-4BBF-848C-DEAA31E665D6(a)gmail.com>
> Content-Type: text/plain; charset=us-ascii
>
> On Nov 19, 2012, at 5:12 PM, Daniel Kinzler <daniel(a)brightbyte.de> wrote:
>
> > On 19.11.2012 17:08, Jeroen De Dauw wrote:
> >> +1. Having a script run that makes pretty arbitrary tags in between
> actual
> >> releases for extensions that have real releases and associated
> >> tags/branches does not seem helpful at all to me.
> >
> > It is, however, extremely helpful for those extensions that don't have
> their own
> > release system.
> >
> > Maybe the script can just skip any extension that has a VERSION or
> RELEASE-NOTES
> > file.
>
>
> Or we don't run it and just create REL branches when we have to and so
> will others.
>
> Extensions that aren't maintained, aren't maintained.
>
> As a start, I created a REL1_20 branch for extensions that were bundled
> with 1.20.0.
>
> -- Krinkle
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Mon, 19 Nov 2012 16:52:20 -0400
> From: bawolff <bawolff+wn(a)gmail.com>
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
> Subject: Re: [Wikitech-l] Please take this survey about new
> contributors
> Message-ID:
> <CA+oo+DUEdk-05yerGUW4T2KAs0fruGC2bFwc6KF4=
> TO-W3MN5g(a)mail.gmail.com>
> Content-Type: text/plain; charset=windows-1252
>
> On Mon, Nov 19, 2012 at 1:40 PM, Quim Gil <qgil(a)wikimedia.org> wrote:
> > Hi, if you joined the MediaWiki / Wikimedia tech community in 2010 or
> > later please consider taking this survey:
> >
> > Newcomer experience and contributor behavior in FOSS communities
> > https://limesurvey.sim.vuw.ac.nz/index.php?sid=65151&lang=en
> >
> > The survey is open for sporadic contributors or full time Wikimedia
> > employees, developers or any other profile. Anybody is welcome to
> > leave their feedback as long as you have started contributing to this
> > community in the past 3 years.
> >
> > 11 mature and well established open source projects are taking part in
> > this survey: Debian, FreeBSD, GNOME, Gentoo, KDE, Mozilla, NetBSD,
> > OpenSUSE, Python, Ubuntu and Wikimedia. Some of them started some days
> > ago and have more than hundred responses by now. The data of this
> > survey is anonymous and will be released under a ?share-alike? Open
> > Data Commons Open Database License (ODbL).
> >
> > Some background:
> >
> > From Kevin Carillo, the researcher:
> > http://kevincarillo.org/survey-invitation/
> >
> > From OpenHatch, a non-profit working on the bridge between free
> > software projects and new contributors:
> >
> https://openhatch.org/blog/2012/a-research-project-to-understand-what-does-…
> >
> >
> > PLEA
> > If you, like me, became a bit tired of survey requests like this
> > please consider filling this one anyway. It focuses in a specific area
> > where we don't have much data. As fresh technical contributor
> > coordinator at the WMF I'm looking forward to the results of this
> > research and the lessons it will bring.
> >
> > Thank you. :)
> >
> > --
> > Quim Gil
> > Technical Contributor Coordinator
> > Wikimedia Foundation
> >
> > _______________________________________________
> > Wikitech-l mailing list
> > Wikitech-l(a)lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
> Hmm, some of the questions were a little unclear - talking about the
> Wikimedia community, but Wikimedia (as a whole) is not a FOSS project.
> I became a developer roughly 3 years ago. I've been a member of
> Wikimedia land since roughly 2005. Similarly, does being a gsoc
> participant count as being paid to work on MediaWiki - after all gsoc
> students do get money for doing MediaWiki things, etc.
>
> -bawolff
>
>
>
> ------------------------------
>
> Message: 5
> Date: Mon, 19 Nov 2012 16:01:08 -0500
> From: Diederik van Liere <dvanliere(a)wikimedia.org>
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
> Subject: Re: [Wikitech-l] Research on newcomer experience - do we want
> to take part?
> Message-ID:
> <
> CAFZ+_qmRaFSNJDQkNtZF7NhpmdV-aHPTN_CO3dhDDezBd7WJzw(a)mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hey Quim
>
> I also sent you this survey a week ago with the question whether we should
> participate :)
> D
>
>
> On Fri, Nov 16, 2012 at 5:13 PM, Quim Gil <qgil(a)wikimedia.org> wrote:
>
> > Hi, sorry for cross-replying.
> >
> > On Wed, Nov 14, 2012 at 3:11 PM, Lydia Pintscher
> > <lydia.pintscher(a)wikimedia.de> wrote:
> > > On Wed, Nov 14, 2012 at 11:00 PM, Marcin Cieslak <saper(a)saper.info>
> > wrote:
> > >> Hello,
> > >>
> > >> Kevin Carillo[1] from University of Wellington is going to research
> > >> "Newcomer experience and contributor behavior in FOSS communities[2]
> > >> So far Debian, GNOME, Gentoo, KDE, Mozilla, Ubuntu, NetBSD, OpenSUSE
> > >> will be taken into account, and FreeBSD recently joined[3] and
> > >> there is still some possibility for other large FOSS projects to join.
> > >>
> > >> I think it could fit nicely into our recent efforts directed
> > >> at newcomer experience after Git migration. And MediaWiki is
> > >> a bit different than above projects.
> > >>
> > >> Are we interested
> > >> to include MediaWiki in that research?
> > >>
> > >> As Kevin explains in his post he tried to avoid spamming mailing
> > >> lists to look for project interested, so I am doing this for him :-)
> > >>
> > >> //Saper
> > >
> > > I've worked with Kevin in preparation for his survey and later
> > > promotion from the KDE-side quite a bit. This is not the kind of
> > > research project that is of no value to the project taking part. I
> > > expect the results to be very useful for KDE (and likely also the
> > > other projects taking part).
> >
> > It turns out that Sumana and me have been in touch with Kevin in the
> > past days after Asheesh Laroia proposed directly to include Wikimedia
> > in this research.
> >
> > Said and done, Wikimedia is also included in the survey and you are
> > encouraged to invest some minutes in it:
> >
> > https://limesurvey.sim.vuw.ac.nz/index.php?sid=65151
> >
> > I will send a proper announcement next Monday, but in the meantime
> > here is an illustrative link of links:
> >
> > http://kevincarillo.org/2012/11/15/survey-update-after-1-week/
> >
> > --
> > Quim
> >
> > _______________________________________________
> > Wikitech-l mailing list
> > Wikitech-l(a)lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> >
>
>
> ------------------------------
>
> Message: 6
> Date: Mon, 19 Nov 2012 13:05:17 -0800
> From: Quim Gil <qgil(a)wikimedia.org>
> To: bawolff+wn(a)gmail.com, Wikimedia developers
> <wikitech-l(a)lists.wikimedia.org>
> Subject: Re: [Wikitech-l] Please take this survey about new
> contributors
> Message-ID:
> <CACxLwR=g3-TMBmqRVF4nYE=+_TaF+oie-vw13qtpe=
> 2-VvGMqw(a)mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi,
>
> On Mon, Nov 19, 2012 at 12:52 PM, bawolff <bawolff+wn(a)gmail.com> wrote:
> > Hmm, some of the questions were a little unclear - talking about the
> > Wikimedia community, but Wikimedia (as a whole) is not a FOSS project.
>
> Well, yes. We could say that Wikimedia is _also_ a FOSS project,
> handling 5,4M lines of code as we speak.
>
> > I became a developer roughly 3 years ago. I've been a member of
> > Wikimedia land since roughly 2005.
>
> The you are fine since the survey is about the Wikimedia technical
> community.
>
> > Similarly, does being a gsoc
> > participant count as being paid to work on MediaWiki - after all gsoc
> > students do get money for doing MediaWiki things, etc.
>
> I wouldn't count a one-off, modest paid contribution like GSoC.
>
>
>
> ------------------------------
>
> Message: 7
> Date: Mon, 19 Nov 2012 13:59:54 -0800
> From: Tomasz Finc <tfinc(a)wikimedia.org>
> To: "Staff (All)" <wmfall(a)lists.wikimedia.org>, Wikimedia
> developers
> <wikitech-l(a)lists.wikimedia.org>
> Subject: [Wikitech-l] Welcome Juliusz Gonera as Software Developer to
> the Mobile Team!
> Message-ID:
> <CAMxhqbeAcnpC16Wz+QzpJsB2D=
> L2b8BneadOSjJuuTZcCf8VWQ(a)mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> I am pleased to announce that Juliusz Gonera joins WMF this week as a
> Software Developer (Mobile team) today.
>
> Juliusz has worked at the University of Virginia, developing software
> for a laboratory that studies the macromolecular structure of
> proteins. Before that he created a system for sending bulk SMS
> messages for a Polish company. Juliusz is a proponent of open source
> and agile methodologies and apart from a few projects of his own [1]
> he contributes to open source software he uses. He has just moved to
> San Francisco and earlier lived in Virginia, Spain and Poland.
>
> The team would like to welcome him and wish him success.
>
> [1] - https://github.com/jgonera
>
> --tomasz
>
>
>
> ------------------------------
>
> Message: 8
> Date: Mon, 19 Nov 2012 15:29:58 -0700
> From: Mono <monomium(a)gmail.com>
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
> Subject: Re: [Wikitech-l] Wikimedia URL shortener
> Message-ID:
> <
> CAD6tHrUqLQk5uN+UHu52fJStfjSUsy6TG6vEi3Dny7fLGqfnyg(a)mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> I think the wmf.co and related URLs are our best bet.
>
>
> On Mon, Nov 19, 2012 at 11:40 AM, Luke Welling <lwelling(a)wikimedia.org
> >wrote:
>
> > There are some practical reasons for providing site specific domain
> > shortening beyond owning a cool domain hack.
> >
> > Discouraging the use of third party shorteners has real value. The
> > web getting littered with urls that camouflage their destination, are
> > tied to loss making commercial entities of unpredictable lifetime (eg
> > tr.im), or tied to very well funded commercial entities that choose a
> > ccTLD of unpredictable stability (eg bit.ly) is a bad thing.
> > Providing the option of a short url that achieves whatever benefit was
> > sought without breaking the way the web is supposed to work is a good
> > thing.
> >
> > Email used to be problematic for url sharing, as line breaks inserted
> > at 70 characters would mean the recipient needed to notice that some
> > urls had been chopped and reassemble them. This is probably only
> > true for mailing lists now, as people who deliberately use a plain
> > text only email client in 2012 will experience obtrusive side effects
> > from senders only providing an HTML MIME part regularly. URL chopping
> > will not be their major annoyance. Mailing lists still routinely
> > strip attachments and encodings from mail that they propagate.
> >
> > Mobile generally and twitter specifically are the most often cited
> > justifications now. Aside from the obvious message length limits,
> > cutting and pasting long strings can be hard on a small screen so
> > people are in the short url habit.
> >
> > Twitter is an annoying use case, as even if presented with a short url
> > it currently replaces it with a potentially longer t.co url.
> >
> > If all the project does is reduces the use of third party services
> > that can permanently or transiently fail, can hide links to malware,
> > break search engine rankings and search behaviour, and provide others
> > with analytic insight into potentially sensitive user click throughs
> > it is a good thing.
> >
> > Luke Welling
> >
> > PS my unobtainable cool domain hack of choice would be en.cy (but
> > Cyprus don't do top level subdomains and require local presence)
> >
> >
> > On Mon, Nov 19, 2012 at 5:49 AM, Neil Harris <neil(a)tonal.clara.co.uk>
> > wrote:
> > > On 19/11/12 02:09, MZMcBride wrote:
> > >>
> > >> Tim Starling wrote:
> > >>>
> > >>> Providing a traditional URL shortener with traditional features would
> > >>> be useful, at least for some people, and would eliminate the need to
> > >>> use third-party URL shorteners internally, which have a commercial
> > >>> focus and unknown lifetime. If there was no integration with MW
> > >>> required, it would only take a couple of hours to set up.
> > >>
> > >> Who's using third-party URL shorteners internally? A lot of services
> > would
> > >> be useful to at least some people (Wikimedians), but the cost of
> setting
> > >> up
> > >> _and maintaining_ such a service can't be overlooked, in my opinion.
> > Yes,
> > >> it
> > >> would take a few hours to set up a URL shortening service (if that),
> but
> > >> who's going to be responsible for fixing bugs in it, adding features,
> > and
> > >> doing general maintenance to the service for the indefinite future?
> > There
> > >> are already a number of Wikimedia services that struggle for limited
> > >> resources. Before we add another, we must answer the maintenance
> > question.
> > >>
> > >> MZMcBride
> > >>
> > >>
> > >
> > > If a Wikimedia URL shortening service was to be created, it would make
> > sense
> > > to, at the very least, (a) make the shortened link to real link
> mappings
> > > part of the standard Mediwiki XML dumps, so that they can be preserved
> > > alongside the content to which they refer, for access by future
> > archivists,
> > > and (b) participate in initiatives such as the Internet Archive's
> > > 301works.org to preserve these links entirely outside the Wikimedia
> > > universe.
> > >
> > > Also, on a separate but related note, has anyone considered creating
> DOIs
> > > for individual wiki page revisions?
> > >
> > > -- Neil
> > >
> > >
> > >
> > > _______________________________________________
> > > Wikitech-l mailing list
> > > Wikitech-l(a)lists.wikimedia.org
> > > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> >
> > _______________________________________________
> > Wikitech-l mailing list
> > Wikitech-l(a)lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> >
>
>
> ------------------------------
>
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
> End of Wikitech-l Digest, Vol 112, Issue 50
> *******************************************
>
On Mon, Oct 15, 2012 at 1:44 AM, S Page <spage(a)wikimedia.org> wrote:
> In the promised land, developers use vagrant to run local VM instances on
> laptops that puppet configures to run a production-ish MediaWiki. At Etsy
> and Facebook, the day a developer walks in she can make changes in her
> personal VM and push them to production (or so they claim in blog posts and
> meetups ;-) ).
The new Mozilla Kuma project is a good example for this as well, and
unlike the aforementioned ones, you can download the VM yourself. See:
https://github.com/mozilla/kuma/https://github.com/mozilla/kuma/blob/master/docs/installation-vagrant.rst
Relevant blog post about their Vagrant setup:
http://decafbad.com/blog/2011/10/02/putting-clouds-in-boxes
Some design notes:
https://wiki.mozilla.org/Webdev:DevBoxVMImages
We have an awesome and unique infrastructure with Labs for testing and
staging, but for local development, having a pre-packaged dev
environment (probably slightly less ambitious than beta.wmflabs) would
indeed seem very useful. How feasible/useful would it be to build on
the existing work, e.g. Andrew Bogott's MediaWiki class, to provide a
first iteration of such an environment? [1]
Erik
[1] https://gerrit.wikimedia.org/r/gitweb?p=operations/puppet.git;a=blob_plain;…
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate