Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] [jakartaee-platform-dev] Slack room for informal discussions ???

We've been using Slack in other places, most recently for AlltheTalks conference where a couple of Java and Jakarta EE experts or Java Champions also gave a talk in a 24 h virtual conference.

The Q&A was done via Slack.


Kevin Sutter <sutter@xxxxxxxxxx> schrieb am Sa., 9. Mai 2020, 00:15:
Thanks for your input, Amelia.

But, as we continue to drive towards the Jakarta EE 9 release, there may be a need for more immediate, informal communications.  I know I have already been using the Slack channel that Scott setup for the TCK (as well as Cesar from TT).  So, I would still like to hear from other's opinions that are intimately involved in the delivery of Jakarta EE 9.  Thanks!

Kevin Sutter
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    

From:        Amelia Eiras <aeiras@xxxxxxxxxxxxx>
To:        jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>, Jakarta EE Community <>
Date:        05/08/2020 13:46
Subject:        [EXTERNAL] Re: [jakartaee-platform-dev] Slack room for informal discussions ???
Sent by:        jakartaee-platform-dev-bounces@xxxxxxxxxxx

Scott and Kevin, 

There is another thread via the community forum about the desire to use slack for "quick -- not important-- exchanges" on the Jakarta EE Project. Sadly the email archive interface to find that thread doesn't make it possible for me to find that conversation. :( 

Summary of that thread, Slack for Jakarta's collaborative work shouldn't exit. 

Many Jakartees stated that they prefer to avoid altogether the usage of another "debt-communication tool" to do any work to move this project forward. 

Using the ASF collaboration tool, IF a discussion didn't arrive at its respective mailing list, it didn't happen at all. 
Email lists enable focus on projects, topics, etc. 
Slack, even if paid is just not efficient for tracing how things are pushed forward. 

For everyone, 
Jakarta EE ecosystem  wants to enable anyone wishing to help (contributor/user) to do so easily without having to decide on owning the project's multiple tools. 
Too many tools convert negatively to higher debt to keep up with and substain. 
This is the community who gets to figure out what it protects. I thought that thread was enough to drop that Jakarta Slack channel yet I see us still talking about it and protecting it even after healthy feedback that it ought to be difficult to ignore. 

At the end of the day,  lowering the barrier to entry to help in any  OSS source project is one of the most important goals there is. 
 It states clearly to anyone watching, that the ecosystem is grounded & fully aware of the limited time its contributor (s). It says, it respects that time and protects it. 
It pays most attention to proactively cutting communication debts. 

For me, Slack in OSS can become EXTRA bothersome if many in the group choose to connect via "private exchanges" instead of public channels for example. 
Scaling has to count for much of enabling others to stand besides us and not behind us, right? 
Collaboration in Slack will minimize the forum email conversations in the short and long term, it will cut diverse voices & ideas from those missing "joining that debt"... 

With that said, like many others-- I won't be joining that slack group. There is no value and that is my choice. That also means that  I am choosing to be side-track and surprise potentially in a bad form when stuff just shows up and I am informed about it. Is that what we want to increase in this ecosystem?

I will continue to use the respective jakarta email forums to participate. 

PS: Added Jkta community forum. 

happy Friday Jakartees, 

Amelia Eiras

On Fri, May 8, 2020 at 8:03 AM Kevin Sutter <sutter@xxxxxxxxxx> wrote:
I was talking with Scott Marlow yesterday about the possibility of using Slack channels for more immediate discussions on various topics.  Scott has volunteered to be the "guinea pig" and he created one for the
Jakarta EE TCK discussions(see below).  If this usage of Slack pans out, then I might also create one for the Platform discussions, especially as we continue to drive towards a Jakarta EE 9 release.  Let me know if the use of a "Jakarta EE Platform Slack" channel would be of use and is desired.  Thanks!

Kevin Sutter
STSM, MicroProfile and Jakarta EE architect @ IBM
sutter@xxxxxxxxxx    Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
----- Forwarded by Kevin Sutter/Rochester/IBM on 05/08/2020 09:56 -----

Scott Marlow <smarlow@xxxxxxxxxx>
05/08/2020 09:29
[EXTERNAL] Re: [jakartaee-tck-dev] Slack room for informal discussion of        Platform TCK tasks/planning...
Sent by:        

On Thu, May 7, 2020 at 1:41 PM Scott Marlow <
smarlow@xxxxxxxxxx> wrote:

I created a #jakartaee-tck [1] room for discussing the EE 9 Platform TCK tasks/planning, that is open for all in the community that would like to join.

Sharing from slack discussion yesterday/today:

Here are some possible ideas for how we can report on our TCK status:

1. Via a shared google document or spreadsheet

2. Via a shared github page.

3. Via an TCK issue, like

4. Something else?

My thoughts are that we should primarily use issue tracking for tasks, as we have been.  And update our Kanban board to show work in sorted order, maybe the ordering could be by milestone number

Regarding how to share status, I am thinking we can send a weekly status email to the tck ml.  That would be useful for all, I think.


jakartaee-tck-dev mailing list

To unsubscribe from this list, visit

jakartaee-platform-dev mailing list

To unsubscribe from this list, visit
jakartaee-platform-dev mailing list
To unsubscribe from this list, visit

_______________________________________________ mailing list
To unsubscribe from this list, visit

Back to the top