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

Call for maintainers & an apology #299

Closed
nucleartide opened this Issue Jun 12, 2018 · 5 comments

Comments

Projects
None yet
4 participants
@nucleartide
Collaborator

nucleartide commented Jun 12, 2018

Hey folks,

Sorry for being unresponsive over the past couple months. I wish I could say it was because of work, but to be honest I just haven’t prioritized maintaining this addon (and related addons).

So, I’d like to step down as a maintainer. @poteto and @Dhaulagiri (I believe you’re also a collaborator), would you be open to finding more maintainers?

While ember-changeset is mostly usable on 1.3.0 (prior to the nested keys updates), the newer versions remain buggy, and cause problems for new ember-changeset users. I’m so sorry about this. @poteto invested a lot of time in this addon and many people in the community chipped in for the nested keys updates, so I’d like to hold myself accountable and fix any remaining bugs.

At the same time, I feel like there are a lot of competing solutions that make it a drag to work on this addon:

It’d be nice to consolidate efforts. Ideally, Ember Data would have built-in changesets of some sort. Maybe it’s most worthwhile to just contribute to Ember Data. Or as @poteto suggests, see if we can implement ember-changeset’s API using validated-proxy, which is the more general version of this addon.

Assuming @poteto and @Dhaulagiri are okay with this – is anyone interested in taking over ember-changeset maintenance?

@Dhaulagiri

This comment has been minimized.

Collaborator

Dhaulagiri commented Jun 13, 2018

I was only recently added as a maintainer and I don't have all that much time to contribute new work myself unfortunately, but my main goal is to ensure that the addon is in a consistent working state. 👍 to getting more folks involved who are interested.

@snewcomer

This comment has been minimized.

Collaborator

snewcomer commented Jun 22, 2018

@Dhaulagiri Also if you would be interested in pairing on setting relationships bug, it would be great to work with someone on it. Currently seeing if I can flush out a solution, but might take some time...

@psteininger

This comment has been minimized.

psteininger commented Jul 11, 2018

@Dhaulagiri @nucleartide I would be glad to contribute. I really want to resolve the relationship issues too

@snewcomer

This comment has been minimized.

Collaborator

snewcomer commented Jul 11, 2018

@psteininger Relationships issue is fixed on master 🎉

Also there is a 1.5.0 release issue #301 that we are focused on that would be great to get some more movement on!

@snewcomer

This comment has been minimized.

Collaborator

snewcomer commented Aug 26, 2018

I love all the work that has gone into this addon from ppl before 🙇 . Hopefully 1.5.0 release this week!

@snewcomer snewcomer closed this Aug 26, 2018

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