X-post: 5.0 Release Retrospective Kickoff

X-comment from +make.wordpress.org/updates: Comment on 5.0 Release Retrospective Kickoff

Replacing SVN with Git for wordcamp.org’s code

WordCamp.org’s code currently uses SVN as the primary tool of version control hosted on the Meta SVN repo. For the last several months we have also been experimenting with Git to see if it improves the development workflow.

Currently there is a GitHub repo which is set up as the mirror of the official SVN repo of WordCamp.org’s code. This repo is used to hold code reviews, and sync with SVN with every  new commit.

So far this setup has been a big help in making it easier to get and give reviews, therefore improving code quality. Many basic features in Git like commit, stash, branch etc have been a delight to use in place of their SVN counterparts because of Git’s decentralized nature.

At this point it’s worth discussing removing SVN altogether, from at least the local development flow. Right now the process is prone to errors, not easy to set up, and has an extra step of manually syncing Git with latest changes in SVN.

New proposed process

It seems like a good idea to change the version control system as follows:

  1. Make the Github repo the primary destination for code reviews. It will be configured on the local system of whoever wants to contribute to WordCamp.org’s code, and will be the primary place to work and develop.

  2. Keep SVN as part of the release process. That is, whenever code is deployed changes will be synced from Git to SVN and start the deploy process. This process will be manual (or at least will be triggered manually) and SVN will be used only as a release tool (i.e. aim is not to preserve commit metadata like author, commit message etc). This approach has two main benefits:

    1. No changes to deploy scripts will be necessary to use Git. These script are used while pushing code from latest SVN revision to WordCamp.org’s server. They would continue using SVN as before.

    2. No dependence on an external tool in order to deploy changes. For example, Github going down will not affect us in case we want to push an emergency fix.

Commits with their authors have already been imported from the SVN repo into the Github repo.

Share your thoughts

Do you have any technical concerns about moving from SVN to Git? Do you suggest any changes to the process?

If the development process is indeed changed, it might be a good idea to also think about importing issues from Meta Trac to Github that are reported for WordCamp.org and its components. Do you have any concerns about importing issues into Github, or should they continue to exist in Trac?

Please leave your suggestions and feedback in a comment on this post.

#wordcamp

Next WordCamp.org ticket scrub on February 21st, 2019

This ticket scrub will happen on 2019-02-21 17:00 UTC in the #meta-wordcamp channel.

The focus is on Meta tickets with the WordCamp Site & Plugins component.

Comment below if there’s a specific ticket or topic you’d like to discuss.

#agenda #ticket-scrub #wordcamp

+make.wordpress.org/community

X-post: Strengths and Challenges: Follow Up

X-comment from +make.wordpress.org/updates: Comment on Strengths and Challenges: Follow Up

X-post: Our Strengths and Challenges

X-comment from +make.wordpress.org/updates: Comment on Our Strengths and Challenges

Next WordCamp.org ticket scrub on January 17th, 2019

This ticket scrub will happen on 2019-01-17 17:00 UTC in the #meta-wordcamp channel.

The focus is on Meta tickets with the WordCamp Site & Plugins component.

Comment below if there’s a specific ticket or topic you’d like to discuss.

#agenda #ticket-scrub #wordcamp

+make.wordpress.org/community

WordCamp US Contributor Day: What Should We Work On?

It looks like we’ve got about a dozen people so far who have listed the Meta team as their preference for WCUS Contributor Day (Sunday, December 9th). How best can we spend our time together?

Here are a few ideas:

  • A scrub for tickets that have patches and need a little jumpstart
  • Work on a tough bug that has been lingering a long time, like #703
  • Improvements to the Meta Environment

Other ideas?

We’ll also have thumb drives available pre-loaded with the Meta Environment to help with onboarding new contributors.

cc @RMarks @nvwd @metalandcoffee @iandunn @julienmelissas @obenland @icaleb @drewapicture @jonoalderson @otto42 @hiddenpearls @joostdevalk

#wordcamp

WordCamp Bug Scrub – October 24th

The next WordCamp.org bug scrub will be Wednesday, October 24th at 4pm UTC in the #meta-wordcamp channel on Slack.

Come join us if you need any feedback on a patch, are looking for a ticket to contribute to, etc.

+make.wordpress.org/community

#wordcamp

Revised Gutenberg Landing Page

Hi everyone! I’m working on a refresh of the current Gutenberg landing page at wordpress.org/gutenberg. The goal is to have a new version of this up by the time the Try Gutenberg callout lands. I’d like to share with you an early draft of the design and content.

Here’s a little background on the goals and intent:

  • The current page is very text-heavy, but this new exercise turns it into more of a “product” page (along the lines of these examples). It’s meant to be a quick, simple way to get up to speed on what Gutenberg is. It’s primarily aimed at all the new visitors that’ll show up via the Try Gutenberg callout, but would contain some external links for people who want to get more in-depth. 
  • The current page discusses much of the background/process behind Gutenberg. It also spends a lot of time aiming to allay the concerns of developers. While the page still needs to do that, it primarily needs to introduce new people to Gutenberg. We can likely move any in-depth content into the handbook or elsewhere.
  • This has all been built using default Gutenberg blocks/styles.

You can check out a live draft of the revised page here:

Gutenberg Landing Page Draft 

Here are some screenshots as well:

So far, the general structure of the page is:

  1. Basic Introduction to Gutenberg (It’s my hope that the image at the very top of the page would be replaced by a video introduction to Gutenberg, but that would likely occur later on.)
  2. Introduction to Blocks
  3. Combining Blocks
  4. Developer Resources
  5. The Future of Gutenberg
  6. Additional Resources

I’d appreciate any initial impressions and feedback on this draft. Thanks!

Thanks @karmatosed for help with this, and @michelleweber for copywriting. 

Google Tag Manager Hangout

We got started using GTM on w.org in #1017-meta. To discuss our next steps there let’s get together on a Zoom hangout on July 5 2018, 15:00 UTC. Everyone with an opinion is invited! I’ll post the link in the #meta Slack channel.

#1017-meta