Hi Everyone, We rolled out Windows builders for the ASWF project and are having some issues building OpenEXR's IlmBase project (see the command and error below) with it (trying to confirm that the

Hi JF, IT gave me the following puppet information in case it's helpful for you but as I suspected we don't have any custom config in place to handle Jenkins and use what's already available out on

Perfect, thank you for the documentation link. I had been using those official containers as a base so looks like I'm on the right track. JF Panisset

Hi JF, I hope you don't mind me cc'ing the mailing lists so that others can benefit from the knowledge from this discussion as well. Syntax error will be fixed once this is merged

I am a 52 years young programmer from Belgium . I am learning Linux on an education site called edx.org because I am very interested in it, and also have Lubuntu 16.04 LTS running on my little PC .

Yep, we'll have to figure out Windows and Mac once we get the infra for those in place and working. I have some experience with signing OSX code from a past life which might be of use. Today our infra

For both Windows and Max OSX, you will need a developer signing certificate which is used to ensure the origin of the compiled code. Similar to GPG, but verified by the OS rather than by a package

Depends a lot on the communities. While I personally prefer IRC (or did, until it started dying of spam :( ), I also participate in many communities that use slack instead. Ed

I think both forms of communication are perfectly fine and have their place, but most importantly I don't think it's the role of the ASWF to dictate the tools to use. It is very much - I believe-- in

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

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

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

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,

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

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

@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

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

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

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

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