Re: [Wikitech-l] GPL upgrading to version 3
On 9 February 2015 at 08:28, Max Semenik maxsem.w...@gmail.com wrote: OpenOffice's woes are unrelated to its license, it was already dead by forking when Oracle transferred it to Apache, facilitating a change from GPL+proprietary CLA to the Apache license. Indeed, but they touted the mythical attractiveness of a permissive license over the bondage of copyleft. And it didn't work that way at all in practice. Again: data, rather than anecdote or surmise? As far as I can tell, the claim that permissive attracts more contributions than copyleft is entirely a myth. - d. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Beta bounce handling completed with new beta-mx
Few more updates: Un-subscribe feature just got enabled[1] in group0 and we could successfully test the same, thanks to our TestVerp account in mediawiki.org. The current failure threshold is kept to 5 bounces in 7 days, to match mailman configs[2]. [1] https://gerrit.wikimedia.org/r/#/c/189316/ [2] http://www.list.org/mailman-admin/node25.html Thanks, Tony Thomas http://tttwrites.wordpress.com/ FOSS@Amrita http://foss.amrita.ac.in *where there is a wifi, there is a way* On Sat, Feb 7, 2015 at 9:24 PM, Tony Thomas 01tonytho...@gmail.com wrote: From the production side: The extension got installed in the group0 wikis including mediawiki.org and is now generating and listening to VERPed bounces within group0. It is working perfect with the multiwiki mode enabled, and bounces returning back only to the API of test2.wikipedia.org. Hoo tells me that we even got the initial first bounces recorded in the db. The un-confirm email configuration is still kept to disabled. Thanks, Tony Thomas http://tttwrites.wordpress.com/ FOSS@Amrita http://foss.amrita.ac.in *where there is a wifi, there is a way* On Mon, Feb 2, 2015 at 9:51 PM, Greg Grossmeier g...@wikimedia.org wrote: quote name=Tony Thomas date=2015-02-02 time=19:38:51 +0530 Hello, Happy to inform that beta got is now routing through its new working mx ( mx.beta.wmflabs.org ). Great work, Tony! -- | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E | | identi.ca: @gregA18D 1138 8E47 FAC8 1C7D | ___ 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] Use of hreflang in the head
This appears to be tracked at https://phabricator.wikimedia.org/T3433 It was reverted in 2009 for (alleged) l10n issues, which should be solvable. FWIW we just saved 4 KB per page with https://gerrit.wikimedia.org/r/#/c/177501/ Nemo ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Urlencoding strip markers
On Tuesday, February 3, 2015 at 10:24 AM, Brion Vibber wrote: Special page inclusions shouldn't be able to do anything privileged; they're meant for public data. If that's not being enforced right now I'd recommend reworking or killing the special page inclusion system... Ok, although Brion's idea preserves more of the original content, these larger security concerns don’t look like they are going to be resolved in short order. I think the pragmatic thing to do is either drop the content and raise an error, or replace the content with a warning string as Gergo suggested. Any takers? -- brion On Feb 3, 2015 10:11 AM, Brad Jorsch (Anomie) bjor...@wikimedia.org (mailto:bjor...@wikimedia.org) wrote: On Fri, Jan 30, 2015 at 4:04 PM, Brion Vibber bvib...@wikimedia.org (mailto:bvib...@wikimedia.org) wrote: On Fri, Jan 30, 2015 at 12:11 PM, Jackmcbarn jackmcb...@gmail.com (mailto:jackmcb...@gmail.com) wrote: On Fri, Jan 30, 2015 at 2:02 PM, Brion Vibber bvib...@wikimedia.org (mailto:bvib...@wikimedia.org) wrote: I'd be inclined to unstrip the marker *and squash HTML to plaintext*, then encode the plaintext... I don't see how that addresses the security issue. Rollback tokens in the Special:Contributions HTML would then not be available in the squashed text that got encoded. Thus it could not be extracted and used in the timing attack. While it would avoid *this* bug, it would still allow the attack if there is ever sensitive data on some transcludable special page that isn't embedded in HTML tag attributes. -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org (mailto:Wikitech-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org (mailto: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] GPL upgrading to version 3
This entire conversation is a bit disappointing, mainly because I am a supporter of the free software movement, and like to believe that users should have a right to see the source code of software they use. Obviously not everybody feels this way and not everybody is going to support the free software movement, but I can assure you I personally have no plans on contributing to any WMF project that is Apache licensed, but at the very least MediaWiki core is still GPLv2, even if it makes things a bit more difficult. Also, I have no idea how the MPL works, but I can assure you that licensing under the “GPLv2 or any later version” cannot possibly imply it is available under both the v2 and v3. The different GPL versions have conflicting terms. You cannot possibly use the terms of the v2 and v3 simultaneously. It is legally impossible. What is means is that you can use the software under the terms of the v2 *or* the v3. And, as I mentioned, since Apache is only compatible with v3, as long as using the software under the v2 is an option, you cannot combine code that is under Apache. -- Tyler Romeo 0x405D34A7C86B42DF On February 9, 2015 at 04:06:54, David Gerard (dger...@gmail.com) wrote: On 9 February 2015 at 08:28, Max Semenik maxsem.w...@gmail.com wrote: OpenOffice's woes are unrelated to its license, it was already dead by forking when Oracle transferred it to Apache, facilitating a change from GPL+proprietary CLA to the Apache license. Indeed, but they touted the mythical attractiveness of a permissive license over the bondage of copyleft. And it didn't work that way at all in practice. Again: data, rather than anecdote or surmise? As far as I can tell, the claim that permissive attracts more contributions than copyleft is entirely a myth. - d. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l signature.asc Description: Message signed with OpenPGP using AMPGpg ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] GPL upgrading to version 3
On Mon, Feb 9, 2015 at 11:37 AM, Tyler Romeo tylerro...@gmail.com wrote: This entire conversation is a bit disappointing, mainly because I am a supporter of the free software movement, and like to believe that users should have a right to see the source code of software they use. Obviously not everybody feels this way and not everybody is going to support the free software movement, but I can assure you I personally have no plans on contributing to any WMF project that is Apache licensed, but at the very least MediaWiki core is still GPLv2, even if it makes things a bit more difficult. You're implying that Apache2 licensed software is somehow not part of the free software movement and that's absurd. Apache2 is technically a freer license than GPLv(anything). Like GPL3, it also provides patent protection. In practice it doesn't matter if software is forked and closed if the canonical source isn't. The org that forks must maintain their fork and all of their modifications without help. It's onerous and generally unmaintainable for most orgs, especially if their core business isn't based on the software, or if the canonical source is fast moving. It's your choice to not participate in any project for any reason, but try to understand that some people (such as myself) much prefer to work on software that's truly free, rather than virally free. - Ryan ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Fix problem with CollapsibleVector
Hi could I have some help to fix a problem that a user reported on the extension talk page. The talk page is at http://www.mediawiki.org/wiki/Extension_talk:CollapsibleVector and the title is flickering. I am not sure how to fix the problem I was wandering if someone on here knew how to fix the problem. the source code is at https://git.wikimedia.org/summary/mediawiki%2Fextensions%2FCollapsibleVector ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] GPL upgrading to version 3
On 9 February 2015 at 04:51, Rob Lanphier ro...@wikimedia.org wrote: Also, one cost of copyleft licenses is that they are much, much more complicated than permissive licenses. Even though many people feel comfortable with the compliance requirements of most OSI-approved licenses, the permissive licenses can usually stand alone without an FAQ, whereas an FAQ is required for just about all of the copyleft licenses. That simplicity reduces a very real barrier to adoption. Is this statement from anecdote or data? Otherwise you need to explain how LibreOffice (copyleft) has fifteen or so companies contributing, whereas Apache OpenOffice (permissive) has one and even they've given up actually paying people to work on it. The idea that permissive works better for getting contributions seems to me completely unevidenced. - d. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] GPL upgrading to version 3
On Mon, Feb 9, 2015 at 12:01 AM, David Gerard dger...@gmail.com wrote: On 9 February 2015 at 04:51, Rob Lanphier ro...@wikimedia.org wrote: Also, one cost of copyleft licenses is that they are much, much more complicated than permissive licenses. Even though many people feel comfortable with the compliance requirements of most OSI-approved licenses, the permissive licenses can usually stand alone without an FAQ, whereas an FAQ is required for just about all of the copyleft licenses. That simplicity reduces a very real barrier to adoption. Is this statement from anecdote or data? Otherwise you need to explain how LibreOffice (copyleft) has fifteen or so companies contributing, whereas Apache OpenOffice (permissive) has one and even they've given up actually paying people to work on it. The idea that permissive works better for getting contributions seems to me completely unevidenced. OpenOffice's woes are unrelated to its license, it was already dead by forking when Oracle transferred it to Apache, facilitating a change from GPL+proprietary CLA to the Apache license. -- Best regards, Max Semenik ([[User:MaxSem]]) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Main themes of the Wikimedia and Wikimania hackathons this year
The MediaWiki Developer Summit had three main themes that helped structuring the schedule. These themes were useful, and they can be more useful for the hackathons in Lyon and Mexico City this year, since defining them indvance will help everybody organizing their travel. Anybody can propose a main theme at https://phabricator.wikimedia.org/T89084 Good candidates include Wikimedia software priorities, project meetings, collaboration with external projects, topics of local relevance... Do not hesitate posting proposals even if they are just an initial idea right now. We want to agree on the main themes by the end of next week in order to help people organizing their travel plans. -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Define entry point to generate documentation
Hello, We are migrating Jenkins jobs to simply invokes [test entry points] (ex: composer test, npm test). Some repositories have documentation generated by Jenkins and pushed under https://doc.wikimedia.org/ . I would like to make it as trivial as possible for developers to configure Jenkins, hence I am looking to establish a convention to generate doc. We would need: - a single command we agree on (ex: make doc) - a way to pass/override the destination directory so the jobs in Jenkins can enforce the output where it expects it I have filled https://phabricator.wikimedia.org/T88999 for it. Discussions on wikitech-l preferred. If there is no objections by next week. I will define the convention to be 'make docs' and create all the needed Jenkins jobs templates. Thanks! [test entry points] https://www.mediawiki.org/wiki/Continuous_integration/Test_entry_points -- Antoine hashar Musso ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Define entry point to generate documentation
On Mon, Feb 9, 2015 at 10:16 AM, Antoine Musso hashar+...@free.fr wrote: Hello, We are migrating Jenkins jobs to simply invokes [test entry points] (ex: composer test, npm test). Some repositories have documentation generated by Jenkins and pushed under https://doc.wikimedia.org/ . I would like to make it as trivial as possible for developers to configure Jenkins, hence I am looking to establish a convention to generate doc. We would need: - a single command we agree on (ex: make doc) - a way to pass/override the destination directory so the jobs in Jenkins can enforce the output where it expects it I have filled https://phabricator.wikimedia.org/T88999 for it. Discussions on wikitech-l preferred. If there is no objections by next week. I will define the convention to be 'make docs' and create all the needed Jenkins jobs templates. Thanks! [test entry points] https://www.mediawiki.org/wiki/Continuous_integration/Test_entry_points I hate Makefiles but I'm all for continuing to standardize our job entry points. We do things in too many different ways today. Bryan -- Bryan Davis Wikimedia Foundationbd...@wikimedia.org [[m:User:BDavis_(WMF)]] Sr Software EngineerBoise, ID USA irc: bd808v:415.839.6885 x6855 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [Engineering] Announcement: Tyler Cipriani joins Wikimedia as Release Engineer
Thanks everybody for the warm welcome! After a whirlwind first day, it's time to retreat to Chipotle and Seinfield re-runs to help digest this massive information intake. Thanks again! Tyler ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Wikitech.wikimedia.org read-only, possible outage, 2015-02-10 0:00GMT
This move is now complete. Things are working fine as best I can tell, but please file a bug or contact me if you see bad behavior. (But FIRST log out and back in, because that bug I already know about. *sigh* ) Many thanks to Sean Pringle for support with this move, and the other folks on IRC who I roped in at the last minute: Daniel Zahn, Alex Monk, and Bryan Davis. Without them this might well have been an all-nighter. -Andrew On 2/6/15 10:24 AM, Andrew Bogott wrote: There were several short wikitech outages last week caused by heavy machine load on the server that (among other things) hosts the site. In an attempt to distribute load a bit more reasonably I'm migrating that web host to new hardware. The transition should be fairly graceful as the new host is already up and running. There will be a few interruptions in service, though: - During the move the new wiki will be read-only. This should only last about 10 minutes or so during the DNS switch-over. - After the move there will almost certainly be a series of mishaps involving the labs-controlling aspects of wikitech. I'll be scrambling to fix them and don't expect to spend more than hour or so; I'll follow up with another email if the interruption is an longer than that. - As usual, login sessions will probably be broken necessitating a fresh login to wikitech. This is scheduled for Midnight GMT Tuesday, February 10th. That's 4PM PST on Monday. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] GPL upgrading to version 3
On February 9, 2015 at 15:17:22, Ryan Lane (rlan...@gmail.com) wrote: You're implying that Apache2 licensed software is somehow not part of the free software movement and that's absurd. Apache2 is technically a freer license than GPLv(anything). Like GPL3, it also provides patent protection. In practice it doesn't matter if software is forked and closed if the canonical source isn't. The org that forks must maintain their fork and all of their modifications without help. It's onerous and generally unmaintainable for most orgs, especially if their core business isn't based on the software, or if the canonical source is fast moving. Please don’t spread misinformation to those who don’t know any better. The goal of the free software movement is to ensure the freedoms of end users to see the source code of the software they use. Any license that allows distributors to deny users this right is not actually protecting the goal of the movement. To be clear, software can be free without specifically supporting the free software movement. The GPLv3 was specifically developed to make distributor enforcement of the GPLv3 easier. Rather than requiring third-parties to give out source code on a physical medium, which, as you mentioned, is onerous for many organizations, the newer license is more lax. It's your choice to not participate in any project for any reason, but try to understand that some people (such as myself) much prefer to work on software that's truly free, rather than virally free. I hope you don’t seriously think GPL software is not “truly free”. -- Tyler Romeo 0x405D34A7C86B42DF signature.asc Description: Message signed with OpenPGP using AMPGpg ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] GPL upgrading to version 3
Le 09/02/2015 21:10, Thomas Mulhall a écrit : Should we create a page on mediawiki and allow people to vote for it or against. And advertise it on Wikimedia wiki so that users know there is a vote going on for GPL3. and we should hold the vote for 2 to 3 months giving time for users to vote and since this would probably be a big update to GPL. There is no point in voting nor in using mediawiki.org right now. It is too early. Lets use the proven process that makes laws: - heated discussions and debates - craft proposals - refine until we get good candidates - put the project on vote and apply We are at the discussion phase :-] -- Antoine hashar Musso ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] GPL upgrading to version 3
On Mon, Feb 9, 2015 at 12:22 PM, Tyler Romeo tylerro...@gmail.com wrote: On February 9, 2015 at 15:17:22, Ryan Lane (rlan...@gmail.com) wrote: You're implying that Apache2 licensed software is somehow not part of the free software movement and that's absurd. Apache2 is technically a freer license than GPLv(anything). Like GPL3, it also provides patent protection. In practice it doesn't matter if software is forked and closed if the canonical source isn't. The org that forks must maintain their fork and all of their modifications without help. It's onerous and generally unmaintainable for most orgs, especially if their core business isn't based on the software, or if the canonical source is fast moving. Please don’t spread misinformation to those who don’t know any better. The goal of the free software movement is to ensure the freedoms of end users to see the source code of the software they use. Any license that allows distributors to deny users this right is not actually protecting the goal of the movement. To be clear, software can be free without specifically supporting the free software movement. flamebait Your third sentence is a non-sequitur. Just because free software can be used in non-free ways doesn't defeat the goals of the free software movement (unless you believe that the free software movement really intends to displace all non-free software, in which case the movement is a complete failure). /flamebait Ryan Kaldari ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] GPL upgrading to version 3
On Mon, Feb 9, 2015 at 12:22 PM, Tyler Romeo tylerro...@gmail.com wrote: I hope you don’t seriously think GPL software is not “truly free”. Well, it all depends on point of view on what is free. The FSF interpretation is you can do it your own way if it's done just how I say. Not everyone agrees that more restrictions is more freedom. Note: I don't disagree with Stallmanian coplyleft principles in all cases, I just consider the word free highly misleading here. -- Best regards, Max Semenik ([[User:MaxSem]]) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Announcement: Tyler Cipriani joins Wikimedia as Release Engineer
Hello all, I’m delighted to announce that Tyler Cipriani[0] is joining the foundation as a Release Engineer (obviously joining the Release Engineering team). Tyler lives (and will continue to work remotely from) where you can see the Flatirons[1] in Colorado and comes to us from SparkFun[2] where he was a web developer and sysadmin. Along with the Wikimedia Foundation being a great fit professionally for Tyler (I’m biased maybe) he is also “thrilled to be working at an organization whose values seemingly so closely align with [his] own.” He’ll be at the San Francisco office the week of the 16th and is seeking any suggestions as to what he should do with his free afternoon on Presidents’ Day. Please join me in welcoming Tyler! Greg [0] https://tylercipriani.com/ [1] https://en.wikipedia.org/wiki/Flatirons [2] https://www.sparkfun.com/ -- | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E | | identi.ca: @gregA18D 1138 8E47 FAC8 1C7D | signature.asc Description: Digital signature ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Use of hreflang in the head
Hi folks, MediaWiki emits the hreflang attribute on language links, but only as part of the links in the body, and not in the head as recommended by Google [1]. The result of this is that Google (and possibly other search engines) doesn't interpret the hreflang attribute for purposes of prioritizing search results in the user's own language. From a contact at Google we asked about this: we currently don't use those annotations on the links, we need to see the hreflang link-elements in the head in order to understand that connection. The important parts there are the we need to have them in the head, we need to have them confirmed from the other versions (so DE needs to refer to EN, and EN to DE -- it can't be one-sided), and it needs to be between the canonical URLs. (...) I imagine if you just added the cross-links as you have them in the sidebar as link-elements to the head then you'd be covered. This of course would add some additional payload to pages with lots of language links, but could help avoid results like [2] where the English language version of an article is #1 and the Indonesian one makes no appearance at all. Results vary greatly and it's hard to say how big a problem this is, but even if boosts discoverability of content in the user's language by only 10% or so, that would still be a pretty big win for local content. I'm curious if folks see any downside, other than the additional page payload, in adding this information to the page header. Given the time it takes for the index to be updated, we should be careful about any potential negative consequences. Thanks, Erik [1] https://support.google.com/webmasters/answer/189077?hl=en [2] https://www.google.co.id/?gws_rd=ssl#q=edison -- Erik Möller VP of Product Strategy, Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Use of hreflang in the head
On 2015-02-09 2:16 AM, Erik Moeller wrote: This of course would add some additional payload to pages with lots of language links, but could help avoid results like [2] where the English language version of an article is #1 and the Indonesian one makes no appearance at all. Results vary greatly and it's hard to say how big a problem this is, but even if boosts discoverability of content in the user's language by only 10% or so, that would still be a pretty big win for local content. I think we used to have links in the head (though the exact implementation may have been wrong), if it wasn't a problem then it wouldn't be one now. Also if it really is a problem for Wikipedia Google also supports getting this data from the sitemap. https://support.google.com/webmasters/answer/2620865?hl=en So if it's a problem we could upgrade the sitemap generator to include this data (maybe as an extra parameter) and we could have a config setting that disables the head output. That should work out pretty well. Small wiki setups don't have many language links so links in the head aren't an issue. And if a wiki setup is big enough to have an issue, then it's probably big enough to be using sitemaps. ~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] [gerrit] EUREKA!
On Sat, Feb 7, 2015 at 2:11 AM, Ricordisamoa ricordisa...@openmailbox.org
wrote:
https://git.wikimedia.org/commit/apps%2Fios%2Fwikipedia/
6532021b4f4b1f09390b1ffc3f09d149b2a8d9d1
https://phabricator.wikimedia.org/rAPIW08f0d835ba4441eab28ce6914
24088e2b4743270
It works, but unlike apps/ios/wikipedia, APIW is not a human-readable
identifier for a repository.
There was a long discussion about callsigns, and this is what it was agreed:
https://www.mediawiki.org/wiki/Phabricator/Diffusion/Callsign_naming_conventions
https://www.mediawiki.org/wiki/Phabricator/Diffusion/Callsign_naming_conventions/Existing_repositories
APIW == AP(ps)I(os)W(ikipedia)
Guessing where cars come from is a fun game in countries that still encode
geographical references in their license plates (Germany are the masters
{{citation needed}} with 1, 2, and 3 letter codes based on the size
population of the department). Callsigns are exactly like license plates,
and now all Wikimedia tech fans can play this game with our repositories.
:)
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [gerrit] EUREKA!
Il 09/02/2015 15:14, Quim Gil ha scritto:
On Sat, Feb 7, 2015 at 2:11 AM, Ricordisamoa ricordisa...@openmailbox.org
wrote:
https://git.wikimedia.org/commit/apps%2Fios%2Fwikipedia/
6532021b4f4b1f09390b1ffc3f09d149b2a8d9d1
https://phabricator.wikimedia.org/rAPIW08f0d835ba4441eab28ce6914
24088e2b4743270
It works, but unlike apps/ios/wikipedia, APIW is not a human-readable
identifier for a repository.
There was a long discussion about callsigns, and this is what it was agreed:
https://www.mediawiki.org/wiki/Phabricator/Diffusion/Callsign_naming_conventions
https://www.mediawiki.org/wiki/Phabricator/Diffusion/Callsign_naming_conventions/Existing_repositories
APIW == AP(ps)I(os)W(ikipedia)
Guessing where cars come from is a fun game in countries that still encode
geographical references in their license plates (Germany are the masters
{{citation needed}} with 1, 2, and 3 letter codes based on the size
population of the department). Callsigns are exactly like license plates,
and now all Wikimedia tech fans can play this game with our repositories.
:)
APIW makes me think of a wiki API...
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] jenkings merging
Le 07/02/2015 01:56, Thomas Mulhall a écrit : Hi how do I get my skins and extensions to be merged automatically by jenkings like it does on centralauth projects are at https://git.wikimedia.org/summary/mediawiki%2Fskins%2FMetrolook and https://git.wikimedia.org/summary/mediawiki%2Fextensions%2FCollapsibleVector Hello, The mediawiki/skins/Metrolook repository has Jenkins jobs. Whenever one vote Code-Review +2 , Jenkins runs the jobs and on success will ask Gerrit to submit the patch (and hence get it merged). -- Antoine hashar Musso ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [Engineering] Announcement: Tyler Cipriani joins Wikimedia as Release Engineer
Welcome Tyler. Great to have you join. Best of luck. --tomasz On Mon, Feb 9, 2015 at 1:28 PM, Greg Grossmeier g...@wikimedia.org wrote: Hello all, I’m delighted to announce that Tyler Cipriani[0] is joining the foundation as a Release Engineer (obviously joining the Release Engineering team). Tyler lives (and will continue to work remotely from) where you can see the Flatirons[1] in Colorado and comes to us from SparkFun[2] where he was a web developer and sysadmin. Along with the Wikimedia Foundation being a great fit professionally for Tyler (I’m biased maybe) he is also “thrilled to be working at an organization whose values seemingly so closely align with [his] own.” He’ll be at the San Francisco office the week of the 16th and is seeking any suggestions as to what he should do with his free afternoon on Presidents’ Day. Please join me in welcoming Tyler! Greg [0] https://tylercipriani.com/ [1] https://en.wikipedia.org/wiki/Flatirons [2] https://www.sparkfun.com/ -- | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E | | identi.ca: @gregA18D 1138 8E47 FAC8 1C7D | ___ Engineering mailing list engineer...@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/engineering ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [Engineering] Announcement: Tyler Cipriani joins Wikimedia as Release Engineer
Welcome, Tyler! I'm looking forward to working together. On Mon, Feb 9, 2015 at 1:28 PM, Greg Grossmeier g...@wikimedia.org wrote: Hello all, I’m delighted to announce that Tyler Cipriani[0] is joining the foundation as a Release Engineer (obviously joining the Release Engineering team). Tyler lives (and will continue to work remotely from) where you can see the Flatirons[1] in Colorado and comes to us from SparkFun[2] where he was a web developer and sysadmin. Along with the Wikimedia Foundation being a great fit professionally for Tyler (I’m biased maybe) he is also “thrilled to be working at an organization whose values seemingly so closely align with [his] own.” He’ll be at the San Francisco office the week of the 16th and is seeking any suggestions as to what he should do with his free afternoon on Presidents’ Day. Please join me in welcoming Tyler! Greg [0] https://tylercipriani.com/ [1] https://en.wikipedia.org/wiki/Flatirons [2] https://www.sparkfun.com/ -- | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E | | identi.ca: @gregA18D 1138 8E47 FAC8 1C7D | ___ Engineering mailing list engineer...@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/engineering -- Dan Duvall Automation Engineer Wikimedia Foundation http://wikimediafoundation.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] GPL upgrading to version 3
On Mon, 2015-02-09 at 20:10 +, Thomas Mulhall wrote: Should we create a page on mediawiki and allow people to vote for it or against. Nope, as software development is not a popularity contest. 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] GPL upgrading to version 3
Hi! This entire conversation is a bit disappointing, mainly because I am a supporter of the free software movement, and like to believe that users should have a right to see the source code of software they use. Obviously not everybody feels this way and not everybody is going to support the free software movement, but I can assure you I personally have no plans on contributing to any WMF project that is Apache licensed, but at the very least MediaWiki core is still GPLv2, even if it makes things a bit more difficult. You seem to be equating access to source code with GPL, which IMHO is a very narrow view of the world. The open source world is much wider than GPL (even though nobody can deny that GPL projects are a substantial part of it), and there are many successful, widely acclaimed and widely used software projects which are open source and not GPL. Of course, the choice where to contribute and on which condition is entirely yours, but I *personally* would view such stance as somewhat counterproductive, if your goal is to contribute to the world's repository of high quality software that can be accessed to everyone. -- Stas Malyshev smalys...@wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] GPL upgrading to version 3
On 09/02/15 20:37, Tyler Romeo wrote: This entire conversation is a bit disappointing, mainly because I am a supporter of the free software movement, and like to believe that users should have a right to see the source code of software they use. Obviously not everybody feels this way and not everybody is going to support the free software movement, but I can assure you I personally have no plans on contributing to any WMF project that is Apache licensed, but at the very least MediaWiki core is still GPLv2, even if it makes things a bit more difficult. Also, I have no idea how the MPL works, but I can assure you that licensing under the “GPLv2 or any later version” cannot possibly imply it is available under both the v2 and v3. The different GPL versions have conflicting terms. You cannot possibly use the terms of the v2 and v3 simultaneously. It is legally impossible. What is means is that you can use the software under the terms of the v2 *or* the v3. And, as I mentioned, since Apache is only compatible with v3, as long as using the software under the v2 is an option, you cannot combine code that is under Apache. It is *available*. You can use, at your choice either of them (or any later version not yet released). Though your options may be decreased if you combine the work with a different one not compatible with both of them. Also note we have traditionally held the position of not considering MW extensions derived works (and thus allowing them to be licensed like eg. MIT), which would be arguable. I wouldn't even be surprised if -supposing we had an AGPL mediawiki- a troll came requesting the full LocalSettings.php contents to be published, password DB included. I also vote for maintaining the current GPLv2+ license. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] jenkings merging
Look at the instructions at https://www.mediawiki.org/wiki/Continuous_integration/Tutorials/Adding_a_MediaWiki_extension The final patch might look something like https://gerrit.wikimedia.org/r/#/c/174797/ On Fri, Feb 6, 2015 at 7:56 PM, Thomas Mulhall thomasmulhall...@yahoo.com wrote: Hi how do I get my skins and extensions to be merged automatically by jenkings like it does on centralauth projects are at https://git.wikimedia.org/summary/mediawiki%2Fskins%2FMetrolook and https://git.wikimedia.org/summary/mediawiki%2Fextensions%2FCollapsibleVector ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] GPL upgrading to version 3
Should we create a page on mediawiki and allow people to vote for it or against. And advertise it on Wikimedia wiki so that users know there is a vote going on for GPL3. and we should hold the vote for 2 to 3 months giving time for users to vote and since this would probably be a big update to GPL. On Monday, 9 February 2015, 19:37, Tyler Romeo tylerro...@gmail.com wrote: This entire conversation is a bit disappointing, mainly because I am a supporter of the free software movement, and like to believe that users should have a right to see the source code of software they use. Obviously not everybody feels this way and not everybody is going to support the free software movement, but I can assure you I personally have no plans on contributing to any WMF project that is Apache licensed, but at the very least MediaWiki core is still GPLv2, even if it makes things a bit more difficult. Also, I have no idea how the MPL works, but I can assure you that licensing under the “GPLv2 or any later version” cannot possibly imply it is available under both the v2 and v3. The different GPL versions have conflicting terms. You cannot possibly use the terms of the v2 and v3 simultaneously. It is legally impossible. What is means is that you can use the software under the terms of the v2 *or* the v3. And, as I mentioned, since Apache is only compatible with v3, as long as using the software under the v2 is an option, you cannot combine code that is under Apache. -- Tyler Romeo 0x405D34A7C86B42DF On February 9, 2015 at 04:06:54, David Gerard (dger...@gmail.com) wrote: On 9 February 2015 at 08:28, Max Semenik maxsem.w...@gmail.com wrote: OpenOffice's woes are unrelated to its license, it was already dead by forking when Oracle transferred it to Apache, facilitating a change from GPL+proprietary CLA to the Apache license. Indeed, but they touted the mythical attractiveness of a permissive license over the bondage of copyleft. And it didn't work that way at all in practice. Again: data, rather than anecdote or surmise? As far as I can tell, the claim that permissive attracts more contributions than copyleft is entirely a myth. - d. ___ 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
Re: [Wikitech-l] Use of hreflang in the head
On Feb 9, 2015 7:07 AM, Daniel Friesen dan...@nadir-seen-fire.com wrote: On 2015-02-09 2:16 AM, Erik Moeller wrote: This of course would add some additional payload to pages with lots of language links, but could help avoid results like [2] where the English language version of an article is #1 and the Indonesian one makes no appearance at all. Results vary greatly and it's hard to say how big a problem this is, but even if boosts discoverability of content in the user's language by only 10% or so, that would still be a pretty big win for local content. I think we used to have links in the head (though the exact implementation may have been wrong), if it wasn't a problem then it wouldn't be one now. I think we still do for lang converter. --bawolff ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [Engineering] Announcement: Tyler Cipriani joins Wikimedia as Release Engineer
Welcome Tyler! Great to have you on board. On Mon, Feb 9, 2015 at 5:35 PM, Emily Blanchard eblanch...@wikimedia.org wrote: Welcome Tyler! Emily Blanchard Talent Acquisition Team Wikimedia Foundation eblanchard@wikimedia. eblanch...@gmail.comorg Follow us on Twitter @wikimediaatwork http://wikimediafoundation.org/wiki/Home Become a Contributor: https://en.wikipedia.org/wiki/Wikipedia:Teahouse Join Us: http://wikimediafoundation.org/wiki/Work_with_us Developers Join the Fun: http://www.mediawiki.org/wiki/Communication *Imagine a world in which every single human being can freely share inthe sum of all knowledge. Help us make it a reality!* On Mon, Feb 9, 2015 at 1:39 PM, Dan Duvall dduv...@wikimedia.org wrote: Welcome, Tyler! I'm looking forward to working together. On Mon, Feb 9, 2015 at 1:28 PM, Greg Grossmeier g...@wikimedia.org wrote: Hello all, I’m delighted to announce that Tyler Cipriani[0] is joining the foundation as a Release Engineer (obviously joining the Release Engineering team). Tyler lives (and will continue to work remotely from) where you can see the Flatirons[1] in Colorado and comes to us from SparkFun[2] where he was a web developer and sysadmin. Along with the Wikimedia Foundation being a great fit professionally for Tyler (I’m biased maybe) he is also “thrilled to be working at an organization whose values seemingly so closely align with [his] own.” He’ll be at the San Francisco office the week of the 16th and is seeking any suggestions as to what he should do with his free afternoon on Presidents’ Day. Please join me in welcoming Tyler! Greg [0] https://tylercipriani.com/ [1] https://en.wikipedia.org/wiki/Flatirons [2] https://www.sparkfun.com/ -- | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E | | identi.ca: @gregA18D 1138 8E47 FAC8 1C7D | ___ Engineering mailing list engineer...@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/engineering -- Dan Duvall Automation Engineer Wikimedia Foundation http://wikimediafoundation.org ___ Engineering mailing list engineer...@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/engineering ___ Engineering mailing list engineer...@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/engineering ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Preparing Google Summer of Code 2015 and Outreachy
Today Google Summer of Code 2015 and Outreachy (was FOSS Outreach Program for Women, now open to other groups) have announced their call for organizations. Wikimedia will apply to both programs. The deadlines are February 20 and 17, respectively. THIS IS 7-10 DAYS FROM NOW! We need to update the ideas page, but this time we will do it differently: all project ideas need to be presented as a Phabricator task only (no excerpt in wiki page page is needed). We will use a workboard to track the readiness of project ideas. If you are interested in participating as intern or mentor, follow https://phabricator.wikimedia.org/T921 If you are interested in proposing a project idea, associate your task to https://phabricator.wikimedia.org/tag/possible-tech-projects/ (work-in-progress drafts and other proposals subject to discussion are welcome too) I'm looking for a co-organizer to drive this round. We have a process that works, a motivated pool of mentors, and room for creativity and improvement. Between two people, the job is actually simple, and the rewards are literally priceless (including the possibility to attend the Mentors Summit). Nemo was a great co-organizer of Google Code-in, setting a precedent that we want to consolidate. If you are interested, contact me. -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [Engineering] Announcement: Tyler Cipriani joins Wikimedia as Release Engineer
On Mon, Feb 9, 2015 at 10:28 PM, Greg Grossmeier g...@wikimedia.org wrote: he is also “thrilled to be working at an organization whose values seemingly so closely align with [his] own.” ... and looking at his personal website he seems to enjoy writing prose! Tyler, welcome, and don't forget to claim your time to write excellent release documentation. :) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [Engineering] Announcement: Tyler Cipriani joins Wikimedia as Release Engineer
Welcome Tyler, great to have you aboard and I'm always happy to welcome folks in the Mountain Timezone :) On Mon, Feb 9, 2015 at 4:24 PM, Kristen Lans kl...@wikimedia.org wrote: Welcome Tyler! Great to have you on board. On Mon, Feb 9, 2015 at 5:35 PM, Emily Blanchard eblanch...@wikimedia.org wrote: Welcome Tyler! Emily Blanchard Talent Acquisition Team Wikimedia Foundation eblanchard@wikimedia. eblanch...@gmail.comorg Follow us on Twitter @wikimediaatwork http://wikimediafoundation.org/wiki/Home Become a Contributor: https://en.wikipedia.org/wiki/Wikipedia:Teahouse Join Us: http://wikimediafoundation.org/wiki/Work_with_us Developers Join the Fun: http://www.mediawiki.org/wiki/Communication *Imagine a world in which every single human being can freely share inthe sum of all knowledge. Help us make it a reality!* On Mon, Feb 9, 2015 at 1:39 PM, Dan Duvall dduv...@wikimedia.org wrote: Welcome, Tyler! I'm looking forward to working together. On Mon, Feb 9, 2015 at 1:28 PM, Greg Grossmeier g...@wikimedia.org wrote: Hello all, I’m delighted to announce that Tyler Cipriani[0] is joining the foundation as a Release Engineer (obviously joining the Release Engineering team). Tyler lives (and will continue to work remotely from) where you can see the Flatirons[1] in Colorado and comes to us from SparkFun[2] where he was a web developer and sysadmin. Along with the Wikimedia Foundation being a great fit professionally for Tyler (I’m biased maybe) he is also “thrilled to be working at an organization whose values seemingly so closely align with [his] own.” He’ll be at the San Francisco office the week of the 16th and is seeking any suggestions as to what he should do with his free afternoon on Presidents’ Day. Please join me in welcoming Tyler! Greg [0] https://tylercipriani.com/ [1] https://en.wikipedia.org/wiki/Flatirons [2] https://www.sparkfun.com/ -- | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E | | identi.ca: @gregA18D 1138 8E47 FAC8 1C7D | ___ Engineering mailing list engineer...@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/engineering -- Dan Duvall Automation Engineer Wikimedia Foundation http://wikimediafoundation.org ___ Engineering mailing list engineer...@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/engineering ___ Engineering mailing list engineer...@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/engineering ___ Engineering mailing list engineer...@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/engineering -- Arthur Richards Team Practices Manager [[User:Awjrichards]] IRC: awjr +1-415-839-6885 x6687 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Fix problem with CollapsibleVector
Bump On Monday, 9 February 2015, 19:34, Thomas Mulhall thomasmulhall...@yahoo.com wrote: Hi could I have some help to fix a problem that a user reported on the extension talk page. The talk page is at http://www.mediawiki.org/wiki/Extension_talk:CollapsibleVector and the title is flickering. I am not sure how to fix the problem I was wandering if someone on here knew how to fix the problem. the source code is at https://git.wikimedia.org/summary/mediawiki%2Fextensions%2FCollapsibleVector ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
