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
Hi all,

The following repositories have been moved to eclipse-che org:

* https://github.com/eclipse/che-jwtproxy
* https://github.com/eclipse/che-website
* https://github.com/eclipse/che-plugin-broker
* https://github.com/eclipse/che-dev
* https://github.com/eclipse/che-workspace-loader (archived)
* https://github.com/eclipse/che-archetypes (archived)
* https://github.com/eclipse/che-dependencies (archived)
* https://github.com/eclipse/che-plugin-svn (archived)

The following repositories has been archived AND move to eclipse-che org:

* https://github.com/eclipse/che-ls-jdt
* https://github.com/eclipse/che-go-jsonrpc
* https://github.com/eclipse/che-lib
* https://github.com/eclipse/che-parent
* https://github.com/eclipse/che-editor-gwt-ide

Let me know if there are issues.

Mario


On Wed, Mar 16, 2022 at 10:17 PM Mario Loriedo <mario.loriedo@xxxxxxxxx> wrote:
Ok thanks for your answers.

I have created an issue [1] to remove any reference to jwtproxy and plugin-broker and adapt the build process. We cannot archive them yet but I will ask to move them to eclipse-che organization.
I will also ask to archive che-parent and move che-dev to eclipse-che organization.
Backup/Restore may eventually come back for DevWorkspace based Che so I would not archive it.



On Tue, Mar 15, 2022 at 4:56 PM Michal Vala <mvala@xxxxxxxxxx> wrote:
is che-parent used? IMO it should not be used by che-server anymore https://github.com/eclipse-che/che-server/commit/98b66ff1f64ebf2174b51e1a348d482590962e82

On Tue, Mar 15, 2022 at 4:29 PM Nick Boldt <nboldt@xxxxxxxxxx> wrote:
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.


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?


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
_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/che-dev


--
Michal Vala
Senior Software Engineer, DevTools
Red Hat Czech
_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/che-dev

Back to the top