+1, see other comments below

On Mon, Apr 24, 2017 at 8:47 AM, Tomer Brisker <[email protected]> wrote:
> +1
>
> On Mon, Apr 24, 2017 at 2:59 PM, Marek Hulán <[email protected]> wrote:
>>
>> Hello devs,
>>
>> based on our handbook [1]. I'd like to nominate Daniel for commit access
>> to
>> the following repositories:
>>
>>  - foreman-infra
>>  - foreman-installer
>>  - foreman-packaging ( to branch and cherry-pick to the release branch )
>>
>> Daniel contributes to the project for a long time, also in this area
>> [2][3][4]
>> and always has only the best intentions. He worked on 1.15 RC1 and I think
>> there's no reason why he shouldn't have access to places which are needed
>> to
>> update during the release process.
>>
>> Also I'd like to nominate him for the following.
>>
>>  - access to deb.theforeman.org to change stable, clone repos, and
>> run freight cache
>>  - add tags and build targets in koji
>>  - access to koji.katello.org to copy the mash scripts and configuration

See: http://projects.theforeman.org/projects/foreman/wiki/Koji

E-mail [email protected] or [email protected] to get Koji
certificates, and probably CC someone who already has Katello Koji
access so they can confirm? I don't see we have actual guidelines
about who should get access.


>>  - access to downloads.theforeman.org to upload signed tarballs
>>  - permission to set /topic on IRC

It would be really useful to have more people with access to IRC in
general.  It's not frequent, but occasionally during non-emea hours
there's someone flooding the channel with join/quits or some other
behavior that might need an op to take care of.  So +1 to Daniel but
it'd be nice if some people in North America had access too.

>>  - redmine permissions to modify fields http://projects.theforeman.org/
>> custom_fields/4/edit (I think administrator permission is required)
>>
>> The process for getting this is not documented anywhere, but I think it's
>> clear that Daniel would only use all of this to improve Foreman.
>>
>> Please thumbs up in the thread. I'll update the thread in one week in case
>> there were some private concerns.
>>
>> [1] https://theforeman.org/handbook.html#Becomingamaintainer
>> [2] https://github.com/theforeman/foreman-packaging/pulls?q=is%3Apr+is
>> %3Aclosed+author%3Adlobatog
>> [3] https://github.com/theforeman/foreman-installer/pulls?q=is%3Apr+is
>> %3Aclosed+author%3Adlobatog
>> [4]
>> https://github.com/theforeman/foreman-infra/pulls?q=is%3Apr+is%3Aclosed
>> +author%3Adlobatog
>>
>> --
>> Marek
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "foreman-dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> For more options, visit https://groups.google.com/d/optout.
>
>
>
>
> --
> Have a nice day,
> Tomer Brisker
> Red Hat Engineering
>
> --
> You received this message because you are subscribed to the Google Groups
> "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to