Displaying 1 To 7 Of 7 Comments Some Orgnizations And WordPress Just Don’t Mix The only thing that fixes any of these issues is committed labor. “They” are us, let’s not forget that. There is no shortage of opinions, there’s a shortage of quality and committed laborers that are willing to put in the time and effort to complete tasks and create v2′s and beyond. » Posted By John James Jacoby On January 11, 2012 @ 2:49 AM Thanks Jeffr0! Happy to help with anything that I can! I missed the past few weeks but I’ll be tuning in again soon. » Posted By John James Jacoby On November 1, 2009 @ 5:51 AM Is A Plugin Validation Team A Pipe Dream? I think leaving the repository open with some behind the scenes code validation makes the most sense. I haven’t seen a deliberately malicious plugin yet, and I have a feeling if it existed it would get pulled down pretty quickly. I think the fundamental reason why WordPress has gained the popularity that it has, is because even a novice can join in and learn with the pros. Everyone is at a different stage of experience and knowledge, and there are bound to be flaws and bugs in just about every plugin out there when someone higher up the ladder looks down at it. I agree that the “just because it works doesn’t mean it’s right” philosophy is one that as a developer you have to adopt fairly quickly, but not everyone has the resources to have their plugin combed through. What I would hate to see is for the repo to follow the iPhone Store way of life and start rejecting or removing plugins. WordPress has always respected its legacy and the code it left behind, so if a stagnant plugin is sitting there and maybe needs some TLC, in our GPL open source world someone is free to pick up that lost code and give it a new home. If plugins were removed or rejected, that option disappears. Imagine the kid that’s submitting their first plugin to the repo, waiting anxiously to show their friends what they did, only they get an email two days later saying it was rejected. With that kind of setup, it breaks their spirits and maybe makes them stop trying. With the current setup, they submit their code to the repo and if people download it they can give feedback to the developer via the wp.org forums, so that kid can learn from their peers and grow to be a better developer. If there’s going to be a community of developers combing through plugin code looking for vulnerabilities or exploits, I hope it’s a positive experience for everyone and it’s treated like the customer service/public relations interaction that it is and that it happens pretty transparently. » Posted By John James Jacoby On September 30, 2009 @ 4:57 PM First Signs Of WordPress Using BuddyPress With Project Wide Profiles At the moment you’ll need to friend request each other through Buddypress.org. The new WordPress.org profiles area is SUPER new; so new they haven’t even made a blog about it themselves, so there’s some things that are sort of just hanging out there waiting to be used or opened up. » Posted By John James Jacoby On September 3, 2009 @ 8:23 PM BuddyPress Takes bbPress Integration Up A Notch I’ve spent the better part of two days testing this, and I have to say it’s a great, great thing. It plays friendly with existing installations if it has to, but I think once people get used to seeing how this works, and the way (like donncha mentioned above) that this allows people to break free from a single forums section and turn this into forums with purpose, it only makes sense to let BuddyPress do the work. The way that BuddyPress is developed also opens the door for other plugins to tap into the forum creation API, so it’s possible to have forums that aren’t just for groups, but maybe events, or blogs, or any other type of object that is centered around users in a group-esque fashion. This isn’t a 100% complete setup yet, as there isn’t a forum directory or a global tag search yet, and things like forum/subforum relationships or groups with multiple forums aren’t implemented. But, it’s safe to assume that much of the bbPress functionality will be mirrored in BP by the time 1.1 comes around. » Posted By John James Jacoby On July 24, 2009 @ 12:00 AM @Andy Peatling – Couldn’t have said it better meself. :) » Posted By John James Jacoby On June 3, 2009 @ 9:44 PM This is really not any different than what’s been happening for years now… Let me paint a picture… Every new version of WordPress that comes out is promptly followed by a supplemental version of WordPressMU, which introduces all of the new .ORG changes into MU. All that will eventually happen, is that .ORG and MU will join up and have 1 installation that asks “Would you like one blog, or many blogs.” And I suspect the answer to this question isn’t permanent, considering it’s totally possible to install WPMU and only have 1 blog. So maybe “merging” isn’t the right word to use when talking to developers that want to know how it’s going to impact them. The answer is that it really won’t. The audience that just wants one blog will continue to have the same plugins working the same way they do now. Users wanting a community with more than one blog will want to use plugins that focus on the USER on the SITE versus the BLOG, just like BuddyPress does. Really, as soon as the 2.8 changes make it into WPMU, I suspect that wordpress.org code will just turn into MU code, but still be called .org. Clear as mud? Haha! This is all just my speculation at this point, but I think from a developmental standpoint this makes sense, and would even make sense if you were looking at this from a long term perspective… Branch apart MU, to figure out a way to make one WordPress installation support many blogs. Okay, got it pretty well mature and figured out. Now, merge it back in and have the new more intelligent code replace the old stuff. Done. Then again, dogs and cats could be living together, and this could be mass hysteria; I really have no idea. :) » Posted By John James Jacoby On June 3, 2009 @ 5:08 PMComments Posted By John James Jacoby
«« Back To Stats Page