You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mynewt.apache.org by Justin Mclean <ju...@classsoftware.com> on 2019/06/21 06:08:36 UTC
Feedback on board report
Hi,
There a couple of minor concerns that have been raised by the last board report:
1. There seem to be a lot of conversion happen on slack (in particular private conversation) rather than on this email list
2. The PMC seems to be not very active in following emails sent to the private list.
Anyone on the PMC care to comment on this? What action (if any) do you think we need to take on this?
Is there some way someone could summarise what happening on slack and bring it back to this list perhaps?
I can see in whimsey, that a number of PMC members are not signed up to the private mailing list. [1] Is it just a matter of getting these missing people subscribed and perhaps reminding people what a PMC’s duties are?
Thanks,
Justin
1. https://whimsy.apache.org/roster/committee/mynewt
Re: Feedback on board report
Posted by Lukasz Wolnik <lu...@gmail.com>.
Slack would be perfect with an unlimited history plan. Shame that a lot of
useful solutions to rare issues are forever loss on the Slack channel at
the moment.
On Mon, 24 Jun 2019, 12:39 Fabio Utzig, <ut...@apache.org> wrote:
>
> On Fri, Jun 21, 2019, at 4:57 PM, Greg Stein wrote:
> > On Fri, Jun 21, 2019, 14:05 Fabio Utzig <ut...@apache.org> wrote:
> >
> > > On Fri, Jun 21, 2019, at 12:39 PM, Sterling Hughes wrote:
> > >
> > > > Most of the technical conversations happen on the pull requests
> > > > themselves, I think this is fine. It’s archived, and people have an
> > > > opportunity to review & comment.
> > > >
> > > > Slack is largely for support, with the occasional “what do you
> > > > think?” So long as that comes back to a conversation on a pull
> > > > request or dev list, I don’t see a huge issue.
> > >
> > > One way to make it more accessible for posterity is to run a daily
> task on
> > > builds.apache.org that runs a bot subscribed to the slack channel,
> pulls
> > > all conversations and deploys to some place like
> mynewt.apache.org/slack...
> > > I double anyone would ever access that but at least it's in the open
> > > instead of requiring people to join the channel, and it's logged
> forever...
> > >
> >
> > Please note that the-asf.slack.com is on a Standard Plan, so all
> history is
> > retained. Dunno what workspace mynewt is using, but if you move there,
> then
> > no need to attach an archive bot.
>
> So the main (or only) issue is with chat history? Moving moves all users
> and history?
>
> >
> > Cheers,
> > -g
> >
>
Re: Feedback on board report
Posted by Fabio Utzig <ut...@apache.org>.
On Fri, Jun 21, 2019, at 4:57 PM, Greg Stein wrote:
> On Fri, Jun 21, 2019, 14:05 Fabio Utzig <ut...@apache.org> wrote:
>
> > On Fri, Jun 21, 2019, at 12:39 PM, Sterling Hughes wrote:
> >
> > > Most of the technical conversations happen on the pull requests
> > > themselves, I think this is fine. It’s archived, and people have an
> > > opportunity to review & comment.
> > >
> > > Slack is largely for support, with the occasional “what do you
> > > think?” So long as that comes back to a conversation on a pull
> > > request or dev list, I don’t see a huge issue.
> >
> > One way to make it more accessible for posterity is to run a daily task on
> > builds.apache.org that runs a bot subscribed to the slack channel, pulls
> > all conversations and deploys to some place like mynewt.apache.org/slack...
> > I double anyone would ever access that but at least it's in the open
> > instead of requiring people to join the channel, and it's logged forever...
> >
>
> Please note that the-asf.slack.com is on a Standard Plan, so all history is
> retained. Dunno what workspace mynewt is using, but if you move there, then
> no need to attach an archive bot.
So the main (or only) issue is with chat history? Moving moves all users and history?
>
> Cheers,
> -g
>
Re: Feedback on board report
Posted by Greg Stein <gs...@gmail.com>.
On Fri, Jun 21, 2019, 14:05 Fabio Utzig <ut...@apache.org> wrote:
> On Fri, Jun 21, 2019, at 12:39 PM, Sterling Hughes wrote:
>
> > Most of the technical conversations happen on the pull requests
> > themselves, I think this is fine. It’s archived, and people have an
> > opportunity to review & comment.
> >
> > Slack is largely for support, with the occasional “what do you
> > think?” So long as that comes back to a conversation on a pull
> > request or dev list, I don’t see a huge issue.
>
> One way to make it more accessible for posterity is to run a daily task on
> builds.apache.org that runs a bot subscribed to the slack channel, pulls
> all conversations and deploys to some place like mynewt.apache.org/slack...
> I double anyone would ever access that but at least it's in the open
> instead of requiring people to join the channel, and it's logged forever...
>
Please note that the-asf.slack.com is on a Standard Plan, so all history is
retained. Dunno what workspace mynewt is using, but if you move there, then
no need to attach an archive bot.
Cheers,
-g
Re: Feedback on board report
Posted by Fabio Utzig <ut...@apache.org>.
On Fri, Jun 21, 2019, at 12:39 PM, Sterling Hughes wrote:
> Most of the technical conversations happen on the pull requests
> themselves, I think this is fine. It’s archived, and people have an
> opportunity to review & comment.
>
> Slack is largely for support, with the occasional “what do you
> think?” So long as that comes back to a conversation on a pull
> request or dev list, I don’t see a huge issue.
One way to make it more accessible for posterity is to run a daily task on builds.apache.org that runs a bot subscribed to the slack channel, pulls all conversations and deploys to some place like mynewt.apache.org/slack... I double anyone would ever access that but at least it's in the open instead of requiring people to join the channel, and it's logged forever...
>
> Sterling
>
> On 20 Jun 2019, at 23:08, Justin Mclean wrote:
>
> > Hi,
> >
> > There a couple of minor concerns that have been raised by the last
> > board report:
> > 1. There seem to be a lot of conversion happen on slack (in particular
> > private conversation) rather than on this email list
> > 2. The PMC seems to be not very active in following emails sent to the
> > private list.
> >
> > Anyone on the PMC care to comment on this? What action (if any) do
> > you think we need to take on this?
> >
> > Is there some way someone could summarise what happening on slack and
> > bring it back to this list perhaps?
> >
> > I can see in whimsey, that a number of PMC members are not signed up
> > to the private mailing list. [1] Is it just a matter of getting these
> > missing people subscribed and perhaps reminding people what a PMC’s
> > duties are?
> >
> > Thanks,
> > Justin
> >
> > 1. https://whimsy.apache.org/roster/committee/mynewt
>
Re: Feedback on board report
Posted by Sterling Hughes <st...@gmail.com>.
Hi Justin,
I think conversations happen in 2 places:
- Slack
- Pull requests
Most of the technical conversations happen on the pull requests
themselves, I think this is fine. It’s archived, and people have an
opportunity to review & comment.
Slack is largely for support, with the occasional “what do you
think?” So long as that comes back to a conversation on a pull
request or dev list, I don’t see a huge issue.
Regarding activity of the PMC, I think there are probably a few people
we can vote in and we should look to do so. Generally, I don’t think
we feel strongly that the list is underused — I imagine if you were
suggesting we stop using slack or pull requests, you’d get a lot more
commentary :)
Sterling
On 20 Jun 2019, at 23:08, Justin Mclean wrote:
> Hi,
>
> There a couple of minor concerns that have been raised by the last
> board report:
> 1. There seem to be a lot of conversion happen on slack (in particular
> private conversation) rather than on this email list
> 2. The PMC seems to be not very active in following emails sent to the
> private list.
>
> Anyone on the PMC care to comment on this? What action (if any) do
> you think we need to take on this?
>
> Is there some way someone could summarise what happening on slack and
> bring it back to this list perhaps?
>
> I can see in whimsey, that a number of PMC members are not signed up
> to the private mailing list. [1] Is it just a matter of getting these
> missing people subscribed and perhaps reminding people what a PMC’s
> duties are?
>
> Thanks,
> Justin
>
> 1. https://whimsy.apache.org/roster/committee/mynewt