On Tue, Mar 28, 2017 at 01:32:02PM +0100, Greg Sutcliffe wrote: > On Tuesday, 28 March 2017 12:50:14 BST Marek Hulán wrote: > > > While I agree that we need a better way to end discussions, I think that > > > on point 1 we can improve as well. To me it feels like we lack > > > visibility. It has been suggested to move back to the mailing list since > > > that has more visibility. Others have suggested discussions on github > > > are easier to read back. I'd suggest that we adopt the github bot to > > > notify the ML of certain events. Some things I can think of are created, > > > reached impasse, closed or merged. For reached impasse we could use a > > > label or [impasse]. A timer could also work. > > > > I like this idea a lot > > So do I, I'd love to see this happen. > > Another suggestion I heard on visibility was to at least cross-post new RFCs > to the mailing list as well - this risks fragmenting the discussion, so we'd > have to be clear about that, but a simple "hey, there's a new rfc, check it > out no replies here" post might be useful?
This would be an implementation of the created event. To prevent a split discussion the bot could avoid sending the full message. Initially I was thinking of the subject but maybe there's an easy way to get the first paragraph as a teaser. -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
