2
Well I would like to share with xoops but I feel I have changed way too much and would break too much for example all your classes, kernel code is gone as I have my own version in my libraries/ dir
as I do have legacy dir in my libraries that I later plan to remove which is basically the old xoops versions that triggers messages for admin telling what code needs to be changed which is also logged in the admin if development mode is enabled
as themes have xml system for example base/blocks.php reads the options.xml for theme for the block positions rather then having hard coded blocks layout how xoops works now.
as xoops is great system and best part is easy to use but trying to recode each file using namespaces, classes etc
also planning on haveing installer rather then upload via ftp as well as ability to use git url in the installer.
as I have plugins for the whole system too so I not sure with these change that I could share what I done too xoops would let you merge code thats the reason I asked about forking before I start prefixing my classes I created with my own headers.
but xoops files that I have not rewritten I will leave xoops copyrights in the headers as they were.
Stephen