Re: [Ietf-and-github] document editing and protocol implementation absent from draft-ietf-git-using-github-05

[Alexandre Petrescu <[e-mail]>]

I need to clarify something about my sensed ubiquiteness and necessity
of github.

Not only I use github for my IETF activities but I also use its access
control for document editing on my projects at work: sharepoint.

The access control of several 'sharepoint' repositories where I connect
is with my github account.

This widely encompassing access control has some drawback in some of
today's browsers: if one logs into one repository (e.g. a github
repository) with one email address then the other repositories of same
access control (e.g. sharepoint) wont work if that's not the same email
address.  A certain browser solves this problem by using 'Private
Browsing' Ctl-Shift-P.  It is the first time I absolutely and
explicitely need privacy.  I am not sure that's the intended goal of
privacy, but that's where I need it.

Alex

Le 10/03/2020 à 13:20, Alexandre Petrescu a écrit :
> 
> 
> Le 10/03/2020 à 13:06, Martin Thomson a écrit :
>> Thanks Tim, I agree.
>> 
>> The document concentrates on document production.  Though GitHub
>> is probably even better suited to software development, that's not
>> an activity that the IETF needs to have such a strong hand in.  If
>> a working group wanted to develop a reference implementation or a
>> test suite or other code product, then I would definitely
>> recommend GitHub.  But that is rare enough to treat on an ad hoc
>> basis. Many people will use the tool for that purpose and more
>> power to them for doing so, but we don't need supporting documents
>> for that.
> 
> In the WGs where I work often times the implementations are referred
> to github.  Many implementations are there.
> 
> But indeed there are more places where the software code is put,more
>  than just github.
> 
> The question would be whether to recommend one (github?), or a list
> of them.
> 
> Alex
> 
>> 
>> 
>> On Tue, Mar 10, 2020, at 22:54, Tim Wicinski wrote:
>>> 
>>> This document very much stays away from suggesting using github
>>> to write software for protocol development. I would argue that
>>> the decision on which tools to use in a WG project should be
>>> decided by the WG based on needs, etc.
>>> 
>>> tim
>>> 
>>> 
>>> On Tue, Mar 10, 2020 at 7:39 AM Alexandre Petrescu 
>>> <[e-mail]> wrote:
>>>> 
>>>> 
>>>> Le 10/03/2020 à 06:50, Martin Thomson a écrit : [...]
>>>>>>> 3.1. What to Use GitHub For
>>>>>> 
>>>>>> This section 3.1 is good in general, but does not seem to
>>>>>> me to say What to Use GitHub For. This is what it should be
>>>>>> used for: share Internet Drafts and share code
>>>>>> implementing protocols.
>>>>> 
>>>>> That is in the Introduction and Document Goals sections[...]
>>>> 
>>>> I think that is not the case.
>>>> 
>>>> It does say in Introduction and Document Goals that one goal
>>>> is document editing.
>>>> 
>>>> It does not say in either section that a goal of using github
>>>> is to write software for protocol developped by that WG.
>>>> 
>>>> Were it to say so, I would discuss it further. In one WG I am 
>>>> active I hesitate between recommending github for software 
>>>> writing, or another one.
>>>> 
>>>> Alex
>>>> 
>>>> _______________________________________________
>>>> Ietf-and-github mailing list [e-mail] 
>>>> https://www.ietf.org/mailman/listinfo/ietf-and-github
> 
> _______________________________________________ Ietf-and-github
> mailing list [e-mail] 
> https://www.ietf.org/mailman/listinfo/ietf-and-github