EPIC - Transfer kiegroup repositories to the apache organization

[eduardocerqueira]

The list of repositories has been identified by #419

• Transfer to Apache the drools repository
• Transfer to Apache the kogito-runtimes repository
• Transfer to Apache the kogito-apps repository
• Transfer to Apache the kogito-examples repository
• Transfer to Apache the kogito-docs repository
• Transfer to Apache the kogito-images repository
• Transfer to Apache the kogito-operator repository
• Transfer to Apache the kogito-website repository
• Transfer to Apache the kogito-pipelines repository
• Transfer to Apache the kie-benchmarks repository
• Transfer to Apache the optaplanner repository
• Transfer to Apache the kogito-serverless-operator repository
• Transfer to Apache the optaplanner-quickstarts repository
• Transfer to Apache the kie-docs repository
• Transfer to Apache the kogito-benchmarks repository
• Transfer KIE-Tools to Apache #700
• Transfer drools-lsp repo to Apache #701
• Transfer dmn-feel-handbook repo to Apache #702

[ederign]

I just would like to double-check that we are planning to keep the commit history of the repositories.

@tiagobento did a similar thing when we moved stunner codebase inside kie-tools in the past and can give us pointers.

[tiagobento]

@ederign I think in this case we just go to Settings and do a "transfer ownership"...

[porcelli]

@mareknovotny This likely will have an impact on product builds.

I think the best option for minimizing impact is to move the repos and, at the same time, create a mirror of the moved repositories in kiegroup org.

This might require some re-configuration.

[mareknovotny]

or just copy/clone them instead of Transfer them /that is possible only on github org to org/

Do we know where the target Apache git repos will live? Is that github Apache org or completely inside Apache git infra? @porcelli @mdproctor

[porcelli]

One big advantage of transferring is to preserve the metadata associated with repositories, like the number of forks and stars... we wouldn't start from scratch.
Given that the future of those codebases will be on Apache, I think it makes more sense to preserve such information in the transfer process.

[radtriste]

what about optaplanner-website and drools-website ?

[porcelli]

@lazarotti @mdproctor @krisv could you chime in related to the repos @radtriste just mentioned?

[porcelli]

@radtriste I think we could postpone the -website repositories for phase 2. as seems that we'll have some challenges with the apache and github pages.

[radtriste]

what about kie-docs and kogito-docs ?
don't we have the same issue there ?

[porcelli]

I'd argue that the docs repos are slightly different, as we would still be able to contribute in updating docs for new features or fixes... even if we have problems to publish it

[porcelli]

closing this epic for now, the remaining repos are tracked individually