<div dir="ltr"><div><div><div><div>Thanks for the context!<br><br></div><div>S: Yes, my first sentence was meant to be TPG-specific. I lost that in editing right before I hit "send". <br></div><div><br></div>Restricted access on mwfoundation is a pretty good argument for not going there. <br><br>Having "one" place to go sounds good in theory, but at least as a foundation employee I find myself bouncing between several wikis, so I don't feel like we have achieved that. <br><br></div>It does seem like if the foundation is focused on the software, then having all the teams on mediawiki would be reasonable. But since we do so much non-software community work, and so much non-software technical work, meta sounds appealing. Shifting from mw.o to meta would actually be moving toward community, as opposed to splitting away from it. However, I have spent almost no time on meta, so that's purely a snap response. <br><br></div>Currently, the Search & Discovery department is working on 3 projects: Cirrus/text search, maps, and Wikidata Query Service. Of those, I think only one is actually "mediawiki" work, which is part of what inspired my question. The other part is that the TPG is starting to work with non-Engineering teams within the foundation, and thus is working more and more on non-mediawiki stuff. I suppose it depends on how broadly you define "MediaWiki". <br><br></div>I was putting myself in the shoes of a non-foundation mediawiki developer. Certainly I would care about Cirrus Search, but would I care about maps? Would I care about the TPG? And, in fact, we have had pushback when naming our new department pages in mediawiki. Both Editing[1] and Search & Discovery[2] have been criticized in their Discussion pages. Reading[3] doesn't have complaints yet, but is newer. That was what triggered my thought that foundation/Editing makes a lot of sense, where mediawiki/Editing might not. <br><br>[1] <a href="https://www.mediawiki.org/wiki/Editing">https://www.mediawiki.org/wiki/Editing</a><br>[2] <a href="https://www.mediawiki.org/wiki/Search_and_Discovery">https://www.mediawiki.org/wiki/Search_and_Discovery</a><br>[3] <a href="https://www.mediawiki.org/wiki/Reading">https://www.mediawiki.org/wiki/Reading</a><br><div><div><div><br></div></div></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><span><font color="#888888"><br>Kevin Smith<br>Agile Coach<br>Wikimedia Foundation<br><br></font></span><br><font><font><i><font color="#888888">Imagine a world in which every single human being can freely share in the sum of all knowledge. That's our commitment. Help us make it a reality.<br></font></i></font></font></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Fri, May 22, 2015 at 7:36 AM, Greg Grossmeier <span dir="ltr"><<a href="mailto:greg@wikimedia.org" target="_blank">greg@wikimedia.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><quote name="Kevin Smith" date="2015-05-21" time="15:14:25 -0700"><br>
<span class="">> Naively, it seems like our home page should be on <a href="http://wikimediafoundation.org" target="_blank">wikimediafoundation.org</a><br>
> rather than <a href="http://mediawiki.org" target="_blank">mediawiki.org</a>.<br>
<br>
</span>The org-specific pages are on wikimediafoundation (staff pages, job<br>
postings etc).<br>
<span class=""><br>
> For engineering departments, it is less clear, but since the entire<br>
> "department" structure is an artifact of the WMF, and not of the mediawiki<br>
> software, my gut reaction would be the same.<br>
<br>
</span>Remember which came first. It wasn't the Foundation. ;)<br>
<span class=""><br>
> Technical pages (such as CirrusSearch) make sense to be on <a href="http://mediawiki.org" target="_blank">mediawiki.org</a>.<br>
><br>
> Are there historical or cultural reasons to keep the team pages on<br>
> <a href="http://mediawiki.org" target="_blank">mediawiki.org</a>?<br>
<br>
</span>For me, mostly due to keeping things in one[0] place. It's easier<br>
mentally to keep team pages and project pages (where project pages are<br>
more sensibly on <a href="http://mw.org" target="_blank">mw.org</a>) together since our teams are heavily<br>
technical/based on MediaWiki development.<br>
<br>
Also, it is cultural because if we put a lot of stuff on the foundation<br>
wiki then we explicitly divide ourselves and our projects from the rest<br>
of the community. This is not a long term positive step to take :)<br>
<br>
Greg<br>
<br>
[0] Yes, we also have some technical documentation on wikitech wiki, but<br>
that is mostly due to 2 reasons. 1) a controlled wiki for the management<br>
of WMF Labs users and 2) a separate wiki (hosted on different hardware)<br>
that will not inherently go down if the rest of the wikis go down.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |<br>
| <a href="http://identi.ca" target="_blank">identi.ca</a>: @greg A18D 1138 8E47 FAC8 1C7D |<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
teampractices mailing list<br>
<a href="mailto:teampractices@lists.wikimedia.org">teampractices@lists.wikimedia.org</a><br>
<a href="https://lists.wikimedia.org/mailman/listinfo/teampractices" target="_blank">https://lists.wikimedia.org/mailman/listinfo/teampractices</a><br>
</div></div></blockquote></div><br></div>