Hi, I switched away from Digest a moment ago, so replying out of thread. I have requested to join ttf yesterday - I humbly hope you will have me and I can be of use. I am resending my NCUC post for context. I hope it clarifies my earlier request. As you see, it was mainly a request for inclusion. After active NCUC engagement, Fellowship FB issue has been resolved. The conversation I had with Fellowship program about the right to opt out of FB shows the lack of awareness over privacy issue. There's strong support and understanding in NCUC, however. In TTF advisory role, I say both Fellowship and other ICANN parts could possibly benefit from short informative sessions: - on secure communication - privacy - (briefly) on being accepting of prerequisites to ICANN volunteer engagement for FOSS, ethical hacking or privacy activists in working groups I see many potential benefits: - raised awareness of FOSS, handling data and Open Standards (Tallinn egov declaration is believed to confirm this direction for the whole of EU this fall, thanks to Estonian leadership) - more private and secure communication when handling sensitive issues within ICANN - being more inclusive towards volunteers from FOSS etc. communities - possibly gaining more qualified volunteers in the distant future - someone being genuinely surprised by some of the fun FB or Google facts :) And the main and most realistic benefit I see: - changing the ICANN awareness climate a little bit Would it be possible for ttf to suggest, and if acceptable even hold such brief session for the Fellowship? (or any interested group within ICANN) If this is out of TTF scope, what would be the appropriate channel for this suggestion? * I kindly request to be included in the next ttf group call where alternatives tools will be discussed - I hope I can contribute to this important discussion. BR, Dina Solveig -- * * * Dina Solveig Jalkanen, thomascovenant on Freenode Friendly geek in Amsterdam chaos, ICANN NCSG, FSFE Fellow https://wiki.techinc.nl/index.php/User:Thomascovenant Hello, I am writing about a general matter that can still be quite important to some. I respectfully disagree with making Facebook obligatory for ICANN Fellowship program participation, yet it doesn't seem possible to question this decision. Further, the decision to deny fellowship to those who do not comply with Facebook demand makes no sense to me. I would welcome diverse participation of FOSS community, privacy activists and ethical hacking communities in ICANN work. It can be very valuable. I don't want any single fellow be forced to compromise their principles in order to make volunteer contribution to ICANN work (please read the links below). At the moment this is solved by forcing to register under a false name, which is not the right thing to do on behalf of a large organization. Alternative means of communication should be easily available to those who ask for them, minor detail of communication platform should not be the reason to discourage volunteer work. We also have Chinese and Iranian fellows. Some countries impose FB cencorship (wiki link below), which can also be an issue... What are your thoughts on this general subject? And how a good solution can be found? Best regards, Dina Solveig Jalkanen, grateful for technical fellowship to ICANN60 Resources: FB Censorship: https://en.wikipedia.org/wiki/Censorship_of_Facebook Some information about Facebook from Richard Stallman: https://stallman.org/facebook.htm http://www.salimvirani.com/facebook

From public Fellowship emails by Siranush Vardanyan Fellowship Program Manager, Public Responsibility Support, ICANN:

"Last but not least: Social Media I will be creating an ICANN60 Facebook page which is a required participation for this program. Those who do not have Facebook page, please, create one, as you will be asked to join ICANN60 Facebook page." -- * * * Friendly geek in Amsterdam, FSFE Fellow https://wiki.techinc.nl/index.php/User:Thomascovenant _______________________________________________ Ncuc-discuss mailing list Ncuc-discuss@lists.ncuc.org http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss