[Internal-cg] Information requested

Kavouss Arasteh kavouss.arasteh at gmail.com
Sun Mar 8 18:49:58 UTC 2015


2015-03-08 19:36 GMT+01:00 Patrik Fältström <paf at frobbit.se>:

> Kavouss, all,
> I am sorry for not explaining in more detail the rationale for my view on
> this issue.
> We as ICG can not send questions to any operational community based on
> requests from individual ICG members. We send questions in the way and form
> that we do have consensus for in the ICG. This does not imply individuals
> in the ICG is not to rise his or her voice when the ICG member see issues.
> But there is a big difference between having a discussion in the ICG that
> either can be resolved by having other ICG members explain (I have myself
> been confused, but later understood things when listening to other ICG
> members), by having representatives / spokes persons from the OCs on ICG
> explain or clarify or ultimately ICG can send questions to the OC of course.
> But questions we should send I view should be based on a general need for
> certain information that we need to be able to do the merge, see overlap,
> gaps and inconstancies in and between the proposals.
> I therefore suggest we try to come up with generic things we as ICG should
> look for in the proposals (or in material referenced from the proposals).
> Given we have those generic issues, we should look for them, ask where data
> is, and that question might very well go back to the OC's.
> This way we will and should also of course be able to gather enough data
> so that every ICG member do they the questions they are curious about
> answered.
> Can this be an acceptable move forward?
>    Patrik
> _______________________________________________
> Internal-cg mailing list
> Internal-cg at ianacg.org
> http://ianacg.org/mailman/listinfo/internal-cg_ianacg.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ianacg.org/pipermail/internal-cg_ianacg.org/attachments/20150308/9f16a851/attachment.html>

More information about the Internal-cg mailing list