Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse.org-committers] Eclipse IT update

There is an option to continue using Gerrit, JGit and EGit moved their repos to GerritHub which is using
Gerrit for code review and mirroring the repos to GitHub.

 

See

https://eclipse.gerrithub.io

https://github.com/eclipse-jgit/jgit

https://github.com/eclipse-egit/egit

 

From: eclipse.org-committers <eclipse.org-committers-bounces@xxxxxxxxxxx> on behalf of Denis Roy via eclipse.org-committers <eclipse.org-committers@xxxxxxxxxxx>
Date: Thursday, 14. November 2024 at 17:16
To: Eclipse Committers general discussion <eclipse.org-committers@xxxxxxxxxxx>
Cc: Denis Roy <denis.roy@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [eclipse.org-committers] Eclipse IT update

Hello Vincent,

These are great questions, and I suggest answers below:

On 2024-11-14 08:59, LORENZO Vincent wrote:

Hello,

   We thank you for these informations.

Concerning the first point, we have several questions :

- Does Eclipse’s GitLab propose a solution like the GitHub Discussion service ?

GitLab does not have a Discussion service like GitHub, but there is a Feature Request for this:

https://gitlab.com/gitlab-org/gitlab/-/issues/15641

One workaround I've seen mentioned: projects use a separate "repository" without code, called "Discussions" and utilize issues for discussion topics. See https://gitlab.com/gitlab-org/geo-team/ (they have a discussions repo).

If your project would like to explore that option, please ask for a dedicated Discussions repo via a HelpDesk issue (and please obtain +1 from the project lead).

https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues

 

- Does the chat service allow to group messages by topic (to keep the same behavior than a forum ) ?

Chat service has the concept of threads, so rather than replying inline in a conversation, a reply can be made inside a thread.

- Can every user access the chat ?

Yes. Since the Chat is based on Matrix, you can use your Eclipse account, and others can use their Matrix account

- How is managed the chat ? Can every user create or invite in a channel ?

Channels (called Rooms in Matrix) can be created by filing a HelpDesk issue.

https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues

 

- Can we reference issues in the threads (aside from the url, e.g. GL-xxx or GH-xxx) ?

There is no shorthand way to reference issues; URLs work fine for this.

 

- Do you plan to evaluate these solutions in order to keep only one in the future ?

If you mean, GitLab and GitHub, both are the solutions for the foreseeable future.

 

 

               Concerning the second point, we already migrated all our gits to GitLab and Eclipse provided us the required help. We thank the foundation for that, but to be honest, we are many to regret the gerrit review tool 😢.

 

The Gerrit workflow was certainly different; those individuals who liked it (I liked it) like it A LOT and prefer it over the Pull Request workflow; those individuals who came from a Pull Request workflow were confused by Gerrit.

There is no wrong answer :)

 

Denis

 

 

Regards,

--

Vincent LORENZO

               

De : eclipse.org-committers <eclipse.org-committers-bounces@xxxxxxxxxxx> De la part de Denis Roy via eclipse.org-committers
Envoyé : mardi 5 novembre 2024 20:49
À : Eclipse Committers <eclipse.org-committers@xxxxxxxxxxx>
Cc : Denis Roy <denis.roy@xxxxxxxxxxxxxxxxxxxxxx>
Objet : [eclipse.org-committers] Eclipse IT update

 

Greetings committers and project leads, I have a relatively long but useful update for you.

 

1. Eclipse Forums is being sunset

A decade ago [0], we began the discussion about what to do with the Eclipse Forums as, with time, the underlying software has become stale and is now a serious security liability for the Foundation. After a decade of reluctance, the Forums will be sunset December 31, 2024.  

Please discuss with your community which location is best for user-centric discussions for your project. Some options include using the Eclipse Chat Service [1], GitHub Discussions that can be enabled for your project, or the creation of a user discussion mailing list. Please use a HelpDesk ticket [5] to request any needed resources for your project.

The Forums will be archived in read-only, static html format. More information can be found in the HelpDesk issue [0].

 

2. Git/Gerrit/Bugzilla deprecation status

The deprecation of Git/Gerrit & Bugzilla is on schedule, and at this time, the vast majority of projects have migrated off those platforms. The plan can be found here [2]

The infra team will create a (very large) static html copy of all Bugzilla bugs in the coming months.  Bugzilla sunset is slated for May 2025.

 

3. Jiro/CBI build infra updates

The Foundation's Releng team has been knee-deep in migrating Jenkins instances to a robust and scalable storage cluster (away from a single storage device operating beyond capacity) to help improve the service availability of the Common Build (CBI) Jenkins offering.

Although the migrations are not yet complete, we're already observing much needed stability improvements across all instances.  You can follow the effort here [3]

For more information on Eclipse Common Build, please see: https://github.com/eclipse-cbi/cbi/wiki

 

4. RISC V platform now available for builds

As detailed here [4] RISC V agents are available for builds in a very limited quantity for building native code. If you'd like to use the agents, please file a HelpDesk ticket [5].

 

5. Eclipse Chat Service

Did you know that the Foundation hosts a Chat Service. You can check it out at https://chat.eclipse.org/ and your project can request a room by filing a HelpDesk ticket [5].

 

6. Release Engineers take note

We encourage all project Release Engineers to subscribe to, and monitor the cross-project-issues-dev mailing list [6]. It is the primary mechanism used by the EF Releng team to communicate about CBI and build/releng issues in general.

 

7. New IT Service Level Objectives

The EF's IT Service Level Agreement (SLA) has been updated to reflect new realities in 2024, and has been renamed to Service Level Objectives. In short, we've removed Git/Gerrit/Bugzilla and other terminated (or deprecated services) and have added GitLab, the Eclipse Downloads area, the ECA and sync mechanisms as Critical or Best Effort Services.  You can consult the new SLO document at [7].

The Foundation is committed to providing a quality, robust and useful infrastructure and set of tools to allow you to get things done.

 

8. New email channel for the Infra team

The Infra team, known previously as Webmasters, can now be reached at infratructure@xxxxxxxxxxxxxxxxxxxxxx. The preferred way of interacting with the EF IT team is through HelpDesk [5].

 

Many thanks for taking the time to read this communication. We understand that migrations and improvements can be disruptive, and we're sparing no effort towards minimizing the downsides and helping your projects be successful.

 

[0] https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/187

[1] https://chat.eclipse.org/

[2] https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Gerrit/Gerrit-and-Bugzilla-deprecation-and-migration-plan#oct-2024

[3] https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/5054

[4] https://gitlab.eclipse.org/eclipsefdn/infrazilla/-/issues/1730

[5] https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/

[6] https://accounts.eclipse.org/mailing-list/cross-project-issues-dev

[7] https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/IT-Service-Level-Objectives

 

e Community for Open Innovation and Collaboration

Twitter: @droy_eclipse


Back to the top