Sweetalert2: Looking for sweetalert2 collaborator(s)

[limonte]

Open-source plugins often have just one person (repo owner) who can manage PRs, issues, releases.

This is a huge problem, as dependency on 1 human is a weakness. If I die suddenly, this plugin will die with me and your PRs and issues will have no sense.

If you want to became a collaborator of this repo, let me know. Users with one or more merged PRs to this repo will become collaborators immediately after comment here. Other users are welcome too :)

More details about colaborators permissions: https://help.github.com/articles/permission-levels-for-a-user-account-repository/#collaborator-access-on-a-repository-owned-by-a-user-account

[Tonkpils]

I am definitely open to being a collaborator. I am still fairly new to Javascript but getting better and I figured since I'm making an addon for this package on ember I could help improve it if you're interested.

[limonte]

@Tonkpils you are very welcome!

[Hucxley]

What sort of features/enhancements are in the pipeline, or what bugs need fixed? In short, what are you looking for from collaborators in the short term?

[limonte]

Thank for good questions @KHam0425!

What sort of features/enhancements are in the pipeline, or what bugs need fixed?

All issues to be fixed, features to be discussed/implemented are here: sweetalert2/issues

In short, what are you looking for from collaborators in the short term?

• taking part in issues/features discussion
• if I'm inactive for month or more, publishing new releases after adding new features or fixing bugs.

[samturrell]

Happy to help! I have a few features i'm keen to add myself and a few issues i've spotted that I'd like to fix.

[limonte]

@samturrell

[jdcrensh]

I'd be happy to help out whenever possible!

[limonte]

@jdcrensh hello old contributor and welcome aboard! :)

[Hucxley]

Oh, I'd also like to help, if you can add me. Even though you hate the idea of queueing the modals, I did implement it in my environment. I'm working on building it into a PR that will allow developers to choose to allow pending alerts (default false).

[limonte]

@KHam0425 let me see that PR, then I'll make a decision :)

[acupofjose]

@limonte I'd love to help out with the project as a contributor if I can!

[limonte]

you're very welcome @acupajoe!

[limonte]

thank you all guys, swal2 is now totally safe if I suddenly disappear :)

[taxpayer]

Just a small thank-you message, @limonte: don't disappear. You had a very
impressive will power to take a good project that was not properly managed
and changed the game completely. As a Swal user since the very beginning, I
thank you for all you did and is still doing. And I hope to see other
projects of you also. :-)

[toverux]

@limonte I'm also quite impressed by the energy you have put in the project. I use Swal on a regular basis, and Swal2 saved me from using another mediocre library that displays alerts, once Swal(1) got too old.

So yes, following your invitation, I would be very happy to help from time to time, on any kind of issues!

[limonte]

Welcome to the team @toverux!

[limonte]

Dear @Tonkpils, @acupajoe, @birjolaxew, and @toverux!

Could you please make accounts on npmjs.com so I can add you to sweetalert2 collaborators there. After this you will be able to update sweetalert2 npm package.

[limonte]

BTW, I made the commit with mentioning all your names in package.json and bower.json.

Thank you so much for helping on SweetAlert2 development, we are so ahead of the original plugin now :rocket:

Happy holidays to you :christmas_tree: :santa: and all the best in New Year!

[toverux]

Thanks @limonte!
I've just created my account on npm (under the username toverux).

Also, I've never published things on npm. I presume it's not sorcery (based on my experience with Packagist), but could you eventually write a little development guide for the contributors? Conventions about code, git, how you're publishing, etc.

[birjolaxew]

Created birjolaxew on NPM

[limonte]

I've just created my account on npm (under the username toverux).

Added :+1:

Created birjolaxew on NPM

Added :+1:

I presume it's not sorcery (based on my experience with Packagist), but could you eventually write a little development guide for the contributors? Conventions about code, git, how you're publishing, etc.

Not much actually to say :)

• Coding style: I just added https://github.com/sweetalert2/sweetalert2/commit/8c5a8f1292a3d8a71eb4d5fec4384268aab3d3f1 which covers it automatically.
• Contributing guide is in the README: https://github.com/sweetalert2/sweetalert2#contributing
• Publishing
  
  
  
  • Bower grabs new versions automatically from Git tags (releases)
  
  
  • for npm there's an automatic releasing: https://github.com/sweetalert2/sweetalert2/commit/c9a027c465b42c2335e353f0f2cde555c149def2 so if I suddenly disappear it will continue to work. And if something will happen to my npm account you will need to generate a new key and put it to the Travis config. Read more about npm releasing: https://docs.travis-ci.com/user/deployment/npm/