Since I have done a hostile takeover on all things freeswitch in sipx it seems, I can also take responsibility for updating all docs related to that part. I have a new guy starting in my office from 01/09 who will be doing our german freeswitch wiki and I will add to his responsibilities to create a whole bunch of freeswitch/sipx related docs in the new wiki.
And just for the record ... I am a xwiki fan and confluence drives me insane ;) Am 05.08.2010 um 15:55 schrieb Geoff Van Brunt: > The issue I see with not copying is that documentation does not get > updated. In the old wiki there was a ton of documentation that was > outdated. Let's face it, most developers hate documenting things... :) > This confused new users which are the very people the project would like > to attract. > > I do however agree with you about the problems with that approach. One > comment I would like to make in general about the project; there is no > formal process for "who is responsible for what". In other open source > projects they often have project leads for various parts. It is > documented on the website etc. Handy for devs as well as end users. It > also makes it easy to see when a particular project losses traction and > might need some people to move it along. it also assures that projects > continue to evolve instead of stagnate. If that approach is adopted, you > (or a committee) could appoint someone to be the "project lead" of > documentation. It would be their job every release to keep everything up > to date. That approach would also let some non-developers contribute > back to the project if they wished to... > > Anyhow, just my 2 cents... > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Douglas > Hubler > Sent: August-04-10 6:54 PM > To: sipx-users > Subject: [sipx-users] Wiki versioning good or bad idea > > Anyone a fan of Confluence's feature to copy entire spaces into new > versions? I'm not and here's why > > * Simple search pulls up redundant copies of probably the same > information > * Editors can easily make mistakes and edit the wrong version if they > are not careful or not aware (just happened with ldap) > > Proposal > * Don't use versioning in confluence and if developers want to version > things that are in upcoming releases to existing pages, they can add an > in-line image denoting the version. Kinda like the "v3.8" image you see > in this page > > > http://sipx-wiki.calivia.com/index.php/Import_User_and_Device_Data_from_ > CSV_Files > > Benefits > * none of the issues notes above > * only the developers need to be aware of this > * worst case if it's not done, it's not a big deal > * if we want to remove all images because version is so old, just delete > image or replace image w/blank image > > Another proposal > * Screw trying to version things, it's a wiki. Go to page history if > you care _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ Michal Bielicki Geschäftsführer / CEO Seventh Signal Ltd. & Co. KG Meiereifeld 2A 14532 Kleinmachnow Büro Berlin: Weigandufer 45, Büro 115 12059 Berlin Amtsgericht Potsdam HRA 4866 P, Ust.-ID: DE266981999 Geschäftsführer: Michal Bielicki Persönlich Haftende Gesellschafterin: Seventh Signal Ltd, 69 Great Hampton St. Birmingham, B18 6EW, GB, Company Nr.: 06889439 WWW.: http://www.seventhsignal.de
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
