Looking for an owner about custom-event-polyfill HOT 7 CLOSED

So after giving the issue some thought, it seems like it'll be too much administrative overhead to setup all those CI systems, etc. And on top of that, you will need to keep changing authentication tokens, etc when they are invalidated (like npm did recently) or Github token changes, or Saucelabs introduce some changes, etc in the future. Plus if things go wrong, I'll have to prod you to login to the saucelabs account to see if connections are happening properly, or edit travis config, etc. I think it might become more pain than it'd be worth for you (and me).

So, I published a new npm custom-event-polyfill version 1.0.6 (thanks for making me admin) - but had to do it from my fork. I hope that's OK with you.

from custom-event-polyfill.

Thanks @krambuhl. I'll make the changes soon.

from custom-event-polyfill.

Sure.

from custom-event-polyfill.

@krambuhl I've setup tests on saucelabs too for my fork of the project. Can I merge that in here?

from custom-event-polyfill.

@kumarharsh I'm adding you as a collaborator on this repo and kumarharsh on npm as an additional maintainer.

Feel free to PR your changes into this repo, version bump, and publish to npm. I've never changed ownership of a open source project before, please let me know if there is anything else I can do.

from custom-event-polyfill.

@krambuhl I'd added travis and saucelabs integration to the project, but I can't find a way to enable travis or sauce integrations for this repo. I think as an owner, only you have the authority to do so. Can you dedicate some time to get it done? I think enabling saucelabs integration (for testing on real IE browsers) would need you to fill out a form telling them that this is an OSS project, without which you can't signup to a free account. Ping me on my email if you need any help on this.

from custom-event-polyfill.

I think a simpler way would be that you give me permission to publish to your repo on npm.

from custom-event-polyfill.