Dear all,
I’m writing to give a heads-up that I expect to be taking medical leave
from today through March 9, due in part to stress caused by the recent
uncertainty and organizational departures. In my absence, my work will be
in the capable hands of Ryan Kaldari and the rest of the Community
Sarah Sharp has an excellent and relevant post on what makes for an active
and welcoming open source community:
http://sarah.thesharps.us/2015/10/06/what-makes-a-good-community/
I would like the Wikimedia technical community to get to Level 0, and this
policy is one tool we can use to get there.
On Mon, Sep 28, 2015 at 12:02 PM, Brian Wolff wrote:
> That said, gsoc/opw usually doesn't reflect Wikimedia community
> priorities all that much (imo).
>
Do you have any thoughts on why that might be? As I'm on the Community Tech
team, I'd love to mentor someone working on a
An excellent article on best practices and pitfalls for in-person technical
events: https://modelviewculture.com/pieces/software-in-person
This has some ideas and framings that can be useful for planning for the
upcoming developer summit.
-Frances
___
On Mon, Aug 24, 2015 at 9:01 AM, Brion Vibber bvib...@wikimedia.org wrote:
But I strongly recommend we seek out people who have experience with
organizing this sort of thing before we try cobbling together an
enforcement committee on our own, just as we seek out people with domain
expertise
Thanks for sharing this, Risker. If I were a casual contributor, I'm not
sure that I would attend either--not because I'd expect that Wikimedia
conferences/hackathons would necessarily be worse than other tech
conferences, but because I'd have no reason to expect them to be better.
Same with our
On Mon, Aug 17, 2015 at 5:22 PM, Alex Monk kren...@gmail.com wrote:
It looks like Communicate about technology in public where possible.
Private means of communication do exist, but prefer to use public places
unless an exception is appropriate. has been removed and Publication of
I was also at the Wikimania session where we worked on this draft. I
strongly support this effort. Best practices for codes of conduct include
clearly defined consequences for breaches, as well as named behaviors that
are unacceptable (as not everyone shares the same common sense, and
people
, Aug 7, 2015 at 9:57 AM, Frances Hocutt fhoc...@wikimedia.org
wrote:
I was also at the Wikimania session where we worked on this draft. I
strongly support this effort. Best practices for codes of conduct include
clearly defined consequences for breaches, as well as named behaviors
Thanks so much, everyone! I'm looking forward to getting started, and also
to figuring out what our team's scope and processes will look like.
-Frances
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
On Wed, Mar 18, 2015 at 11:18 AM, Ricordisamoa ricordisa...@openmailbox.org
wrote:
If you're using Pywikibot, you may want to have a look at its extensive
unit tests :)
Thanks. I'm not, but I'll take a look.
-Frances
___
Wikitech-l mailing list
I'm working on cleaning up the code[1] for GrantsBot[2] and generally
getting it into better and more robust shape. I've started writing basic
unit tests to assist in the refactoring process. Since it interacts so
heavily with the MediaWiki API, however, this isn't a straightforward
process, and
Wonderful! Those look like interesting projects. I'm looking forward
to hearing about how they go.
-Frances
Intern, OPW Round 8
On Wed, Nov 12, 2014 at 3:02 PM, Quim Gil q...@wikimedia.org wrote:
The GNOME Foundation has announced the list of interns accepted in the
FOSS Outreach Program for
Congratulations, Yuvi!
Frances
On Thu, Nov 6, 2014 at 8:55 AM, Mark Bergsma m...@wikimedia.org wrote:
Hi all,
I'm very pleased to announce that as of this week, Yuvi Panda is part of
the Wikimedia Technical Operations team, to work on our Wikimedia Labs
infrastructure. Yuvi originally
What wonderful news! Congratulations, Moriel.
Frances
On Tue, Oct 7, 2014 at 3:58 PM, James Forrester
jforres...@wikimedia.org wrote:
[Second one today!]
I am delighted to announce that Moriel Schottlender [0] has converted to
full time staff member status as a Software Engineer in Features
My (belated) final report for my OPW project is up on my progress
reports page:
https://www.mediawiki.org/wiki/Evaluating_and_Improving_MediaWiki_web_API_client_libraries/Progress_Reports#Final_report
. Thank you to everyone who has helped me learn as much and contribute
as much as I have this
I'm trying to write some basic test bots before I start writing
patches for the Java Wiki Bot Framework (JWBF). I've been able to get
one to compile, but I have persistent runtime errors.
I've put the relevant information and things I've already tried in
this gist:
On Mon, Aug 11, 2014 at 9:01 AM, Brandon Harris bhar...@wikimedia.org wrote:
Ignoring people by actually ignoring people tends to work pretty well.
This depends on your background, your history with them, and why you
are ignoring them. I'm more likely to just leave a discussion than to
://www.mediawiki.org/wiki/Evaluating_MediaWiki_web_API_client_libraries
On Tue, Mar 18, 2014 at 3:03 AM, Frances Hocutt
frances.hoc...@gmail.com wrote:
I have updated and expanded the scope of my OPW project [1],
Evaluating and Improving MediaWiki Web API Client Libraries. Thanks to
Sumana, Tollef, and Brad
, Frances Hocutt
frances.hoc...@gmail.com wrote:
Hello!
My name is Frances Hocutt, and I'm applying for the OPW internship
program. Specifically, I'm interested in improving the documentation
around the available Mediawiki API libraries, writing specifications for what
makes a good one
Congratulations to both of you!
-Frances
On Mon, Mar 17, 2014 at 1:00 PM, Rob Lanphier ro...@wikimedia.org wrote:
Hi everyone,
I'd like to announce some changes in the Engineering Community
Team[1]. The headlines:
* Quim Gil is taking over as the new Engineering Community Manager,
Hello!
My name is Frances Hocutt, and I'm applying for the OPW internship
program. Specifically, I'm interested in improving the documentation
around the available Mediawiki API libraries, writing specifications for what
makes a good one, and generally making API:Client Code a more useful page
22 matches
Mail list logo