On Tue, Oct 5, 2010 at 11:02 AM, Paul Scheepens <[email protected]> wrote: > The http://sipx-wiki.calivia.com/ wiki should disappear, as far as I know
yes, i think the only reason we haven't is because like tony said, i can sometimes find things there in cannot find on current wiki. i think goal of rally should be to safely kill (or move to a very obscure corner of the internet for a while) the old wiki. it appears the old wiki was wholly imported but i cannot be confident of that quite yet. > all that info is also on > the new "old wiki": > http://wiki.sipfoundry.org/display/oldxx/Home > > With every new version of SipX the whole current wiki should be copied to > wiki.sipfoundry.org/oldxx/ (where xx is version number, not xx :), I'm still very much opposed to mass copying of wiki http://thread.gmane.org/gmane.comp.telephony.pbx.sipfoundry.general/27266/focus=27280 this will be a maintenance nightmare and unless you flag as read-only, will definitely get edits meant for current version. > and all pages should get a banner warning you it's not current, something there are 100,000 facets documented on the wiki. Page-level versioning doesn't always work as a page can have one small change that applies to an older version or a future version. A system I proposed long ago and somewhat adopted was to have the author denote a facet/page/chapter/etc w/an icon that pointed out a special version consideration. As time passes, these version icons can be discarded or not, not a big deal. Examples http://sipx-wiki.calivia.com/index.php/The_sipXecs_IP_PBX_Configuration_Server http://sipx-wiki.calivia.com/index.php/Import_User_and_Device_Data_from_CSV_Files Some of the reason why the wiki is in such need of TLC was because of mass copying of pages or starting all new pages. This came thru - not wanting to disrupting information meant for a particular versions. - because one more more things on a page didn't apply directly. - fear or disrupting someone's vision of a page which probably has a direct correlation to the length of a page. - disorganized hierarchy - cannot find things Like code, if we can decouple things and build cohesive small pages, we can keep it maintained going forward then we can avoid inventing extra processes IMHO. I admit sometimes having a single page with all information together is useful without going to a different links, but fact is, that page is probably hard to maintain and will get forked. Also, authors also have a tendency to write long pages and it's up to wiki maintainers that understand this issue to dig in and break into maintainable pieces. > BTW How is this rally going to take place/how is it organized? I was thinking we'd set a date/time, create a punch list in a google spreadsheet, let people grab sections and coordinate on IRC, but feel free to make suggestions. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
