Thanks Chesnay.

+1 to drop since we are not using them (flink-libraries is empty and
incubator-flink redirects to flink in GitHub).

– Ufuk

On Wed, Jan 16, 2019 at 10:38 AM Chesnay Schepler <ches...@apache.org> wrote:
>
> I've filed https://issues.apache.org/jira/browse/INFRA-17666.
>
> On 16.01.2019 10:32, Tzu-Li (Gordon) Tai wrote:
> > Makes sense if we haven't been using them.
> > +1 to drop.
> >
> > On Thu, Jan 3, 2019 at 2:45 PM Aljoscha Krettek <aljos...@apache.org
> > <mailto:aljos...@apache.org>> wrote:
> >
> >     Sounds good.
> >
> >     > On 3. Jan 2019, at 14:27, Chesnay Schepler <ches...@apache.org
> >     <mailto:ches...@apache.org>> wrote:
> >     >
> >     > Since neither of these repositories are in use (flink-libraries
> >     is empty, and incubator-flink is 3+ years old) we could just drop
> >     them I suppose.
> >     >
> >     > Any objections?
> >     >
> >     > On 03.01.2019 14:18, Apache Infrastructure Team wrote:
> >     >> Hello, flink folks.
> >     >> As stated earlier in 2018, all git repositories must be
> >     migrated from
> >     >> the git-wip-us.apache.org <http://git-wip-us.apache.org> URL to
> >     gitbox.apache.org <http://gitbox.apache.org>, as the old service
> >     >> is being decommissioned. Your project is receiving this email
> >     because
> >     >> you still have repositories on git-wip-us that needs to be
> >     migrated.
> >     >>
> >     >> The following repositories on git-wip-us belong to your project:
> >     >> - incubator-flink.git
> >     >> - flink-libraries.git
> >     >>
> >     >>
> >     >> We are now entering the mandated (coordinated) move stage of
> >     the roadmap,
> >     >> and you are asked to please coordinate migration with the Apache
> >     >> Infrastructure Team before February 7th. All repositories not
> >     migrated
> >     >> on February 7th will be mass migrated without warning, and we'd
> >     appreciate
> >     >> it if we could work together to avoid a big mess that day :-).
> >     >>
> >     >> Moving to gitbox means you will get full write access on GitHub
> >     as well,
> >     >> and be able to close/merge pull requests and much more.
> >     >>
> >     >> To have your repositories moved, please follow these steps:
> >     >>
> >     >> - Ensure consensus on the move (a link to a lists.apache.org
> >     <http://lists.apache.org> thread will
> >     >>  suffice for us as evidence).
> >     >> - Create a JIRA ticket at
> >     https://issues.apache.org/jira/browse/INFRA
> >     >>
> >     >> Your migration should only take a few minutes. If you wish to
> >     migrate
> >     >> at a specific time of day or date, please do let us know in the
> >     ticket.
> >     >>
> >     >> As always, we appreciate your understanding and patience as we move
> >     >> things around and work to provide better services and features for
> >     >> the Apache Family.
> >     >>
> >     >> Should you wish to contact us with feedback or questions,
> >     please do so
> >     >> at: us...@infra.apache.org <mailto:us...@infra.apache.org>.
> >     >>
> >     >>
> >     >> With regards,
> >     >> Apache Infrastructure
> >     >>
> >     >>
> >     >
> >
>

Reply via email to