[almighty] Reorg of GitHub team - you might have lost push access

[Monica Granfield]

Thanks Max. I updated my photo and user name so hoping it's easier now.

On Fri, Oct 28, 2016 at 11:15 AM, Max Rydahl Andersen <manderse at redhat.com>
wrote:

> On 28 Oct 2016, at 16:01, Adam Jolicoeur wrote:
>
> Hi Max & Monica,
>>
>> Sarahjane (UXD) is Essjaysee on GitHub
>> Brian (UXD) is bdellasc on GitHub
>>
>
> I have added them to collaborator team so they should have an invite now.
>
> Adam, I notice all of them do not have their real name listed so they are
> actually
> very hard to find unless you know their exact username. Would be great if
> they got real name added.
>
> /max
>
>
>
>> -Adam
>>
>> On Oct 28, 2016, at 9:54 AM, Max Rydahl Andersen <manderse at redhat.com>
>>> wrote:
>>>
>>> On 28 Oct 2016, at 15:06, Monica Granfield wrote:
>>>
>>> Thanks Max,
>>>>
>>>> I understand. Just want to make sure of a couple of things. I was not
>>>> able
>>>> to @tag a person (sarahjane) on core, I believe, in a comment.
>>>>
>>>
>>> Is sarahjane this https://github.com/sarahjane ? That user has no real
>>> name, comments, description anything for me to verify who she is - and she
>>> is set to be from the philippines and a yahoo account.
>>>
>>> If she is the right Sarah, let me know and I'll add her - but would be
>>> great if she could put her real name there.
>>>
>>> If this is not her - then let me know her real username and I'll add
>>> that instead to the collab group. When she is in there she should be
>>> possible to mention/assign etc.
>>>
>>> And we all
>>>> use dev doc. I don't want to dump our busy work of posting links on
>>>> Adam.
>>>>
>>>
>>> I want to make sure that this is not prohibiting us from commenting and
>>>> the
>>>> features that support this, filing issues and posting to dev doc?
>>>>
>>>
>>> No, nothing of this limits your ability to do that. The only thing this
>>> did was
>>> to avoid someone to accidentally push stuff directly to our code repos.
>>>
>>> Issues, pull-requests etc. are all still possible.
>>>
>>> If you find there is something you cannot do that you expected to be
>>> able to let
>>> me or Aslak know and we'll figure out if bug in setup or there is
>>> another way of
>>> doing what you want.
>>>
>>> /max
>>>
>>> Thanks,
>>>> Monica
>>>>
>>>> On Fri, Oct 28, 2016 at 3:55 AM, Max Rydahl Andersen <
>>>> manderse at redhat.com>
>>>> wrote:
>>>>
>>>> Hi all,
>>>>>
>>>>> Monica, Michael V., Adam and Ranjith - you lost push (aka. write
>>>>> access)
>>>>> to the git repositories ( I assume you didn't even know you could push
>>>>> ;)
>>>>> Adam - you still have push accesss to devdoc :)
>>>>>
>>>>> Everyone outside dev group - I've created a "Collaborator" group in
>>>>> GitHub
>>>>> for people that
>>>>> needs to be assignable on issues, but do not need or do not want full
>>>>> push
>>>>> (aka. write access) to all repositories.
>>>>>
>>>>> I've put everyone I could spot that are not maintainers of actual code.
>>>>>
>>>>> Did this to avoid accidental pushes by those who might not realise they
>>>>> actually have full write access.
>>>>>
>>>>> In case I removed you wrongly and you believe you need push access just
>>>>> ask and we'll figure it out ;)
>>>>>
>>>>> p.s. none of this changes your ability to do fork, branch and do pull
>>>>> requests. Just about avoiding
>>>>> accidental pushes.
>>>>>
>>>>> Thanks,
>>>>> /max
>>>>> http://about.me/maxandersen
>>>>>
>>>>> _______________________________________________
>>>>> almighty-public mailing list
>>>>> almighty-public at redhat.com
>>>>> https://www.redhat.com/mailman/listinfo/almighty-public
>>>>>
>>>>>
>>>
>>>
>>>
>>> /max
>>> http://about.me/maxandersen
>>>
>>> _______________________________________________
>>> almighty-public mailing list
>>> almighty-public at redhat.com
>>> https://www.redhat.com/mailman/listinfo/almighty-public
>>>
>>
>>
>
> /max
> http://about.me/maxandersen
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/almighty-public/attachments/20161028/076a0130/attachment.htm>