Quote:
I just thought I would add that I really like the idea of read only access for non project people and contribute access for those associated with a project. It seems to be a nice compromise. The forums are kept useful, and those not involved can benifit.
Weelll... yes.
It's not because we want to keep ourselves separate from "the crowding masses of n00bies" - but keep in mind that the closed forums on dev.x.o are also the place for module developers to discuss security matters, such as cross-site scripting and SQL injection issues. Definitely NOT something we would like just anyone to read (I'm not saying that we have a lot of those discussions - but it would be the right place to have them
)
We can of course only open SOME forums to the public, but then we have to be sure that noone accidently posts such sensitive information in a public forum and yada yada yada. Sorry, I'm stretched too far to add that to my workload when I cannot see that the information in those forums are of much interest to the casual/new developer.
As bd_csmc correctly states, the activity on dev.x.o is very low. In the forums at least.
Looking at the latest threads on dev.x.o, I see things like module caching manipulation, "orphan" module ideas, charset issues and questions about the core. For the beginner, this is quite useless information.
Yes, beginners need to be led and will "take" more than they "give" - at least in the beginning - and I don't want to turn them away, if they have a desire to learn.
In general, I welcome new XOOPS module developers to dev.x.o at any given opportunity, as long as they show that they are willing to do their part of the work (I don't mean giving back straight away, but I do mean that when they ask a question and get an answer that involves some reading/testing/trial-and-error then they DO read, test and try) - a good project description is the first step on the way.
To return to the situation at hand, I do think that it would be best for you, rpclarke, to study existing modules, reading these forums and asking your questions here until you are more at home with the XOOPS way of doing things. Many more people frequent these forums than dev.x.o and you are more likely to find existing answers to your problems here than on dev.x.o for the time being.
Once you have the basics laid out and want to continue your work with such things as Smarty templates, comments, searching, notifications, group permissions, object orientation in the module code -
then I think it would be a good time to join the dev.x.o community.