An urgent request for a new maintainer

[PLynx01]

@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?

[ironhak]

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]

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?

[ironhak]

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]

@PLynx01

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

[oliver-zehentleitner]

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