+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
> > >
> >
> >
>

Reply via email to