Looking for maintainer of this project

[walling]

Hi, I am the author of gulp-raml2html. I started this project, because I really needed it and nothing else existed at the time. Unfortunately I haven't been able to maintain this project for a long time for personal reasons. I will try to look at the issues and pull requests in the following weeks, but I really could use some help maintaining the project. The job includes looking at issues, pull requests, and publishing new releases on NPM. If anyone is interested, please contact me and we will figure out the details.

Relates to issue #13.

[walling]

Updated to raml2html 1.6.0 and ensured that tests pass. Including https option. Released as 0.2.0.

[ducin]

Dear @walling, @shicholas, @iki and @lukaskostial
Thank you for all your work on and around the plugin!

I've been using raml2html and found out this crazy situation around the gulp-raml2html plugin :) I'd like to clean the situation... Currently it's an example proving that JavaScript community seems to be inmature... I'd like to change that and have all the work done on https://gist.github.com/iki/784ddd5ab33c1e1b726b "merged" into gulp-raml2html. Moreover, I'd like gulp-raml2html to be transferred into https://github.com/raml2html. This is how it should look like IMO, but this plugin has to be up to date first.

Let's bring this plugin back to life:

• it's already registered in npm with a perfect name
• @walling includes other people to the github repo:
  
  and to npm package (npm owner add <user> gulp-raml2html)
  
• use the efforts done in https://gist.github.com/iki/784ddd5ab33c1e1b726b
• and update the dependency to raml2html@2.4.0, since the gist is outdated itself.

Let's prove JS community is mature :)

What do you think? Who is interested in it?

[walling]

I'm sorry I haven't had the capacity to update this project in a long long time. I'm up for doing what is needed to make it live again. @ducin, I like your proposal. If interested people share their github + npm usernames, I will give them access as you specified. Then we can start moving forward.

[walling]

Dear all, as a start I added push access for @ducin, @shicholas, @iki and @lukaskostial. If you provide me with npm usernames, I will add publish access as well.

[ducin]

@walling thank you for unblocking this!

My npm username is ducin

[seashootz]

thank for you the offer, however I am not interested in maintaining this as I don't use this library anymore.

cheers,

[walling]

@shicholas, I removed you as a collaborator.

@ducin, I added you to the NPM package. You are displayed on the package page, but there are some issues with the command line tool. Can you maybe try npm owner ls gulp-raml2html? If it doesn't work, I will try again tomorrow.

[ducin]

@walling nope, only you here:

Tomasz.Ducin@WAWLT548 MINGW64 ~/Development/GitHub/raml-editor
$ npm owner ls gulp-raml2html
walling <bwp@bwp.dk>

@iki you are the creator of the (temporary) solution that the community is using right now :) you have the precedence to decide on how should the plugin look like. Could you please reply if you're interested in carrying on with gulp-raml2html?

[walling]

@ducin, try again with the npm owner.

[ducin]

@walling perfect, thanks

$ npm owner ls gulp-raml2html
ducin <tomasz.ducin@gmail.com>
walling <bwp@bwp.dk>

Waiting for @iki...

[homerjam]

@iki?