Google Code-in (GCI) has been running for only one week and students have already resolved 35 Wikimedia tasks!
Some of the achievements: * Citoid offers export in BibTeX format (and more contributions) * Analytics' Dashiki has a mobile-friendlier view * Echo's badge label text has better readability; Echo uses the standard gear icon for preferences * Wikidata's Wikibase API modules use i18n for help/docs * Two MW extensions got patches to not use deprecated i18n functions * MW displays an error when trying to create a self-redirect * The sidebar group separator in MW's Installer looks like in Vector * Our Phabricator docs have video screencasts and an updated "Bug report life cycle" diagram * Huggle's on-wiki docs were updated; exceptions received cleanup * Pywikibot's replicate_wiki supports global args; optparse was replaced by argparse * Reasons for MW sites listed as defunct on WikiApiary were researched * We got logo proposals for the European Wikimedia Hackathon 2015 * ...and many more.
Sounds good? Then please spend 5 minutes to go through your tasks and identify simple tasks to allow more young people contribute!
Got an idea for a task? Become a mentor for that task! And spread the word to other community members who might be good mentors! Read https://www.mediawiki.org/wiki/Google_Code-in_2014#Mentors.27_corner and please contact me if you need help.
Thank you! andre
Hey guys reading through some of these tasks, I am wondering has the wiki media foundation taken into account mobile devices and started taking media wiki down a mobile friendly path through using bootstrap etc?
On Tue, Dec 9, 2014 at 6:00 PM, Andre Klapper aklapper@wikimedia.org wrote:
Google Code-in (GCI) has been running for only one week and students have already resolved 35 Wikimedia tasks!
Some of the achievements: * Citoid offers export in BibTeX format (and more contributions) * Analytics' Dashiki has a mobile-friendlier view * Echo's badge label text has better readability; Echo uses the standard gear icon for preferences * Wikidata's Wikibase API modules use i18n for help/docs * Two MW extensions got patches to not use deprecated i18n functions * MW displays an error when trying to create a self-redirect * The sidebar group separator in MW's Installer looks like in Vector * Our Phabricator docs have video screencasts and an updated "Bug report life cycle" diagram * Huggle's on-wiki docs were updated; exceptions received cleanup * Pywikibot's replicate_wiki supports global args; optparse was replaced by argparse * Reasons for MW sites listed as defunct on WikiApiary were researched * We got logo proposals for the European Wikimedia Hackathon 2015 * ...and many more.
Sounds good? Then please spend 5 minutes to go through your tasks and identify simple tasks to allow more young people contribute!
Got an idea for a task? Become a mentor for that task! And spread the word to other community members who might be good mentors! Read https://www.mediawiki.org/wiki/Google_Code-in_2014#Mentors.27_corner and please contact me if you need help.
Thank you! andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/
MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Jonathan Aquilina eagles051387@gmail.com writes:
Hey guys reading through some of these tasks, I am wondering has the wiki media foundation taken into account mobile devices and started taking media wiki down a mobile friendly path through using bootstrap etc?
There is the MobileFrontend (https://www.mediawiki.org/wiki/Extension:MobileFrontend) and Wikipedia Zero (https://en.wikipedia.org/wiki/Wikipedia_Zero) as well as the Wikipedia app (https://en.wikipedia.org/wiki/List_of_Wikipedia_mobile_applications).
So, yes, the Foundation is taking mobile devices into account.
If you want to run your own instance of MediaWiki with Bootstrap, you can install one of several skins. I'm familiar with Chameleon (https://www.mediawiki.org/wiki/Skin:Chameleon) and Foreground (http://foreground.thingelstad.com/wiki/Main_Page).
I'd say there is plenty of mobile-directed effort.
Jonathan Aquilina wrote:
Hey guys reading through some of these tasks, I am wondering has the wiki media foundation taken into account mobile devices and started taking media wiki down a mobile friendly path through using bootstrap etc?
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering https://lists.wikimedia.org/mailman/listinfo/mobile-l irc://irc.freenode.net/wikimedia-mobile
Yes we have some mobile things. Admittedly the mobile web world is a bit broken and browsers don't use localStorage reliably and don't work on the default CSS being pretty; we end up putting some sweat into writing "native" apps. Mark A. Hershberger linked to more details.
I would like to stress that the MobileFrontend is a bit like a skin and it needs YOUR help to make it reasonable. Last I tried, it was rather limited. I wouldn't mind us writing more mobile-friendly skins which don't involve PHP and redesigning the preferences screen just for one platform.
I could help with this. As of bootstrap 3 it takes into account mobile devices so its easy to code a layout with html and css and no need for php. Question is is it worth fixing whats there or writing something entirely from scratch.
I would advocate a write from scratch approach if possible if not. then I would love to start working on moving the mobile side of things towards bootstrap.
On Wed, Dec 10, 2014 at 10:21 PM, svetlana svetlana@fastmail.com.au wrote:
Jonathan Aquilina wrote:
Hey guys reading through some of these tasks, I am wondering has the wiki media foundation taken into account mobile devices and started taking
media
wiki down a mobile friendly path through using bootstrap etc?
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering https://lists.wikimedia.org/mailman/listinfo/mobile-l irc://irc.freenode.net/wikimedia-mobile
Yes we have some mobile things. Admittedly the mobile web world is a bit broken and browsers don't use localStorage reliably and don't work on the default CSS being pretty; we end up putting some sweat into writing "native" apps. Mark A. Hershberger linked to more details.
I would like to stress that the MobileFrontend is a bit like a skin and it needs YOUR help to make it reasonable. Last I tried, it was rather limited. I wouldn't mind us writing more mobile-friendly skins which don't involve PHP and redesigning the preferences screen just for one platform.
-- svetlana
MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Jonathan Aquilina wrote:
I could help with this. As of bootstrap 3 it takes into account mobile devices so its easy to code a layout with html and css and no need for php.
I have no idea whether mediawiki allows to write "layouts" without touching PHP. Would suggest to check that first.
Would anyone be able to answer the above on this list? Would I still need to touch php for the layouts? or can that be bypassed and pure html and css used instead? Obviously injecting php as needed?
On Wed, Dec 10, 2014 at 10:46 PM, svetlana svetlana@fastmail.com.au wrote:
Jonathan Aquilina wrote:
I could help with this. As of bootstrap 3 it takes into account mobile devices so its easy to code a layout with html and css and no need for
php.
I have no idea whether mediawiki allows to write "layouts" without touching PHP. Would suggest to check that first.
-- svetlana
MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
On Thu, 11 Dec 2014 05:58:48 +0100, Jonathan Aquilina eagles051387@gmail.com wrote:
Would anyone be able to answer the above on this list? Would I still need to touch php for the layouts? or can that be bypassed and pure html and css used instead? Obviously injecting php as needed?
I am not sure what you mean. You can't avoid writing PHP entirely when creating a skin (it's not a real "templating" language), but you don't need to write a lot of it and you can copy-paste samples.
https://www.mediawiki.org/wiki/Manual:Skinning is helpful.
Im not trying to avoid it if its necessary for media wiki. but native skins for MW are they responsive or are 3rd party skins necessary?
On Thu, Dec 11, 2014 at 10:14 AM, Bartosz Dziewoński matma.rex@gmail.com wrote:
On Thu, 11 Dec 2014 05:58:48 +0100, Jonathan Aquilina < eagles051387@gmail.com> wrote:
Would anyone be able to answer the above on this list? Would I still need
to touch php for the layouts? or can that be bypassed and pure html and css used instead? Obviously injecting php as needed?
I am not sure what you mean. You can't avoid writing PHP entirely when creating a skin (it's not a real "templating" language), but you don't need to write a lot of it and you can copy-paste samples.
https://www.mediawiki.org/wiki/Manual:Skinning is helpful.
-- Bartosz Dziewoński
MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
The answer is not as simple as that.
First let's try to explain the structure a bit. All existing skins are a combination of a PHP template and a set of CSS. When we say Vector, we mean the PHP UI template vector, and the CSS that goes with that template. This template itself only handles everything outside the 'content', which is usually the sidebar, topbar, footer, the 'mostly static' areas of every single viewed page. The Vector CSS targets these elements as well, but in addition also targets elements of the content (some of which it shares with other skins).
As you might note, it already sounds chaotic.
The currently shipped by default CSS skins (and especially the MobileFrontend one) are as responsive as is useful, considering the constraints of the user base, our not too consistent classnames and IDs and the totally 'unstructured' content that is created by MediaWiki or that is the output of the wikitext of a page. There are also a lot of constraints on these classnames and identifiers, because they are widely used inside scripts of 100s of modules and extensions etc and used and defined all over the place internally wherever 'content' is generated. And then there are things like rtl and mixed rtl and ltr environments, accessibility etc to consider, which most sites happily ignore :)
These constraints are what makes the authoring of a skin a complex task in MediaWiki-land, especially if you want to target existing audiences. Writing a bunch of CSS and PHP is easy, making it work across everything that is currently already in use without pissing of existing customers is what is hard. Improving the structure, the responsiveness and removing the technical and historical debt are things we work on all the time, but by the nature of our Wiki landscape it will be a very slow process, still requiring some 4 more years to get to where we need to be (just my guess).
To get closer to the answer you were probably looking for: there are no existing layout classes in use by mediawiki, other than the very new and not yet widely deployed https://www.mediawiki.org/wiki/OOjs_UI layouts, If you make a new PHP skin, you can add such classes of course (or u add them by way of JS), but u will break some pages and fixing this 'long tail' is where your biggest challenges would likely be (and the separately shipped and maintained responsive MW skins Chameleon and Foreground, might feel non-responsive due to similar long tails). Experiments in this area are very welcome, and will feed into the improvements we make. Use the skin wherever u want, but don't get your hopes up for a deployment to a WMF wiki, because that is unlikely.
Hope that answers your questions. DJ
On Thu, Dec 11, 2014 at 10:22 AM, Jonathan Aquilina eagles051387@gmail.com wrote:
Im not trying to avoid it if its necessary for media wiki. but native skins for MW are they responsive or are 3rd party skins necessary?
On Thu, Dec 11, 2014 at 10:14 AM, Bartosz Dziewoński matma.rex@gmail.com wrote:
On Thu, 11 Dec 2014 05:58:48 +0100, Jonathan Aquilina < eagles051387@gmail.com> wrote:
Would anyone be able to answer the above on this list? Would I still
need
to touch php for the layouts? or can that be bypassed and pure html and css used instead? Obviously injecting php as needed?
I am not sure what you mean. You can't avoid writing PHP entirely when creating a skin (it's not a real "templating" language), but you don't
need
to write a lot of it and you can copy-paste samples.
https://www.mediawiki.org/wiki/Manual:Skinning is helpful.
-- Bartosz Dziewoński
MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
-- Jonathan Aquilina _______________________________________________ MediaWiki-l mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
On 10.12.2014 15:30, Jonathan Aquilina wrote:
Hey guys reading through some of these tasks, I am wondering has the wiki media foundation taken into account mobile devices and started taking media wiki down a mobile friendly path through using bootstrap etc?
They are a dozen of tasks (mostly for beginners) related to Kiwix for Android.
Emmanuel
mediawiki-l@lists.wikimedia.org