Hi ARIA TOSCA, You have a new direct message from the ASF team (https://the-asf.slack.com/x-185534614710-186296183735/).
--- @digestai View in the archives: https://the-asf.slack.com/x-185534614710-186296183735/archives/D5E4SCANM/p1495170055661886 Digest.AI (8:00 AM, May 19th) Hi ARIA, *Here’s your digest for May 19th 2017* There are 51 messages yesterday, and the most active user is John Ament *#ariatosca* @ran: @maxim @emblemparade re what you wrote about plugins, Tal what I meant was that existing Cloudify plugins are using runtime properties and we have no intention of modifying them; instead, the adapter should take care of conversion between runtime properties and attributes, and in ARIA there should be no mentioning of runtime-properties whatsoever. For ARIA plugins this is not going to be relevant at all as they'd simply use attributes directly. Regarding attributes strictness, at first stage it simply won't be there :slightly_smiling_face: and we'll create a jira for adding this, supposedly this can also take place in the ctx sugaring, simply validating every "set" or so? @alexz Thank you for making a pull request updating the readme! I've made a small comment on your PR on Github. @ran: @arthurberezin Saw you got the bot working :thumbsup: Should probably however configure the account to not receive any random mails from slack, as it gets sent to everyone and is simply spam. We should only be getting the digests. @arthurberezin: I'm not sure how we can that, right now I just used the apache.org alias to log into slack, didn't see any sufisticated option.. The slack bot allows setting up how it does digests but the rest of emails sent to the dev email (slack reset passwd, etc) are just sent to the account that digest.ai uses @ran: Arthur i simply meant to disable random slack emails in the configuration somewhere; indeed not much well be able to do about pass reset emails etc but those aren't not sent all the time so it's fine @alexz thanks! I'll merge it in a bit @johndament: Do you want to start it or you want me to? Regardless, I will point out that my big concern would be the lack of on list communication from the project, and moving to github would be yet another step away from Apache. @emblemparade: i see. i sent the email. i think our problem with email communication is separate. we have to talk about it and see how to change our communication habits. any advice would be appreciated! i'm sure you've seen similar problems with other incubator projects. @johndament: Agreed, its not a problem specific to AT The one thing I didn’t realize is that you aren’t all co-located I was surprised when you mentioned you’re in Chicago As far as advice, its tough. I’m not sure you’re working environment, but it may help to have email clients open and visible while coding. And also send out an email, and ask for someone to respond @emblemparade: slack is just faster in terms of getting answers and having direct conversations. i'm thinking that perhaps our daily [UPDATE] posts could easily be moved to email i suggest that we title them "Daily Update". because they really are daily and it would give the correct impression that there's a lot of daily activity. we have 4 full-time devs on this project, that's impressive in itself but it's hard to see without being on slack. @ran: @alexz I sort-of merged your commit - Basically I had to make a few modifications outside the actual patch since: 1) We'd like all PRs to be a single commit (squashing commits) 2) All commits must be linked to a JIRA issue, even if they're tiny :slightly_smiling_face: 3) The commit message has to follow the guidelines (see more on all of those here - https://cwiki.apache.org/confluence/display/ARIATOSCA/Contributing+Code ) In any case, I pulled the changes from your repo, squashed them, created a JIRA and modified the commit message, and now it's on the master branch. One thing this caused though is that the PR did not automatically close as `merged`, so I'll need to ask you to close it manually - unfortunately I don't have the permissions to do so myself. * * * You can snooze these notifications for an hour: https://the-asf.slack.com/unsub/U5FFQJ2LW-5a1cb74d28-notify-mute-1h eight hours: https://the-asf.slack.com/unsub/U5FFQJ2LW-796e6535e1-notify-mute-8h a day: https://the-asf.slack.com/unsub/U5FFQJ2LW-4e6e073ada-notify-mute-1d three days: https://the-asf.slack.com/unsub/U5FFQJ2LW-806a2d8aa0-notify-mute-3d or the next week: https://the-asf.slack.com/unsub/U5FFQJ2LW-6adc840c34-notify-mute-7d. You can also turn email notifications off: https://the-asf.slack.com/unsub/U5FFQJ2LW-64de78982b-notify. For more detailed preferences, see your account page: https://the-asf.slack.com/account.
