search

utahta / pythonbrew

Python Environment manager
MIT License
1.44k stars 162 forks source link

Maintaining this project #141

Open Kentoseth opened 10 years ago

Kentoseth commented 10 years ago

As I've browsed through some of the issues, it seems that people were willing to maintain it but that nothing materialized from there (or so I assume).

Would any of you be interested in helping me maintain this project (in terms of just updating it for latest versions, fixing bugs)?

If we get maintenance right, perhaps we can consider adding features too (after a while).

I am willing to take on the project lead role (the main responsibility of keeping this alive), so long as I can get at least 5 interested people that can commit some time to this project.

If I get the responses, I will fork this over and link everyone to the maintained version.

mdippery commented 10 years ago

Sure. I'm a big fan of pythonbrew and would love to lend a hand.

Kentoseth commented 10 years ago

Should we fork it and call it something like "pythonbrew2" ?

We will need some type of name that people can identify with, so that they know that we are maintaining this, but it is separate from utahas pythonbrew and will follow its own direction.

mdippery commented 10 years ago

I don't know if we'd necessarily have to change the name. The installs would be disconnected from a forked repo, so there shouldn't be a danger of a user accidentally updating if they didn't intentionally choose to do so. The only technical issue would be the PyPI upload, but maybe utahta would be okay if we took that over, too. I'd say that if he's fine turning over maintainership, we keep the same name.

Otherwise, I vote for pbr. :wink: Just kidding, I don't have any good ideas for names.

Kentoseth commented 10 years ago

It doesn't look like he's even active here anymore. Maybe forking and getting him to just put a link to the new version is the least we could ask him to do without any interruptions.

Plus we'll need to consider possibly rewriting it for Python 3 (far-off thought).

Although names aren't important, we have:

pythonbrew2 pybrew2 pybro?? pb2 pybr2

I'm leaning towards something where the name distinctly exists so that people can identify that it is from the previous project (and works, mostly).

Lets see if utaha responds (i'm not exactly sure how to connect with someone directly on GitHub)

mdippery commented 10 years ago

We should probably skip anything with "2" in the name—what happens if we get up to v3.0? But we could work with the suggestions given otherwise.

Kentoseth commented 10 years ago

Very valid point indeed. Okay, so anything with 2 or any number is out.

Any suggestions?

Otherwise we could just move ahead with "pybrew" or the original name itself.