Thanks for that Erik - and yes, if there's a list, you do appear to be on it!
As I am currently in the middle of packing my bags to move to Europe tomorrow I will return to this topic next week when I officially start in my new role with Europeana - from sunny summery Bologna rather than rainy wintery Sydney. Ciao! -Liam wittylama.com Peace, love & metadata On 10 June 2014 15:32, Erik Moeller <[email protected]> wrote: > I'm on this list, somehow :) (generally the rule seems to be, if it's > a list, I'm on it). Definitely, let's use the mediawiki.org talk page > to discuss your expectations and what WMF can help with. > > Erik > > On Mon, Jun 9, 2014 at 10:10 PM, Liam Wyatt <[email protected]> wrote: > > This email (below) just got sen out by Erik Moeller. Do you think it is > > appropriate for us to contact him (and/or Fabrice - who is responsible > for > > the 'multimedia' section) to ask where the GWT might sit within the WMF > Tech > > plans? > > The document is specifically the WMF's own plans, not about grants, but > > there are dependencies and aspects of what we want to do with GWT (on the > > assumption that we successfully apply for a grant to fund round 2 of > > development) that interrelate to the WMFs core priorities. > > > > -Liam > > > > > > ---------- Forwarded message ---------- > > From: Erik Moeller <[email protected]> > > Date: Tuesday, 10 June 2014 > > Subject: [Wikimedia-l] First _draft_ goals for WMF engineering/product > > To: Wikimedia developers <[email protected]>, Wikimedia > Mailing > > List <[email protected]> > > > > > > Hi all, > > > > We've got the first DRAFT (sorry for shouting, but can't hurt to > > emphasize :)) of the annual goals for the engineering/product > > department up on mediawiki.org. We're now mid-point in the process, > > and will finalize through June. > > > > https://www.mediawiki.org/wiki/Wikimedia_Engineering/2014-15_Goals > > > > Note that at this point in the process, teams have flagged > > inter-dependencies, but they've not necessarily been taken into > > account across the board, i.e. team A may say "We depend on X from > > team B" and team B may not have sufficiently accounted for X in its > > goals. :P Identifying common themes, shared dependencies, and > > counteracting silo tendencies is the main focus of the coming weeks. > > We may also add whole new sections for cross-functional efforts not > > currently reflected (e.g. UX standardization). Site performance will > > likely get its own section as well. > > > > My own focus will be on fleshing out the overall narrative, aligning > > around organization-wide objectives, and helping to manage scope. > > > > As far as quantitative targets are concerned, we will aim to set them > > where we have solid baselines and some prior experience to work with > > (a good example is Wikipedia Zero, where we now have lots of data to > > build targets from). Otherwise, though, our goal should be to _obtain_ > > metrics that we want to track and build targets from. This, in itself, > > is a goal that needs to be reflected, including expectations e.g. from > > Analytics. > > > > Like last year, these goals won't be set in stone. At least on a > > quarterly basis, we'll update them to reflect what we're learning. > > Some areas (e.g. scary new features like Flow) are more likely to be > > significantly revised than others. > > > > With this in mind: Please leave any comments/questions on the talk > > page (not here). Collectively we're smarter than on our own, so we do > > appreciate honest feedback: > > > > - What are our blind spots? Obvious, really high priority things we're > > not paying sufficient attention to? > > > > - Where are we taking on too much? Which projects/goals make no sense > > to you and require a stronger rationale, if they're to be undertaken at > all? > > > > - Which projects are a Big Deal from a community perspective, or from > > an architecture perspective, and need to be carefully coordinated? > > > > These are all conversations we'll have in coming weeks, but public > > feedback is very helpful and may trigger conversations that otherwise > > wouldn't happen. > > > > Please also help to carry this conversation into the wikis in coming > > weeks. Again, this won't be the only opportunity to influence, and > > I'll be thinking more about how the quarterly review process can also > > account for community feedback. > > > > Warmly, > > > > Erik > > > > -- > > Erik Möller > > VP of Engineering and Product Development, Wikimedia Foundation > > > > _______________________________________________ > > Wikimedia-l mailing list, guidelines at: > > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines > > [email protected] > > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, > > <mailto:[email protected]?subject=unsubscribe> > > > > > > -- > > wittylama.com > > Peace, love & metadata > > > > _______________________________________________ > > Glamtools mailing list > > [email protected] > > https://lists.wikimedia.org/mailman/listinfo/glamtools > > > > > > -- > Erik Möller > VP of Engineering and Product Development, Wikimedia Foundation > > _______________________________________________ > Glamtools mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/glamtools >
_______________________________________________ Glamtools mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/glamtools
