search

MichalLytek / type-graphql

Create GraphQL schema and resolvers with TypeScript, using classes and decorators!
https://typegraphql.com
MIT License
8.04k stars 676 forks source link

How to donate this project? #151

Open viktor-ku opened 6 years ago

viktor-ku commented 6 years ago

Owner note

TypeGraphQL is an MIT-licensed open source project. It doesn't have a large company that sits behind - its ongoing development is possible only thanks to the support by the community ❀️

If you fell in love with TypeGraphQL, you can support our efforts and help it grow, especially if you are using it commercially - just to ensure that the project which your product relies on is actively maintained and improved πŸ’ͺ

All the donation can be made using the Open Collective platform:

Original message

Patreon?

Hi,

I'd like to support this project with Patreon. Even though I am ready to donate no more > than $5 a month maybe you could get more people to support it as well?

What do you think about it?

Thanks for your project :heart:

MichalLytek commented 6 years ago

Thanks! Actually, I haven't thought about it. It's a great idea but I'm not sure if it's the time do do that. So if they are more people ready to donate, please πŸ‘ the first post to let me know that you want to support the project πŸ˜‰

And I think that Open Collective is a better place to make a financial contributions to open source projects: https://opencollective.com/

viktor-ku commented 6 years ago

@19majkel94 yeah, the platform doesn't matter. I just want this project running but I don't have enough time to contribute with code so I figured...

anodynos commented 5 years ago

:+1: :+1: :+1: I'm already donating a tenner on the projects I use, type-graphql deserves a few more :-)

tylergets commented 5 years ago

Also would be interested in supporting from our company, we utilize the project in production and would also love to keep it alive :)

anodynos commented 5 years ago

Great news to know @tylergets your company using it in production!

Veetaha commented 5 years ago

Really nice codebase you have :+1:. Unfortunately, I am just a student and possess no money sources rather than my scholarship and parents' donations :unamused:, but all your typestack libraries are very awesome to use in my projects and I wish I could contribute to your library :heart::heart:. I wish you gain more popularity than any other backend framework :muscle::muscle:

MichalLytek commented 5 years ago

all your typestack libraries are very awesome

Thanks but they are not mine - @pleerock is the author, I'm only one of the contributors πŸ˜‰

I am just a student and possess no money sources

You can help TypeGraphQL by spreading the word, sharing on twitter, writing blog posts, tutorials, sample projects on Github and many more πŸ’ͺ

I am starting with TypeGraphQL page on opencollective.com this month (I hope so), so all interested bakers will soon be able to support the project with donations πŸŽ‰

viktor-ku commented 5 years ago

I've used it in one of my projects that are currently in production. Unfortunately I'am switching over to the rust for my next server app, but will support this project nonetheless :heart:

anodynos commented 5 years ago

I 've just started donating $24/year https://opencollective.com/angelospikoulas :-)

I'm happy to be the first one apparently!

@19majkel94 please add https://opencollective.com/19majkel94 to your home page, the github readme.md & everywhere!

And lets all contribute all we can, especially those using it commercially, to make this project even greater!

MichalLytek commented 5 years ago

@viktor-ku @tylergets @Veetaha You can now support TypeGraphQL development efforts πŸŽ‰ All the donation can be made using the Open Collective platform: https://opencollective.com/typegraphql

@anodynos I've modified the first post, pinned this issue, added backers section in readme and donate button in top of the readme, as well as the support section in the website landing page πŸ’ͺ

You can now spread the word and like/retweet 🐦 https://twitter.com/typegraphql/status/1109830853906042880

goldcaddy77 commented 5 years ago

Happy to join as a member! Thanks again @19majkel94 for all of the hard work on this project!!

MichalLytek commented 5 years ago

@goldcaddy77 Thank you very much! 😍

molinto commented 5 years ago

@19majkel94 Donated today - keep up the great work.

Sharry

MichalLytek commented 4 years ago

Quote by @andreimc: https://github.com/MichalLytek/type-graphql/issues/553

I just wanted to do a shout out yo you @MichalLytek and the rest of the contributors, you guys have helped us a lot and we have started contributing a monthly $50 dollars, we know it's not a lot but we are also a start up! Once we get more traction we will become a Gold Sponsor.

πŸ‘ and keep up the good work! We are loving this project and it has saved us numerous hours!

A big shout out from the Mr Yum team and lots of ❀️ from Melbourne, Australia!

MichalLytek commented 4 years ago

Quote by @avin-kavish moved from #574 ❀️

image

StarpTech commented 3 years ago

We also plan to sponsor this project but it's not transparent what we can expect in the near future. According to project (TypeGraphQL vNext) and commit history it looks like there is no progress for months (Also can't see a Next branch) and that throwing money on it will have a marginal or effectively zero impact for us. Could you elaborate on your commitment to this project in 2021?

MichalLytek commented 3 years ago

(Also can't see a Next branch)

I've moved that into a private repo because Kamil MyΕ›liwiec "stolen" my code and embedded it as nestjs-graphql. I don't want to share those vNext ideas anymore before the v2.0 will be ready.

looks like there is no progress for months

I can see plenty of not released yet features: https://github.com/MichalLytek/type-graphql/blob/master/CHANGELOG.md#unreleased

v1.2 needs some polishing and some other pending fixes and PRs before releasing. I see a lot of people still uses v0.17.6 so I try to publish bigger updates less frequently, so they do not need to bump deps every week.

I'm in a process of moving into a new house so temporarily there might be less commit activity because I only have time to answer issues, discussion and stackoverflow. Most of my engagement is now focused on TypeGraphQL Prisma integration.

StarpTech commented 3 years ago

Thank you for the fast response.

I've moved that into a private repo because Kamil MyΕ›liwiec "stolen" my code and embedded it as nestjs-graphql. I don't want to share those vNext ideas anymore before the v2.0 will be ready.

This is no opensource πŸ˜• How is it possible to steal from an MIT licensed project? Please rethink that decision.

I can see plenty of not released yet features: https://github.com/MichalLytek/type-graphql/blob/master/CHANGELOG.md#unreleased

Any release ETA?

I'm in a process of moving into a new house so temporarily there might be less commit activity because I only have time to answer issues, discussion and stackoverflow. Most of my engagement is now focused on TypeGraphQL Prisma integration.

Congrats! 🏑 We would like to see improvements in the core. We are also willing to contribute in form of code.

MichalLytek commented 3 years ago

How is it possible to steal from an MIT licensed project? Please rethink that decision.

Imagine you spend a lot of time working on a new OSS project. Let's say a new NoSQL database. You work very hard for months, coding in silence, having 100 GitHub stars. Then goes let's say Microsoft, "steal" (copy the code or fork the repo), name it "MicrosoftDB", launch in Azure, launch marketing campaigns, tutorial, influencers, etc.

Now everyone is using your project under some other company/project name. People forget about what you've done (or never heard of the origin of "MicrosoftDB", you don't have sponsors anymore. Everyone is using the Microsoft product, you only see your name in some file headers.

Welcome in a OSS MIT world πŸ˜‰ Read about the Redis vs. AWS case to see how others monetize someone's OSS projects: https://techcrunch.com/2019/02/21/redis-labs-changes-its-open-source-license-again/

take their products and sell them as rebranded services without contributing back to the community

StarpTech commented 3 years ago

I created a ton of OOS. Some are more popular than others. I can understand you but the conclusion of such use cases was not to get away from opensource they changed their license to avoid such tricky shoots. Your project and great achievements are still visible and recognized.

StarpTech commented 3 years ago

Welcome in a OSS MIT world πŸ˜‰ Read about the Redis vs. AWS case to see how others monetize someone's OSS projects:

That's a pitfall. If your goal is to make money, MIT or anything in general without a business plan is πŸ’© Someday somebody will eat you πŸ˜„ The motivation to drive this project should be business-driven or purely personal.

MichalLytek commented 3 years ago

If your goal is to make money

The goal is not to make money. The goal is to be able to work full-time on OSS. And that requires variety of ways to raise funds for doing this. We all have mortgages, family, so we can't do it pro-bono, like we were still 23 and studying.

That's the reality, without the funding, it becomes a maintenance only project, as the first wave of excitement, gaining popularity and GitHub stars is putting out...

So having sponsors is really helping me in reducing my daily-job hours, so that I have some time to spend for working on TypeGraphQL πŸ˜‰

Your project and great achievements are still visible and recognized.

Go ask NestJS users if they know who created the code-first, decorator based GraphQL implementation they use. Nobody knows, nobody remembers. It hurt me very bad, so vNext is now developed in secret and be released as MIT when it's done - not as some partial ideas that can be implemented by "the competitor" in the meantime, when I don't have enough time to work on them.

StarpTech commented 3 years ago

As I said before, I understand! But if you develop the software behind the eyes of the opensource community, it will leave a resentful residue.