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

An urgent request for a new maintainer #1146

Open
PLynx01 opened this issue May 27, 2024 · 6 comments
Open

An urgent request for a new maintainer #1146

PLynx01 opened this issue May 27, 2024 · 6 comments

Comments

@PLynx01
Copy link

PLynx01 commented May 27, 2024

@kernc

It seems like you've abandoned this project. There are more and more issues and pull requests piling up constantly.

Can you consider granting someone the maintainer role, as you don't contribute to the project sufficiently often. Maybe I can become the new maintainer?

@edofe99
Copy link

edofe99 commented May 29, 2024

Why don't you fork and call it back2testing.py (or something like that)? I don't think you'll get any feedback from the maintainer.

@PLynx01
Copy link
Author

PLynx01 commented May 29, 2024

Why don't you fork and call it back2testing.py (or something like that)? I don't think you'll get any feedback from the maintainer.

It's a great idea! If a project is abandoned, I can fork it. But what about contributors? Will they migrate to my fork?

How should I name it?

@edofe99
Copy link

edofe99 commented May 29, 2024

Why don't you fork and call it back2testing.py (or something like that)? I don't think you'll get any feedback from the maintainer.

It's a great idea! If a project is abandoned, I can fork it. But what about contributors? Will they migrate to my fork?

How should I name it?

Well, first of all you should be 100% sure to start this new project and maintain it trough the years, or at least set in place some plans for it's continuations even if you will leave it aside at some point... There are already tons of dead backtesting engines.

As for contributors I don't know. But if you pick the project and do substancial fixes / improvements then you can make a post on reddit and you'll get some coverage that can help you find new contributors and let people know to migrate from this to the newst one.

As for the name, you'll work on it so you decide :)

Sorry if I can't give more help, my python knowledge is just enough to use this backtest engine contributing to it is out of my league for now.

Good luck :)

@Redeemer98
Copy link

Redeemer98 commented Jun 2, 2024

@PLynx01

Let us know if you do start a new project based on this project.

@oliver-zehentleitner
Copy link

Here we maintain a fork:
https://github.com/LUCIT-Systems-and-Development/lucit-backtesting

@raphaelheinz
Copy link

raphaelheinz commented Dec 5, 2024

Is there any fork that is still worked on and maintained? Or should we consider backtesting.py as dead?

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

5 participants