As a committer you should already have svn karma.

On Tue, Feb 13, 2018 at 4:03 PM, Edmon Begoli <ebeg...@gmail.com> wrote:
> Yes, I did, but your earlier answer clarified my question about the
> (non-existent) relationship between the key-based authentication, SVN, and
> Github workflow, specially for websites.
>
> What about the SVN privileges?
> "5. You'll need to svn add any new files"
>
> Where is that authentication and privilege setup?
>
>
> On Tue, Feb 13, 2018 at 6:55 PM, Julian Hyde <jh...@apache.org> wrote:
>
>> If easier, you can create one PR containing two commits.
>>
>> Did you see https://github.com/apache/calcite/blob/master/site/README.md ?
>>
>> On Tue, Feb 13, 2018 at 3:50 PM, Edmon Begoli <ebeg...@gmail.com> wrote:
>> > Thanks, Michael.
>> >
>> > Almost everything answered.
>> >
>> > My questions are related to website related workflow:
>> >
>> > I have some small changes to the website (two JIRAs — HOWTO, Research
>> > Activities).
>> >
>> > Should a create two pull requests from my personal Github account and,
>> > after I test locally, ask someone on the team here to review and deploy
>> via
>> > SVN?
>> >
>> > How and where do the website updates get merged and deployed, btw?
>> >
>> > On Tue, Feb 13, 2018 at 18:28 Michael Mior <mm...@uwaterloo.ca> wrote:
>> >
>> >> 1. I believe that's it. Note that this is only necessary for release
>> >> managers.
>> >> 2. There's no extra step here as far as I'm aware.
>> >> 3. No one pushes directly to GitHub. GitHub is simply a mirror of the
>> >> official ASF repo. You can see more details here:
>> >> https://reference.apache.org/committer/github
>> >> 4. SVN is only used for the website and for publishing release
>> artifacts.
>> >> All development happens via git.
>> >>
>> >> Let me know if that answers your questions.
>> >>
>> >> --
>> >> Michael Mior
>> >> mm...@apache.org
>> >>
>> >> 2018-02-13 18:12 GMT-05:00 Edmon Begoli <ebeg...@gmail.com>:
>> >>
>> >> > I have a question about the setup for committers:
>> >> >
>> >> > 1. Does this step of sending a key to a default GPG server sets up
>> >> > everything one needs on the Apache ID server, or is there another step
>> >> that
>> >> > needs to be made:
>> >> > e.g.
>> >> >
>> >> > gpg --send-key B13131DE2
>> >> >
>> >> >  http://www.apache.org/dev/release-signing.html#keyserver-upload
>> >> >
>> >> > Is there something else needed?
>> >> >
>> >> >
>> >> > 2. Once the key is up, how is that propagated to the project? Adding
>> >> > fingerprint to the Apache ID profile?
>> >> >
>> >> > 3. What needs to happen to get committer's github handle added to
>> Apache
>> >> > Calcite github?
>> >> >
>> >> > 4. How does all this get tied up with the Apache SVN for the project?
>> >> >
>> >>
>>

Reply via email to