User:Peter Meyer: Difference between revisions
Jump to navigation
Jump to search
Peter Meyer (talk | contribs) (create user page) |
Peter Meyer (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{{User}} | {{User | ||
|preferred-name=Peter | |||
|mw-username=econterms | |||
|smw-username=pbmeyer | |||
}} | |||
=== MediaWiki in governments === | |||
I am a good contact for MediaWiki users in government establishments. I work in the U.S. government and have been a longtime advocate of MediaWiki there. Can email me from here or post to my discussion page here or maybe more effectively on en.wikipedia.org. | |||
=== Role for Stakeholders in engineering coordination or planning === | |||
I asked: when has MW engineering done something difficult because stakeholders didn't speak up? I got several answers, mostly in a lunchtime conversation at SMWCon 2015: | |||
* hit counters disappeared, summer 2015 | |||
* The new functionality in Flow used something called "handlebars" which was different from other internal architecture and experienced developers were dragged along into learning it | |||
* The new functionality Node.js ("micro services?") wandered in as part of Visual Editor and this makes it hard to get Visual Editor going on servers outside the Foundation. | |||
* PHP Composer wandered in and broke things for some wiki farms, badly, requiring a lot of reengineering | |||
Two ways to avoid such dramas: | |||
* have a road map so people know what's coming and can negotiate, discuss, plan | |||
* confer with Stakeholders when turning technical corners | |||
Revision as of 10:44, 29 October 2015
|
MediaWiki.org User Page:
Semantic-MediaWiki.org User Page:
Open Actions
No actions
MediaWiki in governments
I am a good contact for MediaWiki users in government establishments. I work in the U.S. government and have been a longtime advocate of MediaWiki there. Can email me from here or post to my discussion page here or maybe more effectively on en.wikipedia.org.
Role for Stakeholders in engineering coordination or planning
I asked: when has MW engineering done something difficult because stakeholders didn't speak up? I got several answers, mostly in a lunchtime conversation at SMWCon 2015:
- hit counters disappeared, summer 2015
- The new functionality in Flow used something called "handlebars" which was different from other internal architecture and experienced developers were dragged along into learning it
- The new functionality Node.js ("micro services?") wandered in as part of Visual Editor and this makes it hard to get Visual Editor going on servers outside the Foundation.
- PHP Composer wandered in and broke things for some wiki farms, badly, requiring a lot of reengineering
Two ways to avoid such dramas:
- have a road map so people know what's coming and can negotiate, discuss, plan
- confer with Stakeholders when turning technical corners