This is not an official BuddyPress community statement just something to think about when choosing a name for your themes and plugins…
It even gets more confusing because the BP-Media team originally had uploaded a plugin called BP Album+ to the .org repo and then started coding a separate media plugin not officially released and under development for a few years.
rtCamp are claiming they uploaded their plugin to the .org repo first so they should get to retain the name “BuddyPress Media”. First come sounds fair, right? I never even heard of rtCamp’s plugin until months after the BP-Media’s plugin was in development. This is probably because of the name rtCamp chose, “BuddyPress Media”. I assumed it was the same plugin as BP-Media’s.
How to fix this mass confusion is very simple; DO NOT use BuddyPress in your theme and plugin titles.
rtCamp states that if naming was an issue then it would not have been allowed in the .org repo. Just because something can be done doesn’t mean it should be done. I’ll explain why this argument is false….
BuddyPress is the brand name for the BuddyPress plugin, not add-ons. By using “BuddyPress ****” in the title it is misleading. Only officially endorsed projects should use “BuddyPress ***”.
Months back BuddyPress project lead John Jacoby asked me to remove the word BuddyPress from all my plugin titles. John didn’t want people to confuse 3rd party plugins for officially sanctioned BuddyPress projects. He said that even though people have been allowed to use the BuddyPress name in plugins, it may not be the case in the future. I challenged this stating the very arguments that rtCamp is issuing now.
At first I was offended, how could John tell me this without announcing it to the whole community? Where’s the official statement that BuddyPress should not be used in plugin names? There isn’t one, but I’m here to suggest you not use BuddyPress in your plugin title.
A few reason why:
- It creates confusion (BuddyPress Media as an example)
- Creating your own branded plugins keeps you in control (less confusion + future proof naming)
- You can trademark a name that doesn’t include BuddyPress
In the WordPress Codex the only thing it says about n#Plugin_Name">plugin naming: “think about what the Plugin will do, and make a (hopefully unique) name for your Plugin. Check out Plugins and the other repositories it refers to, to verify that your name is unique; you might also do a Google search on your proposed name. Most Plugin developers choose to use names that somewhat describe what the Plugin does”.
Using “BuddyPress Media” is not unique. Someone else could just as easily create a plugin with the same name and further instigate confusion.
What is acceptable?
When John had contacted me about changing the names of my plugins, I asked what would be acceptable. He didn’t officially say either way but we tossed a few thoughts back and forth. I suggested allowing the **** for BuddyPress title to be used. The WordPress repo is searchable but it’s difficult to find a real BuddyPress plugin because non BuddyPress plugin developers tag non BuddyPress plugins with “buddypress”. John said the main reason plugins are allowed to be uploaded with BuddyPress in the title is that it was better to just get plugins uploaded then worry about policing. The community needed exposure. Agreed.
Apple even with their strict rules allows the use of iOS when you use “**** for iOS”. It’s a clear statement that **** IS for [whatever service].
My suggestions for naming:
**** for BuddyPress
Media Pro for BuddyPress
Another Related Posts for BuddyPress
Even better is to use something unique. I have chosen to use Buddy+ a word to describe what the plugin does, BuddyMobile. The media teams could choose something like, BuddyMedia or Media Buddy.
Just think about these things when naming your plugin. Make it unique. People appreciate originality + good functionality.