👓 Forking is a Feature | Gary Pendergast

Read Forking is a Feature by Gary Pendergast (Gary Pendergast)
There’s a new WordPress fork called ClassicPress that’s been making some waves recently, with various members of the Twitterati swinging between decrying it as an attempt to fracture the WordPress community, to it being an unnecessary over-reaction, to it being a death knell for WordPress. Pers...

Again, here, I’m reminded of some of the benefits that the BackDrop fork of Drupal is providing not only to itself, but to the larger Drupal community. Naturally there’s a better way of doing these things, but it takes foresight and work–a lot of work.

Syndicated copies to:

👓 ClassicPress: Gutenberg Not Included | WordPress Tavern

Read ClassicPress: Gutenberg Not Included (WordPress Tavern)
Depending on how far and deep you look, there is not a lot of positive sentiment surrounding Gutenberg. For Scott Bowler, the notion of merging Gutenberg into WordPress 5.0 represents a shift so de…
Syndicated copies to:

👓 Our Mission Statement | ClassicPress

Read Our Mission Statement (ClassicPress)
1. If it isn’t broken, we won’t fix it
2. Major decisions will be made by the community
3. We will facilitate democratic discussion and decision making
4. We will make people’s lives better
5. We will invest in the future of ClassicPress
Syndicated copies to:

👓 Gary Pendergast Praises ClassicPress, Extends Invitation for Collaboration | WordPress Tavern

Read Gary Pendergast Praises ClassicPress, Extends Invitation for Collaboration (WordPress Tavern)
Gutenberg and WordPress core contributor Gary Pendergast has weighed in with this thoughts on ClassicPress, a fork of WordPress created by Scott Bowler. Pendergast praises the fork and extended an …

The potential forking of WordPress like this actually could present an interesting opportunity for the broader community and the platform. It reminds me a bit of the BackDrop fork of Drupal and how it has benefited both platforms going forward. BackDrop has about 100 solid contributors that are building and iterating much more rapidly on their platform than the bigger behemoth of Drupal. As a result, new plugins and cleaner UI have entered their core and improved more rapidly with active dogfooding while their security teams collaborate closely and pushes go back and forth between the two. In the end both platforms end up benefiting tremendously. Naturally the two need to have some collegiality and collaboration to help make sure this happens.

Syndicated copies to: