You are probably right and it is an access issue. Aizhamal, could you give us edit access? And we can see if notifications work after that.
On Wed, Aug 7, 2019 at 1:41 PM Thomas Weise <t...@apache.org> wrote: > The use of JIRA was also suggested before, but why do the notifications > not work? I wasn't able to subscribe and I suspect that was due to not > having sufficient access to the spreadsheet? > > > > On Wed, Aug 7, 2019 at 1:26 PM Ahmet Altay <al...@google.com> wrote: > >> As far as I understand we have not resolved this discussion and the >> sticking issue is that there is no good way of subscribing to changes (i.e. >> proposals for tweets) for interested parties. The method suggested in this >> thread (e.g. Tools and then Notification rules.) does not work for some >> reason for a few of us including myself. >> >> Could we try to use any of our existing tools? For example, could the >> proposals be done in the form of filing a new JIRA issue under a specific >> component. All of us should be able to get notifications for that. And then >> we can follow the lazy consensus and alternative approval options as >> written down by Robert (1 week or 3 PMC +1s). >> >> Ahmet >> >> On Mon, Jun 24, 2019 at 3:47 AM Robert Bradshaw <rober...@google.com> >> wrote: >> >>> On Fri, Jun 21, 2019 at 1:02 PM Thomas Weise <t...@apache.org> wrote: >>> > >>> > From what I understand, spreadsheets (not docs) provide the >>> functionality that we need: https://support.google.com/docs/answer/91588 >>> > >>> > Interested PMC members can subscribe and react to changes in the >>> spreadsheet. >>> > >>> > Lazy consensus requires a minimum wait. How much should that be? >>> >>> 72 hours is a pretty typical minimum, but I'd go a bit longer. A week? >>> I'd want at least two pairs of eyes though, so if it's a PMC member >>> that proposes the message someone else on the PMC should approve >>> before it goes out on an official channel. >>> >>> > Should there be an alternative approval option (like minimum number of >>> +1s) for immediate post (in case it is time sensitive)? >>> >>> +1. I'd say three is probably sufficient, five at most. >>> >>> For both of these, let's just do something conservative and see how it >>> goes. >>> >>> > On Fri, Jun 7, 2019 at 7:28 PM Kenneth Knowles <k...@apache.org> >>> wrote: >>> >> >>> >> GDocs also have the ability to subscribe to all comments so that >>> works as well. >>> >> >>> >> This does add another system to our infrastructure, versus using >>> Jira. But I think a spreadsheet for tracking what has been sent and when, >>> it could be helpful to have the added structure. >>> >> >>> >> Kenn >>> >> >>> >> On Fri, Jun 7, 2019 at 10:05 AM Thomas Weise <t...@apache.org> wrote: >>> >>> >>> >>> Here is an idea how this could be done: Create a JIRA ticket that >>> will always remain open. Have folks append their suggested tweets as >>> comments. Interested PMC members can watch that ticket. >>> >>> >>> >>> Thomas >>> >>> >>> >>> On Thu, Jun 6, 2019 at 10:41 AM Thomas Weise <t...@apache.org> wrote: >>> >>>> >>> >>>> Pinging individual PMC members doesn't work. There needs to be >>> visibility to proposed actions to anyone that is interested. That would >>> require a form of subscribe/notification mechanism (as exists for PRs and >>> JIRAs). >>> >>>> >>> >>>> >>> >>>> On Thu, Jun 6, 2019 at 10:33 AM Aizhamal Nurmamat kyzy < >>> aizha...@apache.org> wrote: >>> >>>>> >>> >>>>> With the spreadsheet in http://s.apache.org/beam-tweets, anyone >>> can propose tweets. I will check it every few days, and ping/tag PMC >>> members to review tweets and publish. Does that sound fine? >>> >>>>> If you have ideas on how to make the process better, please let me >>> know. >>> >>>>> >>> >>>>> Thanks, >>> >>>>> Aizhamal >>> >>>>> >>> >>>>> On Wed, Jun 5, 2019 at 4:10 AM Thomas Weise <t...@apache.org> >>> wrote: >>> >>>>>> >>> >>>>>> +1 >>> >>>>>> >>> >>>>>> What would be the mechanism to notify the PMC that there is >>> something to review? >>> >>>>>> >>> >>>>>> >>> >>>>>> On Tue, Jun 4, 2019 at 9:55 PM Kenneth Knowles <k...@apache.org> >>> wrote: >>> >>>>>>> >>> >>>>>>> Bringing the PMC's conclusion back to this list, we are happy to >>> start with the following arrangement: >>> >>>>>>> >>> >>>>>>> - Doc/spreadsheet/etc readable by dev@ (aka the public), >>> writable by some group of contributors to set up a queue of news >>> >>>>>>> - Any member of PMC approves and executes the posts, with >>> enough time elapsing to consider it lazy consensus >>> >>>>>>> >>> >>>>>>> Any mistake transcribing this conclusion is my own. And of >>> course nothing is permanent, but we try and iterate. >>> >>>>>>> >>> >>>>>>> Kenn >>> >>>>>>> >>> >>>>>>> On Mon, Jun 3, 2019 at 2:18 PM Aizhamal Nurmamat kyzy < >>> aizha...@google.com> wrote: >>> >>>>>>>> >>> >>>>>>>> Hello folks, >>> >>>>>>>> >>> >>>>>>>> I have created a spreadsheet where people can suggest tweets >>> [1]. It contains a couple of tweets that have been tweeted as examples. >>> Also, there are a couple others that I will ask PMC members to review in >>> the next few days. >>> >>>>>>>> >>> >>>>>>>> I have also created a blog post[2] to invite community members >>> to participate by proposing tweets / retweets. >>> >>>>>>>> >>> >>>>>>>> Does this look OK to everyone? I’d love to try it out and see >>> if it drives engagement in the community. If not we can always change the >>> processes. >>> >>>>>>>> >>> >>>>>>>> Thanks, >>> >>>>>>>> aizhamal >>> >>>>>>>> >>> >>>>>>>> [1] s.apache.org/beam-tweets >>> >>>>>>>> [2] https://github.com/apache/beam/pull/8747 >>> >>>>>>>> >>> >>>>>>>> On Fri, May 24, 2019 at 4:26 PM Kenneth Knowles < >>> k...@apache.org> wrote: >>> >>>>>>>>> >>> >>>>>>>>> Thanks for taking on this work! >>> >>>>>>>>> >>> >>>>>>>>> Kenn >>> >>>>>>>>> >>> >>>>>>>>> On Fri, May 24, 2019 at 2:52 PM Aizhamal Nurmamat kyzy < >>> aizha...@google.com> wrote: >>> >>>>>>>>>> >>> >>>>>>>>>> Hi everyone, >>> >>>>>>>>>> >>> >>>>>>>>>> I'd like to pilot this if that's okay by everyone. I'll set >>> up a spreadsheet, write a blog post publicizing it, and perhaps send out a >>> tweet. We can improve the process later with tools if necessary. >>> >>>>>>>>>> >>> >>>>>>>>>> Thanks all and have a great weekend! >>> >>>>>>>>>> Aizhamal >>> >>>>>>>>>> >>> >>>>>>>>>> On Tue, May 21, 2019 at 8:37 PM Kenneth Knowles < >>> k...@apache.org> wrote: >>> >>>>>>>>>>> >>> >>>>>>>>>>> Great idea. >>> >>>>>>>>>>> >>> >>>>>>>>>>> Austin - point well taken about whether the PMC really has >>> to micro-manage here. The stakes are potentially very high, but so are the >>> stakes for code and website changes. >>> >>>>>>>>>>> >>> >>>>>>>>>>> I know that comdev votes authoring privileges to people who >>> are not committers, but they are not speaking on behalf of comdev but under >>> their own name. >>> >>>>>>>>>>> >>> >>>>>>>>>>> Let's definitely find a way to be effective on social media. >>> >>>>>>>>>>> >>> >>>>>>>>>>> Kenn >>> >>>>>>>>>>> >>> >>>>>>>>>>> On Tue, May 21, 2019 at 4:14 AM Maximilian Michels < >>> m...@apache.org> wrote: >>> >>>>>>>>>>>> >>> >>>>>>>>>>>> Hi Aizhamal, >>> >>>>>>>>>>>> >>> >>>>>>>>>>>> This is a great idea. I think it would help Beam to be more >>> prominent on >>> >>>>>>>>>>>> social media. >>> >>>>>>>>>>>> >>> >>>>>>>>>>>> We need to discuss this also on the private@ mailing list >>> but I don't >>> >>>>>>>>>>>> see anything standing in the way if the PMC always gets to >>> approve the >>> >>>>>>>>>>>> proposed social media postings. >>> >>>>>>>>>>>> >>> >>>>>>>>>>>> I could even imagine that the PMC gives rights to a Beam >>> community >>> >>>>>>>>>>>> member to post in their name. >>> >>>>>>>>>>>> >>> >>>>>>>>>>>> Thanks, >>> >>>>>>>>>>>> Max >>> >>>>>>>>>>>> >>> >>>>>>>>>>>> On 21.05.19 03:09, Austin Bennett wrote: >>> >>>>>>>>>>>> > Is PMC definitely in charge of this (approving, >>> communication channel, >>> >>>>>>>>>>>> > etc)? >>> >>>>>>>>>>>> > >>> >>>>>>>>>>>> > There could even be a more concrete pull-request-like >>> function even for >>> >>>>>>>>>>>> > things like tweets (to minimize cut/paste operations)? >>> >>>>>>>>>>>> > >>> >>>>>>>>>>>> > I remember a bit of a mechanism having been proposed some >>> time ago (in >>> >>>>>>>>>>>> > another circumstance), though doesn't look like it made >>> it terribly far: >>> >>>>>>>>>>>> > >>> http://www.redhenlab.org/home/the-cognitive-core-research-topics-in-red-hen/the-barnyard/-slick-tweeting >>> >>>>>>>>>>>> > (I haven't otherwise seen such functionality). >>> >>>>>>>>>>>> > >>> >>>>>>>>>>>> > >>> >>>>>>>>>>>> > >>> >>>>>>>>>>>> > On Mon, May 20, 2019 at 4:54 PM Robert Burke < >>> rob...@frantil.com >>> >>>>>>>>>>>> > <mailto:rob...@frantil.com>> wrote: >>> >>>>>>>>>>>> > >>> >>>>>>>>>>>> > +1 >>> >>>>>>>>>>>> > As a twitter user, I like this idea. >>> >>>>>>>>>>>> > >>> >>>>>>>>>>>> > On Mon, 20 May 2019 at 15:18, Aizhamal Nurmamat kyzy >>> >>>>>>>>>>>> > <aizha...@google.com <mailto:aizha...@google.com>> >>> wrote: >>> >>>>>>>>>>>> > >>> >>>>>>>>>>>> > Hello everyone, >>> >>>>>>>>>>>> > >>> >>>>>>>>>>>> > >>> >>>>>>>>>>>> > What does the community think of making Apache >>> Beam’s social >>> >>>>>>>>>>>> > media presence more active and more community >>> driven? >>> >>>>>>>>>>>> > >>> >>>>>>>>>>>> > >>> >>>>>>>>>>>> > The Slack and StackOverflow for Apache Beam offer >>> pretty nice >>> >>>>>>>>>>>> > support, but we still could utilize Twitter & >>> LinkedIn better to >>> >>>>>>>>>>>> > share more interesting Beam news. For example, we >>> could tweet to >>> >>>>>>>>>>>> > welcome new committers, announce new features >>> consistently, >>> >>>>>>>>>>>> > share and recognize contributions, promote events >>> and meetups, >>> >>>>>>>>>>>> > share other news that are relevant to Beam, big >>> data, etc. >>> >>>>>>>>>>>> > >>> >>>>>>>>>>>> > >>> >>>>>>>>>>>> > I understand that PMC members may not have time >>> to do curation, >>> >>>>>>>>>>>> > moderation and creation of content; so I was >>> wondering if we >>> >>>>>>>>>>>> > could create a spreadsheet where community >>> members could propose >>> >>>>>>>>>>>> > posts with publishing dates, and let somebody to >>> filter, >>> >>>>>>>>>>>> > moderate, and manage it; then send to a PMC >>> member for publication. >>> >>>>>>>>>>>> > >>> >>>>>>>>>>>> > >>> >>>>>>>>>>>> > I would love to help where I can in this regard. >>> I’ve had some >>> >>>>>>>>>>>> > experience doing social media elsewhere in the >>> past. >>> >>>>>>>>>>>> > >>> >>>>>>>>>>>> > >>> >>>>>>>>>>>> > Best >>> >>>>>>>>>>>> > >>> >>>>>>>>>>>> > Aizhamal >>> >>>>>>>>>>>> > >>> >>>>>>>>>>>> > >>> >>
