+1 I agree On Fri, Feb 7, 2020 at 1:22 PM Jon Malkin <[email protected]> wrote:
> Enough other comments now that I'll vote: +1 > > jon > > On Fri, Feb 7, 2020, 11:20 AM leerho <[email protected]> wrote: > >> Another good idea. Thanks! >> >> Lee. >> >> On Fri, Feb 7, 2020 at 11:13 AM Evans Ye <[email protected]> wrote: >> >>> +1! >>> >>> | For the transition: You could add an auto reply to the Google Group >>> with a convenient link to mailto:[email protected] and >>> leave the group for a while, or indefinitely. >>> >>> I think it helps to migrate the users by putting up a deadline which is >>> the date to set the forum to be read-only alongside with the new users@ >>> message. After that date users can still read previous discussions, but >>> can't post a new one. >>> >>> Evans >>> >>> leerho <[email protected]> 於 2020年2月7日 週五 下午2:36寫道： >>> >>>> Kenn, >>>> Thanks for your suggestion about the alias -- great idea. But how do >>>> we link Slack and StackOverflow to user@ ? I did some searching on >>>> Slack to see if there was some configuration to automatically transcribe >>>> the messages there directly to an Apache mail list, but I could not find >>>> any way to do that. I don't know anything about how StackOverflow works. >>>> >>>> Lee. >>>> >>>> >>>> On Thu, Feb 6, 2020 at 8:42 PM Dave Fisher <[email protected]> >>>> wrote: >>>> >>>>> +1 - thanks for surfacing the reasoning on the dev@ list. >>>>> >>>>> Regards, >>>>> Dave >>>>> >>>>> Sent from my iPhone >>>>> >>>>> On Feb 6, 2020, at 11:24 PM, Kenneth Knowles <[email protected]> wrote: >>>>> >>>>> >>>>> +1 to the proposal >>>>> >>>>> On Thu, Feb 6, 2020 at 8:22 PM Kenneth Knowles <[email protected]> >>>>> wrote: >>>>> >>>>>> For the transition: You could add an auto reply to the Google Group >>>>>> with a convenient link to mailto: >>>>>> [email protected] and leave the group for a >>>>>> while, or indefinitely. >>>>>> >>>>>> From experience, I think Lee is right: many people are shy about >>>>>> writing to dev@ even when they are well-qualified and have very >>>>>> clear and good questions to contribute. TBH they are also shy about >>>>>> writing >>>>>> to user@ in many cases. Users show up in Slack and StackOverflow >>>>>> too. Worth considering how to tie these together to include all these >>>>>> different sorts of users. But I am also on the side of establishing a >>>>>> user@ >>>>>> mailing list early. For Beam, it has always had much less traffic >>>>>> (recently >>>>>> dev@ was 5x user@) but still is a valuable resource for those who >>>>>> use it. >>>>>> >>>>>> If consensus becomes apparent, a mentor can set up user@/users@ >>>>>> (definitely go with an alias for both here). >>>>>> >>>>>> Kenn >>>>>> >>>>>> On Thu, Feb 6, 2020 at 1:39 PM Eric Bax <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> Approve >>>>>>> >>>>>>> >>>>>>> Sent from Yahoo Mail for iPhone >>>>>>> <https://overview.mail.yahoo.com/?.src=iOS> >>>>>>> >>>>>>> On Thursday, February 6, 2020, 10:22 AM, leerho <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>> Folks, >>>>>>> >>>>>>> This is a call for a vote on the following: >>>>>>> >>>>>>> I propose that we deprecate the Google Groups >>>>>>> <https://groups.google.com/forum/#!forum/sketches-user> forum and >>>>>>> direct users to a newly created users@ email list. >>>>>>> >>>>>>> The steps would be as follows: >>>>>>> >>>>>>> 1. Create a new [email protected] email list. >>>>>>> 2. Clearly mark the existing Google Groups site as deprecated >>>>>>> and direct users to the new list. >>>>>>> 3. Update all references to the Google Groups site on our web >>>>>>> site and repository READMEs to the new list. >>>>>>> >>>>>>> This vote will be performed in one stage: >>>>>>> - This letter will be published on dev@ and remain open for at >>>>>>> least 72 hours and at least 3 (+1) PPMC votes or a majority of (+1) are >>>>>>> acquired. All PPMC members including Mentors can vote. >>>>>>> >>>>>>> Please vote accordingly: >>>>>>> >>>>>>> [ ] +1 approve >>>>>>> [ ] +0 no opinion >>>>>>> [ ] -1 disapprove with the reason >>>>>>> >>>>>>> Thanks, >>>>>>> Lee Rhodes >>>>>>> [email protected] >>>>>>> >>>>>>>
