Next WordCamp.org ticket scrub on August 22nd, 2019

Oops! The ticket scrub scheduled for August 15th did not occur, so we’re trying again next week. This time the ticket scrub will happen on 2019-08-22 17:00 UTC in the #meta-wordcamp channel.

The focus is on MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. tickets with the WordCamp Site & Plugins component.

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

#wordcamp

+make.wordpress.org/community

WordCamp.org Dev Update: June 18 – July 15, 2019

Here is a list of WordCamp.org feature developments and maintenance work that has been accomplished since the last update.

### July 2 – July 15

  • Pulled data for 2018 annual WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. report.
  • Improved contributor onboarding by creating new sample database for location environment.
  • Iterated on GitGit Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. Most modern plugin and theme development is being done with this version control system. https://git-scm.com/. -> SVNSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/. sync.
  • Minor maintenance: fixing duplicate invoices, fixing caching bug, tested upstream PWA PRs for compatibility, installed pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party updates.

### June 18 – July 1

  • Rate limited penetration tests against CampTix.
  • Iterated on offline schedule and day-of-event template.
  • Drafted a plan to upgrade our Meetup.com APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. client to use oAuth and v3 endpoints ahead of their last-minute deprecation deadline.
  • Improved committer devex and onboarding process by switching the WordCamp.org repository from SVN to GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/, and setting up fully-trusted SSLSSL Secure Socket Layer - Encryption from the server to the browser and back. Prevents prying eyes from seeing what you are sending between your browser and the server. certs in Docker.
  • Minor maintenance fixes: Installed plugin updates, enabled responsive embeds, updated “Polldaddy” strings to “Crowdsignal”.

#wordcamp

+make.wordpress.org/community

Feature and maintenance update for WordCamp.org: June 2019 edition

Here is a list of WordCamp.org feature developments and maintenance work that has been accomplished since the last update.

  • Completed the first milestone for WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more.’s GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ blocks. They are now available for beta testing.
  • Mitigated an issue with “global terms” on the WordCamp.org multisiteMultisite Multisite is a WordPress feature which allows users to create a network of sites on a single WordPress installation. Available since WordPress version 3.0, Multisite is a continuation of WPMU or WordPress Multiuser project. WordPress MultiUser project was discontinued and its features were included into WordPress core.https://codex.wordpress.org/Create_A_Network. network that caused some taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. terms to be uneditable.
  • Created an experimental Docker-based WordCamp development environment.
  • Partially fixed an old bug where organizers and speaker badges are erroneously removed in some instances.
  • Added a payment gateway for WordCamp ticket purchases in Bangladesh.
  • Added new fields to WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ profiles where people can add details about how they contribute to the project.
  • Merged a feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. created by the WCEU team that adds Progressive Web App (PWA) functionality to WordCamp sites. Currently it is in betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. testing exclusively on the WCEU site.
  • Iterations/fixes for Gutenberg compatibility, themes, error logs, security, updates, taxonomy terms, invoicing, and site URLs.

#wordcamp

+make.wordpress.org/community

Next WordCamp.org ticket scrub on June 20th, 2019

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

The focus is on MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. tickets with the WordCamp Site & Plugins component.

The timing of this meeting nearly coincides with Contributor Day at WordCamp Europe (it will have just ended). So we may end up focusing on tickets that didn’t quite make it over the finish line earlier in the day.

Feel free to comment below if there’s any other specific ticket or topic you’d like to discuss.

#agenda #ticket-scrub #wordcamp

+make.wordpress.org/community

Next WordCamp.org ticket scrub on May 16th, 2019

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

The focus is on MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. 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.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org//community

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 MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. tickets with the WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. 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 WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more.’s shortcodeShortcode A shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site.-to-blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. 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 meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. events after Meetup.com made an unannounced change to their APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.
  • 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 MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. 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:

  • Committed code for the first shortcodeShortcode A shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site.-to-blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. conversion: Speakers
  • Updated wordcamp.org to WordPress 5.1
  • Added 5.1 blog metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. table
  • Removed a duplicate notification to the slackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel when a WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. or MeetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. listing is put into Active/Scheduled status, and already has been put into that status in the past.
  • Reviewed code from community to automate VAT invoices, and proposal from community to build WordCamp.org PWA
  • Made forms-to-drafts compatible w/ Gutenberg
  • Restricted Tagregator date range
  • Added Attendee filtering by flag
  • Automated a check for supporting documentation before allowing reimbursement request to be submitted, to save administrative time
  • Automated reminders to organizers with pending invoices for over 30 days, to reduce our collections backlog
  • Standardized unit test suite to make adding new tests easier
  • Fixed a bug that wiped out WordCamp listing metadata when manually sending an organizer reminder
  • Fixed a bug that was stripping LESS variables from CSS
  • Drafted a proposal to move WordCamp.org to GitHub

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 SVNSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/. as the primary tool of version control hosted on the Meta SVN repo. For the last several months we have also been experimenting with GitGit Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. Most modern plugin and theme development is being done with this version control system. https://git-scm.com/. 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 GithubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ 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 releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. process. That is, whenever code is deployedDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. changes will be synced from Git to SVN and start the deployDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. 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 MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. 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