Find the right place for bosh-package-java-release and bosh-package-cf-cli-release #653
Conversation
…f-cli-release With [Consolidate bosh-packages and bosh-io into cloudfoundry github org](#512) the FI WG got two repositories which don't really belong to the WG. This pr suggests a possible move but our intetion is to start a discussion to find right place for them.
|
Seems good to me, but it would also be good to have somebody from those WGs weigh in too. |
|
@dmikusa or @anthonydahanne could you please comment regarding the move of @reedr3 or @a-b could you please comment regarding the move of |
| @@ -117,6 +117,7 @@ areas: | |||
| - cloudfoundry/java-buildpack-system-test | |||
| - cloudfoundry/java-test-applications | |||
| - cloudfoundry/jvmkill | |||
| - cloudfoundry/bosh-package-java-release | |||
|
Adding @pivotal-david-osullivan for cloudfoundry/bosh-package-java-release |
|
The java package according to bosh.io is only being used by the autoscaler: https://github.com/cloudfoundry/app-autoscaler-release/tree/main/packages/openjdk-17 Maybe it would be more appropriate to move it into the Autoscaler area. |
|
Right, but what is the reason for moving some of the Why is Why is What if another release wants to start using |
|
We certainly know that FI has no expertise with the java package or bosh releases using java or how these packages should be built. It would be good to have an owner that has a vested interest in it, but maybe that doesn't exist... |
|
The alternative is to archive |
|
What is the history for why that package was introduced in the first place? Just for language completeness? |
|
Don't have the full history, but based on some old tracker stories (with virtually zero details), the commit history, and some wild speculation; my guess would be it was created because we were doing it for other languages and we had at least one bosh release using Java. |
Which release was it? Or are you talking about UAA/Credhub using Java in general (but not the bosh package)? |
|
Looks like UAA/Credhub have never used it. It was used by a closed source release from 2018 to 2020, and then app autoscaler has been using it since 2022. 2018 isn't TOO far off from when it was created, but it was ~9 months after. So my guess is it was created because we had some Java releases, primarily UAA/Credhub, and they never adopted it. |
|
I would suggest then to archive the |
|
If we did want to archive it, we'd need to give app-autoscaler-release a chance to move off of it first. |
|
Should we consider transferring ownership to the ARI Autoscaler area then? |
|
Hi @silvestre, With the implementation of #512 the FI WG got the bosh-package-java-release repository which is not used in the FI WG and we don't have expertise to maintain this repository. It looks like the ARI Autoscaler area is the only use of this repository. Do want to take ownership of this repository? The alternative is to archive it. |
Based on the discussions in #653 the decision was taken to maintain this repository. The only user of it is the ARI WG App Autoscaler Area but they are in favor to [package Java themself](#653 (comment)) instead of maintaining this repopository
Based on the discussions in #653 the decision was taken to archive the `bosh-package-java-release` repository. The only user of it is the App Autoscaler Area from the ARI WG but they are in favour to [package Java themself](#653 (comment)) instead of maintaining `bosh-package-java-release` repository.
|
Thanks @silvestre for the response. Based on the discussion I open #687 to archive |
With Consolidate bosh-packages and bosh-io into cloudfoundry github org the FI WG got two repositories which don't really belong to the WG. This pr suggests a possible move but our intention is to start a discussion to find right place for them. cc @rkoster & @jpalermo