Hi all,
I recently saw this
announcement<http://www.gossamer-threads.com/lists/wiki/wikitech/332112>on
wikitech-l aboutUser:Krenair<https://www.mediawiki.org/wiki/Mentorship_programs/LevelUp>getting
+2 status on MW core and extensions and I wanted to send out some
more information on what +2 is and the process of becoming a core
maintainer. I think it might be useful for some of you to consider working
towards +2. Here <http://www.mediawiki.org/wiki/%2B2> is some more info on
what +2 status is. To be granted +2 status you need to post a request
here<http://www.mediawiki.org/wiki/Git/Gerrit_project_ownership> and
be approved.
Quoting from http://www.mediawiki.org/wiki/%2B2 :
*So, you got +2 rights to MediaWiki core or a WMF-deployed extension.*
*That means you can merge changes to the software that's running on
Wikimedia Foundation sites. Your change will be automatically deployed to
the beta cluster <http://www.mediawiki.org/wiki/Beta_cluster>, a
virtualized staging environment, as soon as it's been merged in
Gerrit<http://www.mediawiki.org/wiki/Gerrit>.
It will also be automatically picked up in the next MediaWiki core
deployment window (see
wikitech:Deployments<http://wikitech.wikimedia.org/view/Deployments>)
unless it is reverted before the release branch is cut.*
You can get +2 on specific extensions as well if you wish, which will let
you maintain those only. This is usually much easier, especially if its a
poorly maintained extensions, than getting +2 access to core, so it might
be a good starting point.
I heard from a few of you that the third-party community is lacking code
review support, which prevents some from merging their code with MW. There
is a misconception that all or almost all +2 users are employees of WMF. In
fact there are now( with Krenair) 9 non-WMF developers with +2 status on
core and WMF is looking to expand the +2 group to minimize code review
delays. It took Krenair 1 year of MW development to get to +2 so the
process is not overwhelmingly long.
If you are interested to become a core maintainer or get ownership on some
extension, please consider joining the LevelUp mentorship
program<https://www.mediawiki.org/wiki/Mentorship_programs/LevelUp>,
where you will be matched with a mentor to guide you in the process.
Let me know if you have any questions.
Mariya
Hi everyone,
Here are some tools you might find useful for access control and embedded
content(including social media).
Also, is anyone interested in assisting Clement and Seizam with
refractoring/testing the code to go on git?
Mariya
---------- Forwarded message ----------
From: Clément Dietschy <clement(a)seizam.com>
Date: Mon, Jan 28, 2013 at 10:13 PM
Subject: Re: [MediaWiki-l] Third-Party Users Wish List - Does Anyone Know
of Existing/Experimental Solutions?
To: mediawiki-l(a)lists.wikimedia.org
> 2. Integrated access control
We've developed a rather reliable way for artists to control
read/edit/upload rights on their own page/files. Although the code is
not ready for forking, I haven't seen such advanced feature for MW yet
and it's at least a proof of concept. Note that only the page content
and the files are safely protected, logs (recent changes, histories,
search, edit summaries...) cannot be trusted yet.
Resources:
* Demonstration on Vimeo
https://vimeo.com/57671929
* Extension:ProtectOwn (brings "read right", and "owner" access
control. /!\ ugly, should be broken down)
https://github.com/Seizam/seizamcore/tree/master/WikiZam/extensions/Protect…
* Note: Extension:ProtectOwn comes from Extension:AuthorProtect
http://www.mediawiki.org/w/Extension:AuthorProtect
* Extension:WikiPlace (our concept of private space, could be broken down)
https://github.com/Seizam/seizamcore/tree/master/WikiZam/extensions/Wikipla…
* What is a WikiPlace?
http://www.seizam.com/Help:Wikiplace
The reason why there is no page on MW.org and the code is not on WM's
git is because we don't have the resources to refactor and clean it
(as it should be done to avoid thousands of headaches). Sorry about
that, but it is GPL3 and we're eager to help whoever wants to test it,
use it and/or bring it forward.
> 6. An easy way to share wiki content on social media services.
Our Extension:WidgetsFramework allows easy embedding of external
content in the wiki, including social features. Already available
widgets are AddThis, Google+, Facebook, twitter...
Resources:
Demonstration on Vimeo: https://vimeo.com/57689952MW.org: http://www.mediawiki.org/wiki/Extension:WidgetsFramework
Code on Github:
https://github.com/Seizam/seizamcore/tree/master/WikiZam/extensions/Widgets…
Again, code is not on MW's git because of lacking resources. Again, sorry.
Hope all this can be helpful.
--
Clément Dietschy
75020 Paris
tél. +33 6 87 75 99 27
--
Seizam Sàrl.
24, rue de Bâle
68300 Saint-Louis (France)
tél. +33 970 448 200
http://www.seizam.com
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Hi,
I am an intern working on reaching out to third-party MediaWiki users. I
was pointed to this link with notes on discussion at NOLA Hackaton 2011. I
was wondering if these issues/ideas are still valid and if there was any
follow up on them?
http://www.mediawiki.org/wiki/NOLA_Hackathon/Saturday#Third-party_committer…
Thank you.
Mariya
Hi,
I am forwarding an email from the wikitech-l mailing list, which might be
interesting for people on this list.
If anyone else is maintaining or knows of a bundle that might be reused,
please share it here as well.
Thank you.
Mariya
---------- Forwarded message ----------
From: <vitalif(a)yourcmc.ru>
Date: Mon, Jan 14, 2013 at 6:56 PM
Subject: Re: [Wikitech-l] MediaWiki Extension Bundles and Template Bundles
To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
On 01/14/2013 10:20 AM, Yuvi Panda wrote:
>
>> Is there a sort of 'Extension Bundle' that gets you baseline stuff that
>> people who are used to wikipedia 'expect'? ParserFunctions and Cite come
>> to
>> mind, but I'm sure there are plenty others.
>>
>
I don't know if this would be relevant to your question, but I have to say
that in our company we maintain and use our own MediaWiki distribution
"Mediawiki4Intranet"
(http://github.com/**mediawiki4intranet<http://github.com/mediawiki4intranet>,
http://wiki.4intra.net/) for all MW installations. It includes ~75
extensions, the set is not totally similar to WMF one, but we think it's
good for corporate (intranet) usage. You can try it out if you want, yet
some extensions are documented only in russian :-)
______________________________**_________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/**mailman/listinfo/wikitech-l<https://lists.wikimedia.org/mailman/listinfo/wikitech-l>
(CC'd mediawiki-enterprise since it is relevant.)
On Mon 14 Jan 2013 11:56:50 AM EST, Dmitriy Sintsov wrote:
>> This does point to another possible way to backport the changes -- some
>> sort of compatibility extension. That allows the core to remain stable,
>> but allows people to use some newer extensions if they need the
>> features.
>>
> I am not sure Wikimedia would like to put their efforts on this.
Agreed. I didn't say they should.
The WMF is focused on its vision (which doesn't include supporting
non-WMF users of MW). In the mean time, they've made this software
available for the world to use.
> My own experience shows that most of site owners are quite greedy
> people. Maybe I am bad at business though.
People are people.
We're slipping off topic here, but in as far as this relates to users of
MediaWiki, I'll continue.
First, I should say that I've worked closely with people across the
spectrum of business. I've worked with, and count as friends, several
small business owners who run on-line sites as their core business.
On the other "side", I have friends who work at or run non-profits or
charities including some at the WMF.
My friends who are site owners are, on the whole, no more
self-interested than any of my other friends. They are focused on
maintaining the business just as my friends at the WMF is focused on
keeping Wikipedia and its sister sites running.
If we want something more from MediaWiki, we can ask the WMF for it,
but, since we have the GPL license on the software, we are also
empowered to do it ourselves if the WMF is not interested in helping.
Semantic MediaWiki is a great example of this happening and many non-WMF
users of MediaWiki use SMW.
I think MediaWiki core alone can (and does!) benefit many people outside
the Foundation in just the same way that SMW does. We have the power to
make it more suitable for our own non-WMF uses.
--
http://hexmode.com/
Language will always shift from day to day. It is the wind blowing
through our mouths. -- http://hexm.de/np
Hi,
I run the wiki service on my site and at the moment it is in need of a bit of an overhaul.
I'm hoping to run all of the wiki's under one central service a.k.a. a wiki-farm, and I'd prefer to mirror the quality of service that Wikia offer.
I've already taken a look through the documentation and extensions on the MediaWiki site: https://www.mediawiki.org/wiki/Manual:Wiki_family and I've read through the Wikia staff blogs and got in contact with their Community Support team to try and get a handle on how they manage their service, and they pointed me at their source-code repository: http://trac.wikia-code.com/browser/wikia/trunk.
I was hoping to get some feedback from the wider community on your take on running a multiple wiki service, keeping systems up-to-date, running one central code base all within an enterprise and if anybody is running on Wikia's methodology or similar?
Many Thanks,
Adam Carr
I've just updated https://www.mediawiki.org/wiki/Mailing_lists and
https://meta.wikimedia.org/wiki/Mailing_lists/Overview#Mediawiki_and_techni…
. Sorry for the spam, but you really should take a moment to skim and
see whether there are lists there you should join. I especially want to
single out:
design
mediawiki-api-announce
mediawiki-i18n -- localisation and internationalisation
labs-l -- for when you have a question or request re Wikimedia Labs
analytics
wikitext-l -- the new Visual Editor & parser
--
Sumana Harihareswara
Engineering Community Manager
Wikimedia Foundation