[Wikitech-l] Feedback needed on intro, "Principles", "Expected behavior" and "Unacceptable behavior" sections of COde of Conduct

[Matthew Flaschen]

Consensus was reached in the first discussion regarding the intro, 
"Principles", and "Unacceptable behavior" sections.  See 
https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft#Consensus_discussion_on_intro.2C_.22Principles.22.2C_and_.22Unacceptable_behavior.22_sections 
.


However, while that was being discussed, several of us made changes to 
these sections.  In the future, we need to avoid this (to avoid endless 
discussion).


Thus, in the future I'll send out two separate announcements, one for 
"last call to work on these sections" and one for "consensus discussion 
for these sections".


However, this time, that wasn't done.  So I want to give people a chance 
to weigh in on whether we should accept the changes that were made 
during the first discussion.


Thus, there is a new discussion at 
https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft#Follow-up_consensus_discussion_on_intro.2C_.22Principles.22.2C_.22Expected_behavior.22_and_.22Unacceptable_behavior.22_sections 
.


This will only last a week.  I expect to close it October 6th.

Thanks,

Matt Flaschen

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] RfC reviews meetings(!) this week:

[Rob Lanphier]

Hi everyone,

We have our usually scheduled RfC review meeting on IRC coming up
tomorrow.  At this meeting, we plan to discuss the following RfCs:
* T112553: Integrate the Virtual Rest Service (VRS) into core
* T90914: Provide semantic wiki-configurable styles for media display

We anticipate the first one will be relatively short, then we may run
out of time before feeling "done" with the second one.

Phab event link #1: https://phabricator.wikimedia.org/E68

We're also hoping to pull together an extra discussion later in the
day to discuss "T30085: Allow user login with email address in
addition to username".  That depends on devunt's availability, though,
so that may be postponed.

Phab event link #2: https://phabricator.wikimedia.org/E74

Hope to see y'all there!

Rob

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Port mw-vagrant to Raspberry Pi ( arm )

[Daniel Friesen]

On 2015-09-29 4:55 PM, Brian Wolff wrote:
> On 9/29/15, Tony Thomas <01tonytho...@gmail.com> wrote:
>
> If you're looking to reduce resource usage, and its generally expected
> that there's not very much concurrent access to the wiki, you might
> want to consider using sqlite instead of mysql.
In fact php has a built-in minimal development server.

And some time ago I wrote a series of scripts into maintenance/dev/

Running `maintenance/dev/install.sh` will install MediaWiki using
`install.php` with a sqlite database and then startup a php based webserver.
I don't even have a LAMP stack on my laptop. mediawiki/dev/ is what I
used to test nearly all my contributions to MediaWiki since I wrote it.



~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

[Wikitech-l] REL1_26 Branched

[Chad]

Good afternoon,

Today I went ahead and branched REL1_26 for MediaWiki, all extensions
and skins, and the vendor repository. They were not branched from master,
but rather about a week ago.

The starting point for the core branch was 0652366. It had a timestamp
of Tue 22 Sep 2015 18:24:35 UTC. All extensions and skins were branched
as of this timestamp. Vendor was branched at the same point as well.

Primary development of 1.26 has come to a close, master is now on 1.27
alpha cycle now. It's time to wrap up anything that needs to land in the
release branch, backport as necessary, and try to tidy up the loose ends
before we release. A reminder that our release date is currently scheduled
for the 25th of November. So test your extensions. Fix a blocker[0].
Installer always needs a good workout before we release too.

If you need help backporting things, have a question about whether a
particular change can/should be backported, or anything with this process
please ask.

-Chad

[0] https://phabricator.wikimedia.org/maniphest/query/jcSXdUecbcLp/#R
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Port mw-vagrant to Raspberry Pi ( arm )

[Brian Wolff]

On 9/29/15, Tony Thomas <01tonytho...@gmail.com> wrote:
> Hello,
>
> I was looking at some statistics of school students ( < 17 years )
>  participation from my state in Open Source program like Google Code In,
> and it is ~0. The Government here has initiated a project to distribute
> Raspberry Pi for school students[1], and it would be great to have them
> setup a Mediawiki development environment with the Pi so that they can
> contribute.
>
> The Pi's have 1 Gig ram, and I got a docker container of Ubuntu ( arm )
> running smooth. There are few blockers to install MW-Vagrant or the LXC
> container, which are:
>
>1.  The puppet config for mw-vagrant needs a 64-bit Ubuntu 14.04
>container to run inside
>2.  mv-vagrant has a lot of bells and whistles that make it
>really want a lot of ram and CPU
>3.  hhvm is too ram hungry
>
> and lot more. The other option will be to setup a LAMP stack, which would
> need to be automated ( need scripts ). I wanted to know if this porting
> would be feasible, and worth the development hours, and specifically - if
> someone is interested.
>
> [1]
> http://gadgets.ndtv.com/others/news/kerala-launches-learn-to-code-pilot-will-distribute-raspberry-pi-kits-662412
>
> Thanks,
> Tony Thomas 
> ThinkFOSS 
>
> *"where there is a wifi, there is a way"*
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l

If you're looking to reduce resource usage, and its generally expected
that there's not very much concurrent access to the wiki, you might
want to consider using sqlite instead of mysql.

--
-bawolff

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Port mw-vagrant to Raspberry Pi ( arm )

[Legoktm]

Hi,

On 09/29/2015 10:04 AM, Tony Thomas wrote:
> and lot more. The other option will be to setup a LAMP stack, which would
> need to be automated ( need scripts ). I wanted to know if this porting
> would be feasible, and worth the development hours, and specifically - if
> someone is interested.

MediaWiki-schroot[1] is a lightweight alternative to MediaWiki-Vagrant,
which sets up a LAMH (HHVM, not PHP) stack.

[1] https://www.mediawiki.org/wiki/MediaWiki-schroot

-- Legoktm

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Port mw-vagrant to Raspberry Pi ( arm )

[Jamison Lofthouse]

>
> (Last time I looked the docker catalog had dozens of MediaWiki containers,
> I don't know how people choose one).

Hopefully that will be resolved soon.
Negative24

On Tue, Sep 29, 2015 at 11:39 AM, S Page  wrote:

> Congratulations on the container, mention it on mw.org somewhere. It seems
> with that you've got half the battle won. MediaWiki-vagrant's roles let you
> easily add features to a development wiki, but maybe instead of trying to
> get all MediaWiki-vagrant's vagrant and puppet machinery running in your
> image, you could publish different containers and your recipe for making
> more of them. I imagine some of the roles like browsertests would bring an
> RPi to its knees, so you would have to blacklist some of them.
>
> The most useful day-to-day MW-vagrant feature IMO is `git-update`, it would
> be good to offer that as standalone script.
>
> (Last time I looked the docker catalog had dozens of MediaWiki containers,
> I don't know how people choose one).
> On Sep 29, 2015 10:05, "Tony Thomas" <01tonytho...@gmail.com> wrote:
>
> > Hello,
> >
> > I was looking at some statistics of school students ( < 17 years )
> >  participation from my state in Open Source program like Google Code In,
> > and it is ~0. The Government here has initiated a project to distribute
> > Raspberry Pi for school students[1], and it would be great to have them
> > setup a Mediawiki development environment with the Pi so that they can
> > contribute.
> >
> > The Pi's have 1 Gig ram, and I got a docker container of Ubuntu ( arm )
> > running smooth. There are few blockers to install MW-Vagrant or the LXC
> > container, which are:
> >
> >1.  The puppet config for mw-vagrant needs a 64-bit Ubuntu
> 14.04
> >container to run inside
> >2.  mv-vagrant has a lot of bells and whistles that make it
> >really want a lot of ram and CPU
> >3.  hhvm is too ram hungry
> >
> > and lot more. The other option will be to setup a LAMP stack, which would
> > need to be automated ( need scripts ). I wanted to know if this porting
> > would be feasible, and worth the development hours, and specifically - if
> > someone is interested.
> >
> > [1]
> >
> >
> http://gadgets.ndtv.com/others/news/kerala-launches-learn-to-code-pilot-will-distribute-raspberry-pi-kits-662412
> >
> > Thanks,
> > Tony Thomas 
> > ThinkFOSS 
> >
> > *"where there is a wifi, there is a way"*
> > ___
> > 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] Port mw-vagrant to Raspberry Pi ( arm )

[S Page]

Congratulations on the container, mention it on mw.org somewhere. It seems
with that you've got half the battle won. MediaWiki-vagrant's roles let you
easily add features to a development wiki, but maybe instead of trying to
get all MediaWiki-vagrant's vagrant and puppet machinery running in your
image, you could publish different containers and your recipe for making
more of them. I imagine some of the roles like browsertests would bring an
RPi to its knees, so you would have to blacklist some of them.

The most useful day-to-day MW-vagrant feature IMO is `git-update`, it would
be good to offer that as standalone script.

(Last time I looked the docker catalog had dozens of MediaWiki containers,
I don't know how people choose one).
On Sep 29, 2015 10:05, "Tony Thomas" <01tonytho...@gmail.com> wrote:

> Hello,
>
> I was looking at some statistics of school students ( < 17 years )
>  participation from my state in Open Source program like Google Code In,
> and it is ~0. The Government here has initiated a project to distribute
> Raspberry Pi for school students[1], and it would be great to have them
> setup a Mediawiki development environment with the Pi so that they can
> contribute.
>
> The Pi's have 1 Gig ram, and I got a docker container of Ubuntu ( arm )
> running smooth. There are few blockers to install MW-Vagrant or the LXC
> container, which are:
>
>1.  The puppet config for mw-vagrant needs a 64-bit Ubuntu 14.04
>container to run inside
>2.  mv-vagrant has a lot of bells and whistles that make it
>really want a lot of ram and CPU
>3.  hhvm is too ram hungry
>
> and lot more. The other option will be to setup a LAMP stack, which would
> need to be automated ( need scripts ). I wanted to know if this porting
> would be feasible, and worth the development hours, and specifically - if
> someone is interested.
>
> [1]
>
> http://gadgets.ndtv.com/others/news/kerala-launches-learn-to-code-pilot-will-distribute-raspberry-pi-kits-662412
>
> Thanks,
> Tony Thomas 
> ThinkFOSS 
>
> *"where there is a wifi, there is a way"*
> ___
> 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] Port mw-vagrant to Raspberry Pi ( arm )

[Tony Thomas]

Hello,

I was looking at some statistics of school students ( < 17 years )
 participation from my state in Open Source program like Google Code In,
and it is ~0. The Government here has initiated a project to distribute
Raspberry Pi for school students[1], and it would be great to have them
setup a Mediawiki development environment with the Pi so that they can
contribute.

The Pi's have 1 Gig ram, and I got a docker container of Ubuntu ( arm )
running smooth. There are few blockers to install MW-Vagrant or the LXC
container, which are:

   1.  The puppet config for mw-vagrant needs a 64-bit Ubuntu 14.04
   container to run inside
   2.  mv-vagrant has a lot of bells and whistles that make it
   really want a lot of ram and CPU
   3.  hhvm is too ram hungry

and lot more. The other option will be to setup a LAMP stack, which would
need to be automated ( need scripts ). I wanted to know if this porting
would be feasible, and worth the development hours, and specifically - if
someone is interested.

[1]
http://gadgets.ndtv.com/others/news/kerala-launches-learn-to-code-pilot-will-distribute-raspberry-pi-kits-662412

Thanks,
Tony Thomas 
ThinkFOSS 

*"where there is a wifi, there is a way"*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Would anyone be interested in a tech talk about how to make a mw skin?

[C. Scott Ananian]

On Mon, Sep 28, 2015 at 5:54 PM, C. Scott Ananian
 wrote:
> I'd be interested in this.  Again, partly from the perspective of "I
> like to understand my enemies so I can better destroy them" ;) but I
> would really like to understand better the relationship between skin
> and content in MW.

For a little more detail, see
https://phabricator.wikimedia.org/T106099#1684735 -- I'm interested in
exploring what it would mean to implement a skin in client-side
JavaScript, but I need to understand better how skins works first.
 --scott

-- 
(http://cscott.net)

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] #Possible-Tech-Projects vs WMF Engineering goals (was Mentors and projects needed for Outreachy round 11)

[Quim Gil]

Hi, I'm renaming this spin-off because it has little to do with our real
and urgent quest to find mentors for Outreachy.  :)



> > On 9/28/15, Pine W  wrote:
> > > Hi Quim,
> > >
> > > For projects that don't move forward in Outreachy for any reason, is
> > there
> > > a way of suggesting that the particularly useful open projects get WMF
> > dev
> > > time next quarter? It would be nice if there is a way to incorporate
> > > community priorities into quarterly department goal setting.
>

#Possible-Tech-Projects are in fact bad candidates for WMF goals, almost by
design:

* The WMF's efficiency increases when we focus our resources in
urgent/important tasks that volunteers cannot or prefer not to handle
themselves.

* Interns and mentors participating in outreach programs must be allowed to
learn, have fun, and eventually fail, and for that reason we avoid pushing
urgent/important tasks as #Possible-Tech-Projects for volunteers.

There might be a situation where a #Possible-Tech-Project that didn't get
any intern on Q1 is taken as a last team goal or as an individual goal at
the WMF in a future quarter. But this would be an exception, not the norm.


On Mon, Sep 28, 2015 at 9:09 PM, Pine W  wrote:

> I was told by a WMF non-management employee that they have little
> discretion about which projects they're working on, and that the decisions
> about priorities come top-down.


Sometimes priorities come top-down, where "top" actually means different
teams agreeing on common goals, or guidance coming from the annual plans,
the strategy, the board, some kind of consultation, and whatever other
inputs that make sense. Most of the goals in most of the quarters should be
cooked by the own team members based on the priorities agreed by the team
and with their natural neighbors. If a team feels systematically
disempowered by top-down decisions about their own goals, then that is a
problem that needs solving, but not a situation that should be considered
as the norm.


> Hence my interest in engaging with the
> quarterly planning processes and the people managing those processes to see
> if there's a way to get community input into the teams' quarterly goals.
>

As others have said, a good and direct way to propose tasks as quarterly
goals is to go to those tasks and push for them. Find good arguments, align
with other stakeholders, explain why this proposal fits with other ongoing
plans and work... This is exactly what we do when proposing our own goals.

-- 
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] Would anyone be interested in a tech talk about how to make a mw skin?

[Purodha Blissenbach]

I would like to see a wiki page or to watch a video that I could use
as a guide to make a new skin - a task that I am postponing since long
as "too complex for now".

Purodha

On 28.09.2015 23:00, Isarra Yos wrote:

Jack Phoenix and I were considering doing a tech talk about how to
make a MediaWiki skin. Would there be any interest in this? What 
would

you folks want to see from such a talk?

-I

___
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] Mentors and projects needed for Outreachy round 11

[Andre Klapper]

On Mon, 2015-09-28 at 12:09 -0700, Pine W wrote:
> Hi Brian,
> I was told by a WMF non-management employee that they have little
> discretion about which projects they're working on, and that the decisions
> about priorities come top-down. Hence my interest in engaging with the
> quarterly planning processes and the people managing those processes to see
> if there's a way to get community input into the teams' quarterly goals.

WMF is made up of several teams. For a list, click "Organizational
overview" on https://wikimediafoundation.org/wiki/Staff?showall=1
Some members of some teams might either be or have the feeling of being
more influenced by potential top-down priorities. Others less.

About engaging with the planning processes and people:

For Engineering, the main goals and contacts for Oct-Dec are here:
https://www.mediawiki.org/wiki/Wikimedia_Engineering/2015-16_Q2_Goals

That page links to each team's homepages (they are also linked from
https://www.mediawiki.org/wiki/Wikimedia_Engineering ) which should
cover the planning processes, communication/contact info, etc.

Hope that helps a bit?

Cheers,
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