User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1
Amelia,
Thank you for clarifying. I don't change my vote for Oracle, but
that does seem different than what I originally was voting on. You
may want to allow members an opportunity to confirm their vote
since it's ostensibly closing tomorrow.
Still +1 (Oracle)
-- Ed Bratt
On 2/18/2021 4:13 PM, Amelia Eiras
wrote:
Yes,
Ed. That is correct.
Everyone
in the world can see the external-drive called Community under
the EF infra, as they can see the regular MP original drive.
So, Committee members can add/edit/remove files while
everyone else (users who are not explicitly granted access
as well as users without a credential at all (anonymous) can
read and download the files.
Is that correct?
(As opposed to this folder is for committee members and
the general public is NOT granted access to these files)
-- Ed
On 2/18/2021 3:53 PM, Amelia Eiras wrote:
Kevin,
Good point that was actually
brought up by 1 Jakartee after sending the
vote.
Let's clear it now with written:
All designated members of the
Steering Committee shall be granted
read/write access to this drive, it's
folders and all contents. The access to
unauthenticated users shall not be
allowed.
Adjusted to:
The MPWG
Steering Committee and the assigned
EF-EMO maintain the
space. All
designated members of the Steering Committee
shall be granted write access to
this drive, it's folders and all contents. The write
access to unauthenticated users shall not be
allowed.
Thankful for the feedback.
During my review of Ed's nice summary, I
took for granted that the write-access was
actually an explicit restriction for the
public who has only view-access.
I so appreciate our
open-communications that allow for these and
similar betterment. I think it is wonderful
to spell it & show the how.
On Thu, Feb 18, 2021
at 2:17 PM Kevin Sutter <sutter@xxxxxxxxxx>
wrote:
+1
(IBM)
I'm
voting a +1 so that we can make progress on this
shared drive. But, there's a statement below that
is confusing... We're not going to allow any access
to the shared drive contents outside of the Steering
Committee? That seems counter to what this whole
exercise was about... I thought we were trying to
open the access, not restrict it.
2. All
designated members of the Steering Committee shall
be granted read/write access to this drive, it's
folders and all contents. The access to
unauthenticated users shall not be allowed.
---------------------------------------------------
Kevin Sutter
STSM, Jakarta EE and MicroProfile architect @ IBM
e-mail: sutter@xxxxxxxxxx
Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
Part-time schedule: Tue, Wed, Thu (off on Mon and
Fri)
The
MicroProfile working group establishes the
shared-public repository, under the Eclipse
Foundation Google Drive, for maintaining
documents and material it deems suitable for
public access.
All
designated members of the Steering Committee
shall be granted read/write access to this
drive, it's folders and all contents. The access
to unauthenticated users shall not be allowed.
MPWG
website page
links
the contents to the Community drive
This
ballot will be 7-days, ending on Feb. 19th. The
ballot requires a Supermajority positive vote of the
Steering Committee members. There is no veto.
Community input and Community votes are welcomed.
However, only the votes delivered by Steering
Committee Representatives will be counted.
Thank
you, Amelia
on behalf of MicroProfile Steering Committee