Hello,
not sure which list would be right for this, please re-direct as needed!
We're experimentally using the OCG-PDF-renderer on our wiki, and we're
hoping that it will render pages like this one:
http://oer.educ.cam.ac.uk/wiki/OER4Schools/Questioning
My main concern here is the use of CSS to:
1. Create boxes with "educator notes". These are divs with some css to
provide borders around text. This was one of the major obstacles why the
previous Collection extension never worked well for us.
2. We also use css to prefix the section numbers with an extra string
("2.2." in this case), which helps uniquely identify sections within the
overall OER4Schools programme.
3. (On a tangent:) We extensively use SMW for navigation and various other
things. Is there going to be a problem with that in OCG-PDF-renderer?
I'm sure this has all been discussed in various places - would appreciate
some feedback or links to where I can read up!
Note that the above page actually fails with "Status: ! Package xcolor
Error: Undefined color `linkcolorlinkcolor'.", and we'll start to submit
bugs fairly soon.
Thanks!
Bjoern
Currently our approach on social media is that "Social media websites
aren't useful for spreading news and reaching out to potential users and
contributors." [1] I challenge this though. Is it really true? Twitter
has 254 million active monthly users, with 500 million tweets sent per day
[2], Facebook has 1.35 billion active monthly users users. [3]
I know there are many active Wikipedians who frequent both of these sites.
Should we be more actively encouraging people to share?
The history of the Social Media page indicates this was added as an ‘initial
dump’ back in November of 2011. [4] But I wonder if it might be worth
revisiting or refreshing this decision in light of the current world we
live in.
What do others think? What would the reaction be to a sharethis.com type
service where any site could engage ? Would this be more valuable on
mobile than than desktop?
1: https://www.mediawiki.org/wiki/Social_media
2: https://about.twitter.com/company
3: http://newsroom.fb.com/company-info
4:
https://www.mediawiki.org/w/index.php?title=Social_media&diff=1318877&oldid…
[x-posted announcement]
Hello,
Language Engineering team of the Wikimedia Foundation is hosting the next
IRC office hour on January 14, 2015 (Wednesday) at 1600 UTC on
#wikimedia-office . We will be taking questions and discussing about our
ongoing projects. You may have also read our recent announcement about
making Content Translation available very soon as a beta feature[1] on a
few Wikipedias. We will be happy to address questions you may have about
this.
Please see below to check local time and event details
Thanks
Runa
[1]
http://blog.wikimedia.org/2015/01/10/content-translation-beta-coming-soon
<http://blog.wikimedia.org/2015/01/10/content-translation-beta-coming-soon/>
Monthly IRC Office Hour:
==================
# Date: January 14, 2015 (Wednesday)
# Time: 1600 UTC (Check local time:
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150114T1600 )
# IRC channel: #wikimedia-office
# Agenda:
1. Content Translation beta feature
2. Q & A (Questions can be sent to me ahead of the event)
--
Language Engineering - Outreach and QA Coordinator
Wikimedia Foundation
Hi I used metrolook as a skin and I also edit it. I am wandering can I have some help it fixing it the thing that needs to be fixed is sidebar I would like it to a have a scroll bar if it needs to have one if the content goes out of screen but I doint know how to make the sidebar go auto so the size stays the same and the scroll bars doesent get in the way of content. but as you see here http://www.pidgi.net/wiki/Main_Page the scroll bar goes into the content how do I get the scroll bar to go out of the content have a space for itself. and the scroll to have auto so if there is no need for a scroll bar the scroll bar wont show but also how do I move the content to the left how do I move it so that I moves with the scroll bar if it needs more room please. my site is at http://en.random-wikisaur.tk and the code is at https://github.com/paladox2015/Metrolook.
Hello and welcome to the latest edition of the WMF Engineering Roadmap
and Deployment update.
The full log of planned deployments next week can be found at:
<https://wikitech.wikimedia.org/wiki/Deployments#Week_of_January_12th>
A quick list of notable items...
== All Week ==
* HHVM will be rolled out to the "jobrunner" servers
== Monday ==
* Enable "In other projects" feature as default for French Wikipedia
** <https://phabricator.wikimedia.org/T85971>
** This was a Beta Feature on French Wikipedia (and still is on the vast
majority of wikis)
* Soft launch of the Wikimania Scholarships App for 2015 application
cycle
== Tuesday ==
* MediaWiki deploy
** group1 to 1.25wmf14: All non-Wikipedia sites (Wiktionary, Wikisource,
Wikinews, Wikibooks, Wikiquote, Wikiversity, and a few other sites)
** <https://www.mediawiki.org/wiki/MediaWiki_1.25/wmf14>
== Wednesday ==
* MediaWiki deploy
** group2 to 1.25wmf14 (all Wikipedias)
** group0 to 1.25wmf15 (test/test2/testwikidata/mediawiki)
Thanks and as always, questions and comments welcome,
Greg
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
Running several wiki farms with central code repositories I know this.
The fix is to set the environment variable MW_INSTALL_PATH, eg.:
/home/wiki-site/www/wikifoo $ MW_INSTALL_PATH=$(pwd) php maintenance/update.php --quick
/Manuel
Am 09.01.2015 18:22 schrieb Andre Klapper <aklapper(a)wikimedia.org>:
>
> Hi,
>
> On Thu, 2015-01-08 at 18:51 +0100, Jefsey wrote:
> > I have loaded 1.23 in /wiki
> > I have symlinked it in my /home/wiki-site/www directories.
> > It works without problem. However, when I try
>
> That sounds like a problem with configuring MediaWiki and better suited
> for https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
>
> Thanks,
> andre
>
> [Please do not reply to random messages to start a new topic. It breaks
> threading in email clients. Please start a new message instead. Thanks!]
> --
> Andre Klapper | Wikimedia Bugwrangler
> http://blogs.gnome.org/aklapper/
>
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Hi,
On Thu, 2015-01-08 at 18:51 +0100, Jefsey wrote:
> I have loaded 1.23 in /wiki
> I have symlinked it in my /home/wiki-site/www directories.
> It works without problem. However, when I try
That sounds like a problem with configuring MediaWiki and better suited
for https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Thanks,
andre
[Please do not reply to random messages to start a new topic. It breaks
threading in email clients. Please start a new message instead. Thanks!]
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
Website garnering registrations by "donating" few cents of dollar for
each merged commit. They started a while ago but looks like it's
expanding. Just FYI in case you've not received one yet.
Nemo
-------- Messaggio inoltrato --------
Oggetto: You received a tip for your commit
Data: Fri, 09 Jan 2015 07:36:52 +0000
Hello, Federico Leva!
You were tipped 0.11 XPM for your commit on Project wikimedia/mediawiki.
Please, log in and tell us your primecoin address to get it.
Your current balance is 0.11 XPM. If you don't enter a primecoin address
your tips will be returned to the project in 30 days.
Sign In
Thanks for contributing to Open Source!
Hi!
Tim merged my patch[1] which implements the extension registration RfC[2].
For extensions (and skins!) to use this they need to be converted to
have extension.json (or skin.json) files. A maintenance script,
convertExtensionToRegistration.php, has been written to do this, but
there may be some edge cases that need some manual tweaking.
How should we go about migrating extensions? I've come up with a few
different ideas:
1. Package the extension registration code into an "extension" which can
be used by people who want to run newer copies of extensions on old
MediaWiki versions. We would then convert extensions to the
extension.json format and remove the PHP entry points.
2. Similar to #1, but package the extension registration code in each
individual extension, like was done with the i18n migration. I don't
really like this idea because a change to the code requires updating
every single extension.
3. Convert all extensions to extension.json, but continue to maintain
PHP entry points with duplicated information if the extension wants to
maintain old compatibility.
I'm personally leading towards option #1. Thoughts?
Once we have a migration plan decided, I'll start working on updating
documentation and other fun stuff.
[1] https://gerrit.wikimedia.org/r/#/c/166705/
[2]
https://www.mediawiki.org/wiki/Requests_for_comment/Extension_registration
Thanks,
-- Legoktm
Hi all!
I am thinking about a new idea about a content tree extension of
web/desktop/computer Wiki. When I use mobile phone to access website of
Wikipedia, I can fold and unfold a content item of the content tree. That's
very convenient. However, when I use computer to access Wiki, there is no
such feature, I can not fold or unfold a content item. So shall we add this
feature from mobile Wiki to the web/computer Wiki? In other words, let the
user able to fold and unfold any content item at any level of the content
tree. For example, I search Taipei, I get 1. History, 2. Geography, 1.1
First settlements, and 1.2 Japaneses rule ect. So I would like to able to
unfold 1. History, and 1.1 First settlements, or I just unfold 1. History
and fold 1.1 First Settlements to see 1.2 Japanese rule which is unfolded.
So I would like to fold and unfold any level content items to further the
visit quality. The mobile side wiki also can improve, since it can only
fold and unfold the first level content item.
Also,add a go-back button which let the user go back to the content tree
from any content item of any level in the content tree.
Eallan