Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
looking for new maintainers
See original GitHub issueHello! Recently I have not been as involved with this project as I would like to be, and it is likely that I will not have much time in the future (although I would still like to contribute from time to time). Would anyone be interested in being a maintainer? I will keep reviewing and merging PRs in the meantime but I think this project could use some love!
In the future I would like to have built some more abstraction on top of the core api (@jgraef @Mec-iS python3-ipfs-api has some really awesome ideas), especially seeing as the IPFS team will be eventually rolling out some kick-ass features such as pub-sub. So if anyone is interested in maintaining py-ipfs-api and giving it a face-lift, post here!
Issue Analytics
- State:
- Created 8 years ago
- Reactions:1
- Comments:13 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@amstocker @jbenet @whereswaldon I am also interested in helping. If you are still accepting helpers I will also need some guidance regarding the next step.
I am working on a python based bioinformatics paper that uses the IPFS. So I am very interested in seeing the py-ipfs-api work well!
@lgierth I am a collaborator, as is @alexander255, and we’re doing what we have time to do. Another maintainer would be lovely though. With 3, I think we could safely close this issue. On another note, would it be possible for @alexander255 or I to have admin access to the repo? We can’t add integrations without it (I would love to add Codacy).