Submitted via IRC for Bytram
Google unplugs AMP, hooks it into OpenJS Foundation after critics turn up the volume
AMP – which originally stood for Accelerated Mobile Pages though not any more – was launched in 2015, ostensibly to speed up page loading on smartphones. The technology includes AMP HTML, which is a set of performance-optimized web components, and the AMP Cache, which serves validated AMP pages. Most AMP pages are served by Google's AMP Cache.
AMP looks somewhat like a Google land grab and has been controversial. While better performance is welcome, having to support AMP HTML is also a burden on publishers and a constraint on web design, especially since Google's guidelines state that "users must be able to experience the same content and complete the same actions on AMP pages as on the corresponding canonical pages, where possible." Supporting AMP is optional, though if Google search prioritizes AMP pages, publishers have little choice.
In September 2018, the AMP project announced an "open governance model" where decisions are made by a steering committee and a "wider variety of voices" have a say in the project's direction. The announcement included "exploring moving AMP to a foundation."
That move will now take place. Google principal engineer Malte Ubl, a co-founder of the AMP project, announced last week that "AMP is joining the OpenJS Foundation incubation program." This means that the project will join the foundation once a number of onboarding tasks have been completed. Ubl adds that Google will continue to finance the project, via the foundation, and that "the team of Google employees contributing full time to the AMP open source project will also continue to do so."
In the FAQ here the move is stated to be a response to "communities concerns around [the project's] ties to Google as well as concerns around scaling the project."
(Score: 0) by Anonymous Coward on Thursday October 24 2019, @02:05AM (1 child)
1. Develop CoC
2. Hire some pinkhaired trangenders
3. Redesign CoC to be more inclusive
4. Rewrite code in Ruby on Rails
OK... good to go now.
(Score: 2) by DeathMonkey on Thursday October 24 2019, @04:52PM
Yes, written instructions governing conduct are terrible!
SoylentNews would never write a CoC about moderation [soylentnews.org] or submissions [soylentnews.org] because that would make them SJWs!