On 11 Mar 2016, at 10:27, Rob Stradling <[email protected]> wrote:
> On 10/03/16 23:08, Stephen Kent wrote: > <snip> >> I don't read github posts of proposed text. I read I-Ds when they are >> posted, or text sent to the list, the common methods for IETF WG >> discussions of suggested text for I-Ds. Hmm. As someone who has just sent a revision-marked draft to an IETF mailing list (in proprietary file format, too, I’m ashamed to say), I was somewhat worried about the potential for confusion if someone else happened to be editing another copy of it at the time. If Github offers ways to help with version control on collaborative docs, I think that is to be encouraged. R > > Hi Steve. FWIW, I would classify GitHub as a "common method" these days... > > https://www.ietf.org/mailman/listinfo/ietf-and-github > > "About Ietf-and-github > GitHub is being used by more IETF Working Groups for proposing and tracking > changes to WG Internet-Drafts. Using GitHub for normal WG processes requires > some training, and edge cases in its usage abound. This list will be used for > answering questions of individual WG participants and for creating IETF-wide > documentation on how to use GitHub effectively in WG processes." > > -- > Rob Stradling > Senior Research & Development Scientist > COMODO - Creating Trust Online > > _______________________________________________ > Trans mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/trans
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Trans mailing list [email protected] https://www.ietf.org/mailman/listinfo/trans
