Sorry to top post. Jspwiki has been in the incubator for a few years. There is no guarantee it will ever graduate. They have not switched completely to ASF infrastructure. Please look in the general@i.a.o archives and the incubator board reports.
While this discussion is good lets not be hasty. Best Regards, Dave Sent from my iPhone On Dec 3, 2012, at 10:04 AM, C <smau...@gmail.com> wrote: > On Mon, Dec 3, 2012 at 3:43 PM, imacat <ima...@mail.imacat.idv.tw> wrote: >>>> Which tweaks? >>>> >>> If I knew then I could include it in the new version, problem is that a.o. >>> imicat tells that there have been made modifications, and none of it seems >>> to be documented. >> >> There are 2 ways to find it out: >> >> 1. Ask Terry Ellison himself. He left his e-mail in the user database. >> >> http://wiki.openoffice.org/wiki/User:TerryE > > Terry wasn't so involved in the Wiki - that was my mess (at least when > it was hosted at Sun/Oracle). TerryE was heavily involved with the > User Forum rollout and sustaining maintenance. > > Tweaks/changes on the Solaris Zone were documented (changes outside of > the standard Solaris Zone config that was in place at the Sun Data > Centre in Hamburg). Server tweaks since moving to Ubuntu on Apache... > no idea. I was not involved in that. > > >> 2. A more strict method: Untar a fresh-new MediaWiki 1.15, and run >> diff to find out what is changed. Applied the changes to MediaWiki 1.16 >> *on a test site* to see if they work. If they work, do the same on the >> live site and update the symbolic link to point to the patched MediaWiki >> 1.16. This is how I did when upgrading my lab's WordPress from its >> tweaked older version. > > Any updates I did were pretty basic. A new copy of MWiki was > downloaded. The database was backed up. The standard OOoWikiSkin was > copied over which included the footer tweaks (as documented at the > time) included, and the Google Analytics (also documented). The Wiki > was upgraded using the PHP scripting provided with MWiki and it was > brought online on the testing domain. The extensions/content were > tested and when all was working the new Wiki was brought online on the > main domain. (the details were a bit more complex, but this covers > most of the high level steps that I used to do with each MWiki engine > update). > > No core functionality tweaks were made at any point in the core MWiki > PHP code (none that I was ever aware of or can remember). Standing up > a new Wiki on a new MWiki engine was primarily a task of making sure > the old extensions still worked or were updated ot current versions > compatible with the new MWiki core. Any obsolete extensions woudl be > removed (happened once in a while but the impact was always small). > > There was a lot of discussion around doing work on the caching > configurations on the webserver side, but nothing was ever really done > there. > > Clayton
