-
Notifications
You must be signed in to change notification settings - Fork 110
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
Project is dead? #180
Comments
I have commit access but I don't believe I have the required keys to publish new versions to npm. |
@clarkie ? |
Bump. It is a shame that this project goes to waste, by only reading the README it can be seen that is huge and very useful, but it is too dangerous to use a stalled project :/ |
@clarkie Agree completely. |
created a new project based on this and dynogels-promisified. you can check it out here https://www.npmjs.com/package/dynogels-promise. I updated the dependencies and made some few changes but you can replace it with either packges, and it should work perfectly |
Yo, apologies for going a bit off the grid. I've completely stopped using dynamodb (for now). I'm happy for this to be moved over to a group/org type thing. What needs to happen to get this set up? I've got some time over the next few weeks where I should be able to hand this over to whoever wants to carry on maintaining it. I think there's two bits to do, github and npm. Anything else? |
Probably the CI stuff as well. If the integration tests hit a real DynamoDB then we have to figure out what to do with that AWS account. |
If I remember correctly the CI spins up a "local" dynamodb to run against |
Cool, so in that case just access to the CI backend is an additional piece that would have to transition. |
Any news on project update? I'm currently working on updating it and re-writing it in Typescript |
Sorry! What's the best structure for the new group? Is it a github org and an npm org? I've never set up an npm org before. Would the group be just |
Creating an organisation on npm is quite straightforward... the organisation structure on github is fine.. we can still keep |
Any movement on this? @clarkie |
https://docs.npmjs.com/creating-an-org |
We really need to get this going. I am willing to help. I am already thinking of creating yet another fork to cater to my business needs. I would rather do a PR for dynogels. |
Thanks @ErikBoesen I've created the npm org now I just need to invite @cdhowie in. Can you ping me your email or npm username. |
This will still move the npm dependency though right? So we'll go from |
Oh hang on, we don't need to do all this. I can just add maintainers to the existing npm package. I still need @cdhowie's (and anyone else who y'all think should have publish rights) npm usernames |
I agree that it would be preferable to just add maintainers. |
@clarkie My username is the same over there. :) |
Any news? |
Thanks @clarkie! |
I realise that |
Given that autor didn't respond for over a year, I think the only sensible solution is to fork the project and integrate some much needed PRs.
I can't volunteer much time to it myself but hopefully someone will.
I propose new name - dynogelsNext
The text was updated successfully, but these errors were encountered: