BP Docs-Chat Agenda April 10, 2024

Hi!

Our next documentation meeting will happen on April 10 at 19:00 UTC in #BuddyPress. Here’s our agenda:

• BP Documentation tracker status.
  • Phase 1 complete – BP Codex migration.
  • Phase 2 – Document creation/updating.
    • Discuss documentation tracker status metrics for phase 2.
• Follow-up on BuddyPress Multiblog & BuddyPress Multi Network
  • Review/answer comment by val cosgrave (@delpucci)
• Open floor.

If you have specific or additional points to discuss, please do so in the comments section of this pos

#agenda, #docs-chat, #documentation

BP Dev-Chat Agenda March 20, 2024

Hi!

Our next development meeting will happen on March 20 at 19:00 UTC (tomorrow) in #BuddyPress. Here’s our agenda:

• 12.4.0: let’s build this minor release soon (before WP 6.5)
• 14.0.0:
  • Do the Site Wide Notices feature needs to be reorganized (See #9098) ?
  • Considering the current 28 tickets, what will be the top feature(s) for 14.0.0.
  • Other ticket updates.
• Open floor

If you have specific/additional points you need to discuss about, please share them into the comments area of this post.

🌱☘️

#12-0-0, #14-0-0, #agenda, #dev-chat

BP Dev-Chat Summary March 4, 2024

• See previously BP Dev Chat summary February 19 (2024)
• In attendance: @dcavins @im4th @emaralive @espellcaste
• Slack archive

⏰ New development meeting day/time

@im4th suggested to change the day and time we meet to discuss about BuddyPress development so that it’s more suitable for contributors located in Asian time zones. Let’s come back to our “legacy” day/time: every other Wednesdays at 19:00 UTC!

@emaralive @espellcaste & @dcavins agreed (even during DST, 19:00 UTC can be problematic for David’s presence during 1st meeting half).

As Documentations chats are also happening at this day/time, we’re always meeting on Wednesdays at 19:00 UTC and depending on the current week number, we’ll be talking about development (even weeks) or documentations (odd weeks).

🧰 BuddyPress 14.0.0

Release lead: imath

@im4th asked if one of us was wishing to lead this release: @dcavins won’t be able to find the time to, @espellcaste volunteered to lead next major release. To let the time to @emaralive to experience a full release development cycle, @im4th volunteered & is the 14.0.0 release lead.

Ticket updates

To view the full tickets list slated for this milestone, go there!

• @emaralive hasn’t progressed yet about #8728 (Allow group moderators to moderate group activities).
• @espellcaste has put together a local site about BP CLI commands reference (See #9113).
• @dcavins has not progressed about #8794. It’s a pretty sensitive subject as it deals with capabilities in WP Admin. Best approach seems to be to build a specific & new Admin screen to let users having the bp_moderate cap to manage site membership requests.
• @im4th reopened #9101 as he was worried about the fact we’re adding 2 accordion sections to the site-health debug screen. It’s closed again as using a single section is not separating nicely settings from constants when using the copy feature.
• @im4th moved the ticket about improving Activity Favorites management out of the 14.0.0 milestone (See #5644). He was the only one of the team in favor of introducing Likes as Activity children and highlight this as one of the top features for 14.0.0. Users will need to wait for a future BP Relationships API.
• Without any news from @rayisme, he also moved the Followers feature (See #7133) out of the 14.0.0 milestone. Moreover the plugin’s scope is larger than following members (using it, you can follow activity or blogs for instance).
• @emaralive wanted to talk about #9098 as re-thinking the Site Wide notices feature can have implications about BuddyPress documentations. But we agreed to talk about it during our next development meeting as it was getting late.

Finally @im4th asked the team to use the 2 coming weeks to think about the 14.0.0 top features as @dcavins said “it’s nice to have a focus, so that the release accomplishes something that seems cohesive”. So far many of the enhancements slated for next release are to make administering a BP site easier.

14.0.0 schedule reminder

• June 3: 14.0.0-beta1.
• July 8: 14.0.0.

Next Dev-Chat

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

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

BP Docs-Chat Agenda March 13, 2024

Hi!

Our next documentation meeting will happen on March 13 at 19:00 UTC in #BuddyPress. Here’s our agenda:

• BP Documentation tracker status.
• Open floor.

If you have specific/additional points you need to discuss, please share them in the comments area of this post.

#agenda, #docs-chat, #documentation

BP Docs-Chat Summary February 28, 2024

• See previous Docs Chat Summary (February 14)
• In attendance: @dcavins @im4th @emaralive @vapvarun @espellcaste
• Slack archive

BP Documentation tracker stats

• BP Codex contains 271 pages.
• 202 total tasks were created (migrate + ignore + add + update).
• 194 tasks related to pages reviewed were created (migrate + ignore).
• 42  « migrate » tasks were created.
• 152 « ignore  » tasks were created.
• 5   « add     » tasks were created.
• 3   « update  » tasks were created.
• Approximately, 72% of a total of 271 pages have been reviewed (194 / 271)

There were various comments by @dcavins & @im4th in regard to the stats:

• @dcavins made note of the number of ignore tasks that were created and asked whether this was a indication of out of date documents.
• @im4th made note of the progress made and responded to @dcavins regarding out of date documents, e.g,, pre 1.7 information, Theme changelog, snippets of code, etc.
• @vapvarun & @dcavins conversed a little bit about the efficacy of code snippets.

Review of how WP Docs teams handle discrepancies with published documentation (2 examples)

Example 1 (one) was a DevHub (Advanced Adminstration Handbook) document and example 2 (two) was a HelpHub (End User – Support Guides ) document, of which the purpose was to plant the seed as to how the BP Team would/should handle user feedback:

• DevHub provided a link to GitHub Advanced Admintration repository.
• HelpHub provided a comment box, in which to provide user feedback.

@im4th made note of some confusion regarding the use of discrepancies (the meaning thereof), of which @emaralive provided a general meaning and @dcavins expanded the meaning to include suggestions for improvement. @im4th was initially of the thought to use a method similar to how DevHub handled the situation and wanted a concrete example. @emaralive mentioned that example 2 was an actual issue (the text and screenshots are out of date, from WP v4.9.6, approx.). To move things along and not to belabor the point of this exercise, @emaralive mentioned the opening of a Discussion topic within the document tracking respository whereby further dialogue could be advanced, n,b,, @emaralive still needs to open the topic.

Open Floor

Earlier @vapvarun mentioned he had some documentation related Pull Requests ready to go. During Open Floor @vapvarun indicated the following would be next up for him:

• Configure BuddyPress for Multisite ( possible cases )
• Installation in WordPress Multisite
• Languages and Translations

@im4th indicated the he would review the Pull Requests that @vapvarun had ready to go. During this Open Floor time, @espellcaste indicated that he had documentation (.md files) related to BP CLI that could be placed within the BP docs folder, however, @im4th had some reservations as to where the BP CLI documents should reside. Additiionally, @espellcaste indicated that he had plans to outline the workflow related to BP CLI documents and since we were short on time, I indicated that I would open a Discussion topic in the BP document tracking repository, of which, that discussion can be found here.

Next Docs-Chat

It will happen on March 13, 2024 at 19:00 UTC in #BuddyPress.

#docs-chat, #documentation, #summary

BP Docs-Chat Agenda February 28, 2024

Hi!

Our next documentation meeting will happen on February 28 at 19:00 UTC  in #BuddyPress. Here’s our agenda:

• BP Documentation tracker status.
• Review of how WP Docs teams handle discrepancies with published documentation (2 examples).
• Open floor.

If you have specific/additional points you need to discuss, please share them in the comments area of this post.

#agenda, #docs-chat, #documentation

BuddyPress 12.3.0 is available

12.3.0 is a maintenance release, please upgrade!

BuddyPress 12.3.0 maintenance release

🙏 🍕

#12-3-0, #maintenance, #release

BP Classic 1.4.0 is available

This new maintenance release makes sure bbPress pagination in single Groups/Members forums tab is behaving as expected. Please upgrade.

BP Classic 1.4.0

🍀

#1-4-0, #classic, #release

BP Docs-Chat Agenda February 14, 2024

Hi!

Our next documentation meeting will happen on February 14 at 19:00 UTC ( less than 12 hours from now!) in #BuddyPress. Here’s our agenda:

• BP Documentation tracker status.
• Member Types
• Sitewide Notices
• PHP version support
• Version numbering

If you have specific/additional points you need to discuss, please share them in the comments area of this post.

BP Docs-Chat Summary February 7, 2024

• See previous Docs Chat Summary (January 24)
• In attendance: @im4th @emaralive @vapvarun
• Slack archive

BP Documentation tracker stats

If you missed January 10 docs chat, We decided to create a new GitHub repository: bp-documentation, to use issues as Documentation tasks and to regularly update a GitHub project to track our progress.

• BP Codex contains 271 pages.
• 127 pages were reviewed so far.
• 40 « migrate » tasks were created.
• 87 « ignore » tasks were created.
• 144 BP Codex pages still need a review.

Reasons to ignore a BP Codex page:

• Codex page content is deprecated/outdated.
• Codex page content is a user generated guide containing code snippets.

@im4th thinks checking every code snippets is still accurate would take us too much time. The ignored content is not lost as it will remain into the BP Codex for history.

We think we’ll probably need to include an Advanced Users chapter to the User Handbook.

Contributing to docs is improving code!

@im4th has found bugs with our Site Health debug panel while working on documenting it. He’ll soon open a Trac ticket about it.

@emaralive found another one with Profile photos when the image file contains « -bpfull »or « -bpthumb » within its name.

@vapvarun suggested to create new documentation links closer to WP Admin sections using an information dashicon for instance, these links would direct the user to the specific anchor of the generated Markdown file view on GitHub.

And..

An help tab containing a link to the documentation page on each BP Admin screen

@emaralive started this discussion about it & @im4th thinks we should always have an help tab with a documentation link for any BP Admin screens we’re adding to the WP Dashboard.

Open floor

• We’ve decided to move the docs chat to every other Wednesdays that are a week after dev-chats. We’re starting next week on February 14 at 19:00 UTC. We haven’t changed the hour when we meet as 19:00 UTC is already very late for @vapvarun (he can’t currently contribute to dev-chats as it’s happening at 3 AM his time: we’ll need to discuss about it with other members of the team).
• Take turns leading the documentation meetings: @vapvarun will lead next one, @emaralive the one after, etc… @im4th thinks it can be interesting to do so as he might miss or do not stress enough some points others would have. Here are roughly tasks a leader should achieve:
  • Prepare the docs-chat agenda & publish it on this site.
  • Run the chat in #BuddyPress.
  • Write the chat summary on this site.

Next Docs-Chat

It will happen on February 14, 2024 at 19:00 UTC in #BuddyPress.

⏳♻️

#docs-chat, #documentation, #summary