Marius L. J. 3:32 pm on October 20, 2021  

Planning our shared component-push

During the weekly meeting a few weeks back, I was testing the waters in terms of around doing a joint session where we work out ticket patches together in an event where we jump on a voice/video chat, with a shared screen, and work on patches for the Support ForumSupport Forum WordPress Support Forums is a place to go for help and conversations around using WordPress. Also the place to go to report issues that are caused by errors with the WordPress code and implementations. component.

There appeared to be a bit of interest for this, and will require a bit of setup so that we can reliably work on the various tickets, but I have a vision for how this would work, and want to outline it here ,and gather feedback and opinions.

The setup

Using a shared platform, like for example Spatial Chat, Zoom, Hangouts… it doesn’t really matter which platform we use here, so long as it doesn’t end up having a paywall barring entry for anyone.

@clorith will be your facilitator, to make things easier, sharing his screen, with their own setup of the 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/ support forums available for testing any changes made, or want to look into making. We then pair-program it (if you’re not programmer, no problem, I’ll happily write code if you help with the ideas!), so that we can end up pushing patches for the tickets we care the most about.

By having a ready setup, this saves everyone from needing to set things up locally for this one scenario, and patches can be shared like one would share them on tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/., allowing others work to be ported in and looked at as well, perhaps some tickets have patches that just need testing? Or there’s something visual to change, where just making the code isn’t always enough.

In preparation

Before the time of our session, it is useful if those wishing to participate have had a look at the available tickets, and identified which issues they would like us to tackle and solve. This comes with no guarantee that everything is solvable in one session, but if nothing else it should aim to unblock any issues that have been sitting around if they are too large to tackle in one session.

When will this be held?

That’s the difficult bit, scheduling time, never an easy task, and this relies heavily on participant availability, some initial thoughts for dates and times follow, but if none of these are possible for users, then please let the team know!

Which dates work the best, or are there other dates (or times) that work better based on your geographic location? Again; Please let us know so we can facilitate things to be available to those who wish to take part.

Update

Unfortunately, with the low turnout, and the amount of work required to do these sessions, we’ll be cancelling this proposal at this time, and will instead circle back to it at a point in the future. Thank you to those who showed an interest, and apologies for not being able to follow through at this time.