Release Leads: Call for Volunteers

BuddyPress 2.8 will be released in a couple of weeks, and it’s time for our community to start considering release leads for BuddyPress 2.9 and 3.0.

Our experiments with the release lead role over the last year have worked out well, and for BuddyPress 2.9 and onwards, we’re opening up the nomination process publicly for improved transparency.

The release lead works with all contributors to ensure the success of the release. The role blends aspects of being a product manager, project manager, engineering manager, release manager, and community manager. Release leads do not need to be developers, but having experience contributing to open source projects is required.

Release leads are supported by the lead developers, the project team, and deputies of their choosing. Volunteering as a release deputy is a great way to give it a try and learn about the process, but with a smaller time commitment.

For the sake of clarity, BuddyPress release leads and their deputies, between them, can expect to:

  • Run our weekly project meeting, and write and publish meeting notes on our development blog.
  • Coordinate blog posts and announcements on social media.
  • Make final decisions about whether a proposed feature is able to be put into the release.
  • Help new contributors make their contributions seen and heard in project meetings.

While BuddyPress is built by people volunteering their own time, contributing whatever they want, however they want, the release lead should take advantage of their position and use it to shape BuddyPress. For example, if the release lead feels that the next release should have a focus on specific aspects, we expect them to declare this, and try to encourage regular contributors to make that a reality.

Are you interested?

If you are interested in volunteering to be a release lead, please comment here or contact either myself (@djpaul), Boone (@boone), or John (@jjj) on Slack.

#release-lead

I’ve updated the dates in…

I’ve updated the dates in the Schedule (in the sidebar of the bpdevel.wordpress.com site) for the #2.8 release timetable.

Hi everyone. As usual, BuddyPress’…

Hi everyone. As usual, BuddyPress’ contributor chat has been moved back to 20:00 UTC on Wednesdays, after the recent DST timezone changes for the majority of our frequent contributors.

Apologies to those who get caught off-guard by this late change for today’s meeting; at least you’ll be there on time! 🙂

Build/Test tooling

It’s always fun figuring out improvements for our build and test tooling, to make life easier for regular contributors. Does anyone have any ideas for things we can do to improve this in BP #2.8 ? I’ve given this a bit of thought. We could:

  • Grunt: remove dependency on Ruby by removing grunt-scss-lint#7028 (in progress)
  • Move bbPress 1 out of buddypress.svn.wordpress.org, and manually add it in when we commit the release build to plugins.svn.wordpress.org. We already do this for the bp-default theme. ?
  • Iterate on the NPM package versions and shrinkwrapping and related requirements, and make it work 100% reliable on @boonebgorges computers. 🙂
  • Look into performance improvements using Yarn, which acts as a wrapper/CDN for NPM. ?
  • Add Git commit hooks.
    • All committers work in Git, and commit to BuddyPress via git-svn. It isn’t an option to switch to committing in Git directly as the moment. We should think about what things we could/should pre-commit hook.

Super interested to hear any feedback or other ideas or wishlists around tooling! Share in comments below!

Tooling

BuddyPress integrates with a number of third-party services via Github that help us build a stable piece of software. To document what the project currently uses, I wanted to write a quick list:

  • Travis-CI
    • PHPUnit tests; Grunt build script test; code-coverage generation.
  • Codecov (new!)
    • Code coverage tracking.
  • Scrutinizer
    • Code standards review; PHPDoc review.
    • Scrutinizer is very tricky to configure well, so we’re still unconvinced if this is useful to us. Experimental.

Code coverage reports are new as of this week, and I look forward to using them to help us evaluate if new features we add have adequate test coverage.

#codeco-io, #scrutinizer, #tooling, #travis-ci

I’ve just committed the patch…

I’ve just committed the patch in https://buddypress.trac.wordpress.org/ticket/6923 to trunk/2.7. It’s an enhancement to grunt patch to allow you* to upload patches directly to a Trac ticket, and also to download a Github pull request and apply it as a place. See the commit message https://buddypress.trac.wordpress.org/changeset/10936 for instructions.

*Only BuddyPress Trac admins and bug gardeners have access to upload patches in this way.

Congratulations all contributors to BuddyPress…

Congratulations all contributors to BuddyPress 2.6! For those who attend our dev meetings regularly, please note that next week’s scheduled meeting — 29th June — is cancelled to give everyone a chance to relax. It’s quite probable that some members of the team will be on Slack then anyway, so we’d love to have a casual chat if you happen to be around. 🙂

The dev chat scheduled for 6th July is on, and it will be used to discuss any problems that have been found since release of 2.6, and to discuss ideas for BuddyPress 2.7 and ways to help contribute to it.