Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [che-dev] GitHub repositories to archive
jwtproxy and plugin-broker are still used in CRW 2.15; archiving them will require adapting build processes to not tag/branch/update base images at regular intervals. 

Do we need those in the post-DW world? I've assumed that jwtproxy and the brokers are still needed in Che 7.45 (as they're still in the Che Operator CSV), but if we can drop them from there and remove them from Che 7.45 and CRW 3, that would be great.

che-dev is still used by che-server (and by che-parent), but we haven't built it che-dev or che-parent in forever.

https://github.com/eclipse-che/che-server/blob/main/pom.xml#L1567
https://github.com/eclipse/che-parent/blob/master/pom.xml#L250

The others look archivable to me. 

What about backup-restore functionality? Is that coming back eventually, or is it dead in the new DW era?

https://github.com/che-dockerfiles/che-backup-server-rest/

Nick


On Mon, Mar 14, 2022 at 7:38 PM Mario Loriedo <mario.loriedo@xxxxxxxxx> wrote:
Hi all,

As a follow up of this issue [1] I would like to archive GitHub repositories that are not used anymore. The following GitHub repositories look like good candidates:


Are those still used? Is there any other repository that we should archive?

Mario

_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/che-dev


--

Nick Boldt (he/him/his)

Principal Software Engineer, RHCSA

Productization Lead :: CodeReady Workspaces 

IM: @nickboldt / @nboldt / https://divbyzero.neocities.org



“The Only Thing That Is Constant Is Change” - Heraclitus

Back to the top