Ta4j 0.9

[mdeverdelhan]

Hi there!

Today I am releasing ta4j 0.9. It comes with some changes which are listed here: https://github.com/mdeverdelhan/ta4j/wiki/Release-notes#09-released-september-7-2017

I take advantage of this message to announce that I stop the maintenance of the project.
It is due to the lack of time. Now I am occupied with many other things (as usual: family, work, other projects, etc.) and I cannot spend numerous hours to analyze and treat (and too often reject, sorry) the bugs and the pull requests which emerge. And I am not even talking about enhancing the lib.

I think that today ta4j is in a pretty stable state and may be used as-is. Feel free to fork the repository, extend the code the way you like, and continue the adventure!

Happy trading! :)

Marc

[martinklepsch]

Thanks for the effort and time you poured into this library Marc! 🎉 All the best for the future 🙂

I'm sure someone will step up and take over maintenance. Would you be willing to point to a new fork if/once it emerges?

[team172011]

Thank you very much for the effort and for sharing this beautiful library. It has been a pleasure for me to study it and to work with it!
I am sure without your maintenance it will become a little bit quiter around this lib.

[mransley]

You have done an amazing job with this library and I can see all the work that you have put into it. Good luck on the other things that you work on!

[TheCookieLab]

I'd be happy to take over maintenance (maybe with one or two other contributors) until you return.

[team172011]

@TheCookieLab i could help as collaborator

[martinklepsch]

Just copying over from chat, I think the below could be a reasonable process to transfer ownership:

• add people interested in maintaining as collaborators
• let them manage issues/pr for some time
• later on move repo to new owner/org

[dpalic]

I have also read this message, sadly.... :-(
@mdeverdelhan are you willing to transfer the ownership of this project to others?
@ALL i am also interested in supporting the project, best would be to create a task list of what to do and who to do

[sirajperson]

Thank you Mark for all the work time and energy you have put into this project. We all love and will miss you!

[dpalic]

hello together,
since I could not see any response from Mark, which I can fully understand, I have taken actions to make the project to get back to live again.
I have created a new organisation ta4j and have also registered the domain ta4j.org.
So hopefully there are some developers around who are willing to take over the development again, so I can give these developers the full permissions on the new ta4j organisation to get life back into the project.
I know this sounds maybe somehow weird but this approach makes it possible to get on with the project immediately without the dependency to one specific person. I hope my good will is here considered and not any negative emotions as a reaction to my actions taken.

I can support the board with my team, but this will be the decision of the new ta4j-board which I may or may not be part of (democratic decision of the new ta4j-board)
So if whoever is interested in supporting the new ta4j project please respond on the issue #1
If you have already needs, wishes or ideas I have also prepared a issue to collect them #2

[mdeverdelhan]

Thank you to all of you for your messages. Honestly I was not thinking that ta4j was so popular.

As I said to @dpalic I am glad to see that some of you are motivated to be part of the new ta4j. I am going to point to this new organization (https://github.com/ta4j) and keep this repository as an archive. If you need I can slightly collaborate to the new project (for occasional bugfixes for instance, do not expect any big work from me).

Before making those changes, let me give you some advices from my experience:

• Do not forget that the very initial project was Tail (https://github.com/peas/tail & http://tail.sourceforge.net/) (even if there may not be any line of code that has been kept).
• Learn to say "no". Do not add features in too numerous ways if you don't have the means to maintain them. Remember that it is not only about dev: you also have to test, document, and maintain your feature. You have to know how it works, how to explain it to a newcomer, what are its limitations, what it involves at the API level (and at the lib user level). You have to dive into it after one year when someone comes with a "I found a bug!" statement.
• Have a chief. A so-called democratic governance may work but in last ressort, one has to decide.
• Stay humble, always. :)

Good luck!