Either way we appreciate it! -- Thank you, John Mertic Director of Program Management - Linux Foundation - ODPi, R Consortium, and Open Mainframe Project jmertic@... +1 234-738-4571 Schedule time

I went (and spoke) there last year. It's a great open source event with a community focus. Very well run and well attended. Michael Hallmhall119@... On 08/21/2018 05:29 PM, Rob

I bet security requirements are going to be all over the map in this group. I bet people who are trying to push out media to end user devices are going to be VERY interested in signed code, but other

Hi Everyone, For those who don't know me I'm a Release Engineer at the Linux Foundation and am helping the ASWF project get setup. Feel free to direct any CI related questions to me. I can confirm

Agreed. I've been going to ATO for the last handful of years and it's always been a fantastic event. Well worth going if you can make it. Granted, as a community moderator on Opensource.com (they're

Hello, I'm on the development team for OpenColorIO, and would like to raise the conversation around project communication platforms. Quickly looking at the Collaboration Tools list for ASWF I see the

I'm very familiar with this event and know the organizers well - happy to meetup with folks there this fall as I'm slated as a speaker. Thank you, John Mertic Director of Program Management - Linux

Many Open Source projects use Freenode IRC. Something that I think a lot of these new tools miss is that there's no single agreed upon server for Open Source projects in general, so if folks want to

I would agree that real-time chat is extremely important with any type of project. We use it on a daily basis when we are hashing out ideas, having meetings, or trying to solve problems. We still use

Sean, Community personalities differ, and its important to find the tool that fits them. I’ve worked in communities that *only* operate via mailing lists, you can’t get *anyone* on slack or

Thanks, Yes, I don't want my comment to seem to impose my solution, but exactly to the point above if something isn't chosen at the get-go, each sub-project will do their own thing and some uniformity

I think you just proved that threading is a must :-) +1 A consistent approach among projects would be great. I think it is difficult though to use a new startup’s tool because they are still

Am I just a cranky old man for preferring mail lists and dreading using Slack or IRC? They're ok for totally ephemeral "gotta do this thing right now" stuff, but I hate when actual substantive

@LarryGritz, Perhaps, lol. There are implementations that will allow you to post/read like a mail list but have messages thread and show up in real time on a chat window so everyone is happy. I

Nope. I think its completely fair for the ASWF to just say no to real-time options. Just the number of mile-long emails when something contentious is discussed always irritates me, especially when

I believe Larry has it correct. Chat is amazing for quick collaboration and question answering but I suspect that these discussions are actually meant for discussions and thus belong on an email list

To follow-up on Rob's email. The TAC just had our first meeting where one of the orders of business was an initial review of the project lifecycle and project contribution proposal template document,

Too echo Larry and Darin's the joy of living in a crappy timezone where you are all mostly asleep, I hope that mailing lists can at least be the main form of communication with real-time being a

Not to beat a dead horse, but when somebody says "real time", what I hear is "somebody important on the project, maybe even me, is going to miss it." As I understand it, ASWF projects are intended to

FWIW, I've seen a number of communities start off by adding everyone's favorite real time service - but then they commonly end up back at email and maybe IRC for real time chat during meetings (with a