[NCUC-DISCUSS] confirming which are closed sessions

[Rafik Dammak]

Hi Renata,


>
> Some fellows/newcomers would like to see some sessions to get to know
> the working groups but they are not ready to know whether they'll join
> yet, even as observers
>

for working groups, sessions are usually open and everyone are invited to
welcome so they get a snapshot of ongoing work


>
> So I wonder if they could just watch the session, but they are marked
> in the briefing as * - closed
>
> I don't see a closed GNSO working  group session, can you point to one?


> I should also say that fellows/newcomers have a fluorescent tag along
> their badge so it is easy to identify them and that sometimes lets
> them get in closed sessions. It is also possible to ascertain their SG
> at door (mine are all CS). So an informal OK could also suffice.
>
>
I was not aware about such arrangement for fellows and newcomers :)
to be honest I cannot speak for those leading any closed session .

>
> These are the sessions they could be interested in and I'd like to
> know if they can get in:
>
>
> NCSG and Human Rights Meeting*
>
>
it is definitely an open session to all

>
> GNSO Informal Council Session* (Also appreciate a briefing on what is
> this about)
>
> the session is kind of informal meeting for GNSO council to discuss the
public meeting to held the day after and work on the motions.


> GNSO Development Session* (Also appreciate a briefing on what is this
> about)
>
> it is session for former and new GNSO councillors only and I think even
chair are just invited for some parts but not the whole session.



>
> Another quick question: GNSO and Nomcom – is there any session where?
>

I am not aware of joint session between GNSO and nomcom. or do you mean
separate sessions for GNSO and nomcom? you may find some details about GNSO
schedule and sessions here https://gnso.icann.org/en/icannmeeting

Best,

Rafik

>
>
> Thank you and sorry for all the questions
>
> On Mon, Oct 31, 2016 at 10:42 AM, Rafik Dammak <rafik.dammak at gmail.com>
> wrote:
> > Hi Renata,
> >
> > that is about the working groups session in Hyderabad meeting.
> > the mention of observers there is about the participation in the working
> > groups. Observers can be subscribed to the working groups mailing lists
> but
> > not able to post there nor attending the confcalls. Working group members
> > can of course post in the mailing list and attend the confcalls . the
> > working groups sessions in Hyderabad meeting are opened to everyone.
> people
> > can switch between observer and member just by informing the GNSO
> > secretariat
> >
> > you can find the note in policy brief:
> > "HOW CAN I GET INVOLVED? The WG is open to all, who may join as either a
> > Member (with full posting rights to the mailing list and the ability to
> > participate in all WG meetings) or as an Observer (with read-only status
> for
> > the mailing list). Please email the GNSO Secretariat at
> gnso-secs at ICANN.org
> > if you wish to join the group. You can also attend the WG’s open meeting
> on
> > Monday 7 November."
> >
> > Best,
> >
> > Rafik
> >
> > 2016-10-31 14:00 GMT+09:00 Renata Aquino Ribeiro <raquino at gmail.com>:
> >>
> >> Hi
> >>
> >> I am following the list but I am more confused now that I read the
> >> GNSO Policy Briefing
> >>
> >> Is it possible to confirm please if all these * really mean close
> sessions
> >>
> >> https://gnso.icann.org/en/issues/background-briefing-27oct16-en.pdf
> >>
> >> I'd also kindly ask if fellows/newcomers can be exceptionally let in
> >> as observers on them or at least some of them?
> >> If they have to go through a procedure for the permission (i.e.
> >> emailing chair directly) pls. enlighten
> >>
> >> Thank you
> >> _______________________________________________
> >> Ncuc-discuss mailing list
> >> Ncuc-discuss at lists.ncuc.org
> >> http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncuc.org/pipermail/ncuc-discuss/attachments/20161031/e07c35f6/attachment-0002.html>