Seeking new maintainers

[max-mapper]

I'd like to step down as a maintainer of this module. I'm happy to pinged with questions about the code but I don't have time for daily issue triaging, test maintenance, feature requests and release management. If anyone else is interested in maintaining, please get involved in the managing of pull requests and issues as per the contributing.md and one of the existing maintainers will eventually add you as a maintainer as per the open open source method that is used to govern this module.

@malept @kfranqueiro as main contributors I'd like to get your feedback on what I should do ownership wise, either transfer the repo to one of your accounts or set up an organization for it.

[malept]

@maxogden, if I haven't said it already, many thanks for creating this module.

My suggestion is to set up an organization for this repository. I don't suppose we can set up Travis to publish to NPM when a release tag is created?

Also, we need to make the open open source governance method a bit more prominent in the docs. I think I've only seen it mentioned in issues.

[max-mapper]

@malept thanks :)

Me and @mafintosh moved this, electron-download and electron-prebuilt to a new org electron-userland. I also now mention open open source more prominently in the readme, and on the org page. We'll still be around to help but won't be as involved on a daily basis. Cheers!

[develar]

@malept What about https://github.com/electronjs (I don't know anything, just ask) as an organization?

[malept]

@develar that's more of a question for @maxogden, not me.

[malept]

@maxogden perhaps we should invite @sethlu and ask to move https://github.com/sethlu/electron-osx-sign into the org (if you haven't done so already).

Also, I'm trying to fix the Coveralls integration. (Coveralls apparently does not like it when repositories move.)

[max-mapper]

@develar the electronjs org was created by GitHub, and isn't following the open open source governance model. I'd rather have these live in a neutral org

[sethlu]

Sounds good! 👍 One question from me is if there be any change of license from BSD-2-Clause? I could move electron-osx-sign later today.

[malept]

@sethlu I'm not sure what you're asking regarding the license. The license for both electron-packager and electron-osx-sign look the same to me. The author line would obviously be different since there are different contributors.

[sethlu]

@malept I'm just slightly unsure if to switch to another license as moving it to an org. I'll be keeping it like that for now.

[malept]

@sethlu you're fine.

[sethlu]

@malept Just tried to move my repo to electron-userland; it seems that I may have to be an admin before completing the transfer: https://help.github.com/articles/transferring-a-repository/#transferring-from-a-user-to-an-organization.

[malept]

@sethlu I would do something about that myself, but I am not an owner in the org.

[max-mapper]

sorry, you are now :)

On Sunday, February 28, 2016, Mark Lee notifications@github.com wrote:

@sethlu https://github.com/sethlu I would do something about that
myself, but I am not an owner in the org.

—
Reply to this email directly or view it on GitHub
#272 (comment)
.

Sent from my phone

[malept]

@sethlu you should be able to transfer now 😄

[sethlu]

@malept @maxogden Great, thanks! Just transferred the repo. I'll be updating the authors etc. later.

[malept]

FYI, I've left this issue open mostly because we are lacking a maintainer who can solve issues relating to building on the Windows host platform.

[malept]

Since nothing's happened in about 3 years, I'm closing this issue. This does not, however, mean that we're not still looking for new maintainers, particularly those who can debug on Windows platforms.

[JohnTitor]

@malept It may be a little late, but I'm interested in contributing and maintaining.

[malept]

@JohnTitor thanks for your interest! The best way to get started with contributing is going through the open "help wanted" issues and seeing if any fit your skillset.