[buddypress-trac] [BuddyPress Trac] #9204: Review our release process + enrich release lead's role

buddypress-trac noreply at wordpress.org
Sun Jul 7 04:16:37 UTC 2024


#9204: Review our release process + enrich release lead's role
------------------------------------+-----------------------
 Reporter:  imath                   |       Owner:  imath
     Type:  task                    |      Status:  reopened
 Priority:  normal                  |   Milestone:  14.0.0
Component:  Documentation           |     Version:
 Severity:  normal                  |  Resolution:
 Keywords:  dev-feedback has-patch  |
------------------------------------+-----------------------

Comment (by emaralive):

 @espellcaste,

 I would open a ticket, however, I believe that I don't possess the
 requisite privilege(s) to do so with the **Type** __''option''__ of
 "**task**", the only options available to me are:
 - defect (bug)
 - enhancement
 - feature request
 None of these **Type** __''options''__, that are available to me, seem
 appropriate. So, in lieu of a ticket, I can create a topic in
 **Discussions** within the **bp-documentation** repo since this would be
 related to a discussion related to documentation. I'll try to get that
 accomplished during the upcoming week (Week 28, 2024).

 On another note (another rabbit hole, I fell into), to include @imath, I
 believe there is an issue with **"Props"** because they don't appear in
 **User** profiles for Activities. Apparently there are 2 different
 processes according to the WP Core Handbook -
 [https://make.wordpress.org/core/handbook/best-practices/contributor-
 attribution-props/ Contributor Attribution (“Props”)], specifically:
 - [https://make.wordpress.org/core/handbook/best-practices/contributor-
 attribution-props/#wordpress-develop-commits-in-svn wordpress-develop
 commits in SVN]
 - [https://make.wordpress.org/core/handbook/best-practices/contributor-
 attribution-props/#github-repositories-merge-commits GitHub
 repositories/merge commits]
 For **SVN commits**, apparently there should be a "**.**" (period, dot) at
 the end of the **Props** row. If you take a look at comment
 [https://buddypress.trac.wordpress.org/ticket/9204#comment:6 #6] for this
 ticket you will find the **Props** written as:
 {{{
 Props espellcaste, vapvarun, emaralive
 }}}
 Which appears to be missing a "**.**" (period, dot) at the end of the row.
 Thus, the **Props** row should be written as:
 {{{
 Props espellcaste, vapvarun, emaralive.
 }}}

 In each of the the profiles there should have been an entry, something
 similar to:

 Mentioned in [13948] on !BuddyPress SVN:
 **Update release process & release lead's role**

 I'm guessing !BuddyPress is written as such because I have no examples
 other than examples from **Core** which substitutes "Core" for
 "!BuddyPress".

 As for the **GitHub repositories/merge commits**, the process is different
 and @vapvarun mentioned the **!WordPress/props-bot-action**, during the
 last dev-chat (July 3, 2024), of which he may have alluded that there was
 an issue. The **Props Bot** is also mentioned
 [https://make.wordpress.org/core/handbook/best-practices/contributor-
 attribution-props/#props-bot here].

 How the **Props** process should work is very unclear to me because the
 only mention of **Props** within !BuddyPress documentation is found, maybe
 this is ironic, within the
 [https://github.com/buddypress/buddypress/blob/master/docs/contributor/project/release
 /build-checklist.md#preliminary-tasks Building a new BuddyPress release -
 Preliminary tasks] document item !#2. The irony is that this document is
 part of this ticket and does not lend itself to where one might find out
 how to correctly address **Props**. Referencing the **Core Handbook**
 isn't ideal since it makes references to !WordPress; meaning !BuddyPress
 needs it's own rendition of the **Props** process which I alluded to in
 2nd paragraph of my previous comment (comment
 [https://buddypress.trac.wordpress.org/ticket/9204#comment:5 #5].

 Last but not least, as previously mentioned, I'm unclear as to how the
 **Props** process works or should work and I don't know if what the
 !WordPress Core Handbook has laid out is applicable. All I know is that
 "Proper respect" a.k.a., Contributor Attribution (“Props”), are not given.

-- 
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/9204#comment:10>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac


More information about the buddypress-trac mailing list