On Fri, Mar 6, 2015 at 4:13 PM, Jon Robson <jrob...@wikimedia.org> wrote:

> Any reason this is on mobile-tech and not mobile-l (I'd love to hear from
> people like Amir on this subject)? It would be good to flag this problem to
> a wider audience and part of our problem with most mobile issues is people
> just are not aware of this sort of thing. Many probably haven't even heard
> of the hemingway app...
>

Any reason this on mobile-tech and not on
https://en.wikipedia.org/wiki/Wikipedia_talk:Manual_of_Style/Lead_section?
Content issues are best handled by the community, IMO, not by programmers.
There was recently a discussion there on this exact topic[1] and I think
they would have appreciated input from the WMF designers. Believe it or
not, the community generally appreciates it when the WMF shares opinions
(rather than imposing solutions without discussion), especially when it
comes to content. For example, the Commons community has a good
relationship with WMF Legal and is constantly asking their opinion on legal
issues related to content. Compare this to when Jimmy went in and
unilaterally deleted porn from Commons. It caused a huge fight, which Jimmy
lost and led to him losing his founder rights.[1][2] I would prefer that
WMF Design emulate the relationship with the community that WMF Legal has
cultivated rather than the relationship that Jimmy has cultivated. Let's
actually talk to the community about content issues rather than always
trying to work around them.

Ryan Kaldari

1.
https://en.wikipedia.org/wiki/Wikipedia_talk:Manual_of_Style/Lead_section#Proposal:_remove_parenthetical_information_from_lead_.28RfC.29
2.
http://www.telegraph.co.uk/technology/wikipedia/7711486/Wikipedia-porn-row-sees-founder-give-up-his-editing-privileges.html
3.
http://venturebeat.com/2010/05/16/wikipedia-founder-gives-up-control-of-site-over-fox-news-kiddie-porn-scandal/
_______________________________________________
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Reply via email to