Off-topic and as an exercise, I wrote a simpler version of The Apache Way. Input welcome! https://gist.github.com/bureado/ee91c7ebc397348b0b5e76841fe6184c
Of course just translating "The Apache Way" is a mental exercise in itself but in doing this I tried to reduce the absolute number of words used, paid attention to how often are words used only once (and for those, how common those words might be in someone's vocabulary), simplified the titles, moved some things to "examples" as they distracted from the core concept (for translation purposes) and iterated 2x after the "final" words. The reason why that was helpful was because in reducing the words I introduced new words (such as "Openness") that are hard to translate/understand so I took another pass. I agree it's hard to expect or establish this standard in mailing lists. In fact, in writing my condensed take on The Apache Way I had a gut reaction to the "keep discussions on-list" because I've been guilty multiple times of taking a conversation off-list. This is because I can't keep track with the mailing list, but also because I trust the individual I'm having the conversation with will give me some leeway with language, or I can make my point more eloquently, or try again if I mess up. Mailing lists can be intimidating for that purpose, and that's why I like the idea of having low expectations (within acceptable conduct standards) for mailing lists, and ask probing questions that can help build communication skills for everyone. Doing in the open is a plus, but sometimes that could be negative. ________________________________________ From: Justin Mclean <jus...@classsoftware.com> Sent: Thursday, May 30, 2019 10:44 PM To: diversity@apache.org Subject: Re: Discussion of written English style Hi, It interesting to note the Apache Way page [1] is close to very difficult to read, but it better than the release policy page [2] which is only difficult :-) This for example: Responsible Oversight: The ASF governance model is based on trust and delegated oversight. Rather than detailed rules and hierarchical structures, ASF governance is principles-based, with self-governing projects providing reports directly to the Board. Apache Committers help each other by making peer-reviewed commits, employing mandatory security measures, ensuring license compliance, and protecting the Apache brand and community at-large from abuse. More on responsibility. Basically if you didn’t finish collage (or under 20) you have no chance of understanding all of that. Perhaps making those pages (and others) use simpler English could have an impact? Thanks, Justin 1. https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapache.org%2Ftheapacheway%2Findex.html&data=02%7C01%7C%7C944f90aae5824b65245808d6e58b083e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636948782626696533&sdata=2KGv8FbHjWcS5GepcKpW%2FcJebYAvLnxsl5ett5P%2F1C0%3D&reserved=0 2. https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache.org%2Flegal%2Frelease-policy.html&data=02%7C01%7C%7C944f90aae5824b65245808d6e58b083e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636948782626696533&sdata=iVPtD6MGKygQ5mFbSDsXlZsgEMqzP24pLBeF1HnkEzY%3D&reserved=0 --------------------------------------------------------------------- To unsubscribe, e-mail: diversity-unsubscr...@apache.org For additional commands, e-mail: diversity-h...@apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: diversity-unsubscr...@apache.org For additional commands, e-mail: diversity-h...@apache.org
