From documentation@opengroupware.org Thu Feb 3 20:27:42 2005 From: documentation@opengroupware.org (Chris H) Date: Thu, 03 Feb 2005 15:27:42 -0500 Subject: [OGo-Documentation] user documentation & rpm Message-ID: <4202893E.2010108@magma.ca> David Nalley wrote; > If you chose to move away from the pdf version, we could even change > the format to docbook, as we were doing before VBII gave us one that > was completed, and make it accessible from anywhere within OGo. > Greets David; The source doc is actually sxw, which means that it can easily be converted to text, then docbook. I have tried to learn docbook but have not met with success given my time constraints. So if you want to take this part on _and_ own that process, it would be greatly appreciated. Ownership however is the issue as its a lot or work, to keep the versions in sink. Please give it some thought, the idea is most welcomed, and let me know of you decision as time permitts. /ch From documentation@opengroupware.org Thu Feb 3 20:32:04 2005 From: documentation@opengroupware.org (G. Roderick Singleton) Date: Thu, 03 Feb 2005 15:32:04 -0500 Subject: [OGo-Documentation] user documentation & rpm In-Reply-To: <4202893E.2010108@magma.ca> References: <4202893E.2010108@magma.ca> Message-ID: <1107462724.5546.2.camel@www.pathtech.org> On Thu, 2005-02-03 at 15:27 -0500, Chris H wrote: > David Nalley wrote; > > > If you chose to move away from the pdf version, we could even change > > the format to docbook, as we were doing before VBII gave us one that > > was completed, and make it accessible from anywhere within OGo. > > > Greets David; > > The source doc is actually sxw, which means that it can easily be > converted to text, then docbook. I have tried to learn docbook but have > not met with success given my time constraints. So if you want to take > this part on _and_ own that process, it would be greatly appreciated. > Ownership however is the issue as its a lot or work, to keep the > versions in sink. If you have the filter installed you can go directly to docbook. I have this filter installed and can do this. > > Please give it some thought, the idea is most welcomed, and let me know > of you decision as time permitts. > > /ch > From documentation@opengroupware.org Thu Feb 3 20:36:05 2005 From: documentation@opengroupware.org (Chris H) Date: Thu, 03 Feb 2005 15:36:05 -0500 Subject: [OGo-Documentation] user documentation & rpm In-Reply-To: <1107462724.5546.2.camel@www.pathtech.org> References: <4202893E.2010108@magma.ca> <1107462724.5546.2.camel@www.pathtech.org> Message-ID: <42028B35.2050800@magma.ca> G. Roderick Singleton wrote: >If you have the filter installed you can go directly to docbook. I have >this filter installed and can do this. > > Ya know Rod I tested this a bit and found it not to be acceptable. Mind you the export filter was an early version (OOo release 1.1.3) and at that time it was referred too as a limited capability or something along those lines that produced a near docbook format. Do you have a URL handy that I can review and test where this filter is at, at this time. regards and thanks /ch From documentation@opengroupware.org Thu Feb 3 20:39:03 2005 From: documentation@opengroupware.org (David Nalley) Date: Thu, 3 Feb 2005 15:39:03 -0500 Subject: [OGo-Documentation] user documentation & rpm Message-ID: You are in a far better position to know than I, but around 1.0, this featu= re had some issues. I admittedly haven't tried it since then, but my experi= ence was like using automated html tools, it worked most of the time.=20 That would certainly be an easy option if it has changed..... I will try us= ing this filter and see how it turns out on 1.9.x.=20 -----Original Message----- From: G. Roderick Singleton [mailto:gerry@pathtech.org] Sent: Thursday, February 03, 2005 3:32 PM To: OgO_Docs List Subject: Re: [OGo-Documentation] user documentation & rpm On Thu, 2005-02-03 at 15:27 -0500, Chris H wrote: > David Nalley wrote; >=20 > > If you chose to move away from the pdf version, we could even change=20 > > the format to docbook, as we were doing before VBII gave us one that=20 > > was completed, and make it accessible from anywhere within OGo. > > > Greets David; >=20 > The source doc is actually sxw, which means that it can easily be=20 > converted to text, then docbook. I have tried to learn docbook but have= =20 > not met with success given my time constraints. So if you want to take=20 > this part on _and_ own that process, it would be greatly appreciated.=20 > Ownership however is the issue as its a lot or work, to keep the=20 > versions in sink. If you have the filter installed you can go directly to docbook. I have this filter installed and can do this. >=20 > Please give it some thought, the idea is most welcomed, and let me know= =20 > of you decision as time permitts. >=20 > /ch >=20 --=20 OpenGroupware.org Documentation documentation@opengroupware.org http://mail.opengroupware.org/mailman/listinfo/documentation --=20 This message has been scanned for viruses, spam and dangerous content by MailScanner, utilizing ClamAV=20 and SpamAssassin on RedHat Linux (Valhalla) and is believed to be clean. --=20 This message has been scanned for viruses, spam and dangerous content by MailScanner, utilizing ClamAV=20 and SpamAssassin on RedHat Linux (Valhalla) and is believed to be clean. From documentation@opengroupware.org Thu Feb 3 20:41:20 2005 From: documentation@opengroupware.org (David Nalley) Date: Thu, 3 Feb 2005 15:41:20 -0500 Subject: [OGo-Documentation] user documentation & rpm Message-ID: Chris,=20 I _can_ take ownership of it. However, we've also talked about doxygen. I d= on't think my schedule would permit me to do both and keep up with both if = the manual is going to changing alot. In short, let me know which is the mo= st important, and I can work on it.=20 David Nalley -----Original Message----- From: Chris H [mailto:chris123@magma.ca] Sent: Thursday, February 03, 2005 3:28 PM To: documentation@opengroupware.org Subject: [OGo-Documentation] user documentation & rpm David Nalley wrote; > If you chose to move away from the pdf version, we could even change=20 > the format to docbook, as we were doing before VBII gave us one that=20 > was completed, and make it accessible from anywhere within OGo. > Greets David; The source doc is actually sxw, which means that it can easily be=20 converted to text, then docbook. I have tried to learn docbook but have=20 not met with success given my time constraints. So if you want to take=20 this part on _and_ own that process, it would be greatly appreciated.=20 Ownership however is the issue as its a lot or work, to keep the=20 versions in sink. Please give it some thought, the idea is most welcomed, and let me know=20 of you decision as time permitts. /ch --=20 OpenGroupware.org Documentation documentation@opengroupware.org http://mail.opengroupware.org/mailman/listinfo/documentation --=20 This message has been scanned for viruses, spam and dangerous content by MailScanner, utilizing ClamAV=20 and SpamAssassin on RedHat Linux (Valhalla) and is believed to be clean. --=20 This message has been scanned for viruses, spam and dangerous content by MailScanner, utilizing ClamAV=20 and SpamAssassin on RedHat Linux (Valhalla) and is believed to be clean. From documentation@opengroupware.org Thu Feb 3 20:47:47 2005 From: documentation@opengroupware.org (G. Roderick Singleton) Date: Thu, 03 Feb 2005 15:47:47 -0500 Subject: [OGo-Documentation] user documentation & rpm In-Reply-To: <42028B35.2050800@magma.ca> References: <4202893E.2010108@magma.ca> <1107462724.5546.2.camel@www.pathtech.org> <42028B35.2050800@magma.ca> Message-ID: <1107463667.5546.6.camel@www.pathtech.org> On Thu, 2005-02-03 at 15:36 -0500, Chris H wrote: > G. Roderick Singleton wrote: > > >If you have the filter installed you can go directly to docbook. I have > >this filter installed and can do this. > > > > > Ya know Rod I tested this a bit and found it not to be acceptable. Mind > you the export filter was an early version (OOo release 1.1.3) and at > that time it was referred too as a limited capability or something along > those lines that produced a near docbook format. > > Do you have a URL handy that I can review and test where this filter is > at, at this time. > > regards and thanks > > /ch > > In 1.1.4, docbook is a save as option (simplified) probably the same a 1.1.3. I cannot get 1.9 to work so don't know whether the export filter is better or not. If this is the case, them why not html. Under RH docs go in /usr/share/doc/ and I am guessing that most rpm based distros do the same. From documentation@opengroupware.org Thu Feb 3 20:52:00 2005 From: documentation@opengroupware.org (Chris H) Date: Thu, 03 Feb 2005 15:52:00 -0500 Subject: [OGo-Documentation] user documentation & rpm In-Reply-To: References: Message-ID: <42028EF0.1060307@magma.ca> David Nalley wrote: >Chris, > >I _can_ take ownership of it. However, we've also talked about doxygen. I don't think my schedule would permit me to do both and keep up with both if the manual is going to changing alot. In short, let me know which is the most important, and I can work on it. > Yes I know. The doxygen stuff seems to not have gotten a response from Helge other then info overload, which is correct. What I gather from that is that source documentation is important but its also a function of how that source is bundled. Since there is little communication on this issue at present I would say that its not a priority at this time. Helge if your listening??? I can address this issue on an as needed basis as long as there are others on the lists who can review the output. Code documentation simply is ancient hebrew to me, something that I have not mastered..:) The user documentation IMHO should be the priority at this time. What I meant by owning the work, is simply this. The user manual in theory is a live document. It will require a periodic release based on a yet to be determined incremental release schedule. The conversion of the document into docbook and associated output formats is a process that will be ongoing over time, so if we decide to use this mechansim, then there is a need to consider some form of long term commitment or skill transfer via howto for lesser mortals, which is probably the best way to go. Thoughts?? /ch From documentation@opengroupware.org Thu Feb 3 21:14:16 2005 From: documentation@opengroupware.org (Dustin Machi) Date: Thu, 3 Feb 2005 16:14:16 -0500 Subject: [OGo-Documentation] user documentation & rpm In-Reply-To: <42028EF0.1060307@magma.ca> References: <42028EF0.1060307@magma.ca> Message-ID: <200502031614.16707.dmachi@vbi.vt.edu> > What I meant by owning the work, is simply this. The user manual in > theory is a live document. It will require a periodic release based on a > yet to be determined incremental release schedule. The conversion of the > document into docbook and associated output formats is a process that > will be ongoing over time, so if we decide to use this mechansim, then > there is a need to consider some form of long term commitment or skill > transfer via howto for lesser mortals, which is probably the best way to > go. Thoughts?? What is the process by which we will update the source document. I'm sure that we (VBI) will be updating that document, and we of course want to let that info flow back to the group. How is this expected to be done? From documentation@opengroupware.org Thu Feb 3 21:18:39 2005 From: documentation@opengroupware.org (Chris H) Date: Thu, 03 Feb 2005 16:18:39 -0500 Subject: [OGo-Documentation] user documentation & rpm In-Reply-To: <1107463667.5546.6.camel@www.pathtech.org> References: <4202893E.2010108@magma.ca> <1107462724.5546.2.camel@www.pathtech.org> <42028B35.2050800@magma.ca> <1107463667.5546.6.camel@www.pathtech.org> Message-ID: <4202952F.9000802@magma.ca> G. Roderick Singleton wrote: >In 1.1.4, docbook is a save as option (simplified) probably the same a >1.1.3. I cannot get 1.9 to work so don't know whether the export filter >is better or not. > > Yes its the 'simplified' part that needs testing and proofing..:) >If this is the case, them why not html. Under RH docs go >in /usr/share/doc/ and I am guessing that most rpm based distros do the >same. > > Sure that the file system location on RH. However that differs greatly per distro. The actual location for such docs and required formats is not mine rather Helge's. At this time Im hopping simply to point out that inclussion with the app is a good thing. That I think has been accomplished. The next decision is where on the filesystem such doc's are ideally placed; in the systems directory structure or the applications directory structure. My preferance based on usability would be to place the documents in html format in the application's directory structure as a prelude to making the docs as part of an online help system in a later release version of OGo. By means of example; A help button that is WebUI page specific that calls context specific help notes. In order to get there the placement of the documentation via an rpm load is critical to the applications design. For now however providing the doc in a to be determined format suffices I would say. /ch From documentation@opengroupware.org Thu Feb 3 21:29:11 2005 From: documentation@opengroupware.org (Chris H) Date: Thu, 03 Feb 2005 16:29:11 -0500 Subject: [OGo-Documentation] user documentation & rpm In-Reply-To: <200502031614.16707.dmachi@vbi.vt.edu> References: <42028EF0.1060307@magma.ca> <200502031614.16707.dmachi@vbi.vt.edu> Message-ID: <420297A7.2010208@magma.ca> Dustin Machi wrote: >What is the process by which we will update the source document. I'm sure >that we (VBI) will be updating that document, and we of course want to let >that info flow back to the group. How is this expected to be done? > > The document now resides on asterisk.opengroupware.org to be changed to manuals.opengroupware.org when frank from skyrix gets around to changing the DNS. This site has restricted access so folks interested in contributing to the next release need to apply and take ownership of a chapter(s). Since its a plone based application, the workflow has been changed so that edits are submitted for review. Once approved, they will be added to the next release version or branch that is not visible on line till its complete, reviewed and editted. Users can of course use their personal space on docs.opengroupware.org to create doc's but until they apply for an account on manuals.ogo.org they have no access. The setup is quite simple: docs.opengroupware.org will remain as a user workspace and repository for notes and information (public space; non restricted access with extreme limitations; no email integration, no webdav, etc ) opengroupware.org is where released versions of all project generated documentation eventually is released. (no access) manuals.opengroupware.org is the workplace and release mechansim for manuals only. (qualified access: requires account approval with conditions; fully functional remote access system) /ch From documentation@opengroupware.org Thu Feb 3 21:37:33 2005 From: documentation@opengroupware.org (documentation@opengroupware.org) Date: Thu, 3 Feb 2005 22:37:33 +0100 (CET) Subject: [OGo-Documentation] [Bug 1227] New: DNS change request Message-ID: <20050203213733.B51163005F@bugzilla.opengroupware.org> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. http://bugzilla.opengroupware.org/bugzilla/show_bug.cgi?id=1227 Summary: DNS change request Product: Documentation Version: TRUNK Platform: All OS/Version: other Status: NEW Severity: normal Priority: normal Component: General AssignedTo: ts@skyrix.com ReportedBy: chris123@magma.ca CC: documentation@opengroupware.org >From Bugzilla Helper: User-Agent: Mozilla/5.0 (compatible; Konqueror/3.3; Linux) (KHTML, like Gecko) Description of problem: Currently all manuals are developed and released via asterisk.opengroupware.org Can the DNS be changed to point to manuals.opengroupware.org in order to allow for the following structure. docs.opengroupware.org public space: restricted features; basically a user workspace to collect data and information about OGo opengroupware.org repository where all documentation is officially released hence no public access manuals.opengroupware.org a restricted space where accounts are managed to allow for production of OGo manuals and revisions. Features are turned on for this account; mail, webdav and ftp access Version-Release number of selected component (if applicable): pre 1.0 How reproducible: Always Steps to Reproduce: 1. currently the dns points to asterisk.opengroupware.org 2. 3. Actual Results: as above Expected Results: manuals.opengroupware.org with integrated email access, ftp and webdav access to restricted accounts. Users must apply for access. Additional info: ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. From documentation@opengroupware.org Thu Feb 3 21:42:33 2005 From: documentation@opengroupware.org (David Nalley) Date: Thu, 3 Feb 2005 16:42:33 -0500 Subject: [OGo-Documentation] user documentation & rpm Message-ID: So we are forking VBI's version now, if I understand correctly, and then pl= acing their future changes in, at the discretion of the editor/reviewers? I currently have an account on developer.OGo, and docs.OGo, (both different= usernames interestingly enough) and now it sounds like a third will be nee= ded at asterisk/manuals.OGo. Any way we can get all of these to point to a = central LDAP server to cut down on duplicitous logins?=20 -----Original Message----- From: Chris H [mailto:chris123@magma.ca] Sent: Thursday, February 03, 2005 4:29 PM To: documentation@opengroupware.org Subject: Re: [OGo-Documentation] user documentation & rpm Dustin Machi wrote: >What is the process by which we will update the source document. I'm sure= =20 >that we (VBI) will be updating that document, and we of course want to let= =20 >that info flow back to the group. How is this expected to be done?=20=20 >=20=20 > The document now resides on asterisk.opengroupware.org to be changed to=20 manuals.opengroupware.org when frank from skyrix gets around to changing=20 the DNS. This site has restricted access so folks interested in=20 contributing to the next release need to apply and take ownership of a=20 chapter(s). Since its a plone based application, the workflow has been=20 changed so that edits are submitted for review. Once approved, they will=20 be added to the next release version or branch that is not visible on=20 line till its complete, reviewed and editted. Users can of course use=20 their personal space on docs.opengroupware.org to create doc's but until=20 they apply for an account on manuals.ogo.org they have no access. The setup is quite simple: docs.opengroupware.org will remain as a user workspace and repository=20 for notes and information (public space; non restricted access with extreme limitations; no email=20 integration, no webdav, etc ) opengroupware.org is where released versions of all project generated=20 documentation eventually is released. (no access) manuals.opengroupware.org is the workplace and release mechansim for=20 manuals only. (qualified access: requires account approval with conditions; fully=20 functional remote access system) /ch --=20 OpenGroupware.org Documentation documentation@opengroupware.org http://mail.opengroupware.org/mailman/listinfo/documentation --=20 This message has been scanned for viruses, spam and dangerous content by MailScanner, utilizing ClamAV=20 and SpamAssassin on RedHat Linux (Valhalla) and is believed to be clean. --=20 This message has been scanned for viruses, spam and dangerous content by MailScanner, utilizing ClamAV=20 and SpamAssassin on RedHat Linux (Valhalla) and is believed to be clean. From documentation@opengroupware.org Thu Feb 3 21:52:43 2005 From: documentation@opengroupware.org (Dustin Machi) Date: Thu, 3 Feb 2005 16:52:43 -0500 Subject: [OGo-Documentation] user documentation & rpm In-Reply-To: References: Message-ID: <200502031652.43729.dmachi@vbi.vt.edu> On Thursday 03 February 2005 04:42 pm, David Nalley wrote: > So we are forking VBI's version now, if I understand correctly, and then > placing their future changes in, at the discretion of the editor/reviewers? I think that this is somewhat accurate technically...but in reality I think that we are just handing our stuff over and then we won't maintain our "fork". I want to have our writers submit documentation just as any other writer. In some case we may volunteer to be editors if needed. Dustin From documentation@opengroupware.org Thu Feb 3 22:14:00 2005 From: documentation@opengroupware.org (Chris H) Date: Thu, 03 Feb 2005 17:14:00 -0500 Subject: [OGo-Documentation] user documentation & rpm In-Reply-To: References: Message-ID: <4202A228.2060501@magma.ca> David Nalley wrote: >So we are forking VBI's version now, if I understand correctly, and then placing their future changes in, at the discretion of the editor/reviewers? > > Well not really. The document is a live document with incremental releases based on a revision schedule. VBI in this case donated the source from which we all are working from. We also appreciated all other contributions and contributors who have spend time and effort on preparing documents. There is no exclusivity on our gratitude. >I currently have an account on developer.OGo, and docs.OGo, (both different usernames interestingly enough) and now it sounds like a third will be needed at asterisk/manuals.OGo. Any way we can get all of these to point to a central LDAP server to cut down on duplicitous logins? > > > Yes it can get a bit confusing. Some explanation may be needed. dev.ogo.org was originally donated by Skryix as a developer work space and has certain features that make documentation authoring very simple. Its primarily used however for ogo developers and communications with Skyrix. docs.opengroupware.org was created as a public space with virtually no restruction however is very restricted in terms of services from the outside; basically html access only. manuals/asterisk.ogo.org is intended to be the repository for manuals with a complete services setup which necessitates user access restrictions, and by the nature of the work, limited to those who want to work on the manual only. LDAP integration would be nice but probably not a reasonable request given the work load on skyrix and the actual benefit it would provide to us volunteers only. /ch From documentation@opengroupware.org Fri Feb 4 20:41:22 2005 From: documentation@opengroupware.org (Helge Hess) Date: Fri, 4 Feb 2005 21:41:22 +0100 Subject: [OGo-Documentation] user documentation & rpm In-Reply-To: <42028EF0.1060307@magma.ca> References: <42028EF0.1060307@magma.ca> Message-ID: On Feb 3, 2005, at 21:52, Chris H wrote: > The doxygen stuff seems to not have gotten a response from Helge other > then info overload, which is correct. What I gather from that is that > source documentation is important but its also a function of how that > source is bundled. Since there is little communication on this issue > at present I would say that its not a priority at this time. Helge if > your listening??? Its a "very nice to have", but certainly not a priority. Greets, Helge -- http://docs.opengroupware.org/Members/helge/ OpenGroupware.org From documentation@opengroupware.org Fri Feb 18 17:36:48 2005 From: documentation@opengroupware.org (Chris H) Date: Fri, 18 Feb 2005 12:36:48 -0500 Subject: [OGo-Documentation] inline help system Message-ID: <421627B0.2030902@magma.ca> Greets; Was wondering if someone could provide some information on integrating documents with OGo in terms of an in line (page view) help system. /ch From documentation@opengroupware.org Fri Feb 18 17:39:06 2005 From: documentation@opengroupware.org (Chris H) Date: Fri, 18 Feb 2005 12:39:06 -0500 Subject: [OGo-Documentation] ogo & zope integration Message-ID: <4216283A.2000708@magma.ca> Greets; Im currently searching for documentation on integration zope with OGo. Based on a google search it appears that there have been several attempts and efforts. If anyone has any information or URLs on work in progress or documents, and would be interested in providing, Im most interested in this as I want to include this in a forthcomming admin manual on sub section "Integrating OGo" thanks in advance. /ch From documentation@opengroupware.org Tue Feb 22 15:54:36 2005 From: documentation@opengroupware.org (documentation@opengroupware.org) Date: Tue, 22 Feb 2005 16:54:36 +0100 (CET) Subject: [OGo-Documentation] [Bug 1227] DNS change request Message-ID: <20050222155436.80D9D3041E@bugzilla.opengroupware.org> Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. http://bugzilla.opengroupware.org/bugzilla/show_bug.cgi?id=1227 helge.hess@opengroupware.org changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |critical Priority|normal |high AssignedTo|ts@skyrix.com |frank@opengroupware.org ------- Additional Comments From helge.hess@opengroupware.org 2005-02-22 16:54 ------- => fr ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. From documentation@opengroupware.org Sun Feb 27 20:46:07 2005 From: documentation@opengroupware.org (G. Roderick Singleton) Date: Sun, 27 Feb 2005 15:46:07 -0500 Subject: [OGo-Documentation] Re: Your message to Documentation awaits moderator approval In-Reply-To: <20050227203701.27059.69307.Mailman@mail.opengroupware.org> References: <20050227203701.27059.69307.Mailman@mail.opengroupware.org> Message-ID: <1109537167.14612.139.camel@www.pathtech.org> Shoot! Wrong list. Please nuke. Offending address is grsingleton@openoffice.org On Sun, 2005-02-27 at 21:37 +0100, documentation-admin@opengroupware.org wrote: > Your mail to 'Documentation' with the subject > > Please review A4 template (2.0) > > Is being held until the list moderator can review it for approval. > > The reason it is being held: > > Post by non-member to a members-only list > > Either the message will get posted to the list, or you will receive > notification of the moderator's decision. -- G. Roderick Singleton PATH tech