Re: [Wikitech-l] Please use sitenotice when a new version of software is deployed
People that are interested in the version will more than likely already know about [[Special:Version]], if they want the added onscreen [clutter] presence they could whip up a gadget or something to pull it from the API. On Sat, Dec 7, 2013 at 4:53 PM, Bináris wrote: > There could be a small-sized version number somewhere on screen. Those who > are interested in would learn where it is and could watch it, while others > won't be disturbed. > ___ > Wikitech-l mailing list > Wikitech-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Please use sitenotice when a new version of software is deployed
There could be a small-sized version number somewhere on screen. Those who are interested in would learn where it is and could watch it, while others won't be disturbed. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] MediaWiki 1.22.0 released
Here's the document I've thought to contain the Right Information for the past years: https://www.mediawiki.org/wiki/Version_lifecycle On Sat, Dec 7, 2013 at 3:51 AM, Andre Klapper wrote: > On Fri, 2013-12-06 at 23:02 +, Markus Glaser wrote: > > I am happy to announce the availability of the first stable release of > > the new MediaWiki 1.22 release series. > > Congratulations! > > I'm wondering which older versions are still supported. > https://www.mediawiki.org/wiki/Template:DownloadMediaWiki lists 1.20.8 > as legacy but not 1.21.3, but now also states that "1.20.x [...] was > discontinued." > If the latter is correct, does > https://www.mediawiki.org/wiki/Template:MW_legacy_release_number > need to be changed from "1.20.8" to "1.21.3"? > > andre > -- > Andre Klapper | Wikimedia Bugwrangler > http://blogs.gnome.org/aklapper/ > > > ___ > Wikitech-l mailing list > Wikitech-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > -- Siebrand Mazeland Product Manager Language Engineering Wikimedia Foundation M: +31 6 50 69 1239 Skype: siebrand Support Free Knowledge: http://wikimediafoundation.org/wiki/Donate ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] MediaWiki 1.22.0 released
I only corrected the stable version number templates, Someone else will have to do the others (As well as the [[MW 1.22]] and the release notes page, if they havn't been done) On Sat, Dec 7, 2013 at 12:51 PM, Andre Klapper wrote: > On Fri, 2013-12-06 at 23:02 +, Markus Glaser wrote: > > I am happy to announce the availability of the first stable release of > > the new MediaWiki 1.22 release series. > > Congratulations! > > I'm wondering which older versions are still supported. > https://www.mediawiki.org/wiki/Template:DownloadMediaWiki lists 1.20.8 > as legacy but not 1.21.3, but now also states that "1.20.x [...] was > discontinued." > If the latter is correct, does > https://www.mediawiki.org/wiki/Template:MW_legacy_release_number > need to be changed from "1.20.8" to "1.21.3"? > > andre > -- > Andre Klapper | Wikimedia Bugwrangler > http://blogs.gnome.org/aklapper/ > > > ___ > Wikitech-l mailing list > Wikitech-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] MediaWiki 1.22.0 released
On Fri, 2013-12-06 at 23:02 +, Markus Glaser wrote: > I am happy to announce the availability of the first stable release of > the new MediaWiki 1.22 release series. Congratulations! I'm wondering which older versions are still supported. https://www.mediawiki.org/wiki/Template:DownloadMediaWiki lists 1.20.8 as legacy but not 1.21.3, but now also states that "1.20.x [...] was discontinued." If the latter is correct, does https://www.mediawiki.org/wiki/Template:MW_legacy_release_number need to be changed from "1.20.8" to "1.21.3"? andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Making MediaWiki extensions installable via Composer
On 2013-12-06 5:46 PM, Rob Lanphier wrote:
> It seems that the idea of using Composer more in MediaWiki generally comes
> up at least once every 2-3 months, but we never get beyond the "wouldn't it
> be nice if" stage. I honestly don't think it would take that much of a
> shove to put us on a trajectory to using it much more seriously.
Strictly speaking one thing did get past the "wouldn't it be nice
if" stage. It used to be possible to install PHPUnit and run our
tests with that simply by running `{composer} install`, until someone
went and deleted composer.json as a "feature". Which also now that I
look back has also messed up the implementation of the " Update our code
to use RDFa 1.1 instead of RDFa 1.0"[1] RFC since that feature was the
first one to require a composer installed library to function (it only
needed it to run tests, but it was the first toe dipped into the water).
[1]
https://www.mediawiki.org/wiki/Requests_for_comment/Update_our_code_to_use_RDFa_1.1_instead_of_RDFa_1.0
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://danielfriesen.name/]
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Please use sitenotice when a new version of software is deployed
On 2013-12-06 12:31 AM, Amir E. Aharoni wrote: > The RELEASE-NOTES file should be useful for people who install MediaWiki on > their servers. It isn't so useful for Wikipedia readers and editors. The > Tech News should do the job of RELEASE-NOTES for Wikipedia readers and > editors, and it's easy to update it because it's a wiki page. What can be > suggested is that every time a significant feature that visibly affects > end-users is merged, the developer who committed it should update the Tech > News page, and before publishing Tech News a responsible editor > (Guillaume?) should edit it and remove the less important things. MediaWiki is not a Wikimedia-only product, Wikimedia and Wikipedia are one user of MediaWiki. And the MediaWiki development community is separate from Wikimedia and consists of more than just people developing features intended for the Wiki[pm]edia community. I do not believe it should be the responsibility of volunteer MediaWiki community developers to provide the on-site deployment news for a single user of the software. ~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://danielfriesen.name/] ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Making MediaWiki extensions installable via Composer
Hi everyone, Jeroen let me know offlist that he's not interested in writing an RFC in this area, so I'm wondering if there are any other takers for Composer use in MediaWiki. I think there may be multiple RFCs to consider: 1. Composer as a means of MediaWiki extension management 2. Composer as a means of MediaWiki shared library management 3. Exposing certain functionality in embedded in MediaWiki as reusable Composer libraries. It seems that the idea of using Composer more in MediaWiki generally comes up at least once every 2-3 months, but we never get beyond the "wouldn't it be nice if" stage. I honestly don't think it would take that much of a shove to put us on a trajectory to using it much more seriously. Rob On Fri, Dec 6, 2013 at 11:03 AM, Rob Lanphier wrote: > Hi Jeroen, > > I'd love for someone to take a crack at writing an RFC for this, and maybe > we can get this on the agenda for the Architecture Summit. It seems to be > a topic that comes up frequently, and has a number of champions, so it > doesn't have to be you that does this. Thoughts? > > Rob > > > On Sun, Nov 24, 2013 at 9:10 AM, Jeroen De Dauw wrote: > >> Hey all, >> >> Several MediaWiki extensions, such as Maps and Semantic MediaWiki, are now >> installable via Composer. Lately I've been getting quite a few questions >> from developers on how to have their extensions support this awesome >> dependency manager, and decided to write down the most important points >> that are not obviously evident in the Composer documentation down. >> >> >> http://www.bn2vs.com/blog/2013/11/24/introduction-to-composer-for-mediawiki-developers/ >> >> Cheers >> >> -- >> Jeroen De Dauw >> http://www.bn2vs.com >> Don't panic. Don't be evil. ~=[,,_,,]:3 >> -- >> ___ >> Wikitech-l mailing list >> Wikitech-l@lists.wikimedia.org >> https://lists.wikimedia.org/mailman/listinfo/wikitech-l > > > ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] SkinTemplateOutputPageBeforeExec hook and documenting skin template variables
I created a bug around killing this hook in favour of more specific clearer hooks - https://bugzilla.wikimedia.org/show_bug.cgi?id=58137 - I don't think we should be tinkering with template variables personally under any circumstances and if we are making changes we should be doing them higher up the stack. I would be interested in your thoughts and inevitable screams about how I'm proposing terrible things ;-) On Fri, Dec 6, 2013 at 10:37 AM, Jon Robson wrote: > The mobile skin has traditionally used the template variable > 'language_urls' in SkinTemplate to access the list of alternative > languages of an article. We are now seeing a lot of friction and bugs > as we try to move our codebase closer to core. > > Question 1: > What does 'language_urls' mean - is it acceptable for anything other > than a real language to be in that list? > > Over the course of 3 weeks however we have had 3 bugs that have added > things that are not languages to this list. This has caused various > noticeable problems with how languages works on mobile. > > Question 2: > Why do developers abuse it in this way - is there not a better more > semantic way to do this? > > Currently we have an issue live on all wikipedias which makes a > language button show up on all pages - even those without articles. > x > https://en.m.wikipedia.org/w/index.php?title=Diggers_%26_Dealers&title=Diggers_%26_Dealers > When the language button at the bottom of the screen is clicked it > says "This page is available in 1 language: Edit links (Edit > interlanguage links) > > As a result I've now proposed a change for our skin to override this > [1] so that we can control the list contents and override the effects > of the hook. > > This however is rather frustrating - especially given none of our > template variables are documented and open to this kind of > interpretation > > Question 3: > Should we document these template variables? If so where and how? > > Thanks for your opinions on this matter. > > [1] https://gerrit.wikimedia.org/r/99693 > > -- > Jon Robson > http://jonrobson.me.uk > @rakugojon -- Jon Robson http://jonrobson.me.uk @rakugojon ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] MediaWiki 1.22.0 released
Dear all, I am happy to announce the availability of the first stable release of the new MediaWiki 1.22 release series. MediaWiki 1.22 is a large release that contains many new features and bug fixes. This is a summary of the major changes of interest to users. You can consult the RELEASE-NOTES-1.22 file for the full list of changes in this version. Our thanks to everyone who helped to improve MediaWiki by testing the release candidates and submitting bug reports. == What's new? == MediaWiki 1.22 includes all changes released in the smaller 1.22wmfX software deployments to Wikimedia sites. === Anti-spam and countervandalism improvements === We're improving countervandalism and anti-spam features: * The patrolling system has been improved to make the "mark as patrolled" link available on any patrollable page or revision, without having to go to Special:RecentChanges or Special:NewPages. It is no longer necessary to look up the "rcid" URI parameter from these special pages. (Bug 15936) * Extension:SimpleAntiSpam, a small but harmless shield against the simplest forms of spambots, has been merged into core. ===Editing improvements=== * When comparing revisions in the history or when previewing changes while editing, "(No difference)" is now shown in place of a diff when the revisions are identical. (Bug 14431) * After a successful edit, the confirmation message "Your edit was saved." is now shown. Formerly a separate extension (Extension:PostEdit), this feature is now part of the core software. (Bug 48276) ===Upgrades to Vector and other skins=== The old Vector extension has been merged into core, and the extension has been discontinued. The new version includes several improvements to both the Vector skin and cross-skin features. (Bug 45051) If you were previously using the Vector extension, you must uninstall it (the extension, not the skin) before upgrading to 1.22. All skins: * Section edit links are now displayed next to their respective headings rather than along the opposite side of the page. (Bug 41729) * Lists of templates and categories used on the page, displayed below the edit form, are now collapsible. The area with license information, edit summary, and related functionality below the edit field has received a minor graphical lift. (Bug 43689) * An "edit warning" is now displayed when the user attempts to leave the edit page with unsaved changes, on browsers supporting dialogs. * Vector skin only: ** Navigation menu subsections are now collapsible. ** Page tabs can now dynamically fold into a dropdown menu when the browser window isn't wide enough to fit them. ===Support for Composer=== The Composer PHP dependency manager can now be used to install some extensions. It solves many common problems, including finding where to download an extension, resolving all of its dependencies and libraries, and selecting the right versions. Most MediaWiki extensions do not currently support Composer, but this is expected to change. ==Upgrade notices for MediaWiki administrators== As with every release, there are some routine maintenance and upgrade tasks that go beyond the primary installation process. ===PHP JSON extension now required=== Though the minimum PHP version is still 5.3.2, MediaWiki now requires either the native JSON extension or the pecl-json-c fork. Most servers already have this PHP extension installed and enabled. However, if you administer your own server, and the MediaWiki installer says you don't have this extension: * If you compiled PHP yourself with the --disable-all configure option, you may have to recompile with --enable-json. * On Red Hat or CentOS, check for the line extension=json.so in /etc/php.ini or /etc/php.d/json.ini. * Ubuntu 13.10, Fedora 19, and other recent Linux distributions package pecl-json-c separately, under names such as php5-json (Ubuntu universe) and php-pecl-jsonc (Fedora). They no longer include the original JSON extension because of licensing concerns. === Several ancient skins removed === On April 1, 2013, several ancient skins were removed from core (not an April Fools' joke): Chick, Classic, MySkin, Nostalgia and Simple. Nostalgia was the phase I/UseModWiki-like skin, and Classic was the main skin before the introduction of the default MonoBook in MediaWiki 1.3 on May 22, 2004. Dating back to February 2002 both skins existed over a year before MediaWiki got its name. === Blank system messages must be deleted === Blanking a system message (editing it on wiki to remove all content) will no longer restore the default value for the message, but instead make it show as an empty string in the interface (fixing Bug 14176, "Add ability to disable MediaWiki messages"). If you have blank messages on your wiki (check Special:AllMessages), you must delete them unless you want them to display as empty. ===Protection rights usage has changed=== A new setting ($wgCascadingRestrictionLevels) was added for enabling
Re: [Wikitech-l] Please use sitenotice when a new version of software is deployed
On Fri, 06 Dec 2013 08:53:36 +0100, Guillaume Paumier wrote: Developers would be ideally-placed to help identify noteworthy changes that will affect Wikimedia users, but most find that activity about as interesting as writing documentation, which says something :) Earlier this year, in a discussion about Gerrit keywords, I suggested that we could use them to tag noteworthy changes, in order to make it easier for developers to identify noteworthy changes, while reducing overhead. Unfortunately, the discussion apparently died: http://thread.gmane.org/gmane.science.linguistics.wikipedia.technical/68183/focus=68292 In the meantime, sending a short message to the wikitech-ambassadors list, or dumping a gerrit/bugzilla link at https://meta.wikimedia.org/wiki/Tech/News/Next is the best way to make sure something is communicated to Wikimedians who have subscribed to be informed of tech-related changes likely to affect them. I have ideas on how to improve things in the long term, but I'm open to other suggestions to improve things in the shorter term as well. The reason tech news are not updated is because it has to be done after the patch is merged. The merger will almost always assume it's the patch creator's responsibility (which is reasonable to me, personally). Then, the patch creator will… * likely not even notice the merge happening if he ignores mails from gerrit * just forget to do this * no longer remember what exactly the patch was about which makes writing any notes harder. We should come up with the way to write "Wikimedia" "release notes"/tech news at the same time we write "end-user" release notes – when creating the patch. -- Matma Rex ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Please use sitenotice when a new version of software is deployed
On Fri, 06 Dec 2013 09:31:09 +0100, Amir E. Aharoni wrote: Well actually, this reminds of the perennial "who should update the RELEASE-NOTES" discussion. It's hard to update it all the time in Gerrit, because it creates a lot of conflicts, so people don't do it and leave it to the release manager (or something along these lines). As recently discussed here [1], this is a solved problem, someone just has to write some glue code for jenkins, deploy the new versions and the conflicts will be gone forever. Maybe everyone should ask the responsible people at WMF to prioritize this instead of perennially complaining. [1] http://www.gossamer-threads.com/lists/wiki/wikitech/403927 -- Matma Rex ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Making MediaWiki extensions installable via Composer
Hi Jeroen, I'd love for someone to take a crack at writing an RFC for this, and maybe we can get this on the agenda for the Architecture Summit. It seems to be a topic that comes up frequently, and has a number of champions, so it doesn't have to be you that does this. Thoughts? Rob On Sun, Nov 24, 2013 at 9:10 AM, Jeroen De Dauw wrote: > Hey all, > > Several MediaWiki extensions, such as Maps and Semantic MediaWiki, are now > installable via Composer. Lately I've been getting quite a few questions > from developers on how to have their extensions support this awesome > dependency manager, and decided to write down the most important points > that are not obviously evident in the Composer documentation down. > > > http://www.bn2vs.com/blog/2013/11/24/introduction-to-composer-for-mediawiki-developers/ > > Cheers > > -- > Jeroen De Dauw > http://www.bn2vs.com > Don't panic. Don't be evil. ~=[,,_,,]:3 > -- > ___ > Wikitech-l mailing list > Wikitech-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] SkinTemplateOutputPageBeforeExec hook and documenting skin template variables
The mobile skin has traditionally used the template variable 'language_urls' in SkinTemplate to access the list of alternative languages of an article. We are now seeing a lot of friction and bugs as we try to move our codebase closer to core. Question 1: What does 'language_urls' mean - is it acceptable for anything other than a real language to be in that list? Over the course of 3 weeks however we have had 3 bugs that have added things that are not languages to this list. This has caused various noticeable problems with how languages works on mobile. Question 2: Why do developers abuse it in this way - is there not a better more semantic way to do this? Currently we have an issue live on all wikipedias which makes a language button show up on all pages - even those without articles. x https://en.m.wikipedia.org/w/index.php?title=Diggers_%26_Dealers&title=Diggers_%26_Dealers When the language button at the bottom of the screen is clicked it says "This page is available in 1 language: Edit links (Edit interlanguage links) As a result I've now proposed a change for our skin to override this [1] so that we can control the list contents and override the effects of the hook. This however is rather frustrating - especially given none of our template variables are documented and open to this kind of interpretation Question 3: Should we document these template variables? If so where and how? Thanks for your opinions on this matter. [1] https://gerrit.wikimedia.org/r/99693 -- Jon Robson http://jonrobson.me.uk @rakugojon ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [Wikidata-l] Italian Wikipedia complements search results with Wikidata based functionality
Hi all, Yes! You can do this under the new trademark policy. Here is some discussion about use of logos on Labs: https://meta.wikimedia.org/wiki/Talk:Trademark_policy#Discussion_about_section_2_.28How_to_use_the_Wikimedia_marks.29. We'll add some language to the Trademark Policy FAQ to clarify this. Nice logo, Cristian! Best, Yana On Tue, Dec 3, 2013 at 3:25 AM, Cristian Consonni wrote: > 2013/12/3 Magnus Manske : > > I like it! Can we use the Wikidata color schema, according to the new, > > improved trademark policy (R) (TM)? > > ((... usual big IANAL disclaimer here ...)) > > I think so. On Wikimedia sites "You may use and remix the Wikimedia > marks on the Wikimedia sites as you please."[1], see also this FAQ[2] > which mentions tools. > > Cristian > > [1] https://meta.wikimedia.org/wiki/Trademark_policy#policy-onwmsites > [2] https://meta.wikimedia.org/wiki/Trademark_policy#FAQ-withoutpermission > > ___ > Wikitech-l mailing list > Wikitech-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Language Engineering IRC Office Hour on December 11, 2013 (Wednesday) at 1700 UTC
[x-posted] Hello, The Wikimedia Language Engineering team will be hosting an IRC office hour on Wednesday, December 11, 2013 between 17:00 - 18:00 UTC on #wikimedia-office. (See below for timezone conversion and other details.) We will be talking about some of our recent and upcoming projects and then taking questions for the remaining time. Questions and any other concerns can also be sent to me directly before the event. See you there! Thanks Runa === Event Details === What: WMF Language Engineering Office hour When: December 11, 2013 (Wednesday). 1700-1800 UTC http://www.timeanddate.com/worldclock/fixedtime.html?iso=20131211T1700 Where: IRC Channel #wikimedia-office on FreeNode -- Language Engineering - Outreach and QA Coordinator Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [Wikidata-l] Italian Wikipedia complements search results with Wikidata based functionality
Hoi,
I received this mail ... It answers your question ..
Thanks,
Gerard
Hoi,
Thanks to some help by Ori Livneh, there are some new installation
instructions that I've added for Wdsearch:
https://en.wikipedia.org/wiki/MediaWiki:Wdsearch.js
Would you be able to go around to the various wikis that have enabled
this and get them to update the code? I've lost track of which wikis
are using it.
Thanks,
-- Legoktm
On 6 December 2013 09:52, Cristian Consonni wrote:
> Il 05/dic/2013 07:32 "Ori Livneh" ha scritto:
> > Please don't load the script on every page. It only targets the search
> > result page. This means a redundant request on every page that isn't the
> > search page. You can change it to:
> >
> > if ( mw.config.get( 'wgCanonicalSpecialPageName' ) === 'Search' ) {
> > importScriptURI("//
> >
>
> en.wikipedia.org/w/index.php?title=MediaWiki:Wdsearch.js&action=raw&ctype=text/javascript
> > ");
> > }
>
> It is used also in ns0 pages that do not exist yet.
>
> C
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] 1.22.0rc3 ready for download
On Fri, Dec 6, 2013 at 3:23 AM, Martijn Hoekstra wrote: > In my estimation David is pretty capable of making an informed decision on > the merits of deploying VE to his wikis. > I wouldn't make such assumptions without context. Deploying beta software in a security sensitive environment is never a good idea. It all depends on what type of wikis are being run and what is being stored on them. *-- * *Tyler Romeo* Stevens Institute of Technology, Class of 2016 Major in Computer Science ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Please use sitenotice when a new version of software is deployed
On Fri, Dec 6, 2013 at 9:30 AM, John Vandenberg wrote: > > How true. Alex asked because of a major upgrade problem on Wikisource which > interrupted almost everyone. See wikisource-l for details. > > I think there are times when a community would like a mass notice of some > sort, and it will differ based on the project and community size and the > likely impact of the upgrade. Agreed; while Tech news can help communicate general technical news to Wikimedians, it isn't supposed to be a substitute for targeted communication with specific wikis or language communities. Ultimately, it's the responsibility of the developer (or their product manager / community liaison if they're lucky enough to have one) to make sure users are properly informed of a major technical change they've made. I'm also available to support developers who need help disseminating such information, but I can't do that unless someone asks :) -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [Wikidata-l] Italian Wikipedia complements search results with Wikidata based functionality
Il 05/dic/2013 07:32 "Ori Livneh" ha scritto:
> Please don't load the script on every page. It only targets the search
> result page. This means a redundant request on every page that isn't the
> search page. You can change it to:
>
> if ( mw.config.get( 'wgCanonicalSpecialPageName' ) === 'Search' ) {
> importScriptURI("//
>
en.wikipedia.org/w/index.php?title=MediaWiki:Wdsearch.js&action=raw&ctype=text/javascript
> ");
> }
It is used also in ns0 pages that do not exist yet.
C
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Please use sitenotice when a new version of software is deployed
On Fri, Dec 6, 2013 at 9:31 AM, Amir E. Aharoni wrote: > > * How to get developers not to forget to write that. > > Quim, Guillaume - ideas on how to improve it? There's already a reminder at the top of https://wikitech.wikimedia.org/wiki/Deployments , and Greg does a great job at highlighting the major changes that are going to be deployed every week (which are then included into tech news). Maybe we should add a similar one to the code review checklist? https://www.mediawiki.org/wiki/Gerrit/Code_review#Review_checklist I'm open to other suggestions. -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Please use sitenotice when a new version of software is deployed
2013/12/6 Guillaume Paumier > I think the Tech news page makes it simple enough to get involved and > contribute: https://meta.wikimedia.org/wiki/Tech/News#contribute ; We > also have a reasonably-stable schedule, so now we "just" need more > people to give a hand. I'm actually drafting an overview of how Tech > news works behind the scenes; I'll share it on this list when it's > out. > Well actually, this reminds of the perennial "who should update the RELEASE-NOTES" discussion. It's hard to update it all the time in Gerrit, because it creates a lot of conflicts, so people don't do it and leave it to the release manager (or something along these lines). The RELEASE-NOTES file should be useful for people who install MediaWiki on their servers. It isn't so useful for Wikipedia readers and editors. The Tech News should do the job of RELEASE-NOTES for Wikipedia readers and editors, and it's easy to update it because it's a wiki page. What can be suggested is that every time a significant feature that visibly affects end-users is merged, the developer who committed it should update the Tech News page, and before publishing Tech News a responsible editor (Guillaume?) should edit it and remove the less important things. Of course, there are two problems: * What's a "significant feature that visibly affects end-users" * How to get developers not to forget to write that. Quim, Guillaume - ideas on how to improve it? -- Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי http://aharoni.wordpress.com “We're living in pieces, I want to live in peace.” – T. Moore ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Please use sitenotice when a new version of software is deployed
On Dec 6, 2013 1:12 PM, "Gerard Meijssen" wrote: > > Hoi, > Let us be honest indeed. The others are not heard when they scream and > shout in their little corner of the world.. > Thanks, > Gerard How true. Alex asked because of a major upgrade problem on Wikisource which interrupted almost everyone. See wikisource-l for details. I think there are times when a community would like a mass notice of some sort, and it will differ based on the project and community size and the likely impact of the upgrade. -- John Vandenberg ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] 1.22.0rc3 ready for download
On Dec 6, 2013 3:28 AM, "John" wrote: > > Correct, I see how my words can be taken several ways. Right now VE is a > very unstable, bug filled, obnoxious elephant. Given enough time, testing, > and maturity it as a lot of promise. > > Right now its like trying to use a rocket like > http://cdn.instructables.com/F9Y/2ONP/F4TLKVHS/F9Y2ONPF4TLKVHS.LARGE.jpgto > land a man on the moon. > > I would give VE probably another 18-24 months before its really ready to be > switched on as a default editor for any non-testing wiki. > In my estimation David is pretty capable of making an informed decision on the merits of deploying VE to his wikis. > > On Thu, Dec 5, 2013 at 9:17 PM, K. Peachey wrote: > > > Bad idea [to package/install],… > > > > Is what I believe beta was saying Tyler. > > > > On Friday, December 6, 2013, Tyler Romeo wrote: > > > > > On Tue, Dec 3, 2013 at 4:39 PM, John > > > > > wrote: > > > > > > > VE is a BAD idea, its full of holes and bugs > > > > > > > > > Those are two separate concepts. Just because something has bugs does not > > > make the software itself a bad idea. > > > > > > *-- * > > > *Tyler Romeo* > > > Stevens Institute of Technology, Class of 2016 > > > Major in Computer Science > > > ___ > > > Wikitech-l mailing list > > > Wikitech-l@lists.wikimedia.org > > > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > > > > > > > > -- > > Sent from Gmail Mobile on my iPod. > > ___ > > Wikitech-l mailing list > > Wikitech-l@lists.wikimedia.org > > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > > > ___ > Wikitech-l mailing list > Wikitech-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
