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

Is Seneca still maintained? #593

Closed
StarpTech opened this Issue Dec 30, 2016 · 7 comments

Comments

Projects
None yet
5 participants
@StarpTech
Contributor

StarpTech commented Dec 30, 2016

Dear Senecajs,

https://github.com/senecajs/seneca/graphs/commit-activity

we get no informations about the status of this opensource project. Just a handful of questions were answered in Slack. If you look in the issues you can find lots of untouched issues. The same situation is in the ecosystem of seneca. Lots of people trust in it and did hard work to be familiar with this framework and I think some people already use it in production and facing with issues which can not be fixed easily. The biggest point is the missing documentation about the internal fundamentals/concepts of seneca. That's one of the reason why the community can't run it alone. This is not fair. It's opensource but seneca is in charge of this ship. The roadmap was not kept and not updated. Please give us an update. Thank you.

Btw: Everybody can understand that there are more important things as to maintain an opensource project but I think there is always time to bring the community up to date.

Update (05.01.2017):
Because of this situation I created Hemera perhaps someone can use it too.

@pinxue

This comment has been minimized.

Show comment
Hide comment
@pinxue

pinxue Jan 9, 2017

It is really annoying to advertise your project this way, especially your project is not an alternative at all.

I expected more active support from the maintainer, too. But with last PR merged in 1 month it is obviously maintained.

pinxue commented Jan 9, 2017

It is really annoying to advertise your project this way, especially your project is not an alternative at all.

I expected more active support from the maintainer, too. But with last PR merged in 1 month it is obviously maintained.

@StarpTech

This comment has been minimized.

Show comment
Hide comment
@StarpTech

StarpTech Jan 9, 2017

Contributor

Hi @pinxue it seems that you don't understand my intention. I'm working with senecajs since 2 years. I contributed to the Framework and help people to get familiar with it. All the points I mentioned you can double check. Do you using seneca in production? Do you know the core issues? I open this issue because the activity of the maintainer has reduced dramatically. There are lots of issues but the most important fact is that nobody talks with the community although promises were made see Roadmap. This is no advertising. I recommend my opensource project for people who have issues which cannot be easy solved and for people who need a toolkit I can provide a very similiar approach to create a microservice architecture. I dont want to implement a clone of seneca. Please inform you before you blame someone with good intentions.

Contributor

StarpTech commented Jan 9, 2017

Hi @pinxue it seems that you don't understand my intention. I'm working with senecajs since 2 years. I contributed to the Framework and help people to get familiar with it. All the points I mentioned you can double check. Do you using seneca in production? Do you know the core issues? I open this issue because the activity of the maintainer has reduced dramatically. There are lots of issues but the most important fact is that nobody talks with the community although promises were made see Roadmap. This is no advertising. I recommend my opensource project for people who have issues which cannot be easy solved and for people who need a toolkit I can provide a very similiar approach to create a microservice architecture. I dont want to implement a clone of seneca. Please inform you before you blame someone with good intentions.

@rjrodger

This comment has been minimized.

Show comment
Hide comment
@rjrodger

rjrodger Jan 9, 2017

Collaborator

@StarpTech A lot of my time has been taken up with https://www.manning.com/books/the-tao-of-microservices recently - that's nearly done now. I'll be returning to more active maintenance from January 2017 onwards.

Seneca was first released in 2010 - this is a long term project. I do feel documentation has a higher priority at the moment than code however - hence new tutorials such as: http://senecajs.org/docs/tutorials/unit-testing.html

With respect to Hemera I'm fully supportive of your efforts - this is open source after all :)

Collaborator

rjrodger commented Jan 9, 2017

@StarpTech A lot of my time has been taken up with https://www.manning.com/books/the-tao-of-microservices recently - that's nearly done now. I'll be returning to more active maintenance from January 2017 onwards.

Seneca was first released in 2010 - this is a long term project. I do feel documentation has a higher priority at the moment than code however - hence new tutorials such as: http://senecajs.org/docs/tutorials/unit-testing.html

With respect to Hemera I'm fully supportive of your efforts - this is open source after all :)

@rjrodger rjrodger closed this Jan 9, 2017

@StarpTech

This comment has been minimized.

Show comment
Hide comment
@StarpTech

StarpTech Jan 9, 2017

Contributor

Hi @rjrodger thanks for your words and I agree documentation is at the moment more important. I just want to get some vital signs from the maintainers. In the last months I had the feeling that nobody helped us no matter how big the issue was especially since the big topic of "error handling" but good to hear from you. Are you planning to change the roadmap?

Contributor

StarpTech commented Jan 9, 2017

Hi @rjrodger thanks for your words and I agree documentation is at the moment more important. I just want to get some vital signs from the maintainers. In the last months I had the feeling that nobody helped us no matter how big the issue was especially since the big topic of "error handling" but good to hear from you. Are you planning to change the roadmap?

@gregory

This comment has been minimized.

Show comment
Hide comment
@gregory

gregory commented Mar 11, 2017

@StarpTech looks like sencajs has NATS transport now https://github.com/cmfatih/seneca-nats-transport

@StarpTech

This comment has been minimized.

Show comment
Hide comment
@StarpTech

StarpTech Mar 11, 2017

Contributor

@gregory the transport was not the reason to create hemera.

We want to create a toolkit which is responsible for everything expect the transport. We don't need overall transport independence. We trust in a well tested system. The wrong path in error-handling, logging and tracing are one of the reasons why we couldn't use existing solutions.

https://hemerajs.github.io/hemera/docs/hemera-vs-seneca.html

Contributor

StarpTech commented Mar 11, 2017

@gregory the transport was not the reason to create hemera.

We want to create a toolkit which is responsible for everything expect the transport. We don't need overall transport independence. We trust in a well tested system. The wrong path in error-handling, logging and tracing are one of the reasons why we couldn't use existing solutions.

https://hemerajs.github.io/hemera/docs/hemera-vs-seneca.html

@toanz

This comment has been minimized.

Show comment
Hide comment
@toanz

toanz Mar 19, 2017

@StarpTech totally agree with you . we are really appreciate your effort

toanz commented Mar 19, 2017

@StarpTech totally agree with you . we are really appreciate your effort

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment