Posted by: christianOn 2006/8/20 1:50:026347 reads I published today on xoops France an article about the lastest changes sent to the XOOPS svn during this month. The covered subjects relate : - passage of the trunk svn in version 2.3 - new installer for Xoops 2.3 - zeta1 : new default theme - work on admin interface - working methods - tutorial on the developments, subversions and tortoisvn My English is not good enough to entirely translate this article into English, but if somebody wants to undertake some, not of problems.
(had to drop this here since the correspondent thread was closed)
The XOOPS core developers are indeed a closed circle. They discuss mainly over msn than using a public chatroom. They don't have a public discussion forum. They don't let anyone submit things to the svn. Ergo: They will have to do the most work alone. I have fixed many core bugs, I offered my assistance but demanded svn access...they refused. So that's how it ends. I am an experienced XOOPS programmer, I know what a handler is, I understand the purpose of xoopsObject, i know how to optimize queries and so on. So i didn't understand what their criteria for being part of the team are. Nowadays I have my own personal XOOPS forge for my website without caring for writing generalized code able to be implemented as part of the core.
greetings MK
Re: This month in SVN
@birdseed had seen your contribution to XOOPS core during last year. It's a pity not seeing your discussioin or code submission afterwards.
Perhaps christian would add such relevant tutorial to the article as well.
Re: This month in SVN
Quote:
They discuss mainly over msn than using a public chatroom. They don't have a public discussion forum
That's wrong... we use the SF public forums, and the trackers system. Everything is public.
Quote:
They don't let anyone submit things to the svn. Ergo: They will have to do the most work alone. I have fixed many core bugs, I offered my assistance but demanded svn access.
Well, the point is that I haven't seen a single thing from you, EVER.. So I have absolutely no idea what you're talking about. I checked the bugs trackers: nothing from you. I checked the 2.2 changelog (I wans't here during the 2.2 dev): nothing from you.
So, for sure, you won't get SVN access like that. There are open ways to contribute, show us you're able to understand that, that you're able to respect the work methodology in place, and that you're able to write good code, and you may get SVN access after a while.
Also: our objective is not to make XOOPS bigger but better, and that's different. Core developers are not people who understand how to use XoopsObject but what's wrong with it, and what it should be replaced by to overcome the actual framework limitations.
Last point: experience has shown me that people who really want to helps us make XOOPS better, don't really care about having SVN access or not: seeing their contributions make their way in the code satisfy them. People who want SVN access or "be members of the team" before they did anything, who are not even able to realise that everybody potentially is, almost always turn out to be individualist persons who demand more than they bring and a waste of time.
So I didn't say you are: free to you to show us.
Re: This month in SVN
Hi
So you gave me the forum link. Very interesting. Thank you. I will have a regular look. But: Where did the link come from? By clicking on "Development" in the main menu, I am directed to devteam.xoops.org.
Submitting a core bug. Okay. I could just submit everything in this form and leave a big amount of work for someone else who has to assign it to a file, then look for the right line, check if it has already been fixed in one of the 2.2, 2.0.14 or 2.3 branches, verify it, then copy & paste the fix, finally submit it. Shouldn't XOOPS have public svn write access for everyone who applies for?
In one thing you are right: I don't care about having my own distributions in the core. For me, bugfixes are just side products of my work for my platform. I made two submissions in the Report a Bug Window, they were accepted after half a year (!). So I concluded that you don't care about the Core Bug Report Feature.
greetings bsm
Re: This month in SVN
Quote:
That's wrong... we use the SF public forums, and the trackers system. Everything is public.
Is there a "public" description of the new directories in XOOPS 2.3 and how to use them (in modules and the core)? I'd like to help with testing and development issues, but it's kind of difficult without having information like that. If this info has already been posted somewhere, please point me to it.
Re: This month in SVN
The SVN trunk is always the latest development version ready to be tested.