johnzon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raymond Auge <raymond.a...@liferay.com>
Subject Re: [VOTE] move our Johnzon GIT repo to gitbox.apache.org
Date Tue, 08 Jan 2019 15:24:18 GMT
+1 (non-binding)

- Ray

On Tue, Jan 8, 2019 at 6:44 AM James Carman <james@carmanconsulting.com>
wrote:

> +1
> On Tue, Jan 8, 2019 at 5:01 AM Olivier Lamy <olamy@apache.org> wrote:
>
> > +1
> >
> > On Tue, 8 Jan 2019 at 21:18, Mark Struberg <struberg@yahoo.de> wrote:
> >
> > > Hi folks!
> > >
> > > We've made good experience with gitbox in other ASF projects.
> > > I'd say we just call it 'Johnzon' as is. We just have one repo, so that
> > > would be a 1:1 migration.
> > > As with everything GIT the sha1 doesn't change anyway...
> > >
> > > Can I pull the trigger?
> > >
> > > Here is my +1
> > >
> > > The VOTE is open for 72h
> > >
> > > LieGrue,
> > > strub
> > >
> > >
> > > > Am 03.01.2019 um 14:19 schrieb Apache Infrastructure Team <
> > > infrastructure@apache.org>:
> > > >
> > > > Hello, johnzon folks.
> > > > As stated earlier in 2018, all git repositories must be migrated from
> > > > the git-wip-us.apache.org URL to 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:
> > > > - johnzon.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 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: users@infra.apache.org.
> > > >
> > > >
> > > > With regards,
> > > > Apache Infrastructure
> > > >
> > >
> > >
> >
> > --
> > Olivier Lamy
> > http://twitter.com/olamy | http://linkedin.com/in/olamy
> >
>


-- 
*Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
 (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> (@OSGiAlliance)

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message