Archives

Unknown's avatar emaralive 6:21 pm on August 4, 2025
Tags: , ,   

BP Docs-Chat Summary July 23, 2025

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. Additionally, user handles are taken from their respective Slack accounts and may not match up to WordPress.com accounts.

Summary: There was very little to report due to @emaralive was still ramping up on the learning curve for the Docusauras tool. Additionally, @emaralive was the only one in real-time attendance.

1️⃣ 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.

2️⃣ Continuation of the “revisit for the Update README with Documentation roadmap” – Part 11:

Phase 2 – conduct feasibility studies for potential tools which should determine the “final web home“

General discussion – 2nd feasibility study – Docusaurus – example of use: WordPress Playground

@emaralive reported that he was still digesting the documentation provided by the tool maker (Docusaurus).

Phase 2 feasibility studies status

  • In progress:
  • To Do:
  • Completed:
    • Woocommerce REST API documentation, based on Slate – proposed here. – awaiting final report (star to be appended when final report has been published)

❗ – in progress, ⭐ completed – toying with emojis to indicate basic status of any given study – no emoji indicates “to do”.

To provide context to this ongoing saga, there was information posted related to the backstory of how the documentation effort has progressed from inception to the current process for the creation of documentation, for example:

BP Documentation choices

  • July 12, 2023: use BuddyPress code repository to reorganize/migrate/update/improve the BuddyPress Codex.
  • January 10, 2024: create this repository to track BuddyPress Codex migration tasks as well as new documentation tasks.
  • January 24, 2024: using GitHub to contribute on the next BuddyPress documentation is our choice & it’s a good one!

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

3️⃣ Open Floor:

There were no conversations nor comments to report for this agenda item.

Next Docs-Chat

NOTE: The docs-chat meeting that was scheduled for August 6, 2025 is cancelled due to a conflict in schedule for @emaralive.

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

#docs-chat, #documentation, #summary

Unknown's avatar emaralive 9:59 pm on July 21, 2025
Tags: , ,   

BP Docs-Chat Summary July 9, 2025

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. Additionally, user handles are taken from their respective Slack accounts and may not match up to WordPress.com accounts.

1️⃣ 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.

2️⃣ Continuation of the “revisit for the Update README with Documentation roadmap” – Part 10:

Phase 2 – conduct feasibility studies for potential tools which should determine the “final web home“

General discussion – 2nd feasibility study – Docusaurus – example of use: WordPress Playground

The conversation was basically a first look at the Docusaurus  tool and based on the implementation by the WordPress (WP) Playground team, this tool looks like it might be a nice fit for the 3 BuddyPress (BP) handbooks (User, Developer & Contributor). At this time, the tool had not been installed (locally) by @emaralive and he had indicated that he had queued up a couple of the online demos that were provided by the tool makers.

A main feature is SPA (Single Page Application); Internationalization (i18n) is another feature of which @rollybueno (async) indicated that he had translated documents for the WP Playground project (see Translation: Tagalog (Filipino) #2336).

@dcavins indicated “[t]he result is screaming fast to use” which the tool makers claim:

Lightning-fast. Docusaurus v2+ follows the PRPL Pattern that makes sure your content loads blazing fast.

Phase 2 feasibility studies status

  • In progress:
  • To Do:
  • Completed:
    • Woocommerce REST API documentation, based on Slate – proposed here. – awaiting final report (star to be appended when final report has been published)

❗ – in progress, ⭐ completed – toying with emojis to indicate basic status of any given study – no emoji indicates “to do”.

To provide context to this ongoing saga, there was information posted related to the backstory of how the documentation effort has progressed from inception to the current process for the creation of documentation, for example:

BP Documentation choices

  • July 12, 2023: use BuddyPress code repository to reorganize/migrate/update/improve the BuddyPress Codex.
  • January 10, 2024: create this repository to track BuddyPress Codex migration tasks as well as new documentation tasks.
  • January 24, 2024: using GitHub to contribute on the next BuddyPress documentation is our choice & it’s a good one!

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

3️⃣ Open Floor:

This agenda item was forgone due to an interruption in conversations caused by other pressing matters.

Next Docs-Chat

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

#docs-chat, #documentation, #summary

Unknown's avatar emaralive 7:03 pm on July 7, 2025
Tags: , ,   

BP Docs-Chat Summary June 25, 2025

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. Additionally, user handles are taken from their respective Slack accounts and may not match up to WordPress.com accounts.

1️⃣ 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.

2️⃣ Continuation of the “revisit for the Update README with Documentation roadmap” – Part 9:

Phase 2 – conduct feasibility studies for potential tools which should determine the “final web home“

General discussion – 1st feasibility study – Slate Docs

There were a couple of tests that were failing while deploying to the experimental repository (bp-rest-api-docs) that were related to Ruby versions 2.6 & 2.7. These failures appear to be attributed to upgrading the Bundler version to 2.5.3 which is currently compatible with Ruby version 3.x and not prior versions. Most likely, the testing for Ruby versions of 2.6 & 2.7 should be removed, given that the dependencies have been upgraded to be compatible with Ruby version 3.x.

The Slate tool analysis is basically complete, a documented report will be forthcoming, when time is available.

Phase 2 feasibility studies status

❗ – in progress, ⭐ completed – toying with emojis to indicate basic status of any given study – no emoji indicates “to do”.

To provide context to this ongoing saga, there was information posted related to the backstory of how the documentation effort has progressed from inception to the current process for the creation of documentation, for example:

BP Documentation choices

  • July 12, 2023: use BuddyPress code repository to reorganize/migrate/update/improve the BuddyPress Codex.
  • January 10, 2024: create this repository to track BuddyPress Codex migration tasks as well as new documentation tasks.
  • January 24, 2024: using GitHub to contribute on the next BuddyPress documentation is our choice & it’s a good one!

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

3️⃣ Open Floor:

There was a support forum topic, BuddyPress plugin not tested with my WP version, which brought to light that the latest version (14.3.4) of BuddyPress is only compatible up to WordPress 6.7.2. There was some discussion on how to handle the next upgrade, however the date for release is still yet to be proposed/determined due to not having a list of bug fixes, etc. that would be included within this next release.

Another topic of interest was an issue with fonts as rendered by various browsers and operating systems. an example is a reply to a support forum topic, cant find all the buddypress widgets, whereby some of the text should have rendered as bold. For example, @emaralive indicated that for Chrome based browsers on a Linux 64 bit distro, what should have been bold text does not appear as bold, however, @dcavins indicated that on a Mac with Firefox and Vivaldi the bold text is rendered as such.

Next Docs-Chat

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

#docs-chat, #documentation, #summary

Unknown's avatar emaralive 7:45 pm on June 23, 2025
Tags: , ,   

BP Docs-Chat Summary June 11, 2025

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. Additionally, user handles are taken from their respective Slack accounts and may not match up to WordPress.com accounts.

Summary: There was only one real-time participant (@emaralive) for this meeting: meaning anyone who added a “reaction” or commented after the fact was included as an asynchronous attendee.

1️⃣ 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). The information covered was related the use of Docker as it pertained to the Slate Docs tool, e.g. “Using Slate in Docker”.

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

2️⃣ Continuation of the “revisit for the Update README with Documentation roadmap” – Part 8:

Phase 2 – conduct feasibility studies for potential tools which should determine the “final web home“

Update on the progress of the 1st feasibility study – Slate Docs

Using Slate in Docker – The Docker method proved to be outdated when pulling the “Slate Docs” image from the Docker Hub. It appears the dependency requirements were for Ruby 2.6 which was applicable at the time when Docker image and file known as “Dockerfile” were created and the same was apparently true for the Vagrant method. Updating “Dockerfile” to change the Ruby version from 2.6 to 3.3 along with updating “Gemfile” with the addition of  4 more Ruby gems and then using the “docker build” command created a Docker image that will now successfully build and serve the HTML documents.

All this means is that whichever method(s) is/are provided for building the BP REST API documents via the Slate tool, will have to be maintained to ensure a reliable build process, e.g., checked to make sure that there are no conflicts with dependencies as updates are made to those dependencies.

Phase 2 feasibility studies status

❗ – in progress, ⭐ completed – toying with emojis to indicate basic status of any given study – no emoji indicates “to do”.

To provide context to this ongoing saga, there was information posted related to the backstory of how the documentation effort has progressed from inception to the current process for the creation of documentation, for example:

BP Documentation choices

  • July 12, 2023: use BuddyPress code repository to reorganize/migrate/update/improve the BuddyPress Codex.
  • January 10, 2024: create this repository to track BuddyPress Codex migration tasks as well as new documentation tasks.
  • January 24, 2024: using GitHub to contribute on the next BuddyPress documentation is our choice & it’s a good one!

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

3️⃣ Open Floor:

There were a couple of comments regarding an individual’s inability to attend this meeting in real-time, e.g. scheduling conflicts.

Next Docs-Chat

Our next documentation meeting will happen on June 25, 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 emaralive 12:15 pm on December 23, 2024
Tags: , ,   

BP Docs-Chat Summary December 11, 2024

BP Documentation tracker status:

The stats – 58%, which is a decrease of 1 (one) percentage point – 59% ➡ 58%

NOTE: The decrease is due to 2 new issues that were submitted while the 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 BuddyPress documentation for Build and Test

This conversation was an attempt to verify and validate the current Build and Test documentation to ensure the accuracy and identify any updates that were deemed warranted for continuous improvement.

@dcavins indicated a very important step in the build process is to ” run a dif [sic] against the last released version in that branch–to [sic] check that the total changes are those that are expected and not introduced by an external library/repo.“

In summary, updates to the build document, e.g., clarification of the testing requirements, and the test document, e.g., additional test for BP CLI, are warranted . Issues #300 and #301 had been submitted to the BP Documentation tasks tracker repo prior to this meeting in anticipation that updates were warranted.

Pick date for 1st meeting for January 2025

On the table for a pick was January 8, 2025 @ 19:00 UTC. There were no counter options and thus, January 8, 2025 @ 19:00 UTC will be the next scheduled Docs-chat (documentation) meeting.

Open Floor:

@dcavins asked a question regarding priority level assignments for documentation tasks as viewed from the Project view. In the past, there had been discussion as to the labeling of issues to indicate such, but no further action had been taken. @emaralive took a look and experimented with some possibilities, as can be currently seen for a few issues. However, further thought is under consideration as well as the consideration for a consolidated “Work Flow” document that describes the documentation process from beginning to end.

As a backstory for this portion of the summary, currently bits and pieces of this process are described in various BuddyPress GitHub document sections and various docs-chat meeting summaries. Additionally, there is information that is yet to be determined regarding how the BuddyPress GitHub document sources (currently there are 3 handbooks plus other miscellaneous documentation that weren’t part of any given handbook) are to be rendered as Web based documents.

Next Docs-Chat

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

#docs-chat, #documentation, #summary

Unknown's avatar emaralive 5:28 pm on November 19, 2024
Tags: , ,   

BP Docs-Chat Summary November 13, 2024

There was a brief conversation with SirLouen regarding the comment he made in a comment for Trac ticket #9193, prior to starting with the 1st agenda item (see agenda).

BP Documentation tracker status:

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

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

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

For this meeting additional details regarding the documentation statistics were shared.

TodoIn ProgressDone% Complete
Migrate2113561%
Add71953%
Update20360%
Total3024759%

Review/status of documentation for wp-admin Help tabs related to BuddyPress

There are 20 areas within wp-admin that were identified as having Help tabs that are BuddyPress related, e.g., Activity, Groups, Emails screen/pages (just to name a few):

  • 12 documents have been created and the respective Help tabs have links to their respective documents.
  • 1 document has been started (Site Notices) and put on hold due to Trac ticket #9098, if implemented will cause a revamping of the original draft.
  • The 7 remaining documents are awaiting writers to start and complete such documents.

The quest for finding additional BuddyPress logos

There were only 2 additional logos of the monochrome variety that were found, i.e., the one used by this blog (as seen below) and the other used by buddypress.org (similar but with transparent background).

Since there were no other monochrome logos discovered, a set of monochrome logos were created from the color set. The logo.md file will be updated accordingly, when time permits.

Open Floor:

@dcavins and @emaralive had brief, in general, conversations regarding:

  • Storage of official logos.
  • GitHub markdown files.
  • Biggest opportunity for the documentation effort.

Next Docs-Chat

Our next documentation meeting will happen on November 27, 2024, at 19:00 UTC in #BuddyPress.

#docs-chat, #documentation, #summary

Unknown's avatar Renato Alves 7:06 pm on November 10, 2024
Tags: , ,   

BP Dev-Chat Summary November 06, 2024

Key Highlights

Release Schedule

  • Beta 1 release postponed by 2 weeks;
  • Several tickets need more attention before release.

Documentation Meetings

  • Proposal to merge documentation meetings with dev-chat meetings;
  • Switch from weekly to biweekly schedule.

BuddyPress 15.0.0

  • Several tickets moved out of 15.0.0 milestone
  • Confirmed tickets not making 15.0.0:
    • #9038 (BP Logged in Member’s WP Menu for Block Themes)
    • New BuddyPress network Theme implementation

Theme Development

  • BuddyPress.org theme development currently blocked
  • Potential collaboration with bbPress theme discussed
  • Challenges include complex WP meta setup, limited access, and need for simplified process

Add-ons

  • Hierarchical Groups plugin discussed as potential core add-on;
  • Plugin needs updates to work with Nouveau;
  • Further evaluation needed regarding total planned add-ons.

📆 Next Dev-Chat Agenda

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

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

Unknown's avatar emaralive 2:11 am on November 9, 2024
Tags: , ,   

BP Docs-Chat Summary October 30, 2024

As happenstance would have it, this docs-chat meeting occurred without an agenda, without a designated lead/facilitator and commenced 30 minutes late. What follows is what transpired during the remaining 30 minutes.

BP Documentation tracker status:

The stats – 59%, which is an increase of 1 (one) percentage point – 58% ➡ 59%

NOTE: There are 2 issues that are currently “In Progress“. For details see the “In Progress” section (Note: Project views are dynamic and are subject to change without notice).

Open Floor:

BP REST API V2 Documentation:

During this conversation, @im4th indicated that his strategy for the v2 (version 2) documentation was to complete the main endpoint routes before moving on the the others.

  • At the time of this summary, there are 7 (seven) documents that have been completed:
    • Introduction
    • Activity REST API routes
    • Components REST API routes
    • User Groups REST API routes
    • Members REST API routes
    • Private Messaging REST API routes
    • BP REST API Reference
BuddyPress Constants Documentation:

During this conversation, @emaralive indicated there is some slowness in gathering information that will be used to describe each Constant due to interpreting what the coding reveals and what valid values can be used when defining the various Constants.

The BP_DEFAULT_COMPONENT was used as an example, as this Constant has multiple valid values that can be defined, however, previous documentation and comments in the code only provide information regarding when this Constant is “undefined” or when the value is defined as “profile“. In short, when defined, invalid values can cause unexpected behavior thus, it is important to list the valid values.

Additionally, the BP_DISABLE_AUTO_GROUP_JOIN Constant is slated to become deprecated when Trac ticket #9249 is implemented. This will require changes to the constants.md file (currently a rough draft) and code related to the Site Health Info page/screen – BuddyPress Constants panel.

Further conversation led to when the BP_ENABLE_MULTIBLOG Constant would be deprecated since earlier in the year there was mention of such an occurrence, of which @im4th indicated that, perhaps, after several future major releases had occurred. The conversation segued into the buddypress.org domain since the WordPress Meta Environment (deprecated) contained use of the BP_ENABLE_MULTIBLOG Constant which then further segued into various past and present subdomains of buddypress.org, just to name a few:

  • fr.buddypress.org – (French) – available, but no longer maintained
  • es.buddypress.org (Spanish) – no longer available
  • nl.buddypress.org (Dutch) – no longer available

Lastly, @im4th mentioned that he was improving BP (BuddyPress) to “play nicer” with WP (WordPress) Playground and had also noticed that WP Playground team was making use of GH (GitHub) pages for its documentation which was built with Docusorus.

Next Docs-Chat

Our next documentation meeting will happen on November 13, 2024, at 19:00 UTC in #BuddyPress.

#docs-chat, #documentation, #summary

Unknown's avatar Renato Alves 5:14 pm on November 3, 2024
Tags: , ,   

BP Dev-Chat Summary October 23, 2024

Release Schedule for Version 15.0.0

  • Beta 1 Release Date: November 5, 2024
  • Final Release: End of November 2024 (after WordPress release on November 12)
  • Timeline allows 2-3 weeks for Release Candidates

Version 15.0 Updates

  • WP Playground Integration
    • High priority ticket (#9207) to improve compatibility
    • Will help demonstrate BuddyPress works correctly in clean environments
    • Team discussed its value for debugging user issues
  • Some major features being postponed to 16.0+ (both need additional testing):
    • Site Notices Feature (#9098)
    • Member Signups Component (#9057)

Mentee Opportunities

Several challenges presented for mentees:

  1. CSS work on Twenty Twenty-Five theme integration
  2. React development for Block Themes
  3. Group activity loading bug investigation
  4. Opportunity to write Beta 1 release announcement

Security Update

  • Version 14.2.1 security fix received plugin team approval
  • Team emphasized security as top priority over feature development

Development Tools

  • Discussion about local development setup
  • WP Playground highlighted as useful debugging tool

📆 Next Dev-Chat Agenda

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

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