Forum Replies Created
-
Agreed having some kind of method for BP installs to talk to each other would be pretty awesome. It would require breaking out of the ‘central server’ type method that I think we’re all used to and really require a robust api underneath everything.
Patches welcome!
@rogercoathup Happy to talk privately about why I opted to block the person in question from buddypress.org. Don’t want to air the dirty laundry but rest assured it takes quite a bit to get to that point.
@paulhastings0 Very little ‘risk’ but you’re on the right track. IMO one of the harder things about running such a large project is deciding what belongs in the core and why. It’s something that Andy was really strict about and did a great job of training me on because I was anxious to learn and asked for feedback with every patch I submitted for more than a complete calendar year before asking if he could use more ‘official’ help. You can look back through my commit history and see a few blunders here and there, as they’re fairly easy to make when you’re bouncing between installations. Every one of the guys you mentioned (including @cnorris23 and a few others) are the top of the list of being considered for core commit access. You could say it’s the next step on the ladder for each of these guys and they all deserve the promotion fairly equally.
If/when it comes time, it will be a hard decision to make.
Don’t thank me, thank @r-a-y!
Bulk member moderation is on the roadmap somewhere, at least it used to be and would be very useful.
Quick thoughts from my iPad…
For there to be more core committers, there needs for there to be more outstanding core patchers. There are a handful of great ones already, and they are noticed and recognized for their contributions. The leads are Andy and myself, and ultimately the future of the core project is decided by us. Very similar to WordPress, we keep an eye on developer plugins to look for anything that would make a good core feature.
Feature requests are great when there are people to do create them, but the best place to talk about core development is on the trac. The forums are more for support and discussion than they are for code talk, but part of that is also because currently the forums don’t play nicely with code blocks.
I don’t think we’re closing threads unless the discussion goes severely off topic or is no longer productive. If we are, I would agree that we shouldn’t be locking topics prematurely. Regarding the codex, anyone has the ability to modify it, so if anything is out of date anyone is free to fix it.
I also agree that things will be easier for us and make more sense when buddypress.org is a website worthy of being in its own showcase. Right now it’s a basic install with lots of custom bits to help integrate wp.org plugins.
It hurts to just add committers for the sake of having committers. Commit rights are earned through writing great core patches and showing a comprehension for the direction of the core project. There are plenty of great plugin devs that have written thousands of lines of their own code, but haven’t directly contributed to core.
Ultimately it would be great if we had one developer per core component to focus on it’s future, but so far no one has showed initiative to want to make improvements to anything. Right now we’re in a transition period where the branch and trunk need to be merged before I think a few more people are comfortable writing giant patches, but that time will come.
Paul hit almost every nail on the head in his reply above. It’s great that you see the need, now fill it.
It will get a sweep through for 1.2.6.
I have a surprise for you in the 1.2 branch of code. Check it out.
