Profiles: Badges for BuddyPress contributors and team members

[netweb]

Per the proposal on make/community ​here is to add badges for BuddyPress contributors and team members

Choose a dashicon: BuddyPress Logo Dashicon: “\f448”;

Choose a badge color: BuddyPress: #d84800 ​https://codex.buddypress.org/official-fonts-and-logos/

Define criteria for getting (and, optionally, maintaining) the badge

• Team badge candidates would initially be drawn from a list of everyone who has ever made a commit to the respective project SVN repos. A rep for the team can vet the list for active members. If there are non-committing team members, they can be added as needed. Team badges are only assigned for the duration of a person’s active participation in the team (as assessed by the team itself). Badge assignments/removals would be handled manually going forward.

• Contributor badges would be assigned to anyone who has committed to the SVN repo or been given props in a commit. Contributor badges are permanent and automatically assigned (periodically, if not immediately). Manual adjustments (e.g. a typo in props) can be done as needed.

[netweb]

CC: @coffee2code, @mercime, @johnjamesjacoby, @djpaul

[netweb]

Just adding here that later today/tomorrow @mercime will upload some more/suggested example artwork for the BuddyPress logo/s after a discussion we had on the "circle" that surrounds the dashicons on coloured background for the team icon.

[mercime]

Attached image shows the following:
1) BuddyPress logo - for contributors and core team,
2) BuddyPress logo less outer circle border - for contributors and core team, and
3) BuddyPress logo buddies only - for contributors and core team.

Just found out that color I used was based on logo color #d94e27 not the #d84800 mentioned above. Still, SVGs using either color at 20px x 20px like the other dashicons can be provided should 2) or 3) be chosen.

P.S. rough draft. excuse the imperfect circles et al.

[DJPaul]

Of these, please use the last set, but let's have another pass at the images to make all the lines smooth and adjust the colour. Thanks very much for working on these!

[mercime]

@DJPaul Thank you Paul, will do. Yes, it was a rough rush job :)
I only need to create the "buddies" SVG because the round border and background will be rendered via w.org CSS in our profile pages. Just added them here scaled 1:1 so we can see how each one looks like.

[mercime]

BuddyPress team icon

[mercime]

@johnjamesjacoby, @djpaul, @coffee2code Attached is the SVG version of the BuddyPress icon used in the last set.

[johnjamesjacoby]

These all seem fine, though I agree with Paul that we'd want to clean them up as much as possible.

[melchoyce]

I agree option 3 is the best. I'd decrease the icon size a little so it fits better within the circle. See these icons for an example: ​https://cloudup.com/cGCp5Lp0eWC

[netweb]

Replying to melchoyce:

I agree option 3 is the best. I'd decrease the icon size a little so it fits better within the circle. See these icons for an example: ​https://cloudup.com/cGCp5Lp0eWC

Is the existing dashicon \f448 and/or buddies.svg​ we already have enough here or is something else required?

[DJPaul]

@netweb @melchoyce @coffee2code I'd like to pick this up again. We want to use the f448 dashicon with colour #d84800 (and pick a colour for the team variant background, whatever looks about right).

What needs to happen next? How can I help with that?

[ocean90]

I'm curious why BuddyPress should get a badge and other plugins not? What are the rules here? Can other plugin/theme authors request a badge too?

[johnjamesjacoby]

I'm curious why BuddyPress should get a badge and other plugins not? What are the rules here? Can other plugin/theme authors request a badge too?

If by other plugins, you mean GlotPress & bbPress, I think that's a great question. If you mean all 50k other plugins in the WordPress.org repository, I have a hard time believing you're not being rhetorical.

I'm curious why BuddyPress (and GlotPress & bbPress) aren't automatically blessed as official sister projects to WordPress. Is their status in question? Are they no longer worthy of being special-cased? Do we remove their links from the footer of WordPress.org? Do we remove them from the recommended plugins page?

I know not everyone agrees, and that year-to-year difference people express that some project deserves more or less exposure for one reason or another. I think, though, it's important for the overall health of WordPress, GlotPress, BuddyPress, and bbPress for them to always be perceived, communicated, & expected to be treated as equals, especially where there is little overhead in doing so.

As far as other plugins go, I actually do think that's an idea worth exploring and automating. We did something similar for BuddyPress plugins back in the day (around 2010?) though it became a bit of a maintenance burden for everyone working on WordPress.org at the time.

It'd be pretty cool if all plugins automatically got badges, and could upload their own icons into their assets directories. That would mean they automatically get "groups" in profiles.wordpress.org, which could later be used for all kinds of neat stuff.

[dd32]

Replying to ocean90:

I'm curious why BuddyPress should get a badge and other plugins not? What are the rules here? Can other plugin/theme authors request a badge too?

Since bbPress, BuddyPress, and GlotPress are sister projects of WordPress, and part of the same umbrella group I see no reason why they wouldn't be treated specially here.
Where I draw the line in the sand would be "Does it use WordPress.org infrastructure, and share user tables?"

I also see the other side of the coin though, currently the profile system is for WordPress community contributions; Core, Docs, Translation, Support, WordCamps, etc, it's not immediately expected to see BuddyPress or bbPress core contributions on there (I mean, even WordCamps seems a little odd in that context).
For example, do we add BuddyPress Docs badges too? or do they get the current documentation badge?

I also see benefit of adding "I contributed to plugin x" functionality to WordPress.org profiles in some way, but I don't think I'd encourage that for the current badge system, if only because it wasn't designed to scale that way.

[netweb]

FWIW, here's the related bbPress & GlotPress badges tickets, #1312 & #1314 respectively

[netweb]

Replying to dd32:

I also see the other side of the coin though, currently the profile system is for WordPress community contributions; Core, Docs, Translation, Support, WordCamps, etc, it's not immediately expected to see BuddyPress or bbPress core contributions on there (I mean, even WordCamps seems a little odd in that context).
For example, do we add BuddyPress Docs badges too? or do they get the current documentation badge?

The support team ​proposing to add badges for all language/locale forums, it has yet to be discussed if bbPress, BuddyPress, and GlotPress support contributors should also receive the relevant support badge though I don't see why they shouldn't, likewise for the docs badges and the bb's codex contributiors.

Edit: I don't think the bb's should have their own docs/support etc badges, the current badges would suffice

[ocean90]

Replying to johnjamesjacoby:

If you mean all 50k other plugins in the WordPress.org repository, I have a hard time believing you're not being rhetorical.

Yep, I mean all the other plugins.

Even if it's a sister project (to be fair, I don't why it matters) it's still a plugin. And for plugins we already have a badge. If you want to give your contributors credits I suggest to add them to the 'Contributors' field in the readme.txt. That's something we (the GP team) ​already do for GlotPress. If there are contributors who contribute through support or documentation they should get the docs/support badges.

[johnjamesjacoby]

Even if it's a sister project (to be fair, I don't why it matters) it's still a plugin. And for plugins we already have a badge. If you want to give your contributors credits I suggest to add them to the 'Contributors' field in the readme.txt. That's something we (the GP team) already do for GlotPress.

Absolutely not.

If that's what you're choosing to do with GlotPress, I think that's currently up to you to decide how deeply you choose to integrate it.

BuddyPress & bbPress aren't just some old plugins that deserve to get vetoed out of the community limelight. They are integral parts of WordPress's surrounding culture, community, and history.

You wondering why it matters is not you being fair. The teams of people behind these plugins should not need to fight to maintain their existing relationships every some-odd years. It's insulting, and - to be fair - an exhausting waste of time for everyone that is better spent literally doing anything else.

[Kenshino]

Will be discussed in the next Support Team Meeting - see ​https://make.wordpress.org/support/2016/08/august-18th-support-team-meeting-summary/#comment-172672 for the original suggestion

[JoshuaWold]

We just discussed this in the #design team weekly triage meeting. Based on the last comment it seems it was agreed that the icon should be present on the profiles of folks who have helped out on BuddyPress.

The feedback from our ​triage was to go for one logo to represent all contributions by BuddyPress team members. That simplifies things a bit by having a single logo, and then we can use the text area to explain the specific type of contribution.

Is there a reason why we'd need the logo icon to represent a different kind of contribution? If not we'd suggest only one logo and then text to differentiate.

It was suggested to go with this one:

[johnjamesjacoby]

I agree that the suggested logo matches best.

Also agree that 1 badge for all BuddyPress contributiors is OK. 👍

[dd32]

Fixed in r15415-dotorg

Profiles: Add BuddyPress and bbPress Contributor Badges.

Fixes #1312, #1313.

[coffee2code]

BuddyPress Team badge added in [15571-dotorg].