There was an IRC chat where me and Kelvin participated on Feb 4th, 7.30 a.m. PST for SDO Java 1.1-incubating release. Below is the summary.
1) license files under distribution and sdo-api need to be reviewed/corrected as well as copyright text fro sources/resources under sdo-api need to be reviewed/corrected based on latest from OSOA and based on when the source/resource files are changed. 2) SDO Java will follow the same strategy of providing LICENSE files under src\main\resources\META-INF as before 3) http://cwiki.apache.org/confluence/display/TUSCANYWIKI/SDO+Java+Project is the place to find all unresolved JIRAs list marked for Java-SDO-next, there are a few documentation/website update JIRAs fixed from this list (1026, 1531), all others marked as unresolved are still at same status. 4) Went through the list one by one and covered first 6 JIRAs as below- must have 1293 - important, patch is available, need to review and apply the patch nice to have 1862-workaround available in 1842 and no user issues on it so far 1838-Amita will check the existing solution against the last comment in ASF JIRA comments next release 1725-the scope is big and better justice can be given in next release I will make the same update as above to the table in http://cwiki.apache.org/confluence/display/TUSCANYWIKI/SDO+Java+Project and will have 2 additional columns in it - analysis, release scope(must/nice/next) which can be a handy reference for somebody trying to pitch in and work on this release for some JIRA. Appreciate all help in getting all important JIRAs in this release Regards, Amita On Feb 4, 2008 8:41 PM, kelvin goodson <[EMAIL PROTECTED]> wrote: > On 04/02/2008, Amita Vadhavkar <[EMAIL PROTECTED]> wrote: > > > > Apologies for a lengthy mail,but trying not to keep any ambiguities. > > Please > > see all > > **Question: > > > > Findings for license text and copyright text - > > > > http://www.mail-archive.com/[EMAIL PROTECTED]/msg15317.html > > -> > http://www.mail-archive.com/[EMAIL PROTECTED]/msg16199.html > > -> http://www.osoa.org/sdo/2.1/schemas/license.txt > > So looks like the license text for all except sdo-api will be "as is" in > > svn > > trunk like below - > > i.e. for sdo-impl, tools, sdo-lib, sdo-sample, sdo-plugin > > > correct, it's just the java files that are provided as part of the > specification that are at issue here > > **Question: why tools-test does not contain a license file? > > > The rule is that any downloadable archive needs a license file. > tools-test > does not result in a maven artifact, so the only time a user will get > anything to do with tool-test in an archive will be in the source > distribution, which will be covered by the license file at the top of the > source distro. > > **Question: tuscany sca Java provides DISCLAIMER, LICENSE, NOTICE directly > > under the module e.g. modules\binding-sca > > why tuscany SDO Java provides these files under > > module\src\main\resources\META-INF? > > > I'm not sure of the SCA build structure, but we arrange for the license > artifacts for the jars that are downloadable from maven to be in the > archives meta-inf folder in this way. There are at least two options for > doing this, and I'm not sure if we have a hybrid approach even within > SDO, > I seem to recall we might. If I recall correctly there is a maven plugin > that does this sort of thing, but the example you give is an approach > whereby the layout of the META-INF folder is specified by creating the > hierarchy manually. > > > I'm finding it a bit hard to work out where one point ends and the next > begins here, so I hope I am addressing your issues appropriately. > > > > _________________________________________________________________________________________________ > > > > Apache License > > Version 2.0, January 2004 > > http://www.apache.org/licenses/ > > > > TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION > > > > 1. Definitions. > > > > "License" shall mean the terms and conditions for use, > reproduction, > > and distribution as defined by Sections 1 through 9 of this > > document. > > > > "Licensor" shall mean the copyright owner or entity authorized by > > the copyright owner that is granting the License. > > > > "Legal Entity" shall mean the union of the acting entity and all > > other entities that control, are controlled by, or are under > common > > control with that entity. For the purposes of this definition, > > "control" means (i) the power, direct or indirect, to cause the > > direction or management of such entity, whether by contract or > > otherwise, or (ii) ownership of fifty percent (50%) or more of the > > outstanding shares, or (iii) beneficial ownership of such entity. > > > > "You" (or "Your") shall mean an individual or Legal Entity > > exercising permissions granted by this License. > > > > "Source" form shall mean the preferred form for making > > modifications, > > including but not limited to software source code, documentation > > source, and configuration files. > > > > "Object" form shall mean any form resulting from mechanical > > transformation or translation of a Source form, including but > > not limited to compiled object code, generated documentation, > > and conversions to other media types. > > > > "Work" shall mean the work of authorship, whether in Source or > > Object form, made available under the License, as indicated by a > > copyright notice that is included in or attached to the work > > (an example is provided in the Appendix below). > > > > "Derivative Works" shall mean any work, whether in Source or > Object > > form, that is based on (or derived from) the Work and for which > the > > editorial revisions, annotations, elaborations, or other > > modifications > > represent, as a whole, an original work of authorship. For the > > purposes > > of this License, Derivative Works shall not include works that > > remain > > separable from, or merely link (or bind by name) to the interfaces > > of, > > the Work and Derivative Works thereof. > > > > "Contribution" shall mean any work of authorship, including > > the original version of the Work and any modifications or > additions > > to that Work or Derivative Works thereof, that is intentionally > > submitted to Licensor for inclusion in the Work by the copyright > > owner > > or by an individual or Legal Entity authorized to submit on behalf > > of > > the copyright owner. For the purposes of this definition, > > "submitted" > > means any form of electronic, verbal, or written communication > sent > > to the Licensor or its representatives, including but not limited > to > > communication on electronic mailing lists, source code control > > systems, > > and issue tracking systems that are managed by, or on behalf of, > the > > Licensor for the purpose of discussing and improving the Work, but > > excluding communication that is conspicuously marked or otherwise > > designated in writing by the copyright owner as "Not a > > Contribution." > > > > "Contributor" shall mean Licensor and any individual or Legal > Entity > > on behalf of whom a Contribution has been received by Licensor and > > subsequently incorporated within the Work. > > > > 2. Grant of Copyright License. Subject to the terms and conditions of > > this License, each Contributor hereby grants to You a perpetual, > > worldwide, non-exclusive, no-charge, royalty-free, irrevocable > > copyright license to reproduce, prepare Derivative Works of, > > publicly display, publicly perform, sublicense, and distribute the > > Work and such Derivative Works in Source or Object form. > > > > 3. Grant of Patent License. Subject to the terms and conditions of > > this License, each Contributor hereby grants to You a perpetual, > > worldwide, non-exclusive, no-charge, royalty-free, irrevocable > > (except as stated in this section) patent license to make, have > > made, > > use, offer to sell, sell, import, and otherwise transfer the Work, > > where such license applies only to those patent claims licensable > > by such Contributor that are necessarily infringed by their > > Contribution(s) alone or by combination of their Contribution(s) > > with the Work to which such Contribution(s) was submitted. If You > > institute patent litigation against any entity (including a > > cross-claim or counterclaim in a lawsuit) alleging that the Work > > or a Contribution incorporated within the Work constitutes direct > > or contributory patent infringement, then any patent licenses > > granted to You under this License for that Work shall terminate > > as of the date such litigation is filed. > > > > 4. Redistribution. You may reproduce and distribute copies of the > > Work or Derivative Works thereof in any medium, with or without > > modifications, and in Source or Object form, provided that You > > meet the following conditions: > > > > (a) You must give any other recipients of the Work or > > Derivative Works a copy of this License; and > > > > (b) You must cause any modified files to carry prominent notices > > stating that You changed the files; and > > > > (c) You must retain, in the Source form of any Derivative Works > > that You distribute, all copyright, patent, trademark, and > > attribution notices from the Source form of the Work, > > excluding those notices that do not pertain to any part of > > the Derivative Works; and > > > > (d) If the Work includes a "NOTICE" text file as part of its > > distribution, then any Derivative Works that You distribute > must > > include a readable copy of the attribution notices contained > > within such NOTICE file, excluding those notices that do not > > pertain to any part of the Derivative Works, in at least one > > of the following places: within a NOTICE text file distributed > > as part of the Derivative Works; within the Source form or > > documentation, if provided along with the Derivative Works; > or, > > within a display generated by the Derivative Works, if and > > wherever such third-party notices normally appear. The > contents > > of the NOTICE file are for informational purposes only and > > do not modify the License. You may add Your own attribution > > notices within Derivative Works that You distribute, alongside > > or as an addendum to the NOTICE text from the Work, provided > > that such additional attribution notices cannot be construed > > as modifying the License. > > > > You may add Your own copyright statement to Your modifications and > > may provide additional or different license terms and conditions > > for use, reproduction, or distribution of Your modifications, or > > for any such Derivative Works as a whole, provided Your use, > > reproduction, and distribution of the Work otherwise complies with > > the conditions stated in this License. > > > > 5. Submission of Contributions. Unless You explicitly state > otherwise, > > any Contribution intentionally submitted for inclusion in the Work > > by You to the Licensor shall be under the terms and conditions of > > this License, without any additional terms or conditions. > > Notwithstanding the above, nothing herein shall supersede or > modify > > the terms of any separate license agreement you may have executed > > with Licensor regarding such Contributions. > > > > 6. Trademarks. This License does not grant permission to use the > trade > > names, trademarks, service marks, or product names of the > Licensor, > > except as required for reasonable and customary use in describing > > the > > origin of the Work and reproducing the content of the NOTICE file. > > > > 7. Disclaimer of Warranty. Unless required by applicable law or > > agreed to in writing, Licensor provides the Work (and each > > Contributor provides its Contributions) on an "AS IS" BASIS, > > WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or > > implied, including, without limitation, any warranties or > conditions > > of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A > > PARTICULAR PURPOSE. You are solely responsible for determining the > > appropriateness of using or redistributing the Work and assume any > > risks associated with Your exercise of permissions under this > > License. > > > > 8. Limitation of Liability. In no event and under no legal theory, > > whether in tort (including negligence), contract, or otherwise, > > unless required by applicable law (such as deliberate and grossly > > negligent acts) or agreed to in writing, shall any Contributor be > > liable to You for damages, including any direct, indirect, > special, > > incidental, or consequential damages of any character arising as a > > result of this License or out of the use or inability to use the > > Work (including but not limited to damages for loss of goodwill, > > work stoppage, computer failure or malfunction, or any and all > > other commercial damages or losses), even if such Contributor > > has been advised of the possibility of such damages. > > > > 9. Accepting Warranty or Additional Liability. While redistributing > > the Work or Derivative Works thereof, You may choose to offer, > > and charge a fee for, acceptance of support, warranty, indemnity, > > or other liability obligations and/or rights consistent with this > > License. However, in accepting such obligations, You may act only > > on Your own behalf and on Your sole responsibility, not on behalf > > of any other Contributor, and only if You agree to indemnify, > > defend, and hold each Contributor harmless for any liability > > incurred by, or claims asserted against, such Contributor by > reason > > of your accepting any such warranty or additional liability. > > > > END OF TERMS AND CONDITIONS > > > > APPENDIX: How to apply the Apache License to your work. > > > > To apply the Apache License to your work, attach the following > > boilerplate notice, with the fields enclosed by brackets "[]" > > replaced with your own identifying information. (Don't include > > the brackets!) The text should be enclosed in the appropriate > > comment syntax for the file format. We also recommend that a > > file or class name and description of purpose be included on the > > same "printed page" as the copyright notice for easier > > identification within third-party archives. > > > > Copyright [yyyy] [name of copyright owner] > > > > Licensed under the Apache License, Version 2.0 (the "License"); > > you may not use this file except in compliance with the License. > > You may obtain a copy of the License at > > > > http://www.apache.org/licenses/LICENSE-2.0 > > > > Unless required by applicable law or agreed to in writing, software > > distributed under the License is distributed on an "AS IS" BASIS, > > WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or > > implied. > > See the License for the specific language governing permissions and > > limitations under the License. > > > > > _____________________________________________________________________________________________________________________________________ > > License for sdo-api will be as below - this is way different than the > one > > in > > svn trunk, so please confirm - > > > > > _____________________________________________________________________________________________________________________________________ > > > > License for the Service Data Objects JavaDoc, Interface Definition files > > and XSD files. > > > > The Service Data Objects JavaDoc, Interface Definition files and XSD > files > > are being provided by the copyright holders under the following license. > > By using and/or copying this work, you agree that you have read, > > understood and will comply with the following terms and conditions: > > > > Permission to copy, display, make derivative works of and distribute > > the Service Data Objects JavaDoc, Interface Definition files and XSD > files > > (the "Artifacts") in any medium without fee or royalty is hereby > granted, > > provided that you include the following on ALL copies of the Artifacts, > > or portions thereof, that you make: > > > > 1. A link or URL to the Artifacts at this location: > > http://www.osoa.org/display/Main/Service+Data+Objects+Specifications > > > > 2. The full text of this copyright notice as shown in the Artifacts. > > > > > > > > THE ARTIFACTS ARE PROVIDED "AS IS" AND THE AUTHORS MAKE NO > > REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, REGARDING THE > > ARTIFACTS AND THE IMPLEMENTATION OF THEIR CONTENTS, > > INCLUDING, BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS > > FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT OR TITLE. > > > > THE AUTHORS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, > > INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF OR RELATING TO ANY > > USE OR DISTRIBUTION OF THE ARTIFACTS. > > > > The name and trademarks of the Authors may NOT be used in any manner, > > including advertising or publicity pertaining to the Service Data > > Objects Specification or its contents without specific, written prior > > permission. Title to copyright in the Service Data Objects > > Specification will at all times remain with the Authors. > > > > No other rights are granted by implication, estoppel or otherwise. > > > > Revision level 1.11, last updated on 2007/12/21 > > > > > > > -------------------------------------------------------------------------------------------------------------------------------------- > > And > > http://www.osoa.org/display/Main/Terms+and+Conditions -> copyright > notice > > - > > is different > > and latest than what is there in Tuscany SDO Java svn trunk, so "all > > files" > > (source and resource) under sdo-api > > will need replacement of copyright text to below - > > > > > __________________________________________________________________________________________________________________________________________ > > (c) Copyright BEA Systems, Inc., Cape Clear Software, International > > Business > > Machines Corp., Interface21, IONA Technologies, Oracle, > > Primeton Technologies, Progress Software, Red Hat, Rogue Wave Software, > > SAP > > AG., Siemens AG., Software AG., Sun Microsystems, Sybase Inc., > > TIBCO Software Inc., Xcalia S.A., Zend Technologies Ltd, 2006, 2007. All > > rights reserved. > > > > > ___________________________________________________________________________________________ > > > > _______________________________________________ > > Question: Still just curious to know the reason why in > > tuscany-sdo-api-r2.1so far, the files > > HelperProvider, NoHelperProviderException had ASF license > > and in test in same project -HelperProviderTestCase had (looks like some > > old > > IBM+ASF license), > > DefaultHelperProvider, TCCL1HelperProvider had ASF licenses. Was there > any > > specific reason for that? > > > > > > > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > All source and resource files "other than" the ones under sdo-api in the > > svn > > trunk have correct copyright text as below- > > > > > The files that come from OSOA must remain as they were, here's the link > to > the osoa site that provides those files > > http://www.osoa.org/download/attachments/36/SDO_2.1.0_Java_source_FINAL.zip?version=2 > > Other files have been added to the api jar, e.g. an implementation of > HelperProvider, and test case material. These were created within Apache > and therefore have an Apache license. > > I was misremembering how the license is carried in the files/archives. So > the LICENSE files we need to update will be under the distribution > project, > in src\main\release\src\LICENSE and src\main\release\bin\LICENSE in the > portions that refer to the API files. > > > > _____________________________________________________________________________________________________________________________________ > > Licensed to the Apache Software Foundation (ASF) under one > > or more contributor license agreements. See the NOTICE file > > distributed with this work for additional information > > regarding copyright ownership. The ASF licenses this file > > to you under the Apache License, Version 2.0 (the > > "License"); you may not use this file except in compliance > > with the License. You may obtain a copy of the License at > > > > http://www.apache.org/licenses/LICENSE-2.0 > > > > Unless required by applicable law or agreed to in writing, > > software distributed under the License is distributed on an > > "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY > > KIND, either express or implied. See the License for the > > specific language governing permissions and limitations > > under the License. > > > > > _____________________________________________________________________________________________________________________________________ > > > > regards, > > amita > > > On Feb 4, 2008 5:33 PM, kelvin goodson <[EMAIL PROTECTED]> wrote: > > > > > Hi Amita, > > > apologies, on further detailed inspection I see that whilst the > thread > > I > > > directed you to was relevant, the resolution of the license text was > > > documented at [1] > > > > > > Kelvin. > > > > > > [1] > > http://www.mail-archive.com/[EMAIL PROTECTED]/msg15317.html > > > > > > On 04/02/2008, Amita Vadhavkar <[EMAIL PROTECTED]> wrote: > > > > > > > > Hi, > > > > When confirming for correctness of 3rd party license text, I checked > > the > > > > below thread - > > > > 1]http://www.mail- > archive.com/[EMAIL PROTECTED]/msg05115.html > > > > and got in summary the below guidelines - > > > > > > > > Treatment of Third-Party Works > > > > > > > > 1. The term "third-party work" refers to a work not submitted > > directly > > > > to the ASF by the copyright owner or owner's agent. > > > > 2. Do not modify or remove any copyright notices or licenses > within > > > > third-party works. > > > > 3. Do ensure that every third-party work includes its associated > > > > license, even if that requires adding a copy of the license from > the > > > > third-party download site into the distribution. > > > > 4. Do not add the standard Apache License header to the top of > > > > third-party source files. > > > > 5. Minor modifications/additions to third-party source files > should > > > > typically be licensed under the same terms as the rest of the rest > > of > > > > the > > > > third-party source for convenience. > > > > 6. Major modifications/additions to third-party should be dealt > with > > > > on a case-by-case basis by the PMC. > > > > > > > > But still have a few questions about 3rd party license headers in > the > > > > context of below mail thread > > > > and findings - > > > > > > > > ML thread:- > > > > 2]http://www.mail- > archive.com/[EMAIL PROTECTED]/msg03314.html > > > > > > > > Findings:- > > > > in tuscany-sdo-api-r2.1 > > > > 1> HelperProvider and NoHelperProviderException have ASF license > > > > and in test in same project - > > > > 2>HelperProviderTestCase has (looks like some old IBM+ASF license), > > > > DefaultHelperProvider, TCCL1HelperProvider have ASF licenses, > > > > > > > > These findings are a bit confusing against mail thread 2]. > > > > > > > > Also when checked Luciano's work on DAS in JIRA-620 for license > > headers > > > it > > > > is all for ASF licenses as DAS > > > > does not contain any 3rd party code. > > > > > > > > So, will you please see if there are some changes required in 1> and > > 2>? > > > > > > > > Regards, > > > > Amita > > > > > > > > On Jan 31, 2008 5:52 PM, Amita Vadhavkar <[EMAIL PROTECTED]> > > > > wrote: > > > > > > > > > Hi, > > > > > I am going through all the samples to see if there are any areas > of > > > > > improvement, If anybody has spotted some areas or have some > > > > > suggestions, please explain the details. > > > > > > > > > > Regards, > > > > > Amita > > > > > > > > > > > > > > > On Jan 30, 2008 3:35 PM, Amita Vadhavkar < > [EMAIL PROTECTED]> > > > > > wrote: > > > > > > > > > > > How about having an IRC on 4th Feb ,Monday, 7.30 a.m. PST? > Please > > > feel > > > > > > free to suggest another time if this is not > > > > > > convenient. > > > > > > > > > > > > Regards, > > > > > > Amita > > > > > > > > > > > > > > > > > > On Jan 29, 2008 4:55 PM, kelvin goodson < > [EMAIL PROTECTED] > > > > > > > > > wrote: > > > > > > > > > > > > > I was hoping to have done a full pass through the JIRAs to be > > sure > > > > we > > > > > > > cover > > > > > > > the most important ones. Maybe it would be good to schedule > an > > > IRC > > > > > > > chat to > > > > > > > get community input on what is important. We could go through > > > each > > > > of > > > > > > > the > > > > > > > open JIRAs and see how people rate the importance and who > would > > > step > > > > > > > up to > > > > > > > fixing things. That way we'd get a better picture of what's > > > wanted. > > > > > > > When > > > > > > > would be a good time to do this? > > > > > > > > > > > > > > Kelvin. > > > > > > > > > > > > > > On 25/01/2008, Amita Vadhavkar <[EMAIL PROTECTED]> > > wrote: > > > > > > > > > > > > > > > > I have worked on the comments for RAT report and added the > > > results > > > > > > > at the > > > > > > > > end of - > > > > > > > > > > > http://cwiki.apache.org/confluence/display/TUSCANYWIKI/RAT+Report. > > > > > > > So > > > > > > > > shall > > > > > > > > I go > > > > > > > > ahead and correct the 9 files mentioned there to include > > Apache > > > > > > > header in > > > > > > > > them? > > > > > > > > > > > > > > > > Also, what is the best way to ensure that the Ex:3rd do > > contain > > > > the > > > > > > > > correct > > > > > > > > license text? > > > > > > > > Any old mail ref. or any other documentation? > > > > > > > > > > > > > > > > Regards, > > > > > > > > Amita > > > > > > > > > > > > > > > > On Jan 18, 2008 5:14 PM, kelvin goodson < > > > [EMAIL PROTECTED] > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Hi Amita, > > > > > > > > > > > > > > > > > > Anything unmarked needs checking to see if it fits one of > > > these > > > > > > > > > categories. I only did the ones I marked up from > > > > memory. Ex:IFF > > > > > > > files > > > > > > > > > must > > > > > > > > > me ignored, but it must be clear from the rat report > > > submitted > > > > in > > > > > > > the > > > > > > > > > release vote that thess files have been left as they are > for > > > > this > > > > > > > > reason. > > > > > > > > > You can see this kind of thing in Tuscany-1171, and in > > > previous > > > > > > > release > > > > > > > > > vote threads, where the RAT report is manually marked up. > > > > > > > > > > > > > > > > > > Kelvin. > > > > > > > > > > > > > > > > > > > > > > > > > > > On 18/01/2008, Amita Vadhavkar <[EMAIL PROTECTED]> > > > > wrote: > > > > > > > > > > > > > > > > > > > > What is the action for Ex.IFF - ignore? Also what TBD > for > > > the > > > > > > > xml > > > > > > > > files > > > > > > > > > > under sdo-tools-test which do not contain headers - i.e. > > the > > > > > > > > > > last section from RAT Report - Unresolved. > > > > > > > > > > > > > > > > > > > > Regards, > > > > > > > > > > Amita > > > > > > > > > > > > > > > > > > > > On Jan 18, 2008 4:35 PM, kelvin goodson < > > > > > > > [EMAIL PROTECTED]> > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > I've marked up the Unresolved section. There's a job > to > > > do > > > > to > > > > > > > be > > > > > > > > sure > > > > > > > > > > > that > > > > > > > > > > > each of the instances marked with Ex:TCR is actually > > > > such. We > > > > > > > also > > > > > > > > > need > > > > > > > > > > > to > > > > > > > > > > > work out what to do to take account of the > clarification > > > to > > > > > > > the OSOA > > > > > > > > > > > license > > > > > > > > > > > that happened recently, that the files marked Ex:3rd > may > > > > need > > > > > > > to be > > > > > > > > > > > changed > > > > > > > > > > > to be in line with. > > > > > > > > > > > > > > > > > > > > > > Kelvin. > > > > > > > > > > > > > > > > > > > > > > On 18/01/2008, Amita Vadhavkar < > > [EMAIL PROTECTED]> > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > Thanks Kelvin, will look at all these points. Also, > > > > > > > > > > > > I used rat-5.0.jar and got the report at - > > > > > > > > > > > > > > > > > > > > > http://cwiki.apache.org/confluence/display/TUSCANYWIKI/RAT+Report > > > > > > > > > > > > Please see "Unresolved" section in it and give > > comments > > > > > > > about what > > > > > > > > > is > > > > > > > > > > > > appropriate to fix there. > > > > > > > > > > > > > > > > > > > > > > > > Regards, > > > > > > > > > > > > Amita > > > > > > > > > > > > > > > > > > > > > > > > On Jan 18, 2008 3:56 PM, kelvin goodson < > > > > > > > [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > On 18/01/2008, Amita Vadhavkar < > > > > [EMAIL PROTECTED]> > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > Assuming name of the release as Tuscany SDO Java > > > > > > > > > 1.1-incubatingand > > > > > > > > > > > > > > keeping > > > > > > > > > > > > > > ref. to the > > > > > > > > > > > > > > old mail thread - > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > http://www.mail-archive.com/[EMAIL PROTECTED]/msg27168.html. > > > > > > > > > > > > > > I am starting a new thread now. > > > > > > > > > > > > > > > > > > > > > > > > > > > > Web Site documentation:- I could gather a few > > places > > > > > > > where > > > > > > > > small > > > > > > > > > > > > updates > > > > > > > > > > > > > > can > > > > > > > > > > > > > > be done. Please give your comments > > > > > > > > > > > > > > if these seem fine or need something > > more/something > > > > > > > else. > > > > > > > > > > > > > > > > > > > > > > > > > > > > 1) why on > > > > > > > > > > > > > > > > > > > > > http://incubator.apache.org/tuscany/sdo-java-get-involved.htmlwe > > > > > > > > > > > > > > have - > > > > > > > > > > > > > > Open CSA (SCA Standards) > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > This is confusing and needs investigating. I > think > > > you > > > > > > > are > > > > > > > > > talking > > > > > > > > > > > > about > > > > > > > > > > > > > the transition from ... > > > > > > > > > > > > > http://incubator.apache.org/tuscany/sdo-java.html > > > > > > > > > > > > > to > > > > > > > > > > > > > > > > > > > > http://incubator.apache.org/tuscany/sdo-java-get-involved.html > > > > > > > > > > > > > > > > > > > > > > > > > > In which case the "Get Involved" is a link from > the > > > > > > > "general" > > > > > > > > menu > > > > > > > > > > and > > > > > > > > > > > > > therefore is general to Tuscany. However, the > > page > > > is > > > > > > > > entitled > > > > > > > > > > "SDO > > > > > > > > > > > > > Java > > > > > > > > > > > > > Get Involved", yet seems identical to the "Get > > > > Involved" > > > > > > > page > > > > > > > > > from > > > > > > > > > > > the > > > > > > > > > > > > > Tuscany Home page's Community menu apart from the > > fact > > > > > > > that this > > > > > > > > > > page > > > > > > > > > > > is > > > > > > > > > > > > > entitled "Getting Involved: Apache Tuscany". I'm > > sure > > > > we > > > > > > > used > > > > > > > > to > > > > > > > > > > have > > > > > > > > > > > > our > > > > > > > > > > > > > own SDO Java getting involved page, and I think > it > > > has > > > > > > > > > accidentally > > > > > > > > > > > > been > > > > > > > > > > > > > overwritten at some stage. I guess we need to > look > > at > > > > the > > > > > > > wiki > > > > > > > > > > change > > > > > > > > > > > > > history and see if we can recover it. > > > > > > > > > > > > > > > > > > > > > > > > > > 2) changes in > > > > > > > > > > > > > > > > > > > > > > > > http://incubator.apache.org/tuscany/tuscany-sdo-java-faq.htmlfor > > > > > > > > > > > > > > new features, improvements > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I'm a bit confused here. I think maybe you have > two > > > > > > > separate > > > > > > > > > ideas > > > > > > > > > > > that > > > > > > > > > > > > > have been merged perhaps. I don't think we want > to > > > > detail > > > > > > > new > > > > > > > > > > > features > > > > > > > > > > > > on > > > > > > > > > > > > > the FAQ page. > > > > > > > > > > > > > > > > > > > > > > > > > > TUSCANY-1468 - Use HelperContext for scope in > > Tuscany > > > > API > > > > > > > > > > > > > > TUSCANY-1128 - Support attribute and element > with > > > same > > > > > > > name > > > > > > > > > > > > > > TUSCANY-1359 - New SDOUtil: Upper and lower > bound > > on > > > > > > > > properties > > > > > > > > > > > where > > > > > > > > > > > > > > 'isMany' is true > > > > > > > > > > > > > > CTS TUSCANY-1230 - Improvements to > > > TypeConversionTest > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Something I meant to mention in regards to your > > other > > > > > > > posting is > > > > > > > > > > that > > > > > > > > > > > > the > > > > > > > > > > > > > CTS is not part of an SDO Java release. We > haven't > > > ever > > > > > > > > > "released" > > > > > > > > > > > the > > > > > > > > > > > > > CTS, since it's never yet seemed to make sense > to > > do > > > > so. > > > > > > > SDO > > > > > > > > > > > > > implementers > > > > > > > > > > > > > who want to use the CTS can download the source. > I > > > > think > > > > > > > what > > > > > > > > we > > > > > > > > > > want > > > > > > > > > > > > to > > > > > > > > > > > > > do > > > > > > > > > > > > > here is a respin of the kind of release we have > done > > > > > > > > before, for > > > > > > > > > > the > > > > > > > > > > > > SDO > > > > > > > > > > > > > Java runtime. > > > > > > > > > > > > > > > > > > > > > > > > > > Is there anything else from > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > http://cwiki.apache.org/confluence/display/TUSCANYWIKI/SDO+Java+Project > > > > > > > > > > > > > > that can be added to it? Also do the above > > mentioned > > > > > > > JIRAs > > > > > > > > > useful > > > > > > > > > > as > > > > > > > > > > > > > part > > > > > > > > > > > > > > of > > > > > > > > > > > > > > FAQ, or mention in Release Notes will > > > > > > > > > > > > > > be sufficient? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I see now. Yes, release notes are definitely the > > > place > > > > > > > for > > > > > > > > this. > > > > > > > > > > > > > > > > > > > > > > > > > > 3) > > > > > > > > > > > > > http://incubator.apache.org/tuscany/tuscany-sdo-java-faq.htmlpage > > > > > > > > > > > > does > > > > > > > > > > > > > > not have menu > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Good point > > > > > > > > > > > > > > > > > > > > > > > > > > 4) > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > http://incubator.apache.org/tuscany/sdo-project-code-structure.htmlno > > > > > > > > > > > > > > menu , old structure > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > you are right, we need to add a section for the > lib > > > > > > > project and > > > > > > > > > the > > > > > > > > > > > > > tools-test project > > > > > > > > > > > > > > > > > > > > > > > > > > 5) > > > > http://incubator.apache.org/tuscany/getting-source.htmlno > > > > > > > > menu > > > > > > > > > > and > > > > > > > > > > > > old > > > > > > > > > > > > > > structure > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > again, yes, this doesn't reflect the move of the > > api > > > > > > > project > > > > > > > > into > > > > > > > > > > the > > > > > > > > > > > > > main > > > > > > > > > > > > > sdo trunk > > > > > > > > > > > > > > > > > > > > > > > > > > 6) developer guide - should we refer to > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > http://incubator.apache.org/tuscany/sca-java-development-guide.htmland > > > > > > > > > > > > > > make SDO Dev Guide more complete? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I think ideally we would incorporate some of the > > new > > > > > > > content > > > > > > > > from > > > > > > > > > > the > > > > > > > > > > > > sca > > > > > > > > > > > > > guide into an sdo guide. If the SCA guide is > built > > up > > > > by > > > > > > > wiki > > > > > > > > > > include > > > > > > > > > > > > > directives, there may be scope for including > generic > > > > > > > chunks into > > > > > > > > > out > > > > > > > > > > > own > > > > > > > > > > > > > guide. > > > > > > > > > > > > > > > > > > > > > > > > > > 7) > > > > > > > > > > > > > http://incubator.apache.org/tuscany/sdo-java-user-guide.htmlagain > > > > > > > > > > > no > > > > > > > > > > > > > > menu > > > > > > > > > > > > > > can refer to > > > > > > > > > > > > > > > > > > > > http://incubator.apache.org/tuscany/sca-java-user-guide.html > > > > > > > > > > > > > > > > > > > > > > > > > > > > 8) TUSCANY-1026 > > > > > > > > > > > > > > Also, why > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://svn.apache.org/repos/asf/incubator/tuscany/java/sdo/distribution/src/main/release/bin/samples/sampleProgramContents.html > > > > > > > > > > > > > > opens the html page without browser rendering it > > as > > > > > > > html? > > > > > > > > (like > > > > > > > > > > > shows > > > > > > > > > > > > > all > > > > > > > > > > > > > > html tags etc.) > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I think this is a firefox issue. It's fine in IE. > > Not > > > > > > > sure why > > > > > > > > > it's > > > > > > > > > > > > wrong > > > > > > > > > > > > > in firefox though. > > > > > > > > > > > > > > > > > > > > > > > > > > Can we provide this link in > > > > > > > > > > > > > > > > > > > > > http://incubator.apache.org/tuscany/sdo-java-user-guide.html > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > This looks like a useful rework of some of the > > content > > > > > > > that I > > > > > > > > > think > > > > > > > > > > > is > > > > > > > > > > > > > already in the site. It certainly was at one > time. > > > > > > > > > > > > > > > > > > > > > > > > > > 9) TUSCANY-1531 > > > > > > > > > > > > > > From this - comment #1 - Some pages are only > > > available > > > > > > > on the > > > > > > > > > left > > > > > > > > > > > > menu > > > > > > > > > > > > > on > > > > > > > > > > > > > > this page : > > > > > > > > > > > > > > > > http://incubator.apache.org/tuscany/developing-sdo-java.html > > > > > > > > > > > > > > It should probably be listed/visible from : > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > http://incubator.apache.org/tuscany/sdo-java-documentation-menu.htmlas > > > > > > > > > > > > > > it's > > > > > > > > > > > > > > one of the pages with more contents on it. > > > > > > > > > > > > > > looks like is fixed. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > great > > > > > > > > > > > > > > > > > > > > > > > > > > And with 7) we can fix comment #2 - User guide has > > > wrong > > > > > > > styles > > > > > > > > : > > > > > > > > > > > > > > > > > > > > > http://incubator.apache.org/tuscany/sdo-java-user-guide.html > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > fine > > > > > > > > > > > > > > > > > > > > > > > > > > Thanks Amita for this useful review. I'll pick > some > > > of > > > > > > > these > > > > > > > > > things > > > > > > > > > > > up. > > > > > > > > > > > > > Can you let me know which you plan to do and which > > you > > > > > > > would > > > > > > > > like > > > > > > > > > me > > > > > > > > > > > to > > > > > > > > > > > > > do? > > > > > > > > > > > > > Anyone else watching this thread is of course more > > > than > > > > > > > welcome > > > > > > > > to > > > > > > > > > > > pitch > > > > > > > > > > > > > in > > > > > > > > > > > > > too. > > > > > > > > > > > > > > > > > > > > > > > > > > Kelvin. > > > > > > > > > > > > > > > > > > > > > > > > > > Regards, > > > > > > > > > > > > > > Amita > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
