Codebase IP Clearance
Geb Codebase Intellectual Property (IP) Clearance Status
Description
Apache Geb, Geb is a browser automation solution. It brings together the power of WebDriver, the elegance of jQuery content selection, the robustness of Page Object modelling, and the expressiveness of the Groovy language.
Project info
- Which PMC will be responsible for the code: Apache Groovy PMC
- Into which existing project/module: Geb will be a subproject of Groovy with its own repo and mailing lists
- Officer or member managing donation: Paul King
Completed tasks are shown by the completion date (YYYY-MM-dd).
Identify the codebase
| date | item |
|---|---|
| 2024-10-12 | A WIPO global brand search shows no single word trademarks for GEB under the software classification. Some images with GEB as the description and GEB as part of the image are shown but seem unrelated and are expired. Some multiple word names with GEB and other words appear but seem to be in the construction industry. The Geb project has existed since 2010. |
| 2024-10-16 | Original code: https://github.com/geb/geb/commit/df51ea3b9aba |
| yyyy-mm-dd | The code has been injected in the following git repo: http://git-wip-us.apache.org/repos/asf/geb-tbd/repo with all its history |
Copyright
| date | item |
|---|---|
| 2024-10-12 | Check and make sure that the papers that transfer rights to the ASF been received. It is only necessary to transfer rights for the package, the core code, and any new code produced by the project. |
| 2024-10-12 | Check and make sure that the files that have been donated have been updated to
reflect the new ASF copyright.
You can run the rat gradle task to check that all files have acceptable headers but check rat exclusions in geb.groovy-module.gradle. There are some TODOs there which represent some things we need to add to one or more NOTICE files before first release. |
Verify distribution rights
Corporations and individuals holding existing distribution rights:
- Not applicable
| date | item |
|---|---|
| 2024-10-12 |
Check that all active committers have a signed CLA on record. ICLAs have been signed by the following committers: Marcin Erdmann (GitHub Id: erdi), Luke Daley (GitHub Id: ldaley), Jonny Carter (GitHub Id: jonnybot0) |
| 2024-10-12 | Remind active committers that they are responsible for ensuring that a Corporate CLA is recorded if such is required to authorize their contributions under their individual CLA. |
| 2024-10-12 | Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. |
| 2024-10-12 | Check and make sure that all items depended upon by the
project is covered by one or more of the following approved
licenses: Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or
something with essentially the same terms.
The majority of the build/runtime dependencies are Apache licensed. A small number have other Cat A licenses (MIT, BSD, CC0). A smaller number still have Cat B licenses (EPL, MPL, CDDL) but are only expected in binary form in convenience binaries. Use checkLicense and generateLicenseReport tasks to confirm and check the allowed-licenses.json config file, but note that the plugin isn't perfect. |
Generally, the result of checking off these items will be a Software Grant, CLA, and Corporate CLA for ASF licensed code, which must have no dependencies upon items whose licenses that are incompatible with the Apache License.
Organizational acceptance of responsibility for the project
Related VOTEs:
- o Vote on dev@groovy.apache.org Message-ID : <TBD@TBD>
- o Vote result on dev@groovy.apache.org Message-ID : <TBD@TBD>