WordPress Community Team Proposes Adopting GitHub to Improve Collaboration

Although GitHub is primarily used for code collaboration, WordPress’ Community team is considering adopting the platform to standardize their project management tools.

Contributing to open source can already be challenging but when it requires signing up for multiple services in order to access the team’s many spreadsheets, trello boards, Slack groups, and other modes of communication, onboarding new contributors becomes needlessly difficult.

A new proposal, authored by Community team rep Leo Gopal, outlines the benefits of using GitHub as a central communication tool. These benefits include improved collaboration and communication using the platform’s commenting system and the ability to track progress and assign tasks.

Gopal contends that standardizing on GitHub would increase transparency and accountability while supporting better organization with tools like issues, labels, milestones, and project boards.

“By adopting GitHub for project management and issue tracking, the Community Team will standardize our way of working, making it easier for new team members to get up to speed and enabling more effective cross-team collaboration,” Gopal said. “This standardization also makes it easier for Community Team members to track progress, identify issues and make data-driven decisions.”

Other Make teams, such as Learn, Hosting, Meta, Marketing and more, are already successfully using GitHub to manage communication and prioritize projects. Gopal proposes the Community team learn from their efforts and adopt these tooling methods for a quarter as an experiment.

“If after the first Quarter the consensus is that this does not suit our team, we will revert back to initial project and tracking practices and explore more,” Gopal said.

A few participants in the resulting discussion have concerns about transparency and losing track of conversations, as they would not be linked to WordPress.org profiles.

“The truth is that I am unsure about it,” Weglot-sponsored Community team contributor Juan Hernando said. “I think the community team is not particularly technical, and using GitHub may pose certain barriers we didn’t have so far. Maybe for many people opening an issue, requesting a pull request, or similar is their everyday life, but for others, it can be a bit blocking.

“I’m also afraid that discussions will move from this Make site to GitHub, and we shouldn’t lose the spirit of owning our content (linked to our .org profile) and lose the use of this space for decision-making and public discussions like this one.”

Gopal addressed this concern stating that there would be no code and that users who can work with Trello boards will have no problem adopting GitHub’s tools for planning.

“Trello was used for planning and often forgotten until time for reviews or recaps,” Gopal said. “There was no way other teams would know what we are working on or add to the conversation unless they dug up our trello boards AND if we took their suggestion and weighed it in.”

Gopal said using GitHub would allow the team to incorporate advantages like automations, assignments, and inter-team collaboration with advanced reporting capabilities. Overall, GitHub has the potential to increase the visibility of their work for those collaborating across teams.

Milana Cap, who uses GitHub to help organize the Documentation team for reporting issues and automating tasks, recommended adopting the platform and shared how the Docs team is using it.

“All the other benefits: version control, precise contribution tracking, all sorts of project management tools etc., can not be found all in one tool other than GitHub, and I can not recommend it enough – for everything,” Cap said.

Discussion is still open on the proposal and Gopal has published a Proposal Poll for Community Team members to give their feedback on standardizing communications on GitHub.

6

6 responses to “WordPress Community Team Proposes Adopting GitHub to Improve Collaboration”

  1. Noting that certain activities in GitHub may show as activity on .org profiles if the user has connected those accounts together (view Edit Profile in .org). Also, using GitHub for more work like this can help overall metrics of contribution. As always, a GitHub activity, Core Trac, or any other mechanism doesn’t adequately track time spent thinking or discussing matters. These are just some portion that can be measured. See https://github.com/wordpress/five-for-the-future for ideas on how the use of GitHub is helping start some metrics in Training team (Learn).

  2. If this is a discussion, why only benefits are being mentioned?

    It seems WordPress values poliglots, however its chosen tool, GitHub, only is comprehensible for a subset of users, in english language.

    And Github is full of ethics problems (…) –also covered here on WPTavern — to no surprise, since it is a tool owned by Microsoft.

    They say there is “no tool like Github”.
    Well, just one among responsible and equivalent alternatives available, “Codeberg is a collaboration platform and Git hosting for free and open source software, content and projects.
    Codeberg is not run by a company, but is in the hands of its users – via the non-profit organization Codeberg – feel free to join!”
    WordPress.com > WordPress.org

  3. Thank you Sarah for covering this proposal.

    Many have very validly mentioned concerns especially since the Community team is not a team that actively works on Code and Github by reputation is seen as a place for developers and coders.

    To make clear what the proposed experiment is suggesting is this:
    – We are currently utilising Trello Kanban boards for planning and projects.
    – These Trello boards are under-utilised, and you find them only through actively looking for them and they are usually out of date.

    Therefore:
    – WordPress has contributor teams already using the Github Projects features much the same as Trello has it, with great success and utilisation.
    – Moving to this more standard approach would keep our kanbans on Github up-to-date, more effectively used, and visible across teams that may allow for cross-team engagement like we never had before.

    The Experiment:
    – Attempt to utilise this project standard through Github for Q1 of 2023, should we not see any benefit from it in this time, we revert or look for alternatives.
    – This experiment could only make things better and stay, or not do anything, and revert.

    I hope the intent to help us work better as a community is evident, thats my only goal starting 2023.

    Best, Leo Gopal

  4. I’m concerned about the more and more use of propietary tools by WordPress project. I also think free software projects must to support each other and is dificult to me understand why Codeberg is not seen as a alternative or why (if tooling is the key) Automatic can’t run a Gitea/Forgejo instance and get similar features than Microsoft GitHub while keep the code and the project independent.

    • It’s not about being a Microsoft is a huge proponent of open-source software, there is no such thing as “proprietary” software, that legal term doesn’t exist, it’s only in the minds of a few people that think their software is “free”. There is software with closed source and open source. GitHub is a great place to develop open-source software.

Newsletter

Subscribe Via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

%d bloggers like this: