import KEYS history from svn

[hboutemy]

= https://svn.apache.org/repos/asf/maven/project/KEYS

[slawekjaranowski]

What is purpose of it?

KEYS file used in distribution area https://downloads.apache.org/maven/KEYS

has source in https://dist.apache.org/repos/dist/release/maven/KEYS

[slawekjaranowski]

How we will manage this file in this repository?

[hboutemy]

very good questions

has source in https://dist.apache.org/repos/dist/release/maven/KEYS

please take time to read the content: PMC writable only

updates to be done currently at https://svn.apache.org/repos/asf/maven/project/KEYS
then ask PMC to update dist

updating initially in Git instead of svn would ease committer work AND clarify the difference between original source for committers vs publication to dist

[slawekjaranowski]

updating initially in Git instead of svn would ease committer work AND clarify the difference between original source for committers vs publication to dist

OK, so primary source will be here and after modification a PMC will copy / sync it do dist area - right?

[slawekjaranowski]

Should we update this instruction also in this PR?

[hboutemy]

this PR was about all the svn2git work to get the history (as stated in title)
but of course, updating instructions will be the next step (and I won't do a PR: this is a proof of CTR efficiency for basic updates)

[slawekjaranowski]

even with CRT and simple changes PR can be valuable 😄

[hboutemy]

yes, I fully understand and respect (no fight against)

but TBH, when I am working on 10's of different aspects in parallel in many different Git repos (at ASF and others), it costs so much energy to open PRs here and there, wait, come back on PRs that I remember (eventually forget some), check
=> doing quickly a first commit then having other's feedback by improvement commits on top of the initial commit: this way of reviewing puts less stress and energy cost to me (and review comes in the form of improvements, which I find more positive)

on this one, I wanted a PR because I wanted RTC, but I see that I missed that I need to explain a little bit more my plan as it was not fully obvious that the plan is to migrate one step further from svn to Git

Sorry