Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[wtp-incubator-dev] JAX-WS Contribution. Next Steps.

Hi Hristo, Danail

Following the meeting summary the next steps to proceed with the JAX-WS contribution are:

  • SAP AG needs to open an Eclipse bugzilla entry attaching the code to be contributed along with some additional information (see below).
  • A technical review of the code will need to be done.
  • The PMC will need to approve of the content’s suitability.
  • Followed by submitting a CQ (Contribution Questionnaire) to Eclipse legal requesting the Parallel IP process. Eclipse legal will review the submission and if they're satisfied with it they'll grant preliminary legal approval. This will allow the code to be checked into CVS. Eclipse Legal will continue their due diligence review in parallel and this must be completed before the code is included in a release.

For the Eclipse.org bugzilla entry go to https://bugs.eclipse.org/bugs
Select “Enter an enhancement feature request”
Product : WTP Incubator
Component : wtp.inc.jaxws

The contribution should be attached as a zip file containing the features and/or plug-ins.

In order to do a technical review of the code we'll need the version of Eclipse, WTP and any other required dependencies that are used. Plus any additional instructions that are needed to get it up and running.

There is some work that will need to be done before submitting a CQ and checking the code into CVS including:
  • Removing/Replacing the internal API's used by the JAX-WS runtime.
  • Check that all contributed files (.java, .xml, .properties, etc...) have a copyright statement.
  • Renaming the contributed features and plug-ins, package names to org.eclipse. Axis, Axis2 and CXF use the org.eclipse.jst.ws namespace.

Additional information to include in the bugzilla entry:
  •  A description of the contribution including any related information on intellectual property rights (patents, trademarks, etc..).  Was it written entirely within SAP AG.  Does it incorporate content from elsewhere or rely on the IP of others.
  •  Source of the contribution, where it's coming from e.g. was it part of a commercial product.
  •  If you are authorized by your employer to make the contribution.
  •  Need to identify all applicable licenses. Is it EPL based?
  •  A list of any 3rd party dependencies.
  •  A list of any graphics or icons contained within the contribution and their source e.g. created internally by SAP AG, copied from another plug-in within Eclipse.
  •  Does any of the code in the contribution deal in any way with cryptography.
  •  Contact details for each of the contributors: name, organization, email address and/or phone number, percent of contribution authored.
  • The name(s) of any committer(s) to nominate that will work on the JAX-WS component (integration, maintenance/bug fixes).

I'm here to help with any questions you might have.

Thanks,
Shane



Get the next generation of Free Windows Live Services Click here!

Back to the top