Maintainers Wanted

[glennjones]

Glenn here. I built hapi-swagger over seven years ago and maintained it in the early days. For the past three years, @robmcguinness has supported the project with PR reviews, updates, commits and releases.

We are both coming to a point where we do not have the time to keep track of the issues and actively maintain the plug-in. It's still a popular Hapi plug-in with 284,000 downloads a month and roughly 17% of Hapi projects using it.

We're looking for people to help out and maintain the project. Any help would be appreciated. Comment on this issue if you're interested in helping. Thanks.

[patlehmann1]

I'm interested in contributing to the codebase.

[Spencer814]

I'd like to help out also.

[toddtarsi]

Same here. I'm interested in doing a bit to help if I can.

[AndriiNyzhnyk]

Same here. I am using this package as well so I would like to help somehow.

[robmcguinness]

@glennjones any thoughts on next steps?

[arimus]

Same here. Count me in to put some cycles on improvements.

Don't want to jump ahead, but seems like a good early step would be to do some triage and prioritize items that are critical (security fixes, bugs) vs others.

[patlehmann1]

Any update on this? I'm can make some time to have a virtual meeting if anyone would like.

[robmcguinness]

@patlehmann1 waiting on @glennjones since I am not admin and only maintainer.

[glennjones]

@patlehmann1 Thanks for the offer to help out with hapi-swagger and your patience with the lack of response. Sorry for the radio silence.

If I am honest I am a little uncertain about how you successfully onboard other people into helping maintain the project like this. It is not something I have done before.

The idea of a virtual meeting sounds great. Maybe we could all chat about what help people feel they could contribute, and how the project could be structured to make that work for them. What is needed from me as the original owner to make it happen.

If people (@robmcguinness and everyone who has offered in this thread) think a virtual meeting good way please let me know and we can sort out date/time to do a zoom/teams discussion.

Glenn

[robmcguinness]

That sounds great.

[AndriiNyzhnyk]

Let's do it.

[glennjones]

hapi-swagger maintenance chat - For anyone you wants to contribute.

OK rather than try and arrange this meeting date/time through github issues I have created a calendar poll on doodle. If you can select any of the times that work for you. I have gone evening Europe time hopefully to help with people in America. I am travelling over the next week and a half hence the dates.

Please click on the link below and vote for times that work for you:

https://doodle.com/meeting/participate/id/bYEm0P2b/vote

[glennjones]

OK I have booked in a meeting for - Wednesday, 18 May⋅17:00 UK Time. The zoom link is below. If anyone else wants to join meeting please feel free. We are going to have a chat about the maintenance of hapi-swagger. The meeting is for anyone you wants to contribute, however much or little.

Topic: hapi-swagger
Time: May 18, 2022 05:00 PM London

Join Zoom Meeting
https://us02web.zoom.us/j/89185259999?pwd=VFlUbzNYbS9mcVEzaXgrcllLYStldz09

Meeting ID: 891 8525 9999
Passcode: tu04e9

If you want to come and cannot make this data let me know and I can quickly open the poll again

[ahalf-yuan]

I'd like to help out also.

[glennjones]

@ahalf-yuan your more than welcome to come along to the zoom meeting today 17:00 UK time. Connection details are in thread above. If you cannot make don't worry I will document the outcomes. This will hopefully cover how we hope to make it easier for people to contribute going forward.

[robmcguinness]

Sorry I missed the meeting. Hopefully it was productive. Please let me know next steps.

[glennjones]

That's OK @robmcguinness sorry you could not make it, but we had a good meeting

What was agreed in the meeting today

• Move the project to a Github organisation to make use of the different levels of access rights, Triage, Write, Maintain etc (Glenn)
• Start all the new maintainers on triage rights, add more rights as they are needed (Glenn)
• Create a Slack channel for hapi-swagger maintainers to quickly discuss how to deal with issues and updates (Glenn)
• Go through the backlog of issues and pull requests labelling them so we can see what types of issues we have (Everyone)
• Start picking off the easier issues to learn codebase with input from Robert and Glenn about architect where possible (Everyone)

Future

• Add webhooks to push github project events into slack
• Consider feature development/ roadmap

[arimus]

Same here. Sorry, I was unable to attend. Looks like a good list of action items to me.

…

On Wed, May 18, 2022 at 1:17 PM Glenn Jones ***@***.***> wrote: That's OK @robmcguinness <https://github.com/robmcguinness> sorry you could not make it, but we had a good meeting *What was agreed in the meeting today* - Move the project to a Github organisation to make use of the different levels of access rights, Triage, Write, Maintain etc (Glenn) - Start all the new maintainers on triage rights, add more rights as they are needed (Glenn) - Create a Slack channel for hapi-swagger maintainers to quickly discuss how to deal with issues and updates (Glenn) - Go through the backlog of issues and pull requests labelling them so we can see what types of issues we have (Everyone) - Start picking off the easier issues to learn codebase with input from Robert and Glenn about architect where possible (Everyone) *Future* - Add webhooks to push github project events into slack - Consider feature development/ roadmap — Reply to this email directly, view it on GitHub <#718 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABXYKXN3VPQESILBWGEZ53VKU655ANCNFSM457BVODQ> . You are receiving this because you commented.Message ID: ***@***.***>

[williamolojede]

I use this this library, and it's one of the reasons why I love hapi, if maintainers are still needed, please count me in.