I wonder how we are going to organize the application and review of the Complex Script Support work. Glenn has now submitted a patch and we have created a branch for this work.
We can apply the patch and then make comments or request changes. Glenn does further work and reacts to our comments and requests. Does he then give us a patch agains the HEAD revision of the branch? That would work fine for us. If it would not be possible for Glenn to produce patches against the HEAD revision of the branch, should we then do something with git? I notice that Glenn mentions he uses git. I am not sure how that would help us produce patches against the HEAD revision of the branch, but I presume that a distributed versioning system would at least make it easier. Regarding the application of the patches, I am in favour of applying the patches as soon as we receive them. It makes the code available to many users. We could even build and make available a jar file from the branch, which would allow more users to install and test it. I know for sure that more users in the Arabic world would like to use this functionality. Application of the patches does not imply our endorsement. It requires that the code is donated to the ASF, which is guaranteed by Glenn's submission to the ASF Bugzilla and his CLA. Basis Technology Corporation could augment this with their CCLA, but that is not required. It also requires that there are no IP problems with the code, but basically Glenn assures that by his CLA and submission of the patch. Simon -- Simon Pepping home page: http://www.leverkruid.eu
