I’ve read thread [1] and have a few observations:

1. It happened on the Sling Dev email list. Sling Dev has too many daily 
emails. The context and substance of most messages are difficult to understand 
unless you’re already fully entrenched. I unsubscribed pretty quick. It is not 
the best platform for all collaboration across the project community.

2. To summarize the respondents of thread [1] every non-Adobe responder in the 
thread wanted Slack. Adobe already has a company chat platform. More 
collaboration across organizational boundaries would be a good thing for the 
project.

3. There was no vote. Why don’t we use the decision making process for Apache 
Software Foundation projects [2]?

Let’s put it to a vote and let the Sling Users have a say. Respond with +1 if 
you want a Slack Workspace for the Sling Community. Of course use of Slack is 
optional, so there is no need to vote against. Don’t join unless you want to!

Cris Rockwell
Applications Architect Sr  
College of Literature, Science, and the Arts | University of Michigan 
LSA Technology Services | 301 E Liberty Suite 500 | Ann Arbor, MI 48104
Desk: 734.763.6818 | Email: [email protected] <mailto:[email protected]>

[2]:  https://www.apache.org/foundation/how-it-works.html#decision-making 
<https://www.apache.org/foundation/how-it-works.html#decision-making>




> On Apr 20, 2020, at 4:04 AM, Robert Munteanu <[email protected] 
> <mailto:[email protected]>> wrote:
> 
> Hi Cris,
> 
> On Sat, 2020-04-18 at 11:03 -0400, Cris Rockwell wrote:
>> Hi Sling Users
>> 
>> Is there a community chat platform like Slack or gitter for Sling
>> users and developers?
> 
> Not at the moment. See also [1] where we had this discussion and
> eventually abandoned the idea.
> 
> Thanks,
> Robert
> 
> [1]: 
> https://lists.apache.org/thread.html/r19665a94cb17d9b7607eb9c5fe4c91cfa1df8eed55219f2db9b53f05%40%3Cdev.sling.apache.org%3E
>  
> <https://lists.apache.org/thread.html/r19665a94cb17d9b7607eb9c5fe4c91cfa1df8eed55219f2db9b53f05%40%3Cdev.sling.apache.org%3E>
> 
>> 
>> Cris 
>> 
> 

Reply via email to