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