Skip to content

[Patreon] Remove Info & Maintainership #699

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

Merged
merged 1 commit into from
May 24, 2019
Merged

[Patreon] Remove Info & Maintainership #699

merged 1 commit into from
May 24, 2019

Conversation

metaskills
Copy link
Member

@metaskills metaskills commented May 24, 2019

Why?

About a year ago I setup Patreon for both the adapter and TinyTDS. My hopes were that some monetary gain would help kickstart my involvement and maintain the work I started here over 10 years ago.

Sadly that did not happen and despite many months of closing following the projects' comments, my guidance and stewardship has fallen to nothing. More so, despite my optimism of thinking I will contribute again after a break... like I did some years back with v4.2... I've come to realize that I may never contribute to the adapter again.

Leaving a project I've done so much for is hard for me to come to terms with... but I've been learning to a) realize my time is limited and b) my career has been changing as I put more of my professional development to learning about cloud-native development using AWS and putting focus on projects like Lamby (https://github.com/customink/lamby).

Future Contributors (GitHub & Rubygems)

A long time ago I setup the rails-sqlserver GitHub organization so that it would not be tied to a single person. This proved useful since the adapter is published in a few books. Moving forward I will still maintain admin control of this "org" and will happily keep up with our newest contributors and add new collaborators as the current/active team sees fit so that the project can carry on. The same is true for publishing to Rubygems. Eventually perhaps, someone else can take those on fully too.

However, moving forward, I will un-subscribe/watch both the Adapter and TinyTDS projects. That means I will only get notifications if you call me out using my @metaskills GitHub handle. Please feel free to do this. I am here if you need me.

What About Patreon?

Over the past year it has gained over $1K dollars and very recently I closed out the Patreon campaign. It was my hope to contribute to the adapter again and earn this amount, however I honestly do not think it will happen. To that end, I have decided to split the majority of this revenue up to the two contributors that have been working the adapter over that time.

That would be @matthewdunbar and @wpolicarpo. If y'all would please email me at ken[at]metaskills.net I would gladly coordinate those payments and drop a note/record here of those transactions for transparency.

TinyTDS Pull Request

Here is the change to TinyTDS. I have already committed that to master. rails-sqlserver/tiny_tds@303f885

@metaskills metaskills merged commit a2a1619 into master May 24, 2019
metaskills referenced this pull request in rails-sqlserver/tiny_tds May 24, 2019
@metaskills
Copy link
Member Author

After talking to Matthew he INSISTED that Wanderson take the Patreon earnings for his work over the last year. Today I made a PayPal payment to Wanderson for $1,200.00 USD since he has done the actual work, to which I'm super grateful. Thanks y'all.

@wpolicarpo
Copy link
Member

@metaskills as I told you, I wish you all the best with your new projects and I hope I can help keeping the excellent work you've been doing in the adapter during these years.

@matthewdunbar thank you for your generosity. I wish nothing but the best for you.

wpolicarpo pushed a commit that referenced this pull request Jun 24, 2019
[Patreon] Remove Info & Maintainership
@wpolicarpo wpolicarpo deleted the patreon branch April 9, 2020 09:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants