On Tue, Jun 9, 2020 at 4:15 AM Denny Vrandečić <vrandecic(a)gmail.com> wrote:
1) Privacy policy
2) Terms of use
The Wikimedia Cloud terms of use, which itself is meant for the wiki
operators, has some boilerplates:
https://wikitech.wikimedia.org/wiki/Wikitech:Cloud_Services_Terms_of_use#Wh…
?
Labs had a lack-of-privacy policy that never made it out of draft status:
https://www.mediawiki.org/wiki/Wikimedia_Labs/Agreement_to_disclosure_of_pe…
I imagine we'll go with something low-key like those. We don't really
collect personal information as we use SUL (note to self: delete old
pre-SUL passwords from the database), and the Wikimedia Cloud proxy removes
IP addresses from the requests. We do collect email addresses as there is
no way to send messages without that, and they are taken from Wikimedia
wikis, so I guess there should be a clear warning about that. (I filed
https://phabricator.wikimedia.org/T241039 about avoiding email collection
some time ago, it did not generate much interest.)
3) Code of Conduct
We should just go with the technical CoC (
https://www.mediawiki.org/wiki/Code_of_Conduct ) as it already exists and
has the required institutional infrastructure set up, and in practice I
don't think the contents of the CoC matter much (other than people
complaining when there isn't any). Admin culture is more important, but we
are not at the size yet where even that would really matter.
Arguably the technical CoC already applies, as it covers all
"development-oriented spaces operated by the Wikimedia Foundation", and
wmflabs.org is one of those; but we should probably link it from the footer.
I am sure we'll easily agree on the first two, just taking the respective
> policies from the other WMF Wikis and link them accordingly.
The WMF ToU and PP is huge, most of it is irrelevant, and a lot of it is
infeasible, due to the relatively lax controls on who can access Wikimedia
Cloud hosts.
> 4) Visual Editor?
Visual Editor depends on the Parsoid service. Parsoid has been ported to
PHP, and the port will be bundled with MediaWiki soon (in theory by the MW
1.35 release, which is in a month). Visual Editor should just work at that
point, so unless there is some reason for urgency, I don't really want to
go through the effort of setting it up the traditional node-service-based
way.
It's possible VE with Parsoid/PHP already works and just needs some feature
flag set (
https://phabricator.wikimedia.org/T239660 is marked as
resolved). I'll ask around.