[ X]: Move the read/write repository from Subversion to Git and leverage
the features of Github (for now Actions and PR).
--
Ken Coar ()
Software developer, author, opinionist
Sanagendamgagwedweinini
: Greg Stein
Sent: Wednesday, May 10, 2023 2:59:24 PM
To: Stefan Sperling
Cc: dev@httpd.apache.org
Subject: Re: [VOTE] Switch read/write repository from Subversion to Git
On Wed, May 10, 2023 at 5:18 AM Stefan Sperling
mailto:s...@apache.org>> wrote:
>...
I did have some hope that we
On Wed, May 10, 2023 at 5:18 AM Stefan Sperling wrote:
>...
> I did have some hope that we would see individual self-motivated
> contributors
> arriving via various ASF projects because they are all using SVN every day
> on svn.apache.org, are programmers, might have itches to scratch, already
>
> On May 4, 2023, at 1:34 AM, Ruediger Pluem wrote:
>
> [X]: Move the read/write repository from Subversion to Git and leverage the
> features of Github (for now Actions and PR).
I trust subversion more as a vcs, but that is outweighed by the
convenience of Github's PR and issue management.
On Tue, May 09, 2023 at 11:11:40PM -0500, Greg Stein wrote:
> The ASF is completely confident in svn, and basically 99% of our corporate
> records, and some of our key workflows (eg. account requests, TLP
> graduation, ICLA recording) is all based on Apache Subversion. Also a fact.
> And zero
On Mon, May 8, 2023 at 9:08 AM Stefan Sperling wrote:
>...
> If the ASF at large was confident in SVN as a technology then our current
> reality would look quite different. The Subversion project never managed
> to grow its developer base by becoming part of the ASF. We've mostly seen
>
That is
On 5/8/23 9:16 AM, Greg Stein wrote:
> I might suggest another day or two because of the weekend and because it is
> so high-impact. Maybe an extra post to private@ in
> case some PMC members aren't tracking dev@ very closely.
>
>
I intend to close this vote in about 48 hours. It has been
On 5/4/23 10:34, Ruediger Pluem wrote:
[X]: Move the read/write repository from Subversion to Git and leverage the
features of Github (for now Actions and PR).
--
Cheers
Jean-Frederic
On 5/9/23 12:00 AM, Daniel Gruno wrote:
>
> VHS vs BetaMax anyone? :)
Video 2000 (https://en.wikipedia.org/wiki/Video_2000) rules :-)
Regards
Rüdiger
On 2023-05-08 16:18, Christopher Schultz wrote:
Graham,
On 5/8/23 05:29, Graham Leggett via dev wrote:
On 04 May 2023, at 09:34, Ruediger Pluem wrote:
This is a formal vote on whether we should move our read/write
repository from Subversion to Git.
This means that our latest read/write
> [x]: Move the read/write repository from Subversion to Git and leverage
> the features of Github (for now Actions and PR).
> [ ]: Move the read/write repository from Subversion to Git, but I don't
> want to work with Github and I will only work with
> what gitbox.apache.org offers.
> [ ]:
Graham,
On 5/8/23 05:29, Graham Leggett via dev wrote:
On 04 May 2023, at 09:34, Ruediger Pluem wrote:
This is a formal vote on whether we should move our read/write repository from
Subversion to Git.
This means that our latest read/write repository will be no longer available
via
On Mon, May 08, 2023 at 10:29:04AM +0100, Graham Leggett via dev wrote:
> This is a vote of no confidence in our own projects.
If the ASF at large was confident in SVN as a technology then our current
reality would look quite different. The Subversion project never managed
to grow its developer
On 04 May 2023, at 09:34, Ruediger Pluem wrote:
> This is a formal vote on whether we should move our read/write repository
> from Subversion to Git.
> This means that our latest read/write repository will be no longer available
> via svn.apache.org. It
> will be available via Git at
>
I might suggest another day or two because of the weekend and because it is
so high-impact. Maybe an extra post to private@ in case some PMC members
aren't tracking dev@ very closely.
On Mon, May 8, 2023 at 1:42 AM Ruediger Pluem wrote:
>
>
> On 5/4/23 10:34 AM, Ruediger Pluem wrote:
> > This
On 5/4/23 10:34 AM, Ruediger Pluem wrote:
> This is a formal vote on whether we should move our read/write repository
> from Subversion to Git.
> This means that our latest read/write repository will be no longer available
> via svn.apache.org. It
> will be available via Git at
>
> On May 4, 2023, at 4:34 AM, Ruediger Pluem wrote:
>
> This is a formal vote on whether we should move our read/write repository
> from Subversion to Git.
> This means that our latest read/write repository will be no longer available
> via svn.apache.org. It
> will be available via Git at
On Fri, May 5, 2023 at 3:19 AM Dennis Clarke wrote:
>
> > Everybody says git is decentralized, so why are you even asking this
> > question? Can't you just use any git repository, anywhere? ;-)
>
> Github is microsoft and you can bet they will break things. It is only a
> matter of time with
Everybody says git is decentralized, so why are you even asking this
question? Can't you just use any git repository, anywhere? ;-)
Github is microsoft and you can bet they will break things. It is only a
matter of time with them.
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
Four decades in
On Fri, May 5, 2023 at 2:12 AM Dennis Clarke wrote:
>...
> Why the assumption of Microsoft github? There is no reason to
> migrate to a git service such as Microsoft github when sourcehut works
> just fine as does a private git repo provided by Apache FSF itself.
>
Because the Apache
On 5/5/23 02:15, Ruediger Pluem wrote:
On 5/4/23 10:34 AM, Ruediger Pluem wrote:
This is a formal vote on whether we should move our read/write repository from
Subversion to Git.
This means that our latest read/write repository will be no longer available
via svn.apache.org. It
will be
On 5/4/23 10:34 AM, Ruediger Pluem wrote:
> This is a formal vote on whether we should move our read/write repository
> from Subversion to Git.
> This means that our latest read/write repository will be no longer available
> via svn.apache.org. It
> will be available via Git at
>
+1 for switching to GitHub (which implies a switch to git). So:
[X]: Move the read/write repository from Subversion to Git and leverage the
features of Github (for now Actions and PR).
On Thu, May 4, 2023 at 3:34 AM Ruediger Pluem wrote:
> This is a formal vote on whether we should move our
[x]: Move the read/write repository from Subversion to Git and leverage the
features of Github (for now Actions and PR).
[ ]: Move the read/write repository from Subversion to Git, but I don't want to
work with Github and I will only work with
what gitbox.apache.org offers.
[ ]: Leave
Le 04/05/2023 à 10:34, Ruediger Pluem a écrit :
This is a formal vote on whether we should move our read/write repository from
Subversion to Git.
This means that our latest read/write repository will be no longer available
via svn.apache.org. It
will be available via Git at
Am 04.05.23 um 10:34 schrieb Ruediger Pluem:
This is a formal vote on whether we should move our read/write repository from
Subversion to Git.
This means that our latest read/write repository will be no longer available
via svn.apache.org. It
will be available via Git at
On 2023/05/04 08:34:32 Ruediger Pluem wrote:
> This is a formal vote on whether we should move our read/write repository
> from Subversion to Git.
> This means that our latest read/write repository will be no longer available
> via svn.apache.org. It
> will be available via Git at
>
On 2023-05-04 07:48, Eric Covener wrote:
[x]: Move the read/write repository from Subversion to Git and
leverage the features of Github (for now Actions and PR).
[x]: Move the read/write repository from Subversion to Git and
leverage the features of Github (for now Actions and PR).
[x]: Move the read/write repository from Subversion to Git and
leverage the features of Github (for now Actions and PR).
On 5/4/23 10:34, Ruediger Pluem wrote:
This is a formal vote on whether we should move our read/write repository from
Subversion to Git.
This means that our latest read/write repository will be no longer available
via svn.apache.org. It
will be available via Git at
> Am 04.05.2023 um 10:34 schrieb Ruediger Pluem :
>
> This is a formal vote on whether we should move our read/write repository
> from Subversion to Git.
> This means that our latest read/write repository will be no longer available
> via svn.apache.org. It
> will be available via Git at
>
On Thu, May 4, 2023 at 10:34 AM Ruediger Pluem wrote:
>
> This is a formal vote on whether we should move our read/write repository
> from Subversion to Git.
> This means that our latest read/write repository will be no longer available
> via svn.apache.org. It
> will be available via Git at
>
On Thu, May 04, 2023 at 10:34:32AM +0200, Ruediger Pluem wrote:
> [ ]: Move the read/write repository from Subversion to Git and leverage the
> features of Github (for now Actions and PR).
> [ ]: Move the read/write repository from Subversion to Git, but I don't want
> to work with Github and I
On Thu, May 04, 2023 at 10:34:32AM +0200, Ruediger Pluem wrote:
> This is a formal vote on whether we should move our read/write repository
> from Subversion to Git.
> This means that our latest read/write repository will be no longer available
> via svn.apache.org. It
> will be available via
34 matches
Mail list logo
