Thanks again for your feedback. As we have a consensus, I'm moving forward:
1. I will create a PR to update resources to use main instead of master (mainly the .github/workflows/* files) 2. I will do a pass on the website/doc repository to create PRs there if needed as well (renaming master to main) 3. I will create a INFRA ticket to do the rename I will do that today (my time). Regards JB On Thu, Oct 5, 2023 at 3:02 AM Daniel Weeks <dwe...@apache.org> wrote: > > +1 > > On Wed, Oct 4, 2023, 3:08 PM Julien Le Dem <jul...@astronomer.io.invalid> > wrote: >> >> +1 >> >> On Mon, Oct 2, 2023 at 11:09 PM Fokko Driesprong <fo...@apache.org> wrote: >>> >>> Big +1! >>> >>> Thanks for raising this JB! >>> >>> Kind regards, >>> Fokko >>> >>> Op di 3 okt 2023 om 07:56 schreef Jean-Baptiste Onofré <j...@nanthrax.net>: >>>> >>>> Thanks all for your feedback. >>>> >>>> I will prepare the renaming then, I will keep you posted. >>>> >>>> Regards >>>> JB >>>> >>>> On Tue, Oct 3, 2023 at 2:36 AM Renjie Liu <liurenjie2...@gmail.com> wrote: >>>> > >>>> > +1 >>>> > >>>> > Sent from my iPhone >>>> > >>>> > On Oct 3, 2023, at 08:18, John Zhuge <jzh...@apache.org> wrote: >>>> > >>>> > >>>> > +1 >>>> > >>>> > On Mon, Oct 2, 2023 at 2:48 PM Brian Olsen <bitsondata...@gmail.com> >>>> > wrote: >>>> >> >>>> >> As with any of these changes, the one and only inescapable side-effect >>>> >> is that users' local environments will not be able to be updated. >>>> >> GitHub has otherwise made it very simple to rename branches to >>>> >> accommodate this use case. https://github.com/github/renaming Any old >>>> >> references to master will on the GitHub site itself will reroute to >>>> >> main. >>>> >> >>>> >> It's a small annoyance to make the Iceberg community more inclusive. >>>> >> For those that aren't aware of the why: >>>> >> https://en.wikipedia.org/wiki/Master/slave_(technology)#Terminology_concerns. >>>> >> >>>> >> On Mon, Oct 2, 2023 at 4:34 PM Hussein Awala <huss...@awala.fr> wrote: >>>> >>> >>>> >>> +1 >>>> >>> >>>> >>> On Mon, Oct 2, 2023 at 11:27 PM Anton Okolnychyi >>>> >>> <aokolnyc...@apache.org> wrote: >>>> >>>> >>>> >>>> +1 >>>> >>>> >>>> >>>> On 2023/10/02 20:12:37 Bryan Keller wrote: >>>> >>>> > Hearty +1 from me >>>> >>>> > >>>> >>>> > >>>> >>>> > >>>> >>>> > > On Sep 29, 2023, at 5:37 AM, Brian Olsen >>>> >>>> > > <bitsondata...@gmail.com> wrote: >>>> >>>> > > >>>> >>>> > > >>>> >>>> > >>>> >>>> > > >>>> >>>> > > >>>> >>>> > > +10000000 >>>> >>>> > > >>>> >>>> > > >>>> >>>> > > >>>> >>>> > > >>>> >>>> > > Let me know how I can help! >>>> >>>> > > >>>> >>>> > > >>>> >>>> > > >>>> >>>> > > >>>> >>>> > > On Fri, Sep 29, 2023 at 7:35 AM Jean-Baptiste Onofré >>>> >>>> > > <[j...@nanthrax.net](mailto:j...@nanthrax.net)> wrote: >>>> >>>> > > >>>> >>>> > > >>>> >>>> > >>>> >>>> > >> Hi guys, >>>> >>>> > > >>>> >>>> > > The Apache CoC >>>> >>>> > > (<https://www.apache.org/foundation/policies/conduct>) >>>> >>>> > > especially contains section 5 about the wording we use. Several >>>> >>>> > > Apache >>>> >>>> > > projects renamed the master branch to the main branch (Apache >>>> >>>> > > Karaf, >>>> >>>> > > ActiveMQ, Airflow, ...). >>>> >>>> > > As we already use main for go, rust, and python repositories, I >>>> >>>> > > wonder >>>> >>>> > > (for consistency) if we should not rename master to main on the >>>> >>>> > > "main" >>>> >>>> > > repository. >>>> >>>> > > >>>> >>>> > > Apache INFRA can do this "smoothly" but we would have to do some >>>> >>>> > > changes: >>>> >>>> > > \- update build.gradle >>>> >>>> > > \- update README.md >>>> >>>> > > \- update to GH Actions (in .github/workflows/*) >>>> >>>> > > >>>> >>>> > > Thoughts ? >>>> >>>> > > >>>> >>>> > > Regards >>>> >>>> > > JB >>>> >>>> > > >>>> >>>> > >>>> >>>> > >>>> > >>>> > >>>> > >>>> > -- >>>> > John Zhuge
