BuddyPress.org

I have to agree with @ethanvan on this because there seems to be a you against us attitude going on here. If you can’t work together then nothing will be gained so I would suggest taking a deep breath and be a little more co-operative with each other. If there was more documentation in the codex it would benefit the project by giving developers the knowledge to the inner workings of the software and bringing in some fresh talent with some new ideas. It would also help the moderators here by being able to point the community members to the codex which documents their specific needs. With bad attitudes and being uncooperative then I definitely can see this project ceasing and its probably the same reason there has been a mass exodus in plugin development. I understand people are doing this for free, but if your going to do half efforts then your going to get half the results. How can anyone execute when they don’t even have a descent understanding of the code because nobody wants to waste their time searching for a needle in a hay stack. If proper documentation was in place it would boost development on every level. I am asking nicely for a little more team effort and less throwing stones because that will get nothing done in a positive manner.

@ethanvan I take you seriously but will the gleek club allow it. This seems a bit more like a dictatorship than a democracy because as I stated before it seems there is a you against us attitude and instead of being co-operative. Maybe the transfer of knowledge is frightening but we need to work together instead of against each other. I personally don’t care how long you have been with the project. I have led 24,674 combat troops successfully because we was one and trained as a cohesive unit, so have a better disposition when trying educate people on leadership when you are not really educated in this realm. I am tired of people who live in glass houses casting stones. I would be ashamed of myself to do such. Especially when there is people willing to restructure the documentation that should have been there in the first place. Allow others to help with this project so it can continue to thrive instead of pushing them away. Get your ego’s in check because I think its throwing your judgment off. This goes for everyone because there is no need for this attitude. @johnjamesjacoby I understand you lead this project but with all do respect your a human and so am I. Your judgment on this issue is misguided and your abandonment of people willing to help will come back to bite you. I wouldn’t want that on my resume. I think this issue needs to be taken seriously and stop trying to bully others just because you have access on the site to shut them out and lock the topic whenever you get tired of listening. If that is your position of resolve then your no leader at all. I don’t want to get anyone upset but I want to see results and pushing your weight around and throwing out percentages about who did what is showing your demeanor and from what I have seen its unsatisfactory so lets try to work together here instead of acting like a power hungry dictatorship please?

@mercime I mean no disrespect. I do not want this topic locked sir but when you snuff out people especially ones that is willing to help it only shows dictatorship. Who is abusive? @ethanvan or @johnjamesjacoby? Its a matter of perspective because I can see to a degree a little from both sides. This shall not be a power struggle. We should work as a unit. As stated above one shall not cast stones when you live in glass houses. I think it would be wise to let this topic evolve and hope that there becomes a positive result. So lets keep things positive please because this is something that seriously needs nurturing.
Edit:
We need passionate people here so until it gets to a point where there it is threatening in nature I think it would be wise to allow this topic to evolve and maybe get some good developers helping out more. Thank you!

@travel-junkie Lack of documentation will not necessarily turn developers away but generally the degree to which something is well documented is an indication of how things stand overall and reading how something flows, what is possible or not, is easier than having to trawl through core code to work it out, yes we can and do do that but being able to does not replace or negate the need for a good set of dev docs and having to trawl through core code because there aren’t docs available will turn away many developers..

Codex pages can be created through wp-admin, like any WordPress site: http://codex.buddypress.org/wp-admin/