Re: [platform-dev] Has the time come?

On Tue, Mar 16, 2021 at 7:04 PM Christoph Läubrich wrote: > At least ASF "gitbox" support a "double-master-setup": Apache GitBox is not exactly a comfortable solution. I submitted a few patches to Maven, and while submitting the patch per se was quite easy and convenient (just a GitHub pull re

Re: [platform-dev] Has the time come?

> It's not a rule, it's just the way it works Right! jumped to false conclusions. Thanks for clarifying. 🤐 ___ platform-dev mailing list platform-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev

Re: [platform-dev] Has the time come?

No offense taken Wim, no worries. It's not a rule, it's just the way it works. The publishing process only looks at repo hosted at git.eclipse.org/c/www.eclipse.org for several reasons, IIRC: * Use direct file system access to poll for changes (/gitroo

Re: [platform-dev] Has the time come?

Mikael, I did not mean to lecture you (after reading my reply again 🙏). It's funny, really; we have this hosting rule, but also a trick how to circumvent it 😉 On Tue, Mar 16, 2021 at 4:57 PM Wim Jongman wrote: > > Just a quick note that content served by https://www.eclipse.org/ (and > as such

Re: [platform-dev] Has the time come?

At least ASF "gitbox" support a "double-master-setup": https://gitbox.apache.org/ from a git perspective this would also be possible without any tooling support: - clone the "master"-git repo - add the "mirror" as a another origin - pull the "mirror" orgin and merge/cherry-pick the PR from th

Re: [platform-dev] Has the time come?

The idea of allowing contributors to decide how they want to contribute is an interesting idea. Eclipse CDT has had a mirror on github for a long time, and, as you can't disable Pull Requests on a GitHub repo, we get a sporadic PR via the GH web interface. I wonder whether as an early transition po

Re: [platform-dev] Has the time come?

> Just a quick note that content served by https://www.eclipse.org/ (and as such https://www.eclipse.org/eclipse/) must currently be hosted on a git repository hosted at https://git.eclipse.org/c/www.eclipse.org. That's how it works Git is a blokchain secured source repo. It does not matter where

Re: [platform-dev] Has the time come?

Instead of pushing to a branch in the main repo which is for committers only, there is also the "Fork Workflow". This would be the workflow for contributors. I've added this to the wiki: https://wiki.eclipse.org/Platform-releng/Migration_To_GitHub ___ pl

Re: [platform-dev] Has the time come?

Hi, Just a quick note that content served by https://www.eclipse.org/ (and as such https://www.eclipse.org/eclipse/ ) must currently be hosted on a git repository hosted at https://git.eclipse.org/c/www.eclipse.org

Re: [platform-dev] Has the time come?

The goal is not just to change tools for the sake of changing tools, as there is a relative consensus that the current tools we have (BZ and Gerrit) are pleasant enough to work with. The goal is to facilitate contributions and get more contributors, this is one of the key factors the sustainability

Re: [platform-dev] Has the time come?

I preface everything I say on this thread with the observation that "I am completely uniformed on the details"...  All this squash-merge, force-push means very little to me so I'm admittedly highly ignorant... I continue to get the sense that decisions are being made on what feels like a knee-

Re: [platform-dev] Has the time come?

Note that GitHub doesn't mandate GitHub action nor exclude Gerrit. Wild Web Developer uses GitHub actions and ci.eclipse.org (controlled by a Jenkinsfile), and it's working all right. We could (and IMO should) just start moving code + review for some of the repos, adapt the URIs here and there and

Re: [platform-dev] Has the time come?

JDT gerrit build takes one hour at least. 10 patches with 3 rebuilds and we have no free builds. That is not enough only for a single project. Am 16. März 2021 12:10:16 MEZ schrieb Lars Vogel : >https://github.com/pricing > >2,000 Actions minutes/month Free for public repositories so we would >ge

Re: [platform-dev] Has the time come?

That would be a bad restriction for the for project. Some projects use actions already like Windowbuilder and Wild Web Developer, AFAIK they have not seen issues with time limitations yet. Link for windowbuilder: https://github.com/eclipse/windowbuilder On the plus side, every fork would get the s

Re: [platform-dev] Has the time come?

I may be wrong but I think the Eclipse foundation would fall under the category GitHub Free for Organizations so as a total it would get 2000 mins for *all* its repositories according to https://docs.github.com/en/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-githu

Re: [platform-dev] Has the time come?

https://github.com/pricing 2,000 Actions minutes/month Free for public repositories so we would get ~ 33 hours of free and fast build time per month and repo. Not sufficient for our daily aggregator build but really nice for validation builds and sufficient for most platform repo activities AFAICS

Re: [platform-dev] Has the time come?

As far as I know, there are usage limits for organizations when it comes to Github runners / actions - even for open source projects. Can you please share the source of your information, Lars? On Tue, Mar 16, 2021 at 11:42 AM Lars Vogel wrote: > Moving to Github would allow us to use Github acti

Re: [platform-dev] Has the time come?

Moving to Github would allow us to use Github actions for build verification (using Maven), which can be easily configured to be cross platform and cross Java versions and are free for Open Source projects and run on the Github infrastructure which seems better in terms of scalability and availabil

Re: [platform-dev] Has the time come?

On Tue, Mar 16, 2021 at 10:54 AM Sebastian Zarnekow < sebastian.zarne...@gmail.com> wrote: > Looking at the https://github.com/eclipse/lemminx-maven/pull/205 I don't > see the comments *on* the previous commit that became obsolete due to a > force push. I can still see them as outdated in the line

Re: [platform-dev] Has the time come?

Looking at the https://github.com/eclipse/lemminx-maven/pull/205 I don't see the comments *on* the previous commit that became obsolete due to a force push. I can still see them as outdated in the linear conversation though. This is also the case on Gitlab though. So the force-push habit (which is

Re: [platform-dev] Has the time come?

Force-Push is simply bad and there is a reason git explicitly require the user to 'force' it. If one want's to have "one-change-one-commit" he/she can simply use the "sqash-merge" button. So I don't really see any difference from a user-pov. Am 16.03.21 um 10:27 schrieb Nikita Nemkin: On Tu

Re: [platform-dev] Has the time come?

The _major_ difference is that GitLab supports Gerrit-like review > workflow: it preserves force pushed merge request versions and > comments on them, while GitHub doesn't. > That is not true anymore (it did change about 2 years ago IIRC). See for instance https://github.com/eclipse/lemminx-maven/

Re: [platform-dev] Has the time come?

On Tue, Mar 16, 2021 at 2:03 PM Christoph Läubrich wrote: > > Github / Gitlab are all based on git, so the "workflow" is more a matter > of (web) UIs. The _major_ difference is that GitLab supports Gerrit-like review workflow: it preserves force pushed merge request versions and comments on them,

Re: [platform-dev] Has the time come?

Github / Gitlab are all based on git, so the "workflow" is more a matter of (web) UIs. If a certain "usage" is recommended/preferred I would suggest to integrate support for this in EGit (it might autodetect a project as "eclipse" based on a special marker file or even a config file in the re

Re: [platform-dev] Has the time come?

I don't think I have enough details to make it a valuable addition to the wiki page. As far as I understood the thing is that GitLab is located in Europe while GitHub is located in the US. With the move of the foundation to Europe this is something to consider. Maybe a webmaster or someone from th

Re: [platform-dev] Has the time come?

Given past trends (twists and turns), I would be slightly concerned that the long term trend might be that we should all use GitLab and that the Foundation will want to support only one thing and rather two, to save resource.  Of course that could be a misguided thought, but resource savings do

Re: [platform-dev] Has the time come?

Dirk, All, Please at this concern to the wiki page. Besides the legal consideration, is there a difference in the intended workflow on GitHub or GitLab? IMHO the discussion should first be about the envisioned workflow, the differences between that envisioned workflow and the current workflow, an

Re: [platform-dev] Has the time come?

On Mon, Mar 15, 2021 at 8:22 PM Dirk Fauth via platform-dev < platform-dev@eclipse.org> wrote: > Is there a decision made with regards to GitHub vs GitLab? As far as I > understood there are legal constraints to consider. That is why the > foundation prefers GitLab. > GitLab is a great tool, but

Re: [platform-dev] Has the time come?

https://git.eclipse.org/c/www.eclipse.org/eclipse.git/ can be migrated. I don’t see an issue here. From: Aleksandar Kurtakov Sent: 16 March 2021 12:56 To: Eclipse platform general developers list. Subject: [EXTERNAL] Re: [platform-dev] Has the time come? On Tue, Mar 16, 2021 at 7:14

Re: [platform-dev] Has the time come?

On Tue, Mar 16, 2021 at 7:14 AM Sravan K Lakkimsetti < sravankum...@in.ibm.com> wrote: > Hi, > > > > For the website I am not completely sure on what this entitles. The > current build page(and its contents) for platform is of 5.5 > GB(approximately). I don’t think I would want this kind if data o