[CPWG] [GTLD-WG] Feedback on EPDP Form Community Questions

Satish Babu sb at inapp.com
Wed Dec 19 17:10:37 UTC 2018


We can, of course, take this up as a priority under TTF.

However, it still may not address the issue, as *any* vendor who is giving
us the service has the potential to snoop into the data. The only way would
be to have ICANN's own in-house tool for collaborative working (some of the
open source tools can be hosted on ICANN servers, so no software
development may be required). The choice of such a tool would take time,
and may not be a solution for the immediate term.







satish


On Wed, Dec 19, 2018 at 10:28 PM Judith Hellerstein <judith at jhellerstein.com>
wrote:

> HI All,
>
> Let's add the topic of google forms or alternatives and the testing of
> these to this years work of the TTF.  We could possibly do a table
> comparing all alternatives as one of projects for this year
>
> Best,
>
> Judith
>
> _________________________________________________________________________
> Judith Hellerstein, Founder & CEO
> Hellerstein & Associates
> 3001 Veazey Terrace NW, Washington DC 20008
> Phone: (202) 362-5139  Skype ID: judithhellerstein
> Mobile/Whats app: +1202-333-6517
> E-mail: Judith at jhellerstein.com   Website: www.jhellerstein.com
> Linked In: www.linkedin.com/in/jhellerstein/
> Opening Telecom & Technology Opportunities Worldwide
>
>
> On 12/19/2018 11:54 AM, Justine Chew wrote:
>
> I've come across TellForm before but have yet to test it out extensively
> so cannot say if it's a viable alternative to Google Forms.
>
> But I agree it's a consideration for another day though non-universal
> access to Google products is a legitimate concern IMO. In any case, for our
> purposes, Hadia and Alan are going with the available alternative of
> submission via Word document. So we're good.
>
> Justine
> -----
>
>
> On Thu, 20 Dec 2018 at 00:20, Greg Shatan <greg at isoc-ny.org> wrote:
>
>> On this point:
>>
>> EPDP Leadership chose to utilize Google Forms because Google
>> automatically sorts and organizes answers to questions, which will expedite
>> the process of compiling comments received.
>>
>> To put this in more concrete terms, Google Forms automatically flows the
>> answers through to a spreadsheet, where each submitter gets their own row,
>> and each question gets its own column.  Voila, each each cell contains a
>> single party’s answer to a single question.  This saves untold hours of
>> cutting and pasting.  The spreadsheet also tabulates the answers to
>> multiple choice questions.
>>
>> Think of the spreadsheet as the “admin view” of the Google Form.  That is
>> really where the magic happens.
>>
>> There may be ways to move answers in bulk from Word docs, spreadsheets or
>> possibly even fillable PDFs.  At a minimum this requires some care and
>> precision in setting up the individual input document, so that a bulk
>> transfer of data can be made to the master spreadsheet. Meanwhile Google
>> Form just runs.
>>
>> I would love to find viable FOSS equivalents to Google Docs and Google
>> Forms, but so far I haven’t. If one exists at all, and is workable, only
>> then do we look at whether its privacy, confidentiality, data protection,
>> etc., elements are superior to Google (one assumes they would be, but
>> that’s up to the developer community).  It would be a nice project for
>> somebody.  Maybe that auction money could support developing a platform for
>> ICANN that does this stuff.
>>
>> Greg
>>
>> On Wed, Dec 19, 2018 at 10:12 AM Evin Erdogdu <evin.erdogdu at icann.org>
>> wrote:
>>
>>> Dear All,
>>>
>>>
>>>
>>> Further to the AI from today’s CPWG call, please see below feedback on
>>> EPDP form community questions.
>>>
>>>
>>>
>>> Thanks to all for productive feedback regarding the form.
>>>
>>>
>>>
>>>    - *Community concern about the Google Form “harvesting all the
>>>    information” submitted via the form.* It was noted ICANN org and
>>>    community use forms already, but this would be first time for public
>>>    comment process. The comments are also public, but the concern was Google
>>>    retention of the data.
>>>
>>>
>>>
>>> Any ALAC members concerned with Google’s retention of data may submit
>>> comments by filling out the word version of the form and sending it
>>> to At-Large Staff staff at atlarge.icann.org or policy-staff at icann.org.
>>>
>>>
>>>
>>>    - *Alternatives to the form.* It was noted that for some in the
>>>    world (i.e. in China), Google products are not available. Is there an
>>>    official alternative submission method? One could use a Word Doc or PDF of
>>>    the form. In general, the community wanted to know rationale for using
>>>    Google forms for the whole process, as opposed to a fillable PDF, or Word
>>>    doc template for comments?
>>>
>>>
>>>
>>>
>>>
>>> To facilitate offline work, or for those who may not have access to the
>>> form, you may download an offline version of the form here:
>>> https://gnso.icann.org/en/issues/epdp-gtld-registration-data-specs-public-comment-input-form-21nov18-en.docx. Please
>>> submit completed forms to At-Large Staff staff at atlarge.icann.org or
>>> policy-staff at icann.org.
>>>
>>>
>>>
>>> EPDP Leadership chose to utilize Google Forms because Google
>>> automatically sorts and organizes answers to questions, which will expedite
>>> the process of compiling comments received.
>>>
>>>
>>>
>>> For more information, anyone interested may refer to the EPDP Leadership
>>> webinar
>>> <https://community.icann.org/display/EOTSFGRD/2018-11-29+EPDP+Initial+Report+Webinar>,
>>> during which the rationale for and explanation of the Google Form is
>>> described.
>>>
>>>
>>>
>>>    - *Public visibility of draft mode. *It was noted you may save
>>>    progress on the Google Form, then submit later, but that the saved work was
>>>    public. This was seen as undesirable by many in the community. Is there a
>>>    way to not have the draft/saved form public; only have the final submission
>>>    public?
>>>
>>>
>>>
>>> Commenters have the option of using the word version to work offline and
>>> then can complete the Google form when finished. We are not aware of a way
>>> to save progress privately on Google Forms.
>>>
>>>
>>>
>>>    - *Concerns with mistakes in the form submission process*. The
>>>    suggested alternative to the above was working from a Word doc, then
>>>    copying + pasting over. The concern was the potential for mistakes. If
>>>    mistakes are made on the submission, as is currently done, would it be
>>>    possible to remove or revise the submission to public comment?
>>>
>>>
>>>
>>> Yes. Commenters are able to edit their previous submission by following
>>> prompts in the email they will receive from Google. If the commenter would
>>> like to delete a submission, please notify policy-staff at icann.org, and
>>> EPDP Staff Support can assist.
>>>
>>>
>>>
>>> Kind Regards,
>>>
>>> Evin
>>>
>>>
>>> _______________________________________________
>>> CPWG mailing list
>>> CPWG at icann.org
>>> https://mm.icann.org/mailman/listinfo/cpwg
>>> _______________________________________________
>>> GTLD-WG mailing list
>>> GTLD-WG at atlarge-lists.icann.org
>>> https://atlarge-lists.icann.org/mailman/listinfo/gtld-wg
>>>
>>> Working Group direct URL:
>>> https://community.icann.org/display/atlarge/New+GTLDs
>>
>> _______________________________________________
>> CPWG mailing list
>> CPWG at icann.org
>> https://mm.icann.org/mailman/listinfo/cpwg
>>
>
> _______________________________________________
> CPWG mailing listCPWG at icann.orghttps://mm.icann.org/mailman/listinfo/cpwg
>
> _______________________________________________
> CPWG mailing list
> CPWG at icann.org
> https://mm.icann.org/mailman/listinfo/cpwg
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/cpwg/attachments/20181219/d1ba9ac2/attachment-0001.html>


More information about the CPWG mailing list