> On Feb 12, 2024, at 10:24 AM, sebb wrote:
>
> Why not migrate the SVN repo to Git?
> Is there any need to keep the info in SVN?
FWIW, I have no opinion on this, beyond my fiery and abiding antipathy for Git.
If that’s what people want, go ahead, and I’ll adjust. This is a discussion.
I’m n
> On Feb 12, 2024, at 10:46 AM, tison wrote:
>
>> Why not migrate the SVN repo to Git?
>> Is there any need to keep the info in SVN?
>
> I'm +1 in this direction. But it doesn't bother me if we keep a gate
> to allow commiting via SVN and sync to GitHub. If Rich likes this way
> and now he is th
> Why not migrate the SVN repo to Git?
> Is there any need to keep the info in SVN?
I'm +1 in this direction. But it doesn't bother me if we keep a gate
to allow commiting via SVN and sync to GitHub. If Rich likes this way
and now he is the most active volunteer on this initiative.
Best,
tison.
Why not migrate the SVN repo to Git?
Is there any need to keep the info in SVN?
On Mon, 12 Feb 2024 at 15:14, tison wrote:
>
> According to the INFRA ticket [1], we'd better create the
> apache/community GitHub repo first.
>
> I'm glad to execute the self-serve command but I'm yet to be a COMDEV
On Feb 12, 2024, at 10:13 AM, tison wrote:
>
> According to the INFRA ticket [1], we'd better create the
> apache/community GitHub repo first.
>
> I'm glad to execute the self-serve command but I'm yet to be a COMDEV
> PMC member. I remember that in another thread, it's said that an
> Apache Mem
According to the INFRA ticket [1], we'd better create the
apache/community GitHub repo first.
I'm glad to execute the self-serve command but I'm yet to be a COMDEV
PMC member. I remember that in another thread, it's said that an
Apache Member can self-request to be a PMC member, so:
* If any COMD
