• See previous BP Docs-Chat Summary January 22, 2025
• In attendance: @dcavins, @narenin (async), @1naveengiri (async), @Mark-Andrew (async), @emaralive
• Slack Archive
• @emaralive will lead the next docs-chat 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. Additionally, user handles are taken from their respective Slack accounts and may not match up to WordPress.com accounts.

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.

Revisiting the “Building a new BuddyPress release” document.

This has been a topic of discussion in the past and will, on occasion, continue to be a topic of interest until sufficient clarity has been incorporated into this document. As a general example, there are a number of assumptions that may cause some confusion with the “build process”, e.g., some individuals may be “rate limited” while trying to perform a svn checkout, along with missing information that may result in an improper build, e.g., there is no mention of changing the db_version, let alone, how it is determined for a Major build.

In short, relevant information may exist in other documents that could be used as references that would augment the “release” document. There is an open issue ([Update]: Building a new BuddyPress release – document #300) that was created December 9, 2024 which contained some preliminary thoughts for updates, however, since this time other considerations for updates appear to be warranted and said issue has been updated to reflect these additional thoughts.

Open Floor:

There wasn’t time available for Open Floor.

Next Docs-Chat

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

#docs-chat, #documentation, #summary

• See previous BP Docs-Chat Summary January 8, 2025
• In attendance: @dcavins, @narenin, @emaralive
• Slack Archive
• @emaralive will lead the next docs-chat 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.

Labels to identify the priority level for documentation issues:

See bp-documentation project for example (High, Medium, Normal) of a previous proposal. Additional, conversation indicated that there would be no more than 3 (three) priority levels. Perhaps, in reality only 2 (two) would be needed, e.g., High & Medium.

There was a question as to the current examples were intuitive enough for someone to know that a priority level was meant and whether an adjective such as “Priority” or maybe an abbreviation of thereof or a different scheme, would be necessary. The jury is still deliberating over this question. Maybe try as is and then adjust later if confusion abounds. For the record, the WordPress Docs team utilizes, “high priority” and “medium priority” for labels.

Open Floor:

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

Conversation was mostly about “Spam” and “Clickbait” that appear in the BuddyPress Support Forums due to the New Year starting off with what seems to be an unusual amount thereof.

Next Docs-Chat

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

#docs-chat, #documentation, #summary

• See previous BP Docs-Chat Summary November 13, 2024
• In attendance: @dcavins, @emaralive
• Slack Archive
• @emaralive will lead the next docs-chat meeting!

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 and completions remained the same.

There is 1 (one) issue that is currently “In Progress“. A previous issue (BP REST API for V2) had its status reverted back to “Todo“, pending the availability of a writer. 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.

There was conversation about some of the specifics regarding the BP REST API for V2 documents, e.g., There are, currently, a total of 6 completed and 1 semi-completed documents:

• BuddyPress REST API (v2)
• 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 (semi-completed)

This leave a remainder of 15 documents that require creation that were identified per the BP REST API Reference document.

An opening look at the Deprecation Policy for BuddyPress

Since this was an opening look, there wasn’t time to get to all bulleted items for this agenda item. There was a brief discussion on “deprecated filter hooks“, meaning not all items that had been previously deprecated have been identified and, for example, that the bp_is_profile_cover_image_active filter had been uncovered while researching a support forum topic.

The conversation moved on to “deprecated constants” since these have been identified. An example was shown between a WordPress implementation (deprecated_argument) vs the BuddyPress implementation (doing_it_wrong) and which implementation might make more sense to use. At this time, further discussion is warranted, since the practice/protocol for deprecation of specific items will be part of the rules that will be described by the Deprecation Policy.

Open Floor:

There was a brief discussion regarding the remainder (15) of BP REST API for V2 documents that have yet to be started.

Due to the upcoming holidays (Christmas and New Year’s day), there was a proposal to suspend the Docs-chat meeting until after the holidays, which will allow team members to have some sort of holiday break. The proposal was adopted, so, this will leave December 11, 2024 as the last meeting for 2024 and Docs-Chat meetings will resume in January of 2025, exact date of the 1st meeting in 2025 – TBD.

Next Docs-Chat

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

#docs-chat, #documentation, #summary