Input on the Question of the Secretariat
I have been voluntold to lead a discussion on the secretariat. In the interest of making this effective can those who have strong positions on this to speak/mail to me before start of proceedings tomorrow. Frankly I was surprised at the amount of "complications" such as RFPs in this. I am taking no position on this, just expressing surprise and a willingness to understand the issues. Daniel
I do not think that a long RFP process is needed, but that is a separate topic. I think we will need secretariat support for: - minutes - action item tracking - calendar for meeting and teleconference schedules - mail list management - web pages -- facilitate meeting information distribution -- information dissemination to the public -- wiki pages (or other technology) that allows us to each make edits to content -- posting draft document -- posting meeting minutes, transcripts, audio streams, and so on -- coordinate with ICANN staff on meeting arrangements and media interactions I have assumed that ICANN staff will continue to handle the meeting venue arrangements and travel arrangements. Russ On Jul 17, 2014, at 11:35 AM, Daniel Karrenberg wrote:
I have been voluntold to lead a discussion on the secretariat. In the interest of making this effective can those who have strong positions on this to speak/mail to me before start of proceedings tomorrow.
Frankly I was surprised at the amount of "complications" such as RFPs in this. I am taking no position on this, just expressing surprise and a willingness to understand the issues.
Daniel
I would add some more issues related to content, as there will be A LOT of text floating around, and we can not rely on us volunteers to read and write every single character: - Operate and managed contact points for the community - Compile and summarize input from the community, so that it is easily digestible by CG members (so we can dive into details where needed) - Copy editing of documents, output and whatever else CG need help with paf On 17 jul 2014, at 18:19, Russ Housley <housley@vigilsec.com> wrote:
I do not think that a long RFP process is needed, but that is a separate topic.
I think we will need secretariat support for: - minutes - action item tracking - calendar for meeting and teleconference schedules - mail list management - web pages -- facilitate meeting information distribution -- information dissemination to the public -- wiki pages (or other technology) that allows us to each make edits to content -- posting draft document -- posting meeting minutes, transcripts, audio streams, and so on -- coordinate with ICANN staff on meeting arrangements and media interactions
I have assumed that ICANN staff will continue to handle the meeting venue arrangements and travel arrangements.
Russ
On Jul 17, 2014, at 11:35 AM, Daniel Karrenberg wrote:
I have been voluntold to lead a discussion on the secretariat. In the interest of making this effective can those who have strong positions on this to speak/mail to me before start of proceedings tomorrow.
Frankly I was surprised at the amount of "complications" such as RFPs in this. I am taking no position on this, just expressing surprise and a willingness to understand the issues.
Daniel
_______________________________________________ Internal-cg mailing list Internal-cg@icann.org https://mm.icann.org/mailman/listinfo/internal-cg
Some vacation Patrik :-) And would you see the same requirement as below for external contacts and digestibility of actions or emerging directions for broad public consumption? Lynn On Jul 17, 2014, at 12:25 PM, Patrik Fältström <paf@frobbit.se> wrote:
I would add some more issues related to content, as there will be A LOT of text floating around, and we can not rely on us volunteers to read and write every single character:
- Operate and managed contact points for the community - Compile and summarize input from the community, so that it is easily digestible by CG members (so we can dive into details where needed) - Copy editing of documents, output and whatever else CG need help with
paf
On 17 jul 2014, at 18:19, Russ Housley <housley@vigilsec.com> wrote:
I do not think that a long RFP process is needed, but that is a separate topic.
I think we will need secretariat support for: - minutes - action item tracking - calendar for meeting and teleconference schedules - mail list management - web pages -- facilitate meeting information distribution -- information dissemination to the public -- wiki pages (or other technology) that allows us to each make edits to content -- posting draft document -- posting meeting minutes, transcripts, audio streams, and so on -- coordinate with ICANN staff on meeting arrangements and media interactions
I have assumed that ICANN staff will continue to handle the meeting venue arrangements and travel arrangements.
Russ
On Jul 17, 2014, at 11:35 AM, Daniel Karrenberg wrote:
I have been voluntold to lead a discussion on the secretariat. In the interest of making this effective can those who have strong positions on this to speak/mail to me before start of proceedings tomorrow.
Frankly I was surprised at the amount of "complications" such as RFPs in this. I am taking no position on this, just expressing surprise and a willingness to understand the issues.
Daniel
_______________________________________________ Internal-cg mailing list Internal-cg@icann.org https://mm.icann.org/mailman/listinfo/internal-cg
_______________________________________________ Internal-cg mailing list Internal-cg@icann.org https://mm.icann.org/mailman/listinfo/internal-cg
On 17 jul 2014, at 19:00, Lynn St.Amour <Lynn@LStAmour.org> wrote:
Some vacation Patrik :-)
Yeah, I know...can not stop thinking about the CG though...although my stay in southern France (Carpentras at the moment) is quite nice actually...
And would you see the same requirement as below for external contacts and digestibility of actions or emerging directions for broad public consumption?
Let me put it this way...I think the secretariat should help with writing and reading. That said, I am of the specific view that secretariat never ever speak on behalf of the CG and never tries to draw conclusions of the text it summarizes. I.e. summary is one thing, draw conclusions another. I have, I must say, very very good experience from SSAC and the staff support that ICANN is providing us, where we have found a good division of labour between the members of SSAC and the secretariat. Patrik
Lynn
On Jul 17, 2014, at 12:25 PM, Patrik Fältström <paf@frobbit.se> wrote:
I would add some more issues related to content, as there will be A LOT of text floating around, and we can not rely on us volunteers to read and write every single character:
- Operate and managed contact points for the community - Compile and summarize input from the community, so that it is easily digestible by CG members (so we can dive into details where needed) - Copy editing of documents, output and whatever else CG need help with
paf
On 17 jul 2014, at 18:19, Russ Housley <housley@vigilsec.com> wrote:
I do not think that a long RFP process is needed, but that is a separate topic.
I think we will need secretariat support for: - minutes - action item tracking - calendar for meeting and teleconference schedules - mail list management - web pages -- facilitate meeting information distribution -- information dissemination to the public -- wiki pages (or other technology) that allows us to each make edits to content -- posting draft document -- posting meeting minutes, transcripts, audio streams, and so on -- coordinate with ICANN staff on meeting arrangements and media interactions
I have assumed that ICANN staff will continue to handle the meeting venue arrangements and travel arrangements.
Russ
On Jul 17, 2014, at 11:35 AM, Daniel Karrenberg wrote:
I have been voluntold to lead a discussion on the secretariat. In the interest of making this effective can those who have strong positions on this to speak/mail to me before start of proceedings tomorrow.
Frankly I was surprised at the amount of "complications" such as RFPs in this. I am taking no position on this, just expressing surprise and a willingness to understand the issues.
Daniel
_______________________________________________ Internal-cg mailing list Internal-cg@icann.org https://mm.icann.org/mailman/listinfo/internal-cg
_______________________________________________ Internal-cg mailing list Internal-cg@icann.org https://mm.icann.org/mailman/listinfo/internal-cg
You are welcome to call in tomorrow. :-) Kuo Wu 從我的 iPhone 傳送
Patrik Fältström <paf@frobbit.se> 於 2014/7/17 20:00 寫道:
On 17 jul 2014, at 19:00, Lynn St.Amour <Lynn@LStAmour.org> wrote:
Some vacation Patrik :-)
Yeah, I know...can not stop thinking about the CG though...although my stay in southern France (Carpentras at the moment) is quite nice actually...
And would you see the same requirement as below for external contacts and digestibility of actions or emerging directions for broad public consumption?
Let me put it this way...I think the secretariat should help with writing and reading. That said, I am of the specific view that secretariat never ever speak on behalf of the CG and never tries to draw conclusions of the text it summarizes. I.e. summary is one thing, draw conclusions another.
I have, I must say, very very good experience from SSAC and the staff support that ICANN is providing us, where we have found a good division of labour between the members of SSAC and the secretariat.
Patrik
Lynn
On Jul 17, 2014, at 12:25 PM, Patrik Fältström <paf@frobbit.se> wrote:
I would add some more issues related to content, as there will be A LOT of text floating around, and we can not rely on us volunteers to read and write every single character:
- Operate and managed contact points for the community - Compile and summarize input from the community, so that it is easily digestible by CG members (so we can dive into details where needed) - Copy editing of documents, output and whatever else CG need help with
paf
On 17 jul 2014, at 18:19, Russ Housley <housley@vigilsec.com> wrote:
I do not think that a long RFP process is needed, but that is a separate topic.
I think we will need secretariat support for: - minutes - action item tracking - calendar for meeting and teleconference schedules - mail list management - web pages -- facilitate meeting information distribution -- information dissemination to the public -- wiki pages (or other technology) that allows us to each make edits to content -- posting draft document -- posting meeting minutes, transcripts, audio streams, and so on -- coordinate with ICANN staff on meeting arrangements and media interactions
I have assumed that ICANN staff will continue to handle the meeting venue arrangements and travel arrangements.
Russ
On Jul 17, 2014, at 11:35 AM, Daniel Karrenberg wrote:
I have been voluntold to lead a discussion on the secretariat. In the interest of making this effective can those who have strong positions on this to speak/mail to me before start of proceedings tomorrow.
Frankly I was surprised at the amount of "complications" such as RFPs in this. I am taking no position on this, just expressing surprise and a willingness to understand the issues.
Daniel
_______________________________________________ Internal-cg mailing list Internal-cg@icann.org https://mm.icann.org/mailman/listinfo/internal-cg
_______________________________________________ Internal-cg mailing list Internal-cg@icann.org https://mm.icann.org/mailman/listinfo/internal-cg
_______________________________________________ Internal-cg mailing list Internal-cg@icann.org https://mm.icann.org/mailman/listinfo/internal-cg
We are already behind schedule and I believe it is important that we are not rushed when we prepare the "communique" from this meeting. So I will charge ahead and summarise the discussion so far. I hope that this will enable us to come to consensus about the secretariat more quickly than scheduled. I suggest we do this as a two stage discussion. First agree on the tasks and then agree on how we get them done. Daniel So, can we get consensus about the following first: Secretariat tasks: - minutes - action item tracking - calendar for meeting and teleconference schedules - mail list management - web pages -- facilitate meeting information distribution -- information dissemination to the public -- wiki pages (or other technology) that allows us to each make edits to content -- posting draft document -- posting meeting minutes, transcripts, audio streams, and so on -- meeting venue arrangements -- travel arrangements -- Operate and managed contact points for the communit -- Compile and summarize input from the community, so that it is easily digestible by CG members (so we can dive into details where needed) -- Copy editing of documents, output and whatever else CG need help with -- referring press to our public information -- providing press with a complete list of ICG members for interviews etc. ... Secretariat non-tasks: -- talking to the press other than as specified above -- develop conclusions from or interpret material both from the community and the ICG ... ---- Once we have agreed on the task list we have to discuss how to obtain these services. From the discussion so far I get the impression that the emphasis is on expediency here. Would it be acceptable to ask ICANN if they are prepared to do this work as we specified provided that they will provide dedicated *people* for the duration and clearly instruct them to take direction *exclusively* from the ICG and that the web presence and outside communication is not ICANN branded? I realise that many people feel some discomfort with such a way forward and I share that discomfort to some extent. My question really is whether this discomfort is strong enough to warrant spending the energy a different solution would require. Once the discussion is moving in the direction of spending that energy I intend to very quickly get into who exactly is going to do the work of finding and contracting another party. ---
My suggestion for the part of the communique/press release regarding the secretariat: The IGC wishes to be supported by a secretariat and has agreed on a initial list of tasks for that secretariat. To execute the more sensitive tasks, IGC wishes to have dedicated persons who take their direction exclusively from the IGC. The IGC has not yet come to an agreement on the specific organisation of these sensitive secretariat functions, specifically the level of organisational independence from ICANN. The ICG has asked ICANN to provide these services until te IGC comes to consensus about specific organisational arrangements.
The IGC wishes to be supported by a secretariat and has agreed on a initial list of tasks for that secretariat. To execute the more sensitive tasks, IGC wishes to have dedicated persons who take their direction exclusively from the IGC. The IGC has not yet come to an agreement on the specific organisation of these sensitive secretariat functions, specifically the level of organisational independence from ICANN. The ICG has asked ICANN to provide these services until te IGC comes to consensus about specific organisational arrangements.
Fair summary. I’d suggest though that we do not need this to go into a communique, but rather than meeting summary/minutes. (Assuming we have a two-tier result set from the meeting, of course.) Jari
participants (6)
-
Daniel Karrenberg -
Jari Arkko -
Lynn St.Amour -
Patrik Fältström -
Russ Housley -
Wu Kuo