Re: sr.ht --- "sir hat" --- alternatives to Github

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




> On 23 Jan 2019, at 12:07, tom petch <daedulus@xxxxxxxxxxxxx> wrote:
>> 
>> Here we seem to be saying that answer is Github, all you have to do is
>> ensure that your way of working is amended to fit that answer.
> 
> No, I don't think that's accurate.
> 
> A number of us found that developing drafts by email was not working for
> us. We had experience with revision control systems in general and
> Github
> in particular, so tried Github, and found it works, refining from there.
> It's not perfect, but it was close enough to win the make/buy decision.
> 
> <tp>
> 
> Of course it works for you but think of the arithmetic. A mailing list
> has hundreds, may be a thousand or more, people on it of whom a handful,
> less than ten perhaps, are authoring or editing; the vast majority are
> just trying to keep up with the proposed changes and comment thereon.
> 
> What that small number of authors are now doing, at least on some of the
> lists I follow, is requiring everyone to go to Github to see the changes
> that they are proposing, perhaps discussing them there and finally
> coming back to the list with, more or less, a fait accompli. (I have
> seen an AD wanting to know what discussion there was on the list over an
> issue to which the answer is none - the discussion took place outside
> the IETF technology).
> 
> So I now see e-mails tellling me
> 
> "This has caused confusion in the past; see
> <https://github.com/httpwg/http-core/issues/103>. "
> 
> or
> 
>>> 
> https://github.com/wkumari/effect-encrypt/commit/974db6cb13faecbf5b1704c
> 1da580b320843d0b3
> 
> or
> 
> where changes were made, you can see them in the working copy at:
> https://github.com/netconf-wg/rfc5277bis/blob/master/draft-ietf-netconf-
> subscribed-notifications-11.txt
> 
> So this technology will be good for the "in-crowd" but potentially bad
> for peer review and wider participation..
> 
> Tom Petch

I’m no big fan of GitHub, but it is possible to “watch” a repository and get a web or email notification for every issue or conversation.  It’s not quite the same as having the conversation actually be over email, but it still gets you the conversation delivered in email.

Yoav




[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux