Re: Collaboration Tools

Sean Cooper

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 tool
This 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 tool
because they are still chasing a business model.  What features will still be present and/or advancing and which
go by the wayside.  

For a project started in 2004, I found it very useful at times to have the history of the project and 
sample images that were used still available.  It is a significant nuisance when past e-mail/posts point to dead links
because of a change in the collaboration tool.  This is true as well in SMPTE’s Kavi (higher logic) where reorganizations
have 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 efforts
sometimes ignoring the benefits of tested and working codes.  (acknowledging that sometimes spaghetti just has to GO )

Jim Houston

Larry Gritz

Join { to automatically receive all group messages.