Agreed, Mailing lists may be old school and no longer (if ever) hip, but they do have a lot going for them:
- Data is retained. - Threads are maintained, and often self contained - save the last message in a thread to archive the entire discussion. - Searchable archives (usually) both online, and stored locally. - Low investment - you can ignore the list until you need it, search for applicable stuff, and post if you cannot find anything. Not as quick turnaround as a chat platform for kibitzing and building community, but for actual knowledge retention, much better IMHO. -- D On October 20, 2016 at 1:19:53 PM, Andrus Adamchik (and...@objectstyle.org) wrote: > I tried to follow the threads but soon got lost. I strongly suggest that such > technical issues MUST NOT be discussed on Slack but must be CARRIED OUT ON > THE MAILING LIST. Slack is not searchable, the threads are not followable, > Google does not index Slack discussions (as far as I know). And most of all > the discussion thread is not easily archived. Good assessment. A few thousands people at the Apache Software Foundation would likely concur. Mailing lists may feel old, but so far are the best way of communication for distributed volunteer communities. Andrus _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/dleber_wodev%40codeferous.com This email sent to dleber_wo...@codeferous.com
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com