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

New maintainer requested #37

Open
fgimian opened this issue Jan 20, 2016 · 28 comments
Open

New maintainer requested #37

fgimian opened this issue Jan 20, 2016 · 28 comments

Comments

@fgimian
Copy link
Collaborator

fgimian commented Jan 20, 2016

Hey there guys,

Originally @nnathan and I re-developed this library for use in one of our projects at work. Unfortunately, I am no longer working on the project at all and Nav (and the guys) have decided not to use this library in the end.

AS such, we are unlikely to continue developing it, although we do feel it has great potential and is a far better starting point than the original Net-SNMP Python bindings with proper unit tests and a Pythonic interface, along with documentation and an installer which is accessible via pip.

I would like to open the floor to anyone who would be interested in taking over this project and owning it moving forward.

Thanks so much for your time
Fotis

@bwks
Copy link

bwks commented Jan 21, 2016

Bummer :( I hope someone is willing to continue this project, its the best SNMP library ever made by far. Thanks for your efforts so far team, it is much appreciated.

@kamakazikamikaze
Copy link
Collaborator

That's sad to hear, but completely understandable. You guys have done a great job so far.

@fgimian
Copy link
Collaborator Author

fgimian commented Jan 26, 2016

Thanks so much guys! Really sorry for the bad news 😄

@nnathan
Copy link
Contributor

nnathan commented Mar 16, 2016

To give some information as to why I decided not to use the library in our internal project.

I just couldn't squeeze the performance I needed. The Perl library is significantly faster even though the backing C code is incredibly similar.

This is a great starting point. If you need performance you might want to look into fastsnmpy.

I wish I had the mental bandwidth to continue improving this code, but I hope someone can address some of the issues.

@ghost
Copy link

ghost commented Mar 17, 2016

Hi guys, I forked the project and implemented bulkwalk along with refactoring the code behind the functions considering how similar the functions are as well as squeezing out the memory leaks. I've only used it with SNMP v2c, so far. I deprecated support for SNMP v1 and Python < 2.7 as they are not in my use case.

The project is also debianized.

https://github.com/normanuber/ezsnmp

I am using it in production right now, but will not maintain it as much since the long running program I am using will be deprecated in a few weeks.

@kamakazikamikaze
Copy link
Collaborator

Nicely done! I'm still waiting for bulkwalk (hhnnngggghhhh!) but squeezing out those memory leaks is a great improvement.

@ghost
Copy link

ghost commented Mar 17, 2016

I meant bulkwalk, since that was my use case

@kamakazikamikaze
Copy link
Collaborator

I'm willing to test it out. My coworker and I would much prefer bulkwalk over the normal walk. Would it be possible to pull it into this package?

@ghost
Copy link

ghost commented Mar 17, 2016

Actually, why not just clone my repo? and I cannot guarantee snmpset works, since that was out of scope for me.

@kamakazikamikaze
Copy link
Collaborator

It just makes it easier if it's in one package that can be upgraded directly through Python/Pip than having to download several and keep tabs on each. I can clone it and test it out tomorrow when I'm at work

@kamakazikamikaze
Copy link
Collaborator

@fgimian Three months have passed and nobody else has taken up the offer, so I'll do it, or at least request the access to be a contributor. I don't have any experience with Python C-extensions, Travis-ci, Coveralls, or Flake8, so someone else may be a better option, but I don't want to see this project become "stale" and go to waste.

@fgimian
Copy link
Collaborator Author

fgimian commented Apr 30, 2016

@kamakazikamikaze Thanks for your help. Let's start with a few pull requests if that's OK and we'll go from there.

@kamakazikamikaze
Copy link
Collaborator

That's perfectly fine! Thank you!

@kamakazikamikaze
Copy link
Collaborator

kamakazikamikaze commented May 17, 2016

@fgimian bulkwalk should be ready for testing and review. I've tested both the brew and bulkwalk commits on OS X successfully, as well as two other individuals here on Github.

@sivabudh
Copy link

@fgimian I see that you guys would like to move on and are seeking new maintainers for this project.

Currently, my team is installing easysnmp by putting this into our requirements.txt at the moment:

-e git+git://github.com/kamakazikamikaze/easysnmp.git@44c62317dbd38b9f3bccf90fac9078b2434c00d9#egg=easysnmp

Any chance you might be so kind as to publish a 0.2.5, please? :)

@sivabudh
Copy link

sivabudh commented Jul 17, 2016

@normanuber, I see you have forked this project. I will try to use your ezsnmp in my project and see if I can install it normally like a regular python package. :)

@fgimian
Copy link
Collaborator Author

fgimian commented May 18, 2017

Just wanted to greatly thank Kent for deciding to take this project on! 😄

@kamakazikamikaze
Copy link
Collaborator

Thank you for transferring the project to me, Fotis. I hope I can continue to release updates on a regular interval! This has been a great project that we found to be very useful in my previous workplaces.

@tyler-8
Copy link

tyler-8 commented May 22, 2017

Extremely excited to see this project moved over and development continuing. Thanks for all you do @kamakazikamikaze and thank you @fgimian for starting easysnmp in the first place!

@kamakazikamikaze
Copy link
Collaborator

Unfortunately, due to recent events I will not be able to actively maintain the repository as I had previously hoped. I apologize for the inconvenience and will reopen this issue to invite anyone to contribute or request collaboration access to maintain the repository.

@rogerwh
Copy link

rogerwh commented Aug 24, 2020

Hello there!

In my work I used easysnmp, after trying two or three libraries, this was the best and most effective.
I forked the project to copy a pull request, because it fix a problem in the project that I work.

I don't know about CI, but I can learn about it, and help with the maintenance and development of the project

I hope you can consider it!

@carloswh
Copy link

Hi,
I'm working in a company that is developing a software that use snmp protocol and use easysnmp to communicate with his OLT Hardware devices. And if you need a maintainer for the project, can help you, sincerely i don't know about CI, but can learn about it.

Thank you.

@MichalMazurek
Copy link

Hey!

I would also love to help, I'm using easysnmp too as the main core of one of the projects I work with, as I see people above are also willing maybe we could make a team? 😄 If not maybe it's time to fork this project?

All the best,
Michal

@kamakazikamikaze
Copy link
Collaborator

@rogerwh, @carloswh, and @MichalMazurek I owe you all an apology for not responding promptly. I keep getting distracted with other things I have going on.

It's alright if you guys don't have experience with CI. I honestly don't have much either, but I found the setup that the previous maintainers used to be really helpful in running tests across supported operating systems to check for issues. Since there seems to be a need for a patch anyways to get it working again, it's not a problem if things continued without it for a while.

If any of you really do want to help with maintaining the project, please submit changes via pull requests and complete proper testing. Once we get a rhythm going for regular updates, I can add you as a collaborator.

@MichalMazurek
Copy link

I have some, I will try to fix it.

@rogerwh
Copy link

rogerwh commented Oct 5, 2020

"If any of you really do want to help with maintaining the project, please submit changes via pull requests and complete proper testing."

Here I have a doubt, there are pull request in the project, so, when you said "submit changes via pull request", I use the opened pull request in a branch, add testing and if okay, redo the pull request?

Sorry, if there is a flow of how to, can you tell us?

@kamakazikamikaze
Copy link
Collaborator

@rogerwh sorry for the late response. Open a pull request, include a screenshot or a link to a screenshot showing that all tests pass. I don't have my testing environment anymore to clone the requests and verify tests myself.

@kamakazikamikaze
Copy link
Collaborator

For anyone still following this thread, I've created a new Easysnmp org that this project will eventually be moved to. Since I've had some time recently to look at things I've attempted to revitalize the code and CI/CD pipeline. I'm still not certain how I want to manage teams for development but if anyone has interest in supporting the project long-term and adding features is welcome to request access over in #140.

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

9 participants