Hi!
Our development meeting will happen today (July 21) at 19:30 UTC and of course in #BuddyPress.
Here’s our agenda:
If you have specific/additional points you need to discuss about, please share them into the comments area of this post.
👋
Following the discussion we had during June 23 meeting about the frequently requested Follow feature, and a very interesting discussion between @sbrajesh, @espellcastewe and @johnjamesjacoby, we decided to improvise a new Dev Chat about a possible larger scope about it. We shared our views about building a wider vision for “relationship types” in BuddyPress. A new API that would firstly be used for the Follow feature, but could also be used for potential other needs: user likes, improved user favorites, blocking users, what may come to our mind in the future!
@sbrajesh will lead this new project using the “feature as a plugin” model like WordPress does from a BuddyPress GitHub repository. If you’re interested in contributing to this project, please “raise your hand” commenting this summary.
@im4th starts with an apology: unlike what was scheduled (July 8), we were not able to release the 9.0.0 first beta so far. Sorry about it.
We’ve migrated 90% of Widgets as Block Widgets from the GitHub repository we use to build BuddyPress blocks. We also improved some BP REST API endpoints and we’re on our way to include a new endpoint to deal with Sitewide Notices. BP Block Widgets have been built on 2 principles: use the BP REST API every time it’s possible and use Modern JavaScript on front-end and the Widget/Post Block Editor’s APIs (mainly built on top of React.JS) on back-end.
@dcavins has made great progress about the Sitewide Notices Block Widget (👉 the last one to reach 100%) and about the corresponding REST API Endpoints. @espellcaste gave great advices about the BP REST API to speed up the process.
We also talked about directly packaging a Release Candidate without doing a Beta release. As the 9.0.0 development cycle is focused on migrating Widgets as Blocks, we have a very limited risk of messing with other parts of BuddyPress. @im4th said he’ll work on merging the BP Blocks code into BuddyPress core and will try to find the time to quickly build a Beta Release and some time after the Release Candidate (he hates when he doesn’t do what he has written he would do).
We finally talked about the great work @vapvarun has done building a test drive to host the BuddyPress code reference. The goal is to make it available asap and before the end of the year here. The main difficulty is to generate the documentation using the WP CLI parser command directly from the server (10 minutes). @im4th wondered if this could be achieved using the WP import/export tool (the documentation plugin is using custom post types). This is an approach we’ll try to test to avoid possible downtimes of the BuddyPress.org network.
It will happen on July 21 at 19:30 UTC and of course in #BuddyPress. If you have ideas or questions, feel free (and we are strongly encouraging you) to comment this summary to share them!
As we are running a short development cycle, @im4th will be available every Wednesday at 19:30 UTC in #BuddyPress for an hour or more time if needed. Don’t hesitate to ping him (@imath) for help or inputs about contributing to this version of BuddyPress.
Hi!
Our development meeting will happen today (July7) at 19:30 UTC and of course in #BuddyPress.
Here’s our agenda:
PS: 9.0.0 is a short development cycle, here’s our schedule for it:
If you have specific/additional points you need to discuss about, please share them into the comments area of this post.
👋
During yesterday’s development meeting we’ve discussed about @im4th‘s proposal to run the 9.0.0 development cycle very shortly targeting a release date before WordPress 5.8 final release is made available to the planet (~ July 20, 2021)!
@im4th was a bit worried about being too much directive and/or too ambitious, so he specified it was ok to disagree with this proposal. We quickly agreed, but here are some opinions we shared about this idea:
So we are going to try to do it!
As WordPress 5.8 is introducing the Widgets Block Editor, we are going to start migrating our legacy widgets. We actually already started the process from the GitHub plugin we use to develop BuddyPress Blocks. The first step is building a block for every BP Widgets and making it possible to transform existing BP Widgets to their corresponding BP Block. BP Widgets won’t disappear in 9.0.0 yet (no worries), but they’ll get a well deserved retirement progressively 😁. You can expect (at least) 10 new BuddyPress Blocks to be introduced in BuddyPress core.
@sbrajesh volunteered to satisfy a frequent request about this feature and he’s very welcome to contribute and lead this effort to make it happen! We talked about the “Followers” plugin @rayisme built which can be a source of inspiration. We’ll organize it from another specific GitHub repository. After the dev-chat, we had a complementary discussion about it, you can have a look at it for more information about early directions about the feature.
And of course, we’ll fix issues related to our latest major release (8.0.0) that may be found.
During the dev-chat, we also discussed about the feedbacks we got from the support forums about 8.0.0. We shared our surprise that plugins that appear to rely on BP aren’t tested in the beta window. This is something we need to carry on trying to improve. Working on documentation could be a way. On this topic, @vapvarun informed us he would prepare a list about which documentation resources need updates & then update them one by one 😍. Many thanks to him: it’s a very important work that will benefit to us all.
It will happen on July 7 at 19:30 UTC and of course in #BuddyPress. If you have ideas or questions, feel free (and we are strongly encouraging you) to comment this summary to share them!
As we are running a short development cycle, @im4th will be available every Wednesday at 19:30 UTC in #BuddyPress for an hour or more time if needed. Don’t hesitate to ping him (@imath) for help or inputs about contributing to this version of BuddyPress.
Hi everyone, sorry this summary is published very late (the day before we’re having another development meeting).
@imath).So here’s the question we need to reply to during tomorrow’s development meeting:
So here’s my plan: July 16 is my birthday and WP 5.8 is slated to July 20. What about releasing BP 9.0 on July 16 with only blocks (and some other fixes of course) ?
@im4th on June 9
It will happen on June 23 at 19:30 UTC and of course in #BuddyPress.
If you have specific/additional points you need to discuss about, please share them into the comments area of this post.
Hi!
Our development meeting will happen on June 9 (tomorrow) at 19:30 UTC and of course in #BuddyPress.
Here’s our agenda:
If you have specific/additional points you need to discuss about, please share them into the comments area of this post.
👋
@im4th noticed the only feedback we got from this beta release was about the BP Beta Tester plugin. The issue about this testing tool was fixed in 1.2.0. Does it mean everything’s fine with 8.0.0? We’ll see with the release candidate that was published 4 days ago: if you haven’t tested it yet, please do so 🙏.
We’ve been talking about the BuddyPress code reference. It’s still under construction and we really need to make it available asap. @vapvarun had the opportunity to test the parser tool and the only thing we need to make sure is to avoid parsing the BP REST API controllers to avoid some kind of duplicate information with the BP REST API documentation. As it was getting late @im4th suggested to have a specific dev-chat about it.
@dcavins shared a proof-of-purpose plugin that adds some limitations on who can send site membership invites.
If anyone has ideas for limits to add, please let @dcavins know adding issues to this GitHub repository.
It will happen on June 9 at 19:30 UTC and of course in #BuddyPress. We’ll probably talk about the first results/feedbacks about the 8.0.0 stable release but If you have ideas or questions, feel free (and we are strongly encouraging you) to comment this summary to share them!
PS: we count on you to test the 8.0.0 release candidate!
Hi!
Our development meeting will take place tomorrow (May 26 at 19:30 UTC) in #BuddyPress.
Here’s our agenda:
8.0.0 release schedule’s reminder
If you have specific/additional points you need to discuss about, please share them into the comments area of this post.
👋
@vapvarun checked our support forum and hasn’t found concerning feedbacks relative to this release.
@im4th replied to one of the comments that was posted on the announcement post about the next WordPress Full Site Editing (FSE) & Widgets Block Editor features. He tested the first one before our meeting and told us about his concerns during the chat. In short it’s a breaking change for the BuddyPress Theme Compat API. A pretty long discussion took place between @johnjamesjacoby @im4th and @vapvarun about it. We finally decided to open a very important ticket on our Trac to decide whether it’s on BuddyPress or FSE to adapt. If you have an opinion about it, please take a few minutes to share it with us.
bp_core_new_nav_default()function ticket (#8471), we decided we were too close to release date to do the necessary tests to be sure the patch doesn’t introduce some regressionWe agreed to build a new beta release before our release candidate. @im4th will take care of it next week.
It will happen on May 26 at 19:30 UTC and of course in #BuddyPress. If you have ideas or questions, feel free (and we are strongly encouraging you) to comment this summary to share them!
PS: we count on you to test the 8.0.0 beta release!
Hi!
Please join our development chat tomorrow (May 12 at 19:30 UTC). It will happen in #BuddyPress.
Here’s our agenda:
8.0.0 release schedule’s reminder
If you have specific/additional points you need to discuss about, please share them into the comments area of this post.
See you 🔜
