Skip to content
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

Ongoing Support and Request for Maintainers #151

Open
rveachkc opened this issue Dec 18, 2023 · 7 comments
Open

Ongoing Support and Request for Maintainers #151

rveachkc opened this issue Dec 18, 2023 · 7 comments
Assignees

Comments

@rveachkc
Copy link
Owner

I probably should have done this a long time ago, but I honestly have neither the time, nor the energy to continue development on this project. I no longer have a use for it in my own projects, and I find it healthier to have hobbies that are not too similar to my daily job at work.

Truthfully, this whole project could really use an uplift to the new api, better tests and code style, but I'd rather pass it off to a new maintainer.

pymsteams does have an extensive dependency tree, so I feel quite a bit of responsibility to those who have trusted this project in the past.
I'm committing to the following:

  • stable code base with no breaking changes
  • Update dependency requirements to pass GitHub
  • Verify any new maintainer can be trusted. (I'd honestly love to turn this over to Microsoft)

If you're finding this project for the first time, and it hasn't transferred ownership, perhaps you should try something else. Apprise looks pretty cool.

@rveachkc rveachkc self-assigned this Dec 18, 2023
@gplssm
Copy link

gplssm commented Feb 22, 2024

Since we're using this package quite extensively in our company, we, I and a colleague of mine, might can jump in as maintainers.

We it be possible to agree a hand-over phase where we get introduced to not so obvious details of the package and get advice how we should proceed in the mid-term future? I assume you have ideas what should be done next.

@th3happybit
Copy link

Hi @rveachkc i would love to be one of the maintainers, since we using this package.

@rveachkc
Copy link
Owner Author

While I can appreciate the offers to maintain, I'm really looking to turn this over to some sort of organization that can be trusted vs individuals on github.

@mkpnitorenergy
Copy link

Isn't this library becoming obsolete with the deprecation of "Incoming Webhooks" in teams?
https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/

@jroosameresco
Copy link

Isn't this library becoming obsolete with the deprecation of "Incoming Webhooks" in teams? https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/

I came here to confirm this as well. I'm assuming it's not going to support the adaptive card/workflow style azure webhooks until told otherwise.

@rveachkc
Copy link
Owner Author

The Microsoft deprecation is being discussed in #155

@DeathRabbit679
Copy link

While I can appreciate the offers to maintain, I'm really looking to turn this over to some sort of organization that can be trusted vs individuals on github.

That's too bad, but in the wake of that unfortunate JiaTan business, totally understandable. I hope you find a sponsor, I'm sure plenty of orgs have used your work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants