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

Inviting A Successor/Maintainer To PyInquirer Future #159

Open
CITGuru opened this issue Apr 14, 2021 · 6 comments
Open

Inviting A Successor/Maintainer To PyInquirer Future #159

CITGuru opened this issue Apr 14, 2021 · 6 comments

Comments

@CITGuru
Copy link
Owner

CITGuru commented Apr 14, 2021

Hi all,

I want to thank everyone who has taken their time to create Pull requests and Issues on PyInquirer and as well as this Repo hitting 1.2k.

When I started working on PyIquirer, I was working on a CLI project in Python that required us to ask the user prompt question to be able to make decisions. Blessings, blessed and python-inquirer are similar that seems to do half of what needs to be done and also have a lot of compatibility issues with Windows.

Most issues either with ncurses or something similar, I was able to find a project that has ncurses ports (prompt-toolkit) and fixed the Windows issue.

During the process, I enjoyed working on the project and was able to use it finally in the original project I was working on. I wrote about PyInquirer in most of my CLI articles and so on.

This was actually my first openly public open source project and a lot of people started using it as well. I was really new to open source and I had no idea how to manage it either.

The issue started when managing this with my normal daily work. From answering issues to PRs. This was becoming too tasking for me as I juggle between remote jobs and writing gigs.

Many times a lot of people reached out to me on the progress and way forward, I could be available for some time and caught up with work again. The cycle goes on and goes on again.

A lot of people including companies are using this in their project, software, and CLI packages and they heavily depend on this to ask their users for inputs. Definitely, a lot of people would like to contribute to what's missing, report bugs, create issues and PRs.

However, due to my work schedule, these issues and PRs are usually left unattended to leaving people in circles and either fixing it locally or look for another option.

I would not want this project to be another dead project, so I would be accepting a successor/maintainer that would help move this project forward, maintain, and contribute to this project.

I am really sorry for the inconvenience this must have caused everyone using this package and I would be happy if this kicks off and back to its active state.

If you like this project and you would like to move this forward, send me a message on:

Email: oyetoketoby80[@]gmail.com
Twitter: twitter.com/@oyetoket

PS: You must be familiar with python and command-line applications. Thanks.

Btw, I am currently the lead engineer at https://bitpowr.com for blockchain payment and wallet solutions. You can also reach out to me if you have any inquiries on that.

@CITGuru CITGuru changed the title Inviting A Successor To PyInquirer Future Inviting A Successor/Maintainer To PyInquirer Future Apr 14, 2021
@septatrix
Copy link

Maybe you could try to upstream some parts of this as new prompt options in prompt_toolkit?

@SolebaySharp
Copy link

It's a shame but I'm also really grateful that you built and provided it at all, as it helped me in my learning of python. I made something that just about worked and was useful.

@TarunavBA
Copy link

I could maintain it very well @CITGuru

@rfrezino
Copy link

Hi!
I'm a staff engineer for Freshbooks, and I've been working in the dev area for more than 15 years.
I'm using PyInquirer in an IDP tool I developed for my company.
I can join in maintaining the project, as it's in my interest, we are using new Python versions, and PyInquirer is incompatible. I can solve it by forking it and solving it for me, but it would be nice if I could help the community as well.

My company profile is: https://github.com/fbrodrigorezino

bkus added a commit to HamWAN/packer-routeros that referenced this issue Jan 21, 2023
There's a fix for the PyInquirer breakage:
  CITGuru/PyInquirer#194
But PyInquirer doesn't have a maintainer anymore:
  CITGuru/PyInquirer#159

The sudo bundle update is because some gems have native extensions, and those
don't get installed or recognized properly by the subsequent rake build.
@okainov
Copy link

okainov commented Aug 24, 2023

Any update on this? Seems like there were some volunteers to take over the project, but has there been any progress on this? @CITGuru

@kylhuk
Copy link

kylhuk commented Feb 16, 2024

@CITGuru yo, we can see you are active on github 😏

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

No branches or pull requests

7 participants