Thanks to both.
I had the dream with the proposal group which is discussing on my board we could bring xoops back on track, but i guess this was a dream nothing more. I believe that the work and efforts of this group (proposal group) is wasted time so i hate to waste time and i see a lot also hate it
To fork xoops was and is the last option we had and now some did it.
I welcome this as this could be a new fresh start - easier and better as a restructure of xoops which will never happen, so to fork is the only logic decision which people with responsability had made.
It is sad but i believe the name XOOPS is burned and will not resurrect, so better stop it and make a new start. So thanks who act insteed of just talk ;-D
I've always wondered why the date/time script has to be hardcoded in global.php
could we not put this into a preference setting that will allow users to change this from admin without editing files?
use the php date function etc, i'm not sure if by doing that it would make multilanguage easier in that regard.
I don't know exactly if this is required or not, but would it be an idea if we could get a full audit of the core?
by this I mean find a professional or someone with enough knowledge to go through the core and audit the code for security issues etc.
would it be worthwhile?
it could be expensive i know, but the cost could be justified providing it isn't going to break the bank as to speak.
just an idle thought on my part, but thought it worthy of discussion.
Where do you suggest we put this :<hr class="clear" />
Might be a good idea. That way no tasks or feature requests are accidentally ignored.
Perfect, then we will start using them.
I already created an impresscms-bugs mailinglist. All activity of the bug tracker will be sent to this mailing list.
Shall I create 2 others for features tracker and tasks tracker ?
The cat is out of the bag. The sooner we move from behind closed doors, the happier I'll be. I say, move forward with open development.
I would agree with maintaining compatibility with PHP4 until 2008-08-08. From what I've seen, it's not so difficult to do. Yes, it would be nice to have new features, but as pointed out, a lot of hosts are slow to upgrade.
Well lets be honest.
If we where developing in secret, people would not be able to have access to the code in svn.
But they can, if they wish, access svn.
So perhaps we should use this - and therefore allow people to help error test if they so wish.
Let's get a decision on this
Again, I'm coming back with this request. Would you see any serious problem in starting to use the trackers at SF ?
I know we are still discussion about what our long term objectives are and it would be better not to start coding before this is all decided. But altought I agree we need to decide all this sooner than later, but we already have enough of an idea about where we are going that we can start coding 0.5 version.
So, in order to get things organized and track what we are doing, it is essential we use the bug, feature and tasks tracker. It is the only way we can be efficient and productive.
ImpressCMS can be found in a few places now on the web and XOOPS.org has discussed it briefly, and so does frxoops. So it is not a secret anymore.
Was the language fix included?
Any new language differences?