Next WordCamp.org ticket scrub on April 18, 2019

This ticket scrub will happen on 2019-04-18 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

Feature and maintenance update for WordCamp.org: March 18-29, 2019

Here’s a list of the WordCamp.org feature developments and maintenance work that was accomplished in the last two weeks:

  • Continued iterating on WordCamp’s shortcode-to-block conversions
    • Introduced the Organizers block
    • Updates to Speakers, Sessions, and Sponsors blocks
    • Began tracking progress in a milestone
  • Investigated and mitigated two server downtime incidents
  • Fixed a problem with retrieving data about meetup events after Meetup.com made an unannounced change to their API
  • Fixed a bug that wiped out sponsor data in some situations
  • Updated the verbiage in ticket receipts to reflect current global sponsors
  • Began the process of implementing a more reliable cron system on WordCamp.org

#wordcamp

+make.wordpress.org/community

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

This ticket scrub will happen on 2019-03-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

Feature and maintenance update for WordCamp.org: February and March 2019

Here’s a list of the WordCamp.org feature developments and maintenance work that was accomplished in February 2019:

Here’s what folks working on WordCamp.org hope to accomplish in March:

  • Complete the rest of the shortcode-to-blocks conversions (Sessions, Organizer, Sponsors, Schedule) — this will probably be the majority of the work in March
  • Continue to give feedback to the teams working on automating VAT invoices and the WordCamp.org PWA.
  • Update global sponsor acknowledgement on ticket purchase emails and landing pages.
  • As always, fix bugs as they are reported and maintain wordcamp.org

#wordcamp

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

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

Agenda for WordCamp.org ticket scrub on January 16th

This bi-weekly WordCamp.org ticket scrub will happen on 2018-01-16 19:00 UTC in #meta-wordcamp.

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

Specific tickets

Other items?

Comment below if there’s any other ticket or topic you’d like to discuss.

#agenda #ticket-scrub #wordcamp

+make.wordpress.org/community

#1097-meta, #3202-meta, #3283-meta