Re: Collaboration Tools
toggle quoted message Show quoted text
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 MeetBot addon).
On Wed, Aug 22, 2018 at 9:33 PM Larry Gritz <lg@...> wrote:
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 have a very high level of autonomy in what gets developed and how. I can't imagine that each project community wouldn't decide on its own communications style and mode. Though it's possible that for the ones who choose to have a real time (aka people left out 😜) comm channel, there may end up being an org-wide preference for which one.
On August 22, 2018 2:48:01 PM PDT, Ben De Luca <bdeluca@...> wrote: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 supplement for the real-time interactions.On Wed, 22 Aug 2018 at 19:59, Darin Grant <darin.grant@...> wrote: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 / forum.
On Aug 22, 2018, at 10:50 AM, Sean Cooper <sean@...> wrote:
Am I just a cranky old man for preferring mail lists
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 usually people can be calmed down and come to level ground when its a real-time interaction. So real solutions happen faster. That's all hearsay, conjecture, and personal bias of course.
It is a significant nuisance when past e-mail/posts point to dead links because of a change in the collaboration toolThis is precisely why I propose the ideal solution would be open source and hosted as a part of ASWF stack (sorry to maintainers in advance if that actually happens)
On Wed, Aug 22, 2018 at 6:25 PM, Larry Gritz <lg@...> wrote:
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 discussions or decisions for projects are made on those channels.
On August 22, 2018 10:08:04 AM PDT, Jim Houston <jim.houston@...> wrote:
On Aug 22, 2018, at 9:04 AM, Sean Cooper <sean@...> wrote:
I think you just proved that threading is a must :-)
I agree though, an option to join a channel without signing up would be great.
A consistent approach among projects would be great. I think it is difficult though to use a new startup’s toolbecause they are still chasing a business model. What features will still be present and/or advancing and whichgo by the wayside.
For a project started in 2004, I found it very useful at times to have the history of the project andsample images that were used still available. It is a significant nuisance when past e-mail/posts point to dead linksbecause of a change in the collaboration tool. This is true as well in SMPTE’s Kavi (higher logic) where reorganizationshave wiped clean previous threads. Although working in the moment on current topics is important for collaboration,I would also suggest the benefits of long-term learning from past decisions can be useful.
Especially in software projects where it seems that every decade or so, there is a significant throwing out of previous effortssometimes ignoring the benefits of tested and working codes. (acknowledging that sometimes spaghetti just has to GO )
Chief Technology Officer
T: +61 2 9383 4800 (main)
D: 604 398 3945 (direct)
Bld 54/FSA #19, Fox Studios Australia 38 Driver Ave
Moore Park, NSW 2021
CONFIDENTIALITY AND PRIVILEGE NOTICE
This email is intended only to be read or used by the addressee. It is confidential and may contain privileged information. If you are not the intended recipient, any use, distribution, disclosure or copying of this email is strictly prohibited. Confidentiality and legal privilege attached to this communication are not waived or lost by reason of the mistaken delivery to you. If you have received this email in error, please delete it and notify us immediately by telephone or email.