[GitHub] [mynewt-artifact] ccollins476ad merged pull request #1: Add "verify" functionality

2019-06-21 Thread GitBox
ccollins476ad merged pull request #1: Add "verify" functionality
URL: https://github.com/apache/mynewt-artifact/pull/1
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


Re: Feedback on board report

2019-06-21 Thread Greg Stein
On Fri, Jun 21, 2019, 14:05 Fabio Utzig  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


[GitHub] [mynewt-artifact] ccollins476ad opened a new pull request #1: [DO NOT MERGE] Verify

2019-06-21 Thread GitBox
ccollins476ad opened a new pull request #1: [DO NOT MERGE] Verify
URL: https://github.com/apache/mynewt-artifact/pull/1
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


Re: Feedback on board report

2019-06-21 Thread Fabio Utzig
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

2019-06-21 Thread Sterling Hughes

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


Feedback on board report

2019-06-21 Thread Justin Mclean
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