[RFD] Merge proposals and code reviews too private

[Ben Finney]

"Matthew D. Fuller" <fullermd at over-yonder.net> writes:

> OTOH, to take an example off my list, the DWIM revspecs need review on
> the code, BUT also deserve at least some discussion on the feature
> itself.  And a lot of people can have opinions on that that should be
> given a chance to air, who aren't going through extra undocumented and
> practically unmentioned steps to subscribe to the REAL dev discussions
> ("this time for sure!").

Right. One of the highlights of Bazaar in my eyes is that for much of
its history feature changes were discussed right here in the public
mailing list, and any user could have input; I feel this open discussion
has shaped many feature changes for the better.

If such discussions are now behind a registration-required gate, that
can only reduce the level of end-user input, and I fear it would be to
Bazaar's detriment.

> [Aaron Bentley:]
> > Code review is not designed to interoperate with mailing lists. For
> > example, unlike BB, code review could not read mail addressed to
> > bzr.dev without substantial redesign.
>
> But it's perfectly capable of having the list subscribed to it, and
> the Reply-To on the mails would ensure that comments by people on the
> list ended up in the review history.

I'm sure I'm not alone in being a Bazaar user interested in taking part
in such discussions (or at least seeing them flow past and being able to
jump in at any point), but not (yet) having or desiring a Launchpad
account. Would contributions from such people be rejected automatically?

-- 
 \     “Nature is trying very hard to make us succeed, but nature does |
  `\       not depend on us. We are not the only experiment.” —Richard |
_o__)                                   Buckminster Fuller, 1978-04-30 |
Ben Finney