Incubation public comment period


Quinton Hoole <quinton@...>
 

+1. People have other jobs and vacations too. I don't see the need to rush this.


On Fri, May 15, 2020, 13:13 Kris Nova <kris.nova@...> wrote:
Strong agree with alexis - I’m booked solid these days and unless something is on fire it usually gets bumped down the list.

I usually book at a minimum one week out from initial engagement and I believe that’s fairly common in the industry. So setting aside time for myself for something like this would require 7+ days to even get it on my calendar to review.


Kris Nova
Chief Open Source Advocate


> On 15 May 2020, at 09:38, alexis richardson <alexis@...> wrote:
>




Vinod
 

Hi Chris,


Not all DD reviews and discussions are open and public. The communications are happening in the private channels, this has been confirmed by the TOC in the meetings.


I believe this proposal is related to my comments on the Contour submission, about the decision to go to the TOC vote without public comment ( https://github.com/cncf/toc/pull/330#issuecomment-626820824 ), the particular submission was a bit out of normal from the beginning itself.


I think reducing the time for public comment will result in less transparency. The transparency is one of the main issues in the TOC survey ( https://docs.google.com/presentation/d/1gTTf6USC0wDOCbwd5goS7e4qjGO8nqiPQO4fl_D3OuQ/edit#slide=id.g71ebafc016_0_237 )


There are many other submissions which are waiting longer than the Contour, it would be appreciated if the proposal would improve the experience for all, not just a few.


Thanks,


Vinod


On Fri, May 15, 2020 at 9:13 PM Kris Nova <kris.nova@...> wrote:
Strong agree with alexis - I’m booked solid these days and unless something is on fire it usually gets bumped down the list.

I usually book at a minimum one week out from initial engagement and I believe that’s fairly common in the industry. So setting aside time for myself for something like this would require 7+ days to even get it on my calendar to review.


Kris Nova
Chief Open Source Advocate


> On 15 May 2020, at 09:38, alexis richardson <alexis@...> wrote:
>




Kris Nova <kris.nova@...>
 

Strong agree with alexis - I’m booked solid these days and unless something is on fire it usually gets bumped down the list.

I usually book at a minimum one week out from initial engagement and I believe that’s fairly common in the industry. So setting aside time for myself for something like this would require 7+ days to even get it on my calendar to review.


Kris Nova
Chief Open Source Advocate

On 15 May 2020, at 09:38, alexis richardson <alexis@...> wrote:


alexis richardson
 

Busy people just don't pay attention to Github notifications until it
really matters?


On Fri, May 15, 2020 at 5:32 PM Chris Aniszczyk
<caniszczyk@...> wrote:

Maybe the weeks feel extra long these days but it seems just an extra unnecessary amount of time.

All the work and review happens in the open so it's not like people will be surprised.

On Fri, May 15, 2020 at 11:27 AM alexis richardson <alexis@...> wrote:

I see no reason to move to one week if the meetings are two weeks
apart. This is like an auction "asking once, asking twice..."


On Fri, May 15, 2020 at 5:20 PM Matt Farina <matt@...> wrote:

This sparked a few thoughts I figured I would share...

1. If someone goes on vacation for a week they could miss a public comment period in its entirety. As someone who went through the 2 week period for my project I'd like it to go faster. But, as someone who takes vacations for a week I like that a comment period would not be so short that I'd miss it.

2. Has anyone ever commented in the second week?

3. In my experience, which may not mirror everyone, the DD's are primarily done by the projects. The SIGs they are presented to are small groups in the broader system. There are others who might have very relevant feedback.

4. Has anyone ever put in the time to provide comment feedback of any kind of useful or detailed nature? If no one is gonna use it does it matter?

I'm obviously not of one mind on this. But, I figured someone should comment in a comment period on comment periods.

- Matt Farina

On Fri, May 15, 2020, at 11:26 AM, Liz Rice wrote:

Chris is suggesting reducing the comment period after a vote is called from two weeks to one week.



I can see the attraction, because in practice if people are going to comment it seems they’re likely to react pretty fast rather than leave it to the end of the comment period. And this won't be the first anyone hears about it because the DD will have been happening for some weeks prior to this. But it seems worth highlighting for public comment (how meta!)




--
Chris Aniszczyk (@cra) | +1-512-961-6719


Chris Aniszczyk
 

Maybe the weeks feel extra long these days but it seems just an extra unnecessary amount of time.

All the work and review happens in the open so it's not like people will be surprised.

On Fri, May 15, 2020 at 11:27 AM alexis richardson <alexis@...> wrote:
I see no reason to move to one week if the meetings are two weeks
apart.  This is like an auction "asking once, asking twice..."


On Fri, May 15, 2020 at 5:20 PM Matt Farina <matt@...> wrote:
>
> This sparked a few thoughts I figured I would share...
>
> 1. If someone goes on vacation for a week they could miss a public comment period in its entirety. As someone who went through the 2 week period for my project I'd like it to go faster. But, as someone who takes vacations for a week I like that a comment period would not be so short that I'd miss it.
>
> 2. Has anyone ever commented in the second week?
>
> 3. In my experience, which may not mirror everyone, the DD's are primarily done by the projects. The SIGs they are presented to are small groups in the broader system. There are others who might have very relevant feedback.
>
> 4. Has anyone ever put in the time to provide comment feedback of any kind of useful or detailed nature? If no one is gonna use it does it matter?
>
> I'm obviously not of one mind on this. But, I figured someone should comment in a comment period on comment periods.
>
> - Matt Farina
>
> On Fri, May 15, 2020, at 11:26 AM, Liz Rice wrote:
>
> Chris is suggesting reducing the comment period after a vote is called from two weeks to one week.
>
>
>
> I can see the attraction, because in practice if people are going to comment it seems they’re likely to react pretty fast rather than leave it to the end of the comment period. And this won't be the first anyone hears about it because the DD will have been happening for some weeks prior to this. But it seems worth highlighting for public comment (how meta!)
>
>
>





--
Chris Aniszczyk (@cra) | +1-512-961-6719


alexis richardson
 

I see no reason to move to one week if the meetings are two weeks
apart. This is like an auction "asking once, asking twice..."

On Fri, May 15, 2020 at 5:20 PM Matt Farina <matt@...> wrote:

This sparked a few thoughts I figured I would share...

1. If someone goes on vacation for a week they could miss a public comment period in its entirety. As someone who went through the 2 week period for my project I'd like it to go faster. But, as someone who takes vacations for a week I like that a comment period would not be so short that I'd miss it.

2. Has anyone ever commented in the second week?

3. In my experience, which may not mirror everyone, the DD's are primarily done by the projects. The SIGs they are presented to are small groups in the broader system. There are others who might have very relevant feedback.

4. Has anyone ever put in the time to provide comment feedback of any kind of useful or detailed nature? If no one is gonna use it does it matter?

I'm obviously not of one mind on this. But, I figured someone should comment in a comment period on comment periods.

- Matt Farina

On Fri, May 15, 2020, at 11:26 AM, Liz Rice wrote:

Chris is suggesting reducing the comment period after a vote is called from two weeks to one week.



I can see the attraction, because in practice if people are going to comment it seems they’re likely to react pretty fast rather than leave it to the end of the comment period. And this won't be the first anyone hears about it because the DD will have been happening for some weeks prior to this. But it seems worth highlighting for public comment (how meta!)



Matt Farina
 

This sparked a few thoughts I figured I would share...

1. If someone goes on vacation for a week they could miss a public comment period in its entirety. As someone who went through the 2 week period for my project I'd like it to go faster. But, as someone who takes vacations for a week I like that a comment period would not be so short that I'd miss it.

2. Has anyone ever commented in the second week?

3. In my experience, which may not mirror everyone, the DD's are primarily done by the projects. The SIGs they are presented to are small groups in the broader system. There are others who might have very relevant feedback.

4. Has anyone ever put in the time to provide comment feedback of any kind of useful or detailed nature? If no one is gonna use it does it matter?

I'm obviously not of one mind on this. But, I figured someone should comment in a comment period on comment periods.

- Matt Farina

On Fri, May 15, 2020, at 11:26 AM, Liz Rice wrote:

Chris is suggesting reducing the comment period after a vote is called from two weeks to one week.

 

I can see the attraction, because in practice if people are going to comment it seems they’re likely to react pretty fast rather than leave it to the end of the comment period. And this won't be the first anyone hears about it because the DD will have been happening for some weeks prior to this. But it seems worth highlighting for public comment (how meta!) 



Liz Rice
 

Chris is suggesting reducing the comment period after a vote is called from two weeks to one week.

 

I can see the attraction, because in practice if people are going to comment it seems they’re likely to react pretty fast rather than leave it to the end of the comment period. And this won't be the first anyone hears about it because the DD will have been happening for some weeks prior to this. But it seems worth highlighting for public comment (how meta!)