BJ Hargrave wrote:

As requested in the RFC (section 0.3) and the OSGi design git hub repo
README ( <https://github.com/osgi/design#feedback>
https://github.com/osgi/design#feedback), please provide any comments on an
RFC in the form of a bug at
<https://www.osgi.org/bugzilla/enter_bug.cgi?product=OSGi%20Specification>
https://www.osgi.org/bugzilla/enter_bug.cgi?product=OSGi%20Specification.  

I sympathize with the idea of having input to specifications traceable in
the bug ticket system. Though, a downside is that this often in practice
kills the discussion. It's an additional space to watch outside of your
normal mailing list flow, you have to register an additional account to be
able to reply, etc. This pattern seems to be confirmed when looking at the
OSGi bugzilla; a typical ticket only involving the reporter and an OSGi
representative.
 
>From working in several open-source projects my impression is that the
following is the sweet spot for where to host design discussions:
 
1) Pure questions about design choices -> mailing list
2) Early phase of design proposal discussions -> mailing list
3) Late phase of design proposal discussions -> ticket system
4) Complete design proposals -> ticket system
 
My rationale is that (1) and (2) usually contain a number of "why is" and
"what is the reason for" questions that are ill suited to pile up in a
ticket system. Also, these stages are probably the ones that are of most
general interest and may attract other mailing list subscribers to join the
topic.
 
So, my experience is that a good process is to start out discussion on the
mailing list. When the question phase is over with and the proposal starts
to stabilize, a project representative either creates the ticket or asks the
reporter to do so. At this time it is possible to include appropriate
mailing list posts in the bug ticket description.
 
Of course, YMMV depending on the traffic volume of the project mailing list.
If you have very high traffic on the list, and high participation in the
ticket system, then your sweet spot for when switching to the ticket system
is probably somewhat earlier.
 
So, what's your stance on the best place to discuss (1) - (4) ?
 
Best regards
Mike
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev

Reply via email to