On Fri, 2010-10-29 at 11:19 +0200, ext Carsten Munk wrote:
> 2010/10/29 Igor Stoppa <[email protected]>:

> As such, there's really not much issue about hiding some things, but
> we need procedures to handle these kind of situations, publically
> described - people are much much more inclined to accept things if
> they're documented.

yup, i blame this mostly on the fact that we all are getting used to a
new way of doing things.

> We can have a win-win situation by having more community in the
> bugzilla, so people feel free to discuss the entire platform from top
> to bottom.
> 
> 8474 is a nightmare because currently, as stated in
> http://wiki.meego.com/Quality/HandsetTestReport/1.2_N900Acceptance20101028
> , [1.2] "org.oFono" service can not be found on Dbus, which causes
> modem power on fail. This blocks N900 images naturally and probably
> also others.
> 
> This could be handled much better since there's obviously a deeper
> issue beyond 'modem power on fail' and -that- bug could be forked and
> made 'secret'.

I believe that specific one should be reworked and forked, possibly as
proposed below.

What we have seen was an emergency situation where the emergency brake
was pulled and it's not meant to be nice, it's meant to be mostly
effective.

> So, I propose the following procedure:

<snip>

> Just don't get things to a point where we require a NDA to help admin
> the bugzilla. Think that in the future, Linux Foundation, Intel,
> Nokia, Acer and many others has to work together to make that central
> piece of -community infrastructure- work properly. So maybe we should
> instead help in MeeGo with central functions to say "export/move this
> bug to bugzilla instance http://bugzilla.momcorp.com"; where private
> talks can go on. And the same from the products bugzilla's vendors
> build, think Nokia MeeGo exporting a bug to MeeGo.com.

:-)

I'm not the one to be convinced, but it's a fact that legal agreements
are binding and must be respected.

Things can be changed, but playing by the rules.

Starting from existing setups usually helps.

For example this:

http://www.kroah.com/log/linux/free_drivers.html

could also be extended to bugs-handling.

cheers, igor

_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev

Reply via email to