You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the project is just starting, and a lot of discussions are already happening, I'm quite strongly concerned that we'll soon start losing history. Given the scope for this work, history is critical for us to be able to go back and understand after a few months why we went one way or another.
So, my request is that we get an ETA for going a paid account.
Note: that I am also fine with an answer saying this sounds unlikely. This will allow us to warn the community that the chat must only be used for very transient discussions, but decisions and design work must happen in PRs or in mailing-list.
Thank you!
The text was updated successfully, but these errors were encountered:
On Fri, Jan 10, 2020 at 8:34 AM Baptiste Mathus ***@***.***> wrote:
Hello,
------------------------------
We are starting a new UX Special Interest Group on the Jenkins Project:
https://jenkins.io/sigs/ux/
As chat tool, we have started using the CDF Slack, and we are working in
the #jenkins-ux-sig channel
<https://cdeliveryfdn.slack.com/archives/CR47PU411>.
As the project is just starting, and a lot of discussions are already
happening, I'm quite strongly concerned that we'll soon start losing
history. Given the scope for this work, history is critical for us to be
able to go back and understand after a few months why we went one way or
another.
So, my request is that we get an ETA for going a paid account.
Note: that I am also fine with an answer saying this sounds unlikely. This
will allow us to warn the community that the chat must only be used for
very transient discussions, but decisions and design work must happen in
PRs or in mailing-list.
Thank you!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#127?email_source=notifications&email_token=AAAPSIJ2FNQSNYOHKICVGC3Q5CBOPA5CNFSM4KFIUNP2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IFLRDWA>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAPSIPAWOMRY2WWRMGW4ATQ5CBOPANCNFSM4KFIUNPQ>
.
@batmat I would echo @caniszczyk comments. For things that require longer term history, indexing, or collaboration please use github. Treat Slack as your scratchpad or from-the-hip communication and notification system. Check out https://github.com/cdfoundation/sig-security as an example SIG in progress
Hello,
We are starting a new UX Special Interest Group on the Jenkins Project:
https://jenkins.io/sigs/ux/
As chat tool, we have started using the CDF Slack, and we are working in the #jenkins-ux-sig channel.
As the project is just starting, and a lot of discussions are already happening, I'm quite strongly concerned that we'll soon start losing history. Given the scope for this work, history is critical for us to be able to go back and understand after a few months why we went one way or another.
So, my request is that we get an ETA for going a paid account.
Note: that I am also fine with an answer saying this sounds unlikely. This will allow us to warn the community that the chat must only be used for very transient discussions, but decisions and design work must happen in PRs or in mailing-list.
Thank you!
The text was updated successfully, but these errors were encountered: