[Bitcoin-segwit2x] SegWit2X Working Group and list charter

Thank you for this, Jeff. Given the contentiousness of this issue at multiple levels, I believe it may become important (at some point) for there to be guidelines or examples of the kinds of things that are acceptable and the kinds of things that are discouraged. Also, I believe someone will need to put forth time to moderate and apply those rules as impartially as possible, and that someone should not be you or anyone whose time is needed to hit the working group's aggressive timelines. My proposed first specific guidelines/rules, based on the comments on the github to date, would be: 1. No messages that intend to argue against the spirit of the charter itself. Specifically that means anything that argues against the hardfork portion of the charter itself, or arguments to split the charter into two unrelated, independent changes. 2. No messages that suggest or argue for very large (3+months) or undefined/undefinable delays in the timelines that have been laid out. 3. No further replies to messages that break one of these (or other) guidelines, except as a polite reminder of the guidelines and charter. There's no need for anyone to extend the arguments when already off-topic. Does this seem like a starting point to help prevent things from being derailed? Your list is also very helpful, but is less specific and is only a list of "shoulds" rather than "should nots." Thanks, Jared On Thu, Jun 15, 2017 at 8:23 AM, Jeff Garzik via Bitcoin-segwit2x <bitcoin-segwit2x at lists.linuxfoundation.org> wrote: > > This list and working group is organized in the spirit of other working > groups such as IETF, T10, T13 (or even USB 2.0), where key players - even > competitors - come together to execute on a common goal. In my past history > at Red Hat, I've seen working groups where bitter Fortune-500 rivals, with > lawsuits flying back and forth in the background, successfully work together > to produce a compatible, interoperable, vendor supported network [or > hardware] protocol. The key is a focused, limited mission with a well > defined outcome. > > This purpose of this working group and this list are not to rehash > inter-industry arguments, but to move beyond that and accomplish the > publicly stated goals (deliver SegWit + 2M HF). > > Specific technical/operational/economic issues - precisely defined - are > on-topic. Code review. Test plan review and additions. Testing and study > data. Unique problems to test. Improved solutions vs. what's committed > to the segwit2x release branch. Contributing resources > (dev/test/nodes/other). > > I'll kindly ask the other material to be in blog posts :) This list goes > out to the entire working group, and the list must have a useful > signal-to-noise ratio and high productivity, otherwise people will start > unsubscribing. > > Thanks! > > Jeff > > > > -- > Jeff Garzik > CEO and Co Founder > Bloq, Inc. > > > > _______________________________________________ > Bitcoin-segwit2x mailing list > Bitcoin-segwit2x at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-segwit2x >