Ping again, I need at least one more PMC vote.
Konrad
> On 21. May 2020, at 14:14, Konrad Windszus <[email protected]> wrote:
>
> I little bit more formal:
> Vote is open for 72 hours.
> [ ] +1, migrate FileVault to Git
> [ ] 0
> [ ] -1, because...
>
> Thanks,
> Konrad
>
>> On 21. May 2020, at 10:45, Konrad Windszus <[email protected]> wrote:
>>
>> For the actual migration we need a more formal vote than just
>> https://lists.apache.org/thread.html/8ea0d827d9e8488183648f2364ecd4e178b6d82e03193735aae6b5cd%40%3Coak-dev.jackrabbit.apache.org%3E.
>>
>> So please vote on the migration of FileVault to Git as outlined in the
>> original post. Thanks in advance.
>> Konrad
>>
>> On 2020/03/16 21:02:13, Konrad Windszus <[email protected]> wrote:
>>> Hi,
>>> I would like to tackle the git migration of FileVault [1] soon.
>>>
>>> I would propose to create two new repositories named
>>>
>>> - jackrabbit-filevault and
>>> - jackrabbit-filevault-package-maven-plugin
>>>
>>> Since this is already the names of the github svn mirror repos [2][3]
>>> currently in place, those would need to be reset during the migration. That
>>> would mean that the open PRs would be lost during the transition....
>>> (currently 5 open PRs)
>>> The question is if there is the need to keep the old svn mirror somewhere
>>> else, or if it is fine, if just the SVN (read-only) repo is used as
>>> reference archive.
>>>
>>> I would open an INFRA ticket soon, asking how to deal with the old svn
>>> github mirror and what options we would have for keeping the old svn github
>>> mirror (at a different location)
>>>
>>> Konrad
>>>
>>> [1]: https://issues.apache.org/jira/browse/JCRVLT-398
>>> [2]: https://github.com/apache/jackrabbit-filevault
>>> [3]: https://github.com/apache/jackrabbit-filevault-package-maven-plugin
>>>
>>>
>
