Re: Complex Script Support - Trac Site Access
Hi Glenn, Glenn Adams wrote: more On Thu, Aug 5, 2010 at 8:20 PM, Glenn Adams gl...@skynav.com wrote: On Thu, Aug 5, 2010 at 7:18 PM, Vincent Hennebert vhenneb...@gmail.comwrote: Hi Glenn, From you first message I had the impression that you wanted to keep using that tool for future documentation as i've said, i intend to transition the documentation to the FOP wiki over a period of time, so that it will all end up on the latter we've pretty much exhausted this thread, but perhaps it would be clearer to you if you view the trac wiki site I am using as a working copy, sandbox or as a staging area as I compose my ideas and documentation; i could have merely done it on my local drive or on a private server, but i preferred instead to make it visible early, even though it is in preliminary stage which does not meet the standards I would expect for documentation that is promoted to the FOP wiki; i very well may rip up, rewrite, replace, restructure, etc., the content i am composing on my trac wiki before i feel it is ready for the FOP wiki; as I say, i could be doing that privately, but then interested viewers would not have early access to my preliminary work; overall, it is to your and the communities benefit that i choose to expose this preliminary work, with all its defects plainly visible; That’s fair enough, but you’re describing the very purpose of the FOP wiki here :-) Moreover, notification is sent to the fop-commits mailing list whenever a change is made to the wiki, which allows us to easily follow people’s progress. Vincent
Re: Complex Script Support - Trac Site Access
I've noticed that this has changed: Wiki changes are notified to fop-dev list. -- Pascal Le 06/08/2010 12:09, Vincent Hennebert a écrit : Moreover, notification is sent to the fop-commits mailing list whenever a change is made to the wiki, which allows us to easily follow people’s progress.
Re: Complex Script Support - Trac Site Access
Hi Glenn, Thanks for the background information ;-) From you first message I had the impression that you wanted to keep using that tool for future documentation, which I don’t think is the way to go. If only because we don’t have write access to that site and can’t update your doc with our own comments and suggestions. While your patch is being processed, it would be good to progressively transfer what’s already there to the FOP wiki; And write new documentation directly on the FOP wiki. There’s no rush in it, it’s going to take some time to process your patch anyway. You said you also used git; now that would be something useful to us if we had access to it (or at least the history of commits). That would allow us to follow the progression you undertook, which isn’t as easily done with a patch. Thanks, Vincent Glenn Adams wrote: on a personal note, perhaps I should add that I've been writing code for 40 years, and am nearing 60 myself, so i'm not quite as nimble as some in making transitions, especially with dev tool chains... :) g. On Wed, Aug 4, 2010 at 6:56 PM, Glenn Adams gl...@skynav.com wrote: i am using a combination of tools from codesion on this project...
Re: Complex Script Support - Trac Site Access
On Thu, Aug 5, 2010 at 7:18 PM, Vincent Hennebert vhenneb...@gmail.comwrote: Hi Glenn, From you first message I had the impression that you wanted to keep using that tool for future documentation as i've said, i intend to transition the documentation to the FOP wiki over a period of time, so that it will all end up on the latter it’s going to take some time to process your patch anyway. keep in mind that the current patch is a starting point in what i expect to be a number of patches on top of it; in discussing this with Benson, we thought that getting something working into peoples hands earlier was a good policy (release early, release often!), even though it is not functionally complete nor adequately tested; in reviewing this initial patch, you may want to keep in mind that I view it as a temporary milestone, subject to considerable change, optimization, etc, before i will be ready to propose merging into the dev trunk; therefore, you may wish to incrementally review it, and save the more in-depth review effort for when i make such a proposal; that is, after all, my understanding of the purpose of doing this on a temporary branch, to give it time to mature; i see that Pascal has already built it and successfully produce a correct Arabic rendering, so that is one data point you might use; You said you also used git; now that would be something useful to us if we had access to it (or at least the history of commits). That would allow us to follow the progression you undertook, which isn’t as easily done with a patch. let me investigate this, if i can't easily do it on codesion, i'll push a remote to github or another site with anonymous access g.
Re: Complex Script Support - Trac Site Access
more On Thu, Aug 5, 2010 at 8:20 PM, Glenn Adams gl...@skynav.com wrote: On Thu, Aug 5, 2010 at 7:18 PM, Vincent Hennebert vhenneb...@gmail.comwrote: Hi Glenn, From you first message I had the impression that you wanted to keep using that tool for future documentation as i've said, i intend to transition the documentation to the FOP wiki over a period of time, so that it will all end up on the latter we've pretty much exhausted this thread, but perhaps it would be clearer to you if you view the trac wiki site I am using as a working copy, sandbox or as a staging area as I compose my ideas and documentation; i could have merely done it on my local drive or on a private server, but i preferred instead to make it visible early, even though it is in preliminary stage which does not meet the standards I would expect for documentation that is promoted to the FOP wiki; i very well may rip up, rewrite, replace, restructure, etc., the content i am composing on my trac wiki before i feel it is ready for the FOP wiki; as I say, i could be doing that privately, but then interested viewers would not have early access to my preliminary work; overall, it is to your and the communities benefit that i choose to expose this preliminary work, with all its defects plainly visible; g.
Re: Complex Script Support - Trac Site Access
Hi Glenn, Well, this is hardly different from the previous situation. I’m curious: what does this site provide that FOP’s wiki and Bugzilla don’t? The kind of documentation that is there at the moment would perfectly match the purpose of the DeveloperPages area on FOP’s wiki. It would really be preferable to work in the ASF area... Thanks, Vincent Glenn Adams wrote: Vincent, Chris, et al. to clarify my earlier message, lest it be misread, i was not asking for (premature) commit access to FOP; i understand the ASF process, and have no issue with the fact that it will take time and contributions on my part to be deemed a candidate as committer; what i was doing was merely citing the fact that i am not a committer, and assumed (wrongly as it turns out) that one had to be a committer to add documentation to the FOP wiki; my intention in setting up a trac database was to satisfy my immediate need for documenting my work, and further, to integrate this documentation with my ongoing issue resolution process, which is handled nicely by the system I refer to below; for me, it will be easier and more productive to use this system; in the interim, i've create a simple FOP wiki page which refers to this site; as the work is completed, stabilized, and merged into the FOP trunk, i can easily migrate my design and other useful documentation into the FOP wiki directly; is that acceptable? G. On Wed, Aug 4, 2010 at 9:09 AM, Glenn Adams gl...@skynav.com wrote: I added a Complex Scripts link under Design Documents heading in the FOP's wiki. G. On Tue, Aug 3, 2010 at 11:14 PM, Chris Bowditch bowditch_ch...@hotmail.com wrote: Glenn Adams wrote: Hi Glenn, i hear you, but I prefer to use the mechanism I described, since I have control over it; until I am granted committer status, I don't have that control within ASF; i would be happy to transition when I am granted committer status; in the mean time, i will use the mechanism i described; I don't want to discourage you from documenting your work but I agree with Vincent, using the Wiki is the preferred place to document your progress. I don't understand why committership status would matter? As Vincent already indicated anyone can view/modify the Wiki. Thanks, Chris regards, glenn On Tue, Aug 3, 2010 at 6:30 PM, Vincent Hennebert vhenneb...@gmail.commailto: vhenneb...@gmail.com wrote: Hi Glenn, That sounds good but it would be preferable to work in the ASF area, mainly use FOP’s wiki: http://wiki.apache.org/xmlgraphics-fop/DeveloperPages Anyone can add content to the wiki, you just need to create an account. You can create a new page related to your work on complex scripts and add a link to it on the above page. For issues, Bugzilla should cover your needs. If you deem necessary you can use bug #49687 as a meta-bug and create individual issues on which that bug would depend. Thanks, Vincent Glenn Adams wrote: In order to better communicate with those interested in this work, I have enabled an anonymous reas access to the following Trac site, with wiki, ticket, and report views enabled. https://skynav.trac.cvsdude.com/fop/wiki I will be using this site during the development process to aid in documentation of this feature and to track related issues. I intend to also use it for other FOP related work I plan or may accomplish. Regards, Glenn
Re: Complex Script Support - Trac Site Access
i am using a combination of tools from codesion on this project, specifically git and trac (on which i have enabled anonymous access), where trac issues and git commits are integrated with wiki, ticket, timeline, and milestone management; it is a set of tools I am accustomed to working with, so this is an efficiency issue for me; as I become more accustomed to the ASF toolset, i will be more comfortable in doing such work there. but i need time to transition, and the important thing at this point (for me, and for potential users of the results) is progress on the work itself, and for that, i will be using the existing ASF tools to post patches, etc; as i've said a few times, i fully expect to transition my documentation over to the FOP wiki as this work progresses, and as I become more familiar with the ASF environment; i'm sure you realize this is a bit of a chicken and egg process, not only from the ASF side, but from my side as well; it is my wish to become part of the FOP committers community over time, but that will take time and learning from both sides, yes? best, G. On Wed, Aug 4, 2010 at 6:42 PM, Vincent Hennebert vhenneb...@gmail.comwrote: Hi Glenn, Well, this is hardly different from the previous situation. I’m curious: what does this site provide that FOP’s wiki and Bugzilla don’t? The kind of documentation that is there at the moment would perfectly match the purpose of the DeveloperPages area on FOP’s wiki. It would really be preferable to work in the ASF area... Thanks, Vincent Glenn Adams wrote: Vincent, Chris, et al. to clarify my earlier message, lest it be misread, i was not asking for (premature) commit access to FOP; i understand the ASF process, and have no issue with the fact that it will take time and contributions on my part to be deemed a candidate as committer; what i was doing was merely citing the fact that i am not a committer, and assumed (wrongly as it turns out) that one had to be a committer to add documentation to the FOP wiki; my intention in setting up a trac database was to satisfy my immediate need for documenting my work, and further, to integrate this documentation with my ongoing issue resolution process, which is handled nicely by the system I refer to below; for me, it will be easier and more productive to use this system; in the interim, i've create a simple FOP wiki page which refers to this site; as the work is completed, stabilized, and merged into the FOP trunk, i can easily migrate my design and other useful documentation into the FOP wiki directly; is that acceptable? G. On Wed, Aug 4, 2010 at 9:09 AM, Glenn Adams gl...@skynav.com wrote: I added a Complex Scripts link under Design Documents heading in the FOP's wiki. G. On Tue, Aug 3, 2010 at 11:14 PM, Chris Bowditch bowditch_ch...@hotmail.com wrote: Glenn Adams wrote: Hi Glenn, i hear you, but I prefer to use the mechanism I described, since I have control over it; until I am granted committer status, I don't have that control within ASF; i would be happy to transition when I am granted committer status; in the mean time, i will use the mechanism i described; I don't want to discourage you from documenting your work but I agree with Vincent, using the Wiki is the preferred place to document your progress. I don't understand why committership status would matter? As Vincent already indicated anyone can view/modify the Wiki. Thanks, Chris regards, glenn On Tue, Aug 3, 2010 at 6:30 PM, Vincent Hennebert vhenneb...@gmail.commailto: vhenneb...@gmail.com wrote: Hi Glenn, That sounds good but it would be preferable to work in the ASF area, mainly use FOP’s wiki: http://wiki.apache.org/xmlgraphics-fop/DeveloperPages Anyone can add content to the wiki, you just need to create an account. You can create a new page related to your work on complex scripts and add a link to it on the above page. For issues, Bugzilla should cover your needs. If you deem necessary you can use bug #49687 as a meta-bug and create individual issues on which that bug would depend. Thanks, Vincent Glenn Adams wrote: In order to better communicate with those interested in this work, I have enabled an anonymous reas access to the following Trac site, with wiki, ticket, and report views enabled. https://skynav.trac.cvsdude.com/fop/wiki I will be using this site during the development process to aid in documentation of this feature and to track related issues. I intend to also use it for other FOP related work I plan or may accomplish. Regards, Glenn
Re: Complex Script Support - Trac Site Access
on a personal note, perhaps I should add that I've been writing code for 40 years, and am nearing 60 myself, so i'm not quite as nimble as some in making transitions, especially with dev tool chains... :) g. On Wed, Aug 4, 2010 at 6:56 PM, Glenn Adams gl...@skynav.com wrote: i am using a combination of tools from codesion on this project...
Complex Script Support - Trac Site Access
In order to better communicate with those interested in this work, I have enabled an anonymous reas access to the following Trac site, with wiki, ticket, and report views enabled. https://skynav.trac.cvsdude.com/fop/wiki I will be using this site during the development process to aid in documentation of this feature and to track related issues. I intend to also use it for other FOP related work I plan or may accomplish. Regards, Glenn
Re: Complex Script Support - Trac Site Access
i hear you, but I prefer to use the mechanism I described, since I have control over it; until I am granted committer status, I don't have that control within ASF; i would be happy to transition when I am granted committer status; in the mean time, i will use the mechanism i described; regards, glenn On Tue, Aug 3, 2010 at 6:30 PM, Vincent Hennebert vhenneb...@gmail.comwrote: Hi Glenn, That sounds good but it would be preferable to work in the ASF area, mainly use FOP’s wiki: http://wiki.apache.org/xmlgraphics-fop/DeveloperPages Anyone can add content to the wiki, you just need to create an account. You can create a new page related to your work on complex scripts and add a link to it on the above page. For issues, Bugzilla should cover your needs. If you deem necessary you can use bug #49687 as a meta-bug and create individual issues on which that bug would depend. Thanks, Vincent Glenn Adams wrote: In order to better communicate with those interested in this work, I have enabled an anonymous reas access to the following Trac site, with wiki, ticket, and report views enabled. https://skynav.trac.cvsdude.com/fop/wiki I will be using this site during the development process to aid in documentation of this feature and to track related issues. I intend to also use it for other FOP related work I plan or may accomplish. Regards, Glenn
Re: Complex Script Support - Trac Site Access
Glenn Adams wrote: Hi Glenn, i hear you, but I prefer to use the mechanism I described, since I have control over it; until I am granted committer status, I don't have that control within ASF; i would be happy to transition when I am granted committer status; in the mean time, i will use the mechanism i described; I don't want to discourage you from documenting your work but I agree with Vincent, using the Wiki is the preferred place to document your progress. I don't understand why committership status would matter? As Vincent already indicated anyone can view/modify the Wiki. Thanks, Chris regards, glenn On Tue, Aug 3, 2010 at 6:30 PM, Vincent Hennebert vhenneb...@gmail.com mailto:vhenneb...@gmail.com wrote: Hi Glenn, That sounds good but it would be preferable to work in the ASF area, mainly use FOP’s wiki: http://wiki.apache.org/xmlgraphics-fop/DeveloperPages Anyone can add content to the wiki, you just need to create an account. You can create a new page related to your work on complex scripts and add a link to it on the above page. For issues, Bugzilla should cover your needs. If you deem necessary you can use bug #49687 as a meta-bug and create individual issues on which that bug would depend. Thanks, Vincent Glenn Adams wrote: In order to better communicate with those interested in this work, I have enabled an anonymous reas access to the following Trac site, with wiki, ticket, and report views enabled. https://skynav.trac.cvsdude.com/fop/wiki I will be using this site during the development process to aid in documentation of this feature and to track related issues. I intend to also use it for other FOP related work I plan or may accomplish. Regards, Glenn
Re: Complex Script Support - Trac Site Access
I added a Complex Scripts link under Design Documents heading in the FOP's wiki. G. On Tue, Aug 3, 2010 at 11:14 PM, Chris Bowditch bowditch_ch...@hotmail.comwrote: Glenn Adams wrote: Hi Glenn, i hear you, but I prefer to use the mechanism I described, since I have control over it; until I am granted committer status, I don't have that control within ASF; i would be happy to transition when I am granted committer status; in the mean time, i will use the mechanism i described; I don't want to discourage you from documenting your work but I agree with Vincent, using the Wiki is the preferred place to document your progress. I don't understand why committership status would matter? As Vincent already indicated anyone can view/modify the Wiki. Thanks, Chris regards, glenn On Tue, Aug 3, 2010 at 6:30 PM, Vincent Hennebert vhenneb...@gmail.commailto: vhenneb...@gmail.com wrote: Hi Glenn, That sounds good but it would be preferable to work in the ASF area, mainly use FOP’s wiki: http://wiki.apache.org/xmlgraphics-fop/DeveloperPages Anyone can add content to the wiki, you just need to create an account. You can create a new page related to your work on complex scripts and add a link to it on the above page. For issues, Bugzilla should cover your needs. If you deem necessary you can use bug #49687 as a meta-bug and create individual issues on which that bug would depend. Thanks, Vincent Glenn Adams wrote: In order to better communicate with those interested in this work, I have enabled an anonymous reas access to the following Trac site, with wiki, ticket, and report views enabled. https://skynav.trac.cvsdude.com/fop/wiki I will be using this site during the development process to aid in documentation of this feature and to track related issues. I intend to also use it for other FOP related work I plan or may accomplish. Regards, Glenn
Re: Complex Script Support - Trac Site Access
Vincent, Chris, et al. to clarify my earlier message, lest it be misread, i was not asking for (premature) commit access to FOP; i understand the ASF process, and have no issue with the fact that it will take time and contributions on my part to be deemed a candidate as committer; what i was doing was merely citing the fact that i am not a committer, and assumed (wrongly as it turns out) that one had to be a committer to add documentation to the FOP wiki; my intention in setting up a trac database was to satisfy my immediate need for documenting my work, and further, to integrate this documentation with my ongoing issue resolution process, which is handled nicely by the system I refer to below; for me, it will be easier and more productive to use this system; in the interim, i've create a simple FOP wiki page which refers to this site; as the work is completed, stabilized, and merged into the FOP trunk, i can easily migrate my design and other useful documentation into the FOP wiki directly; is that acceptable? G. On Wed, Aug 4, 2010 at 9:09 AM, Glenn Adams gl...@skynav.com wrote: I added a Complex Scripts link under Design Documents heading in the FOP's wiki. G. On Tue, Aug 3, 2010 at 11:14 PM, Chris Bowditch bowditch_ch...@hotmail.com wrote: Glenn Adams wrote: Hi Glenn, i hear you, but I prefer to use the mechanism I described, since I have control over it; until I am granted committer status, I don't have that control within ASF; i would be happy to transition when I am granted committer status; in the mean time, i will use the mechanism i described; I don't want to discourage you from documenting your work but I agree with Vincent, using the Wiki is the preferred place to document your progress. I don't understand why committership status would matter? As Vincent already indicated anyone can view/modify the Wiki. Thanks, Chris regards, glenn On Tue, Aug 3, 2010 at 6:30 PM, Vincent Hennebert vhenneb...@gmail.commailto: vhenneb...@gmail.com wrote: Hi Glenn, That sounds good but it would be preferable to work in the ASF area, mainly use FOP’s wiki: http://wiki.apache.org/xmlgraphics-fop/DeveloperPages Anyone can add content to the wiki, you just need to create an account. You can create a new page related to your work on complex scripts and add a link to it on the above page. For issues, Bugzilla should cover your needs. If you deem necessary you can use bug #49687 as a meta-bug and create individual issues on which that bug would depend. Thanks, Vincent Glenn Adams wrote: In order to better communicate with those interested in this work, I have enabled an anonymous reas access to the following Trac site, with wiki, ticket, and report views enabled. https://skynav.trac.cvsdude.com/fop/wiki I will be using this site during the development process to aid in documentation of this feature and to track related issues. I intend to also use it for other FOP related work I plan or may accomplish. Regards, Glenn
