You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed this package/repo has gone a long time without any updates. My team at the organization I work use this package often in our test suites and have noticed some of the same issues as others. Right now we have a local fork maintained for our use which resolves some of these issues.
We were planning to publish our fork as a separate npm package but then thought maybe we ask to become the maintainers or the original repo/package. We would be open to either becoming maintainers under your ownership of this package or you could transfer ownership to my team and we would continue to maintain it. We have no desire or intent to change the licensing or accessibility of this package; only to improve and add features and upgrade dependencies.
What are your thoughts on this?
-Zippanova
The text was updated successfully, but these errors were encountered:
Hello @johntimothybailey,
I've noticed this package/repo has gone a long time without any updates. My team at the organization I work use this package often in our test suites and have noticed some of the same issues as others. Right now we have a local fork maintained for our use which resolves some of these issues.
We were planning to publish our fork as a separate npm package but then thought maybe we ask to become the maintainers or the original repo/package. We would be open to either becoming maintainers under your ownership of this package or you could transfer ownership to my team and we would continue to maintain it. We have no desire or intent to change the licensing or accessibility of this package; only to improve and add features and upgrade dependencies.
What are your thoughts on this?
-Zippanova
The text was updated successfully, but these errors were encountered: