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 Wayne,

Thanks for reporting this. I have opened an issue about that [1] that's going to be included in the next sprint backlog.

Regards,
Mario

[1] https://github.com/eclipse/che/issues/21944

On Fri, Jan 20, 2023 at 10:12 PM Wayne Beaton via che-dev <che-dev@xxxxxxxxxxx> wrote:
Hi Eclipse Che project leads and committers.

The Eclipse Foundation holds the registered trademark for "Che" as a vendor neutral agent on behalf of the project team and community. As the holder of the trademark, we have certain responsibilities to protect it, which we do -- again -- on behalf of the project team and community.

Generally, protection takes the form of limiting potential for confusion regarding who owns the name and managing how it is used by others. An adopter cannot, for example, create a product named "Che".

The "che-incubator" GitHub organisation is not, AFAICT, managed by the Eclipse Foundation and so is effectively a property that is external to the project and the Eclipse Foundation that is using the Eclipse Foundation's registered trademark.

So... please:
  • Add a line in the organisation comment that states "Che" is a registered trademark of the Eclipse Foundation;
  • Add the same trademark statement in the README for each repository;
  • Add an "®" after the word "Che" in the title; and
  • Change "Che" to "Eclipse Che®" in the first, and all prominent occurrences in the org and all repositories.
Thank you for your prompt attention in this matter.

Please let me know if you have any questions.

Wayne


On Fri, Jan 20, 2023 at 7:18 AM Ilya Buziuk <ibuziuk@xxxxxxxxxx> wrote:
Hello, folks
We are going to proceed with the next round of repositories cleanup.
Please, find the GitLab ticket [1] for archiving the following obsolete `eclipse` foundation repositories - https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/2537 


As part of the cleanup, we are also going to archive the following  `che-incubator` repositories:

- https://github.com/che-incubator/che-cpptools
- https://github.com/che-incubator/che-gateway-poc
- https://github.com/che-incubator/che-java-tests
- https://github.com/che-incubator/che-plugin-registry-dev-image
- https://github.com/che-incubator/che-plugin-viewer
- https://github.com/che-incubator/che-test-harness
- https://github.com/che-incubator/che-theia-dev-plugin
- https://github.com/che-incubator/chedo
- https://github.com/che-incubator/custom-native-editor-base-image
- https://github.com/che-incubator/dash-licenses
- https://github.com/che-incubator/devfile-api
- https://github.com/che-incubator/devworkspace-che-operator
- https://github.com/che-incubator/ms-code.typescript
- https://github.com/che-incubator/quarkus-api-example
- https://github.com/che-incubator/vscode-git
- https://github.com/che-incubator/vscode-intelephense
- https://github.com/che-incubator/vscode-teletype-guest
- https://github.com/che-incubator/release-tag-check-action
- https://github.com/che-incubator/trigger-workflow-action

Let me know if there are any questions. Thanks


On Wed, Mar 23, 2022 at 11:09 AM Mario Loriedo <mario.loriedo@xxxxxxxxx> wrote:

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


--

ILYA BUZIUK

He/Him/His

PRINCIPAL SOFTWARE ENGINEER

Red Hat

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


--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation


My working day may not be your working day! Please don’t feel obliged to read or reply to this e-mail outside of your normal working hours.

_______________________________________________
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