On Tue, Jun 9, 2020 at 4:15 AM Denny Vrandečić &lt;vrandecic(a)gmail.com&gt; wrote: Thank you Denny for bringing this up! Much appreciated and important now. Though I think being explicit about #Unacceptable_behavior <https://pdxruby.org/CONDUCT#3-expected-behavior%20https://www.mediawiki.org/wiki/Code_of_Conduct%23Unacceptable_behavior> https://www.mediawiki.org/wiki/Code_of_Conduct#Unacceptable_behavior <https://pdxruby.org/CONDUCT#3-expected-behavior%20https://www.mediawiki.org/wiki/Code_of_Conduct%23Unacceptable_behavior> I find it super-important to have consensus also on #3-expected-behavior ! My preferences here are with https://BerlinCodeOfConduct.org/ <https://berlincodeofconduct.org/> that originated from https://pdxruby.org/CONDUCT#3-expected-behavior <https://pdxruby.org/CONDUCT#3-expected-behavior%20https://www.mediawiki.org/wiki/Code_of_Conduct%23Unacceptable_behavior> Personally I find most of the older projects often unsupportive and even made toxic for newbies to join due to 'legal' bot-like behavior or passive agressive of older (highly patronizing and teritorial) admins... ...as the project matures this should be monitored for and suppressed, but ideally also discouraged from the start by Expected_Behavior policy. Best Z _______________________________________________ Wikispore mailing list Wikispore(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikispore

Maybe we can bring some of the unfinished discussions like CoC to this Sunday? On Mon, Jun 15, 2020 at 5:19 AM Samuel Klein &lt;meta.sj(a)gmail.com&gt; wrote: > > +1 to the berlin COC. > > On Tue, Jun 9, 2020 at 5:14 AM Željko Blaće &lt;zblace(a)mi2.hr&gt; wrote: >> >> On Tue, Jun 9, 2020 at 4:15 AM Denny Vrandečić &lt;vrandecic(a)gmail.com&gt; wrote: >>> >>> I have checked with a few people, and here are some concerns regarding Wikispore, which, I am sure, can be easily resolved. I am happy to help with the first three if I sense consensus on these topics. >>> >>> 1) Privacy policy >>> 2) Terms of use >>> 3) Code of Conduct >> >> >> Thank you Denny for bringing this up! Much appreciated and important now. >> >>> >>> 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. >>> >>> Regarding 3), mediawiki.org has a CoC, meta does not, and I would really like us to start Spores per default with a CoC. What are your thoughts? >> >> >> Though I think being explicit about #Unacceptable_behavior >> https://www.mediawiki.org/wiki/Code_of_Conduct#Unacceptable_behavior >> I find it super-important to have consensus also on #3-expected-behavior ! >> My preferences here are with https://BerlinCodeOfConduct.org/ >> that originated from https://pdxruby.org/CONDUCT#3-expected-behavior >> >> Personally I find most of the older projects often unsupportive >> and even made toxic for newbies to join due to 'legal' bot-like behavior >> or passive agressive of older (highly patronizing and teritorial) admins... >> ...as the project matures this should be monitored for and suppressed, >> but ideally also discouraged from the start by Expected_Behavior policy. >> >> Best Z

https://www.mediawiki.org/wiki/Code_of_Conduct in my view is the lowest common denominator not enough and certainly not optimum On Thu, Jul 16, 2020 at 11:44 AM Alastair Dickson &lt;adickson(a)allyd.co.uk&gt; wrote: Sunday? wrote: wrote: regarding Wikispore, which, I am sure, can be easily resolved. I am happy to help with the first three if I sense consensus on these topics. now. respective policies from the other WMF Wikis and link them accordingly. really like us to start Spores per default with a CoC. What are your thoughts? #3-expected-behavior ! behavior admins... suppressed, policy. _______________________________________________ Wikispore mailing list Wikispore(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikispore

On Tue, Jun 9, 2020 at 4:15 AM Denny Vrandečić &lt;vrandecic(a)gmail.com wrote: 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. _______________________________________________ Wikispore mailing list Wikispore(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikispore