Forum Replies Created
-
In reply to: Buddypress 1.7
If you’re starting a new site with BuddyPress, and are a developer, you should be using trunk. By the time your site ships, so will 1.7.
In reply to: Bizarre avatar Issue After BP 1.6.2 UpdateFixed with WordPress 3.5. Closing this.
Confused. You say it’s our code, but you link to something you wrote yourself. Also, consider that it’s a weekend, and that we’re as entitled to days away as you are.
In reply to: Why is my custom component inactiveDid you mean this page:
https://codex.buddypress.org/developer/plugin-development/component-api/
In reply to: [Resolved] Sitewide & Group ForumsIf you didn’t convert them over using: Tools > Forums > Import, then you’ll be fine.
In reply to: how dangerous is it to delete buddypress?Deleting and replacing the files themselves is non-destructive. You’re fine to do it.
In reply to: Buddypress Themes MissingSorry about that. Put up a message for now explaining why the page is vacant. We’ll have something fun there next weekish.
In reply to: Registration sign in missing on installCreate the page, and set it in Settings > BuddyPress.
In reply to: [REQUEST] Fix BuddyPress’s Gravitational Orbit.@michaelecklund BuddyPress is built with the intentions of scaling into millions of users, something individual WordPress sites were not originally intended to handle. Shoving everything into a WordPress post type/taxonomy is not the answer, and does not solve any immediate problems.
Square pegs, round holes, and all that.
Thanks for the feedback.
In reply to: has anyone converted BP forums to bbpress?* Backup your database (you may need to restore if migration fails)
* Disable BuddyPress’s Forums component
* Tools > Forums > Import
* Choose bbPress1
* Run the converter
* Visit Tools > Forums
* Run all of the repair tools (most likely one at a time)
* Visit Settings > Forums
* Make sure “Enable Group Forums” is checked
* Make sure the BuddyPress root forum is correct
* DoneWhy do y’all think calling people names is going to help anything? That’s pretty silly.
Closing this topic, since it’s another one that’s all about criticism, and not about execution.
Through-out BuddyPress’s life (since 2007) numerous people have come into the forums and demanded change, talked about how much they dislike everything, and “if only we’d do X” that person would finally be able to do Y and Z, and it’s totally “the core team” that are holding them back.
That’s crap.
You’re an editor on the codex; if you want to edit, no one is stopping you. If you want to improve the organization of the pages and content, great — do it!
Instead, you want a “clean slate” to work on indefinitely until you feel a brand new codex is ready to ship? I’m afraid to ask how long you realistically think it will take to document 5 years worth of 100k lines of code, and why you think doing something manually is more effective than writing software to automate the process — see PHP Documenter?
Your logic, and approach, are flawed.
I just want people to share their experiences and knowledge, and that’s what the codex allows. Any time or work anyone is willing to put in above and beyond that is awesome, but we need less ideas, and more execution.
—-
What I won’t tolerate is the irony of you coming into our support forums, being disrespectful, then *demanding* respect because you have an idea about doing something you haven’t actually done yet. Note: since the beginning of the BuddyPress Codex, you’ve modified 1 page, 11 times, in the past 2 days. Total, we have 155 pages, and 3,040 total page revisions. Your contributions amount to 0.3% of total changes.
How you think you’re the guy to jump in and fix all our problems, is confusing to me. The only way to clarify this confusion, is to actually put some time into the codex!
Look… I’ll respect you no matter what you do, but I won’t trust your leadership until you treat other members of this site with with the respect they’ve earned and deserve… then you can have the keys to the codex after you start acting out your good intentions.
Until then, any contributions you give are appreciated, and will be well received. I’m sure you’re willing, and able, now all you have to do is execute.
My point is simply give people the documentation they need to participate.
Is there something preventing you from doing this that I can help with?
The “if you don’t do %, you’re going to lose %” attitude isn’t a great motivator; it’s leading with fear, which isn’t how I choose to lead my projects. Future development will cease when the project is no longer relevant; that will be a sad day, but it isn’t anytime soon. BuddyPress is as strong of a project as it’s ever been, so worrying about it’s future is wasteful.
A few things:
Manually writing documentation about code, is an infinite loop, where no one is satisfied. Code changes quickly, line numbers change, hooks change, things get deprecated, and one becomes a bottle neck for the other.
If you want to write pages on the codex, have at it. The taxonomies can change, we can add new ones, remove ones that aren’t helpful, whatever we want. Ultimately, I picked a few taxonomies that seemed to fit the project at the time, just to have *something* since before, we literally had nothing at all.
Regarding setting up a forum for the codex we have one: https://codex.buddypress.org/team/
Regarding having longer, slower release cycles, it’s not going to happen. If anything, they’ll get smaller and faster, with less code changing more frequently.
Releases shouldn’t be held because of out-of-date documentation, and the documentation shouldn’t wait until the release. It’s a wiki for a reason, and if you’re passionate about doing the documentation labor, you’re free and able to do it. If it’s not satisfying or rewarding for you, no one expects for you to do it. Obviously, we want to create an environment that’s fun to work in, and it’s my responsibility to make sure that happens.
Regarding feeling dismissed, try to keep the negative emotions out of this. No one here wants anyone to feel bad, and the people that do work themselves out. Reread for tone and clarity, and understand that we’re all passionate, and just want to do good things together.
Codex contributors are not more or less important than anyone else, but the BuddyPress Core team is going to make the decisions about code changes and release cycles, and that won’t likely ever change.
The fact is, that documenting an open-source project is neither glamorous nor sexy, an it’s easy to feel like you’re efforts are not appreciated. That last part’s not true, but since there’s no obvious or advertised audit trail, and no reward system in place, people working on the codex are often separated and in the dark about what’s going on around them.
If you want to keep up, you just have to try harder; no one is going to slow down for anyone else. As an example, I’m often in the dark about what’s going on in WordPress core, so I spend an extra 2 hours every night reading through the changelog, testing BuddyPress against WordPress trunk, and generally just spend more time doing more labor. It sucks, but I can’t ask them to slow down production and put their initiatives on hold.
It’s ironic y’all want to move towards the way the WordPress codex; many of their documenters strongly dislike Mediawiki for this purpose, and want to move towards a WordPress based approach like we have here.
Anyways, this is all good and healthy debate, but in the end it comes down to earning the right to have your opinion carry more weight than someone else’s, the old “meritocracy” approach. “Assigning a project manager” isn’t how this works. It’s an open system where everyone volunteers their efforts, and if you volunteer a higher quality of work more efficiently, you win the game and get to start making decisions.
Regarding having ducks in rows, ducks organize themselves into the pattern that suits them best at the time. It’s great to want to lead the pack, but you don’t self-appoint in an established and mature project.
Metaphors and responses aside, what 1 thing can I do immediately to improve the codex experience? Let’s pick 1, and talk about it, and make a decision on what to do about it.
Creating a child theme and forking an existing plugin seem like a lot of extra work. What was wrong with contributing a patch upstream to one of the other follower plugins?
In reply to: Search Buddypress Support Forum??Criticizing and complaining isn’t the way to motivate anyone to volunteer anymore time than they already do. You don’t like it? Neither do we, and we’re working on fixing everything up, similar to what we did to bbPress.org.
It’s okay to be frustrated, but it’d be great to channel that passion into something positive.
In reply to: Should my team fork BuddyPress?Coming into our support forums and asking us if you should fork our software that’s still in active development is pretty silly. If you want to fork it, go. We’ll miss your contributions, but kindly talk about your future endeavors in your own support forums.
In reply to: Add Profile link to WP Custom Nav Menu@shawn38 – Firstly, thanks for the kind words. Secondly, if someone wants to try and charge for a plugin, they are free to do so. Also, telling someone you’re not trying to attack them, and then attacking them, isn’t going to yield positive results. If you don’t have anything nice or helpful to contribute, it’s best to keep it to yourself, or that you share it outside of these support forums.
(Emailed @shawn38 privately to continue chatting.)
In reply to: User Registration ProblemsI’m all for people helping people, but please take this conversation into email, chat, or someplace else.
Closing.
Not the place to vent your frustrations. Closing this.
In reply to: Manually Access Installation Wizard@ffadler – open up your favorite database manager, and search the options tables for anything that looks like ‘bp-db-version’
We’ve changed the option key over the years, so it’s possible something is someplace it’s not supposed to be anymore.
In reply to: BuddyPress Plugin Directory – is it broken?Fixed. Might break again. Keeping an eye on it.
In reply to: BuddyPress Plugin Directory – is it broken?Yes. Working on a fix.
In reply to: Please Delete our BP account and PostsSorry that you feel that way.
I’ve looked through the topics, and for what it’s worth, I don’t see any hostility towards you from anyone on the BuddyPress team. Probably not what you want to hear, and probably not unexpected.
I’ll happily remove access to your account if you’d like to be prevented from using it in the future, but we don’t delete user accounts anywhere on the WordPress.org family of sites.
I’m replying to your emails to Paul now, and it would be great if we speak directly for any issues regarding your account going forward.
Bumping this, since it still sounds like a neat opportunity and I’m curious what progress was made.
