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

Is the project still active? #1511

Closed
Playrom opened this issue Feb 3, 2017 · 19 comments
Closed

Is the project still active? #1511

Playrom opened this issue Feb 3, 2017 · 19 comments
Labels

Comments

@Playrom
Copy link
Contributor

Playrom commented Feb 3, 2017

I'm trying to learn this fantastic framework , but i suspect that this is gonna die

Last commits are of months ago , there is not a timeline for future version etc...

Is it worth it?

@ricardogama
Copy link
Contributor

I would take a look at Objection.js

@absolux
Copy link

absolux commented Feb 6, 2017

Or Vitamin

@zamiang
Copy link

zamiang commented Apr 22, 2017

Starting a new project and was considering using this but due to lack of activity, elected to go with Objection.js. Extremely happy with it vs the other contender (sequelize). Objection is, like bookshelf, built on Knex. It has an active gitter and works very well with typescript.

@crunchtime-ali
Copy link
Member

Is there already an official statement whether bookshelf is discontinued/deprecated?

@mrhwick
Copy link
Member

mrhwick commented Jun 19, 2017

We're also curious about the active maintenance status of this library. @tgriesser, any thoughts?

@crunchtime-ali
Copy link
Member

I sent him a mail in the meantime asking for a statement as well.

@Playrom
Copy link
Contributor Author

Playrom commented Jun 19, 2017

we could fork the project in the case he will not respond, but we have to promote the fork across the pull request and the issues in this repository to help and direct the community

there are 430 issues and 60 PR, I think that the demand is high

@mrhwick
Copy link
Member

mrhwick commented Jun 20, 2017

In the case that my organization decides to switch to another ORM (an unlikely possibility at the moment), suggestions for alternative ORM libraries are welcome.

In the more likely case that we continue to use bookshelf.js for our current implementation, we are interested in helping the library mature. Of particular interest at this time is solving concerns expressed in issues such as #813, as they are threats to the usefulness of this library at scale. We are currently working through ways to reduce the impact of these limitations, but the best solution would be to mature this library to make use of SQL constructs such as table joins, which are supported by the underlying querybuilder, knex.

If there is interest in an effort to support a new fork of this project, please keep this thread informed.

@crunchtime-ali
Copy link
Member

I never got a response from Tim Griesser.

To kick things up I forked the current bookshelf into a new bookshelfjs organisation https://github.com/bookshelfjs/bookshelf

I invited you @mrhwick & @Playrom. Who else is interested in maintaining Bookshelf? @rhys-vdw what about you?

This first goals should be:

  • Get Bookshelf in line with the current Knex.js
  • Promote the fork across all open pull requests

@rhys-vdw
Copy link
Contributor

@dj-hedgehog I have permission to add people to this project.

@rhys-vdw
Copy link
Contributor

And am willing to do so if nobody else is maintaining it.

@tgriesser
Copy link
Member

@dj-hedgehog hey - sorry about that, must've missed your message (and this thread) until I just saw it on my feed... I've had a lot going on lately and unfortunately I've been been pretty bad about keeping up with open source maintenance :(

I have an org setup for bookshelf, I could transfer the project there and add you as an admin (meant to do this awhile ago but never did).

@crunchtime-ali
Copy link
Member

@tgriesser I gladly accept your offer but won't be able to keep up with everything myself. So @rhys-vdw and the others your help is greatly appreciated :)

I deleted the fork and bookshelfjs organisation.

@Playrom
Copy link
Contributor Author

Playrom commented Jun 29, 2017

I think the same as @dj-hedgehog, I can help but I can't be the only one ( also because there are a tons of backlog PR and Issues to look at )

@Playrom
Copy link
Contributor Author

Playrom commented Jun 29, 2017

we could create a slack team to organise the work, what do you think?

@rmharrison
Copy link
Contributor

If there's no Slack channel, #express-js is hosted on node-js.slack.com

Would be perfectly reasonable to have a #bookshelf.

Typeform for invite: http://www.nodeslackers.com/
Maintainer is active. Received invite in ~10 min.

@mrhwick
Copy link
Member

mrhwick commented Nov 16, 2017

I firmly believe we need to reduce the number of communication channels we use to manage this project. I've settled on only using the github repo for communication because it is the most publicly linked to the project.

@rmharrison
Copy link
Contributor

Fair enough.

@Playrom: Close issue with "Yes" (the project is still active under 'new management')?

@crunchtime-ali
Copy link
Member

Thanks for bringing this up @rmharrison. I agree with you.
Since @Playrom became maintainer of the project I guess its answered :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

10 participants