Dear Olivier, I agree with Ali. What I thought Cheryl was suggesting in Singapore that the RALO can select a person to be the Cropp RT who is not currently on the outreach or budget. We want to expand the pool and the best way of doing this is to find people who are active contributors in one other forum and get them to take on a new role. We need to find a way to energize people in the RALOs to take on new responsibilities and one way of doing this is to ask people who have contributed in some other groups to take on a mor active role and become a cropp rt. We ate not going to choose people who will not be good at this as in NARALO we already have had the experience of having a person who is not active on any committees we want to avoid this and at the same time get new blood and new people interested in becoming involved and asking them to take a job is one way of doing this and is why I thought Cheryl had suggested this. If we are restricted to choosing people who currently are on outreach or budget it really constricts us on who we can appoint and then makes us choose some one who is already active and not get a way to get more people active in leadership roles. The CROPP RT role is an important role but it is not so time consuming so is a good way to have a past contributor at meetings and working groups, just not these 2 specific ones, become more active These are my thoughts Judith Sent from my iPad Judith@jhellerstein.com Skype ID: judithhellerstein
On Mar 6, 2015, at 5:51 AM, Ali AlMeshal <dralialmeshal@gmail.com> wrote:
Thanks Olivier, While it make sense in one side "as you explained" , but on the other side you are limiting the participation of new members as well as you are giving more opportunity to the existing members of the FBSC and Outreach (in this example). In my personal view I can see this approach and concept is leading to "CLOSE Loop participation", which it should not be the case.
Ali
On 6 Mar 2015 11:53, "Olivier MJ Crepin-Leblond" <ocl@gih.com> wrote:
That makes sense.
A quick reminder why the people on the CROPP need to be either from the Finance & Budget Sub-committee or from the Outreach & Engagement Sub-committee:
- FBSC: because the FBSC is tasked with drafting financial requests from the ALAC and also engaging in all matters related to ICANN's financial plan, strategic plan, operational plan. Knowledge of these matters is mandatory when approving/amending CROPP requests especially when it comes approving requests in-line with ICANN's strategy. - Outreach & Engagement: because CROPP stands for Community Regional Outreach Pilot Program - it is a program for *Outreach* so it makes sense that the Outreach & Engagement WG is directly involved.
It would not make any sense that someone not a member of these sub-committees be a CROPP Review Team.
Kind regards,
Olivier
On 06/03/2015 09:07, Cheryl Langdon-Orr wrote: I believe I argued that any "picks / suggestions" from a RALO should be actual effective contributors to their roles in FBSC or Outreach SC and so is in total keeping with the new outline distributed by Alan, and not the thought that Judith attributed to me... (Unless I was perhaps in a fugue state ;-)
*Cheryl Langdon-O**rr ... *(CLO)
about.me/cheryl.LangdonOrr [image: Cheryl Langdon-Orr on about.me] <http://about.me/cheryl.LangdonOrr>
On 6 March 2015 at 17:56, Ali AlMeshal <dralialmeshal@gmail.com> wrote:
I am not aware of the reason behind this change but if this is something that has been discussed and agreed on initially in Singapore, then I would support the thought of Cheryl as mentioned by Judith. Ali On 6 Mar 2015 04:37, "Judith Hellerstein" <judith@jhellerstein.com> wrote:
Hi Allan,
I thought that Cheryl had added another verse to the rules stating that the RALOs could appoint anyone to serve as the CROPP RT person and this person does not have to be in the fsbc or in the outreach team
Cheers, Judith
Sent from my iPad Judith@jhellerstein.com Skype ID: judithhellerstein
> On Mar 5, 2015, at 5:41 PM, Alan Greenberg <alan.greenberg@mcgill.ca> wrote: The main difference is that there are people on the current CROPP RT who may not be on the current FBSC or the new Outreach & Engagement SC. Or may be on, but not the preferred one to be chosen. Also the selection process is somewhat different. Alan -- Sent from my mobile. Please excuse brevity and typos.
> On March 5, 2015 5:25:32 PM EST, Olivier MJ Crepin-Leblond < ocl@gih.com> wrote: > Dear Alan, > > thanks for this. Could you please explain what is the difference with > the current CROPP Review Team that is currently functioning and is > being > led by Dev Anand Teelucksingh? > Kindest regards, > > Olivier > >> On 05/03/2015 17:48, Alan Greenberg wrote: >> The CROPP Review Team is currently composed of two people per Region, >> one from the FBSC and one from the Outreach Subcommittee. >> >> Based on deliberations of the ALAC in Singapore, the recommendation > is >> that: >> >> - CROPP RT for the FY16 will consist of ten people, two per region. >> >> - One person from each region, representing the FBSC, from among FBSC >> regional Members and Participants, will be selected by the FBSC >> Members and Chair. This selection must be ratified by regional >> leadership. >> >> - One person from each region, representing the Outreach and >> Engagement SC, from among the Members or Participants of the Outreach >> and Engagement SC, will be selected by regional leadership. >> >> With this message, I am requesting a CONSENSUS CALL of the ALAC to >> approve the above CROPP Review Team composition. If you oppose this, >> please let your feelings be known no later than 12 March 2015. >> >> For clarity, in a CONSENSUS CALL, you may choose to explicitly voice >> your support, but silence will be taken as agreement. >> >> Alan >> >> _______________________________________________ >> ALAC mailing list >> ALAC@atlarge-lists.icann.org >> https://atlarge-lists.icann.org/mailman/listinfo/alac >> >> At-Large Online: http://www.atlarge.icann.org >> ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...) > _______________________________________________ > ALAC mailing list > ALAC@atlarge-lists.icann.org > https://atlarge-lists.icann.org/mailman/listinfo/alac > > At-Large Online: http://www.atlarge.icann.org > ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...) _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
-- Olivier MJ Crépin-Leblond, PhD http://www.gih.com/ocl.html
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)
ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)