profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/rsalmond/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

rsalmond/hubot-stashboard 2

Allows Hubot to read and write status changes on Stashboard.

mikemorgan15/theappnetas 0

Appliance API config module

rsalmond/atlantis 0

Terraform collaboration and automation for your team

rsalmond/aws-cli 0

Universal Command Line Interface for Amazon Web Services

rsalmond/aws-grab 0

Grab an instance that will grab some files.

rsalmond/client 0

Keybase Go Library, Client, Service, OS X, iOS, Android, Electron

rsalmond/concrete-jumble 0

Rearrange the letters and tell the world

created repositorynicholasjackson/hashicorp-shipyard-modules

HashiCorp modules for Shipyard (shipyard.run)

created time in 5 hours

startedPOSTECH-CVLab/PyTorch-StudioGAN

started time in a day

startedgofiber/fiber

started time in a day

issue commentskoczen/will

Slack APIs consumed by will are slated to be shut off in Feburary 2021

So, the good news is that Legal has approved a new contribution process. The bad news is that while I'll happily contribute my work back, there's no way it's going to happen in less than two weeks, and more likely three. There are also the complications that my fork now has significant changes not strictly related to the Slack backend update. It'll take me some work to split up my efforts into targetted chunks.

On Thu, Feb 18, 2021 at 11:10 PM Steven Skoczen notifications@github.com wrote:

@BrianGallew https://github.com/BrianGallew if you're willing or able to share that work, that'd be tremendous. Over the years (8 of them now!), the community has done the bulk of the support on this project, so I don't think your team sharing code to a project that's benefitted you all over the years puts any onus for support on you - it just makes other folks lives easier, and if anything, might even get you some upstream bugfixes down the road.

Not to put too fine a point on it, but nobody's Will would have worked for all these years without the contributions of everyone here. So if there's a way it can be done, that'd be lovely.

That said -- I know legal's gonna legal. (And it might be too late for the ask questions later approach.)

If that's the case, as Brian alluded to, V2 of Will was specifically designed to make adding or replacing a backend easy, as it came out of hipchat's sudden collapse - there's just a handful of methods that need built out. (Take a look at the shell backend https://github.com/skoczen/will/blob/master/will/backends/io_adapters/shell.py for an example of this.) Brian, if legal's not on board, if you'd be willing to paste links to the relevant parts of the slack docs / SDKs or toss up some pseudocode, and mention bugs and workarounds you ran into, it sure would make the implementation job easier.

On the broader issues of Will, and whether the project is dead - I think an open source project is dead if one of two things is true:

Nobody is working on it anymore. Some projects hit maturity and see significant drop-offs in code additions; it doesn't mean they're dead. From this thread, it seems like folks are still interested in keeping it going, so I'm going to assume we're still good there. 2.

There's bureaucracy, cruft, or blocks in the way of new releases, or nobody's sure who's running things. This sounds like it might be the case.

About two years ago, there was a long discussion https://github.com/skoczen/will/issues/395#issuecomment-461092630 about the future of Will. TL;DR, I recognized that I didn't have time for Will (it's been a project of love since ~2015), wasn't coding full-time for work anymore, and handed the reins over to the folks who were most active at the time, @Ashex https://github.com/Ashex, @chillipeper https://github.com/chillipeper , @rsalmond https://github.com/rsalmond , and @wontonst https://github.com/wontonst .

It seems like there's still friction on this, so if there are other ownership or changes that need to be made, we need to move will to an org repo, whatever it is, I'm happy to do it.

Most of all, I hope all of you are staying well, hanging in there, and I'm glad to hear from you, and see your voices after all we've all been through in the past year.

I'm in a van on a distant coast of New Zealand on pretty shoddy internet at the moment - so if I don't reply to this thread immediately, please be patient. I'll for sure reply, and get the repo and access sorted out to whatever folks here decide.

Be well, -Steven

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/skoczen/will/issues/426#issuecomment-781851866, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAC5MS5ICEA3TAH57NI7V5LS7X6G3ANCNFSM4TNETJOA .

dpritchett

comment created time in 3 days

startedOpenMined/PySyft

started time in 3 days

fork nicholasjackson/GoMicroservices

Building microservice with Nic from yourube series.

fork in 4 days

created repositoryjpetazzo/webcolor

created time in 5 days

startedenix/helm-charts

started time in 8 days

startedenix/x509-certificate-exporter

started time in 8 days

MemberEvent

startedCompVis/taming-transformers

started time in 9 days

created repositoryjpetazzo/ras21

created time in 9 days

startedenix/dothill-csi

started time in 11 days

issue commentskoczen/will

Slack APIs consumed by will are slated to be shut off in Feburary 2021

@BrianGallew if you're willing or able to share that work, that'd be tremendous. Over the years (8 of them now!), the community has done the bulk of the support on this project, so I don't think your team sharing code to a project that's benefitted you all over the years puts any onus for support on you - it just makes other folks lives easier, and if anything, might even get you some upstream bugfixes down the road.

Not to put too fine a point on it, but nobody's Will would have worked for all these years without the contributions of everyone here. So if there's a way it can be done, that'd be lovely.

That said -- I know legal's gonna legal. (And it might be too late for the ask questions later approach.)

If that's the case, as Brian alluded to, V2 of Will was specifically designed to make adding or replacing a backend easy, as it came out of hipchat's sudden collapse - there's just a handful of methods that need built out. (Take a look at the shell backend for an example of this.) Brian, if legal's not on board, if you'd be willing to paste links to the relevant parts of the slack docs / SDKs or toss up some pseudocode, and mention bugs and workarounds you ran into, it sure would make the implementation job easier.

On the broader issues of Will, and whether the project is dead - I think an open source project is dead if one of two things is true:

  1. Nobody is working on it anymore. Some projects hit maturity and see significant drop-offs in code additions; it doesn't mean they're dead. From this thread, it seems like folks are still interested in keeping it going, so I'm going to assume we're still good there.

  2. There's bureaucracy, cruft, or blocks in the way of new releases, or nobody's sure who's running things. This sounds like it might be the case.

About two years ago, there was a long discussion about the future of Will. TL;DR, I recognized that I didn't have time for Will (it's been a project of love since ~2015), wasn't coding full-time for work anymore, and handed the reins over to the folks who were most active at the time, @Ashex, @chillipeper , @rsalmond , and @wontonst .

It seems like there's still friction on this, so if there are other ownership or changes that need to be made, we need to move will to an org repo, whatever it is, I'm happy to do it.

Most of all, I hope all of you are staying well, hanging in there, and I'm glad to hear from you, and see your voices after all we've all been through in the past year.

I'm in a van on a distant coast of New Zealand on pretty shoddy internet at the moment - so if I don't reply to this thread immediately, please be patient. I'll for sure reply, and get the repo and access sorted out to whatever folks here decide.

Be well, -Steven

dpritchett

comment created time in 12 days

issue commentskoczen/will

Slack APIs consumed by will are slated to be shut off in Feburary 2021

Let me see how much hassle it's going to be with legal

On Wed, Feb 17, 2021 at 9:32 AM Ron Hudson notifications@github.com wrote:

@BrianGallew https://github.com/BrianGallew Would you be willing to make your backend public? Did you have to change many other things or just will/backends/io_adapters/slack.py ? Even if it's a gist? I'd like to get my fork running, and would love to jump off of your slack.py.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/skoczen/will/issues/426#issuecomment-780681261, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAC5MS5I3COXWWZI4BTKWRDS7PVQLANCNFSM4TNETJOA .

dpritchett

comment created time in 13 days

issue commentskoczen/will

Slack APIs consumed by will are slated to be shut off in Feburary 2021

@BrianGallew Would you be willing to make your backend public? Did you have to change many other things or just will/backends/io_adapters/slack.py ? Even if it's a gist? I'd like to get my fork running, and would love to jump off of your slack.py.

dpritchett

comment created time in 13 days

created tagappneta/wireshark

tagv3.4.3.appneta.52

The Wireshark Network Protocol Analyzer. Pull requests will be ignored. Please upload changes to https://code.wireshark.org/review/ .

created time in 14 days

create barnchappneta/wireshark

branch : wireshark-3.4.3-appneta.52

created branch time in 14 days

startedVITA-Group/TransGAN

started time in 14 days

PublicEvent

push eventappneta/wireshark

Fred Klassen

commit sha 2b7b987a69668c9ebf7fd2e3ad49f7c4f78e8b8c

fixes for Windows build

view details

push time in 15 days

created tagappneta/wireshark

tagv3.4.3.appneta.51

The Wireshark Network Protocol Analyzer. Pull requests will be ignored. Please upload changes to https://code.wireshark.org/review/ .

created time in 19 days

delete tag appneta/wireshark

delete tag : v3.4.3.appneta.51

delete time in 19 days

created tagappneta/wireshark

tagv3.4.3.appneta.51

The Wireshark Network Protocol Analyzer. Pull requests will be ignored. Please upload changes to https://code.wireshark.org/review/ .

created time in 19 days

delete tag appneta/wireshark

delete tag : v3.4.3.appneta.51

delete time in 19 days

push eventappneta/wireshark

Fred Klassen

commit sha d7c604c161fcfa69f6ccb4fa184ded9ce5659c88

update rules and libwireshark14.symbols

view details

push time in 19 days

issue commentskoczen/will

Slack APIs consumed by will are slated to be shut off in Feburary 2021

I had taken it that we'd have to do a separate rewrite since you had elected to not make your fork public. You've seen the other issues discussing where to take the project in which no consensus was ever reached (primarily not wanting to drop support for python 2.7). I would like to see the project come back in some form but we'd need to settle on a roadmap of features/improvements so that we can tackle them even when the contributors availability is limited.

I do feel some level of responsibility to get this project moving again so if we do have developers interested in contributing we can determine what to fix (priority #1 being the slack api) and get started, I'm not able to be super active as the bulk of my work these days is audit related (and there's a bit of irony in that). This of course may involve a full fork of the project so we have full access as I and a few other individuals only have contributor access with the owner being largely absent from the project.

dpritchett

comment created time in 19 days

create barnchappneta/wireshark

branch : wireshark-3.4.3-appneta.51

created branch time in 19 days

issue commentskoczen/will

Slack APIs consumed by will are slated to be shut off in Feburary 2021

Not really. I've already done it. Took me 3 days to learn the existing code and make the required changes. I didn't extend the tests at all, but the existing ones continue to work. We've been running our fork in production for almost 2 months now. The real issue is the complete lack of progress from the committers: no issue review, no PR merging/rejection, commits, or really any evidence that the project is not stone dead.

On Thu, Feb 11, 2021 at 3:11 AM Evelyn notifications@github.com wrote:

I'm afraid I won't be able to make any contributions in the near future so this project may be put on ice as a result. Having worked with the slack backend it's been in a half-baked state for some time but reworking it to the latest API is doable, it's just going to require serious commitment to refactor and write the associated tests.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/skoczen/will/issues/426#issuecomment-777335004, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAC5MS7HIMHGV7ZXJ7LTQPDS6OUOXANCNFSM4TNETJOA .

dpritchett

comment created time in 19 days

issue commentskoczen/will

Slack APIs consumed by will are slated to be shut off in Feburary 2021

I'm afraid I won't be able to make any contributions in the near future so this project may be put on ice as a result. Having worked with the slack backend it's been in a half-baked state for some time but reworking it to the latest API is doable, it's just going to require serious commitment to refactor and write the associated tests.

dpritchett

comment created time in 19 days