Search Results for 'code'
-
Search Results
-
An extremely, over exaggerated word that has been used to change the developmental focus of bbpress is Integration.
Its time we address this burdening issue and close the book on this 2 year old bug, mental or developmental. And to do this we will collectively discussion what integration is, what its not, and what is best for the bbpress project and community in the long run.
1st. One of the most important points that I would like to express is, Integration doesn’t mean Plugin. I could talk till im blue in the face on this, or link old posts where unknowing users use the words interchangeably … but its easier to point to this open and active discussion
http://bbpress.org/forums/topic/bbpress-a-plugin-or-independent-software-with-integration
Integration can mean, user integration, data sharing, shared user profiles etc. This doesn’t have to be just WordPress, but if bbpress is reduced to nothing more than a WordPress plugin, than the future of bbpress is contingent upon wordpress not to mention the effects this has on development “which is evident”
I wanted to keep this topic short and to the point, but isnt to say i wont weigh in with lengthy replys
To end this chapter of confusion and to get bbpress back on trac, on February 14 I propose a IRC meeting which will follow with a blog post of the results with a roadmap for the future.
For what it’s worth, I nominate chrishajer as bbPress Project Lead.
It was brought up as an excellent next step in the thread linked below that Matt closed.
http://bbpress.org/forums/topic/whats-happening-with-bbpress
@chrishajer, I’m not sure if you will accept this nomination. If you do, I’m definitely willing to donate $100 to you to help augment your expenses. I know it’s not much but it’s what I can budget right now.
Reason why I believe chrishajer is the most qualified:
* To date, chrishajer has been the only remaining devoted lead of bbPress. To my understanding, it’s also the only moderator of this forum beside Matt.
* chrishajer understands the needs of what bbPress users want. He also understands what’s need for a product be successfull, such as: setting release dates, establish features & bug fixes to work on, etc
* people respect chrishajer and would easily take lead from him
[EDITED title chrishajer 11 Feb 2010]
Hi:
I discovered an issue that I just wanted to share:
I installed bbpress in a subdirectory of WordPress without integrating. I used a new database and did not touch cookie integration. There are no plugins or content, as this installation is just for building a new child theme.
My WordPress child theme was designed using the Thematic theme framework. Now, I’m trying to design a bbPress child theme with the Hybrid theme framework.
However, my bbpress child theme will only refer to my WordPress Thematic child theme stylesheets in a completely different directory. This was even true when I tried to hardcode the @import lines in the bbpress child theme functions.php file.
I don’t know the solution, here, but thought I’d share for anyone else. If you want to test a child theme on your server, make sure you don’t install bbpress in a subdirectory of WordPress. I don’t know yet if it will work when I integrate WordPress and bbPress, but I assume it does since so many have already done that.
Topic: Premium Theme's and Plugins
I was hoping that someone could point me towards BBpress or Automattic’s official stance on this. From what I’ve read, the PHP code that interacts with WordPress/BBpress should all be released under the GPL, but HTML/CSS/JavaScript/Images are not.
I bring this up, because a fellow developer (an old Bbprogress contributor), pointed me towards this piece by Jeff Chandler: http://weblogtoolscollection.com/archives/2010/02/08/where-is-the-line-drawn/
The main thing that caught my attention was the comment of Chip Bennet , who states that:
[a] plugin uses a separate library – and it is that library (presumably not released under GPL) that requires purchase if it is used on a commercial site.
This practice is perfectly acceptable under the GPL. Whether or not it is acceptable under the double-secret probation, unwritten, subjective rules of the plugin repository is anyone’s guess.
Can anyone shine some light on this from a BBpress perspective?
I’m going to quote Matt here:
…that themes link and use lots of internal WordPress functions, which make them linked under the GPL and subject to being a GPL-compatible license.
If a theme (or a plugin) used no internal WP functions or APIs, then it could probably be considered independent, but that would be really really hard for a theme.
Basically, I’m asking because BBpress, probably more than WP (at least if you’re only using WP as blog platform) has potentail for premium theme’s and plugins at this moment in time. Getting some clarification would make things alot simpler.
My real concern here is one that won’t go down well…
BBpress forums have 1 current/active moderator
I ask for two reasons.
Should a premium theme/plugin be created and sold, and given that BBpress currently has 1 active Moderator, what is there to stop someone posting the code here or reusing the code that is NOT under GPL?
Not a huge concern of mine just now, but it seems like a likely question of anyone supporting premium BBpress additions.
). All I’d need is to possibly be informed on new features or functions that I could design for. I could come up with cool mock-ups, and if the community likes it, I could chop it up into a theme.
)