Archives

Unknown's avatar emaralive 10:51 pm on March 12, 2025
Tags: 296, , ,   

BP Docs-Chat Summary March 5, 2025

In summary, there were various arrival times in attendance to this meeting which did not afford a decent amount of time for conversation.

BP Documentation tracker status:

The stats – 58%, there was no change in percentage points – 58% ➡ 58%

NOTE: The stats remained flat due to no new issues were submitted and completions remained the same..

There is 1 (one) issue that is currently In Progress. For details see the In Progress section (Note: Project views are dynamic and are subject to change without notice).

Due to a reduction in the number of writers/authors, the documentation effort has slowed to a crawl.

Revisit the Update README with Documentation roadmap:

This was mainly a posting of a backstory regarding a previous effort to provide a Roadmap for the documentation effort that was represented by a Pull Request (Update README with Documentation roadmap). Additional actions to take place as part of the indicated Pull Request are, for example:

  • Remove the data folder & it’s content, since we would have an archive branch that has this info, in the event we need to reference anything from that content.
  • Remove 1-migrate-task.yml from the .github/ISSUE_TEMPLATE folder since it is now obsolete and will exist in the archive branch.
  • Remove 3-ignore-task.yml from the .github/ISSUE_TEMPLATE folder since it is now obsolete and will exist in the archive branch.
  • Rename 2-add-task.yml to 1-add-task.yml, keeping a similar numeric prefix.
  • Rename 4-update-task.yml to 2-update-task.yml, keeping a similar numeric prefix.
  • Create a folder named roadmap, which will contain any detailed info that further describes/defines the top-level roadmap (as spelled out by the final version of the README.md), e.g., there would be links from the roadmap (README.md to whatever detailed .md files that are created).

The last bullet item may or may not be required, it will all depend on the amount of information that will be used to convey the Roadmap.

There was a brief “after the meeting” conversation regarding the naming of the archived (original) branch. A consensus was:

  • There should be a branch (archive) that represents the original content prior to any changes to the trunk branch
  • On the table was a possible name of “version_1” for this original (archive) branch.

Note: This agenda item is slated to be on the agenda for the next documentation meeting as a continuance.

Open Floor:

Due to time constraints, this agenda item was forgone.

Next Docs-Chat

Our next documentation meeting will happen on March 19, 2025, at 19:00 UTC in #BuddyPress.

#296, #docs-chat, #documentation, #summary

Unknown's avatar emaralive 9:06 pm on March 3, 2025
Tags: , ,   

BP Docs-Chat Summary February 19, 2025

BP Documentation tracker status:

The stats – 58%, there was no change in percentage points – 58% ➡ 58%

NOTE: The stats remained flat due to no new issues were submitted and completions remained the same..

There is 1 (one) issue that is currently In Progress. For details see the In Progress section (Note: Project views are dynamic and are subject to change without notice).

Due to a reduction in the number of writers/authors, the documentation effort has slowed to a crawl.

Open Floor:

Open Floor was basically a revisit of the moderation tasks for the BuddyPress Support Forums. There was consideration of reinstituting a past/previous practice of prefixing/prepending a “[Resolved]” to topic titles (See Search Results for ‘[resolved]’). This practice appears to have been dated back to the year 2018 and for inexplicable reasons appears to have been dropped/abandoned. Additionally, there is interest in closing topics that have been resolved to further comments/replies in an effort to limit the areas/places where spam can occur.

Other considerations for limiting areas/places where spam can occur is to close topics after a, yet to be defined, period of time. For example, the CloudFlare automatically closes topics 15 days after the last reply and an example topic for CloudFlare is; A timeout occurred Error code 524 Visit cloudflare.com for more information, of which, at the bottom there is a entry that reads:

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.

The WordPress Jobs site adopts a different principle whereby Job posting only stay alive for 21 days unless the original poster removes the posting prior to the 21 day limit. Additionally, It also appears the postings are moderated prior to public display. Notwithstanding a different purpose, there are some aspects worthy of some discussion/considerations that may apply to specific forums not related to BuddyPress proper/per se.

The 2, indicated, example sites are just some food for thought in consideration of revamping previous written and/or unwritten policies that have/had existed for BuddyPress Support Forum content moderation. There is a discussion topic that exists, Support Forum – Some Notes about Moderating #294, however, further discussions are yet to be realized.

@johnjamesjacoby made comment about:

  • Marking an account as a spammer has some negative consequences if the decision to do so was incorrect.
  • There is some automation which attempts to identify spam and mark new user accounts accordingly but, manual review is probably the most effective method.
  • Auto archiving topics will eventually be implemented (a plugin that is in use by wp.org)

Last but not least, there was brief conversation regarding additional consideration for the look and feel of buddypress.org, e.g, just to name a few:

Next Docs-Chat

Our next documentation meeting will happen on March 5, 2025, at 19:00 UTC in #BuddyPress.

#docs-chat, #documentation, #summary

Unknown's avatar emaralive 5:46 pm on January 13, 2025
Tags: , ,   

BP Docs-Chat Summary January 8, 2025

In summary, the meeting progressed with @emaralive posting items according to the agenda for the first 30 minutes by pacing the 2 (two) scheduled agenda items to fit within a 30 minute time frame. Prior to the start of the meeting @narenin posted a 👋 and then apparently returned after the conclusion of the meeting and posted additional reactions.

@dcavins made an appearance during the Open Floor part of the meeting which lasted for around 15 minutes, after which the meeting was adjourned.

@johnjamesjacoby joined in on the 🍕 reaction, after the adjournment of the meeting.

To Note: async (asynchronous) is a situation when an individual is not present during the meeting but, made an effort to make their presence known after the adjournment of the meeting.

BP Documentation tracker status:

The stats – 58%, there was no change in percentage points – 58% ➡ 58%

NOTE: The stats remained flat due to no new issues were submitted and completions remained the same..

There is 1 (one) issue that is currently In Progress. For details see the In Progress section (Note: Project views are dynamic and are subject to change without notice).

Due to a reduction in the number of writers/authors, the documentation effort has slowed to a crawl.

Open Floor:

The expectation for open floor was just to ease into the new year, given that this was the 1st meeting after the holiday break.

@emaralive mentioned that there should be emphasis placed on getting the GitHub sourced documentation rendered as Web based Handbooks which would make it easier for end-users to navigate through the content. @dcavins indicated that this would be a major undertaking, of which it will be.

Next Docs-Chat

Our next documentation meeting will happen on January 22, 2025, at 19:00 UTC in #BuddyPress.

#docs-chat, #documentation, #summary

Unknown's avatar Renato Alves 4:30 pm on November 3, 2024
Tags: , ,   

BP Dev-Chat Summary October 09, 2024

Review the “New BuddyPress network Theme call” meeting;

Status: Blocked pending information from @johnjamesjacoby regarding:

  • Feasibility of changing BuddyPress.org theme without affecting other sites;
  • Options for improving navigation and responsiveness;
  • Clarification on commit access requirements for Meta repository.

Contributor Mentorship Program

  • Status: Kickoff meeting scheduled for tomorrow at 22:00 UTC
  • Lead: imath
  • Purpose: Onboarding and orientation for new contributors

Version 15.0.0 Development Updates

  • REST API (@espellcaste)
    • Progress on ticket #9145 (REST API V2)
    • Fixed ticket #9231 (spammed user information retrieval)
    • Fixed ticket #9160 (message data anonymization)
    • Noted discrepancies between web and REST API implementations
  • Documentation (@im4th)
    • REST API documentation migration in progress
    • Expected completion: within 2 weeks
    • Using manual conversion process due to export limitations

Release Planning Changes

  • Target Timeline:
    • Beta release: First week of November 2024
    • Final release: After WordPress core release (planned for following month)
  • Current Status:
    • Approximately 50% of milestone tickets completed
    • Major changes include REST API V2 implementation
  • Testing Requirements:
    • Additional testing needed for REST API changes
    • Focus on real-world usage scenarios
    • Unit tests in place but need practical validation

📆 Next Dev-Chat Agenda

It will happen on Wednesday October 23, 2024 at 18:00 UTC in #BuddyPress.

#15-0-0, #dev-chat, #summary

Unknown's avatar im4th 7:07 pm on October 26, 2024
Tags: , ,   

BP Docs-Chat Summary October 16, 2024

View full Docs-Chat transcript (PDF)

We were very happy to welcome @rfluethi, one of bbPress / BuddyPress mentees from the 3rd cohort of the WordPress Contributor Mentorship program, for his first participation to our regular Wednesday dev/docs meeting.

BP Documentation tracker status:

The stats – 58%, which is an increase of 2 (two) percentage point – 56% => 58%.
@emaralive explained @rfluethi these stats represent our efforts in producing BuddyPress documentation. @im4th shared the link to our todo list as well as the tutorial about how to contribute to writing BuddyPress documentation. If @rfluethi and other mentees choose to pick up an issue, someone from the BP Team members will always be be available to walk them through the process and answer any questions, simply ping one of us on Slack/Matrix.

Documentation updates

@emaralive informed he’s paused on his efforts documenting the Site Health Info BP debug panel due to waiting for some clarifications on whether a few Constants are actually deprecated. He reminded us he previously shared a GH discussion about it. Moreover he found out there were an ugly error about the Site Health Info BP debug panel when the xProfile component were not active (this bug has been fixed, see #9245). We took the time to check these contants and brought the needed clarifications. @emaralive also plans to update documentation for the v1 of the BP REST API.

@im4th is currently working on documenting the v2 of the BP REST API, so far he took care of the Activity, Groups and Messages REST API routes.

Open floor

@emaralive shared his experience installing the BuddyPress Network from the Meta Trac. He’s now ready to give a hand to @johnjamesjacoby in contributing to our official site.

Next Docs-Chat

It will happen on October 30, 2024 at 19:00 UTC in #BuddyPress.

#docs-chat, #documentation, #summary

Unknown's avatar Renato Alves 12:29 am on October 2, 2024
Tags: , ,   

BP Dev-Chat Summary September 25, 2024

Review the “New BuddyPress network Theme call” meeting;

We started the meeting trying to review if we made any progress regarding some questions to @johnjamesjacoby We haven’t yet.

@vapvarun expressed a concern we are stuck pending the feedback of this decision (@emaralive agreed). I personally agree too and that’s frustrating. At the same time, I feel we are making meaningful progress, but we are blocked by lack of information and access. I’m hopeful we will get more traction soon. =D

WordCamp US

@espellcaste attended WordCamp US – Contributor Day and had good discussions about BuddyPress integration with Ferdiverse and GatherPress.

A repo was created here: https://github.com/GatherPress/gatherpress-buddypress and @mauteri will be creating tickets/issues there. Besides getting the basic setup in place to start development.

Contributor Mentorship Program

This program is starting soon:

  • Starts October 7th with 5 mentees
  • Goal: Increase contributors for BuddyPress/bbPress
  • @patriciabt is leading this task and will onboard mentees and schedule calls with @im4th and @johnjamesjacoby
  • More information can be found here.

15.0.0 Milestone Updates

Activity Block Editor Plugin

  • @im4th is working on compatibility issues with WordPress 6.6+;
  • And moving away from Isolated Block Editor to a custom solution.

📆 Next Dev-Chat Agenda

It will happen on Wednesday October 9, 2024 at 18:00 UTC in #BuddyPress.

#15-0-0, #dev-chat, #summary

Unknown's avatar Renato Alves 11:49 pm on October 1, 2024
Tags: , ,   

BP Dev-Chat Summary September 11, 2024

Review the “New BuddyPress network Theme call” meeting;

There were some pending questions to @johnjamesjacoby. He was not available at this meeting to provide answers. And we postponed this topic to the next dev-chat. 🙂

15.0.0 Milestone Updates

  1. V2 – REST API: the ticket is pending @espellcaste to apply code review suggestions.
  2. Revamped Site (Wide) Notices
  3. Import/Export of all BuddyPress user data: @vapvarun continues to make progress.
  4. Misc tickets:
    • #8986 (Register page input validation): Ready for commit (@espellcaste)
    • #9232 (Notifications bug fix): Ready for commit (@dcavins)
    • #9223 (Groups WP Admin feedback messages): Needs work on improving error messages (@im4th)

General Notes

  • Props were given to new contributors sending patches to tickets;
  • @espellcaste needs to compile list of tickets for Contributor Day at WordCamp US;
  • The team feels good about progress on main announced features;
  • Beta release expected in about 5-6 weeks.

📆 Next Dev-Chat Agenda

It will happen on Wednesday September 25, 2024 at 18:00 UTC in #BuddyPress.

#15-0-0, #dev-chat, #summary

Unknown's avatar Renato Alves 2:39 am on August 30, 2024
Tags: , ,   

BP Dev-Chat Summary August 28, 2024

BuddyPress 14.1.0: Release Schedule

We set a date to release BuddyPress 14.1.0. September 4th, 2024. This is a minor release with two bug fixes and one enhancement.

New BuddyPress Standalone Theme – Upcoming Call

We have a day and time scheduled for a group call about the new BuddyPress standalone theme for buddypress.org. The last piece missing before the call was an agenda. @vapvarun suggested a pretty detailed one, of what we need to get out of the call with:

  1. Theme Selection
    • Use an existing theme for quick implementation.
    • Consider creating a custom theme for a unique design.
  2. Timeframe
    • Existing Theme: 2-3 weeks.
    • Custom Theme: 8-10 weeks.
  3. Team Involvement: 1-2 people will work on design, development, and content.
  4. Dependencies
    • Ensure compatibility with BuddyPress plugins and custom functionalities.
    • Check for shared resources that might impact bbPress.org.
  5. Impact on bbPress.org

15.0.0 Milestone Updates

  1. V2 – REST API: ticket identified as a priority since it is blocking other REST API related tickets for this milestone.
  2. Import/Export of all BuddyPress user data: @vapvarun has made good progress. There was some discussion about what sort of export/import tool is being built.
  3. Revamped Site (Wide) Notices
  4. Update WordPress and PHP Version Requirements: We are raising the minimum requirements to WordPress 6.4 and PHP 7.0.
  5. WPCS Improvements: @espellcaste is going to try to fix WPCS styling issues in bulk. But asked for at least one code review for the pull request.
  6. Notification Cleanup: @espellcaste asked for a second opinion on a proposed approach for cleaning read notifications.

Other Developments

📆 Next Dev-Chat Agenda

It will happen on Wednesday September 11, 2024 at 18:00 UTC in #BuddyPress.

#15-0-0, #dev-chat, #summary

Unknown's avatar im4th 9:13 am on June 20, 2024
Tags: , ,   

BP Dev-Chat Summary June 19, 2024

⏳ BuddyPress 14.0.0

2 tickets were needing attention:

  • #8319 was reopened due to an issue with the BP Default theme: the way we are filtering current_theme_supports-buddypress needs some extra checks to avoid PHP warnings. The goal of this improvement is to let BP standalone theme developers opt-in for BuddyPress support globally using add_theme_support( 'buddypress' ) as well as for future specific component features using bp_current_theme_supports( array( 'activity' => 'block-editor' ) ) for instance. A patch has been added and will be committed shortly.
  • #9187 is a last minute improvement to bring back custom locations for language files. Thanks to it users will be able to fully customize all BuddyPress texts to match their community needs (eg: using “teams” instead of “groups” etc..) without fearing their language files to be updated with the regular BuddyPress ones. A patch enjoying WordPress 6.5 l10n improvements is ready to be committed.

Working on BuddyPress documentation is helping us finding bugs or potential improvements: #9187 can thank this PR being reviewed, @emaralive found a regression introduced in 12.4.1 as well as an issue with the BP Opt-outs tools screen options.

We’ve decided to set Beta2 release date to June 24 (next monday). If you haven’t tested Beta1 yet, please be our guests!

14.0.0 updated schedule

  • June 13: 14.0.0-beta1 ✅.
  • June 24: 14.0.0-beta2
  • July 8: 14.0.0.

Open floor

  • 12.6.0 milestone is there in case we’re releasing 14.0.0 after WordPress 6.6 is released. Main goal is to preserve the Notification WP Admin bar “bubble” position since 6.6 has made some changes into this area lately (See #9182).
  • We talked about the BuddyPress.org site’s new theme project (see #9193). The simpler the better (@emaralive).
  • @johnjamesjacoby reminded us that when we were batch closing all buddypress.org issues, we are effectively also closing them for bbPress.org, because they share a common codebase 😬.
  • WCEU 2024 was great! @vapvarun went there, met with Matt and with other great developers that may get involved into BuddyPress. The more we are the better (@im4th).

Next Dev-Chat

It will happen on Wednesday July 3, 2024 at 19:00 UTC in #BuddyPress.

#14-0-0, #dev-chat, #summary

Unknown's avatar vapvarun 7:52 pm on April 8, 2024  

BP Docs-Chat Summary March 28, 2024

BP Documentation tracker stats

  • BP Codex contains 271 pages.
  • 279 total tasks were created (migrate + ignore + add + update).
  • 267 tasks related to the pages reviewed were created (migrate + ignore).
  • 43 Open | 15 Closed « migrate » tasks.
  • 0 Open | 209 Closed « ignore » tasks.
  • 5 Open | 4 closed « add » tasks.
  • 2 Open | 1 closed « update » tasks.
  • Approximately 82% of 279 tasks have been reviewed (229 / 279).

Multisite and Multiblog Testing:

@vapvarun is testing multisite cases to prepare new screenshots and documents. Discussion on issues and complexities related to multiblog setup, including configuration and potential bugs.

Object Cache Testing:

@espellcaste mentioned limited testing against plugins like Redis and plans to set up CI for testing against Memcache. #9076

CSS Issues and Tickets:

Identified CSS issues with the “hello” screen and other areas. Discussion on related tickets and ongoing efforts to resolve them. @emaralive tasked with investigating a specific #9111 ticket related to BP Hello menu. Discussion on focusing documentation efforts on multiblog configurations for BuddyPress.

Multiblog Feature:

@vapvarun working on documenting various multiblog configurations and use cases. Consensus to deprecate multiblog due to low usage and maintenance challenges.

@imath suggest to consideration of deprecating multiblog feature. @patriciab mentioned using multiblog for multilingual communities where each subsite represents a different language. @imath reassured that deprecation is not happening soon and emphasized the need to preserve backward compatibility.

Participants discussed the use cases and challenges of the multiblog feature, as well as potential implications of deprecation. Plans were made for further discussions and a demo of the multilingual community site.

Next Docs-Chat

It will happen on April 10, 2024 at 19:00 UTC in #BuddyPress.