-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Project status? #19
Comments
I'm interested in what ever happened to this tool, a year later - is it still actively used in Slack? What are development plans? Will it continue to get support and features? |
Yes, please update on the plans! |
Looks like it's been abandoned. Maybe someone can fork it and maintain that version? |
On github, that someone can be you :) But it won't be me, im not even sure if there are any active users. But the project looked cool anyway, if only for the delivery structure ideas it provided. |
I asked Kelly Ann, Product Security Engineer at Slack, for the status of this project. |
Went to a security conference in Sept. and heard Kelly talk about a security checklist that Slack is about to open source. Looks like it is this project. It seems like a good start for companies that want to promote security awareness and distribute responsibilities. Looking forward to the Python version of this app and giving it a try. |
Latest status found here: https://locomocosec.com
|
Any news on the status of goSDL? Has they Python app come out? Looks like Kelly Ann was the lead for rewriting goSDL into Python but went to Apple in August. Not sure how that impacted the project? |
Description
Project is open sourced only to be immediately abandoned.
What type of issue is this? (place an
x
in one of the[ ]
)Requirements (place an
x
in each of the[ ]
)Bug Report
Reproducible in:
github.
Steps to reproduce:
Expected result:
Some @slackhq teammember to respond to open issues/PR's.
Actual result:
What actually happened: nothing
Attachments:
https://github.com/slackhq/goSDL/pulls
https://github.com/slackhq/goSDL/issues
The text was updated successfully, but these errors were encountered: