Status of project and main dev: ypid

[ypid]

I just want to use this issue to track my plans on spending time on this project as I have the feeling I am doing too little over the last years, I want to at least have a clear stand on it. I have been very active on this "little" project for years (https://github.com/opening-hours/opening_hours.js/graphs/contributors). But the spare time I put into the project has (sadly) been dedicated into other projects over the last years. This is my decision of course, it is still not ideal for this project.

My current policy (that I adapted over the last years) is: I continue to maintain the project. I will answer to all questions/feature requests in a timely manner, fix important bugs within a few days and of course review/merge pull requests. Other than that, I currently have too many other projects so that I am not likely to invest time for implementing new features or larger stuff. Expect this policy to be valid at least until 2021-12.

That just to keep things straight. When you want more progress, I guess you will have to speak up and make it happen.

[ypid]

Still valid. I would even welcome help maintaining the package. JavaScript is just not what I do outside of this project. If somebody steps up, I would appreciate it.

[ypid]

Status update. I still find it difficult to dedicate time to this sadly. Help in the form of reviewing PRs, commenting on them and approving them would help me very much.

[ypid]

I would be open to hand this over to another maintainer in the long term. But this is kinda difficult with situations like the takeover of the xz project. I don’t want this to happen.

[KristjanESPERANTO]

Thanks for putting so much work into this project! 👏

I am not yet familiar with all parts of the code and the toolchain, but I would like to help. My suggestion: If you give me the rights, I would review PRs that I can understand and merge them into a develop branch.

Additionally, I would start looking at the toolchain and either update or replace one tool at a time. I would also take a look at the GitHub workflow to update to newer node versions.

I don't know if I could do it completely, but as a first step I could take care of the low hanging fruits and let you know when I think a release could be made. That would at least be a baby step forward. What do you think?

[ypid]

@KristjanESPERANTO Thanks for stepping up, sounds good to me! I remember from Changelog Interviews – Episode #596: Securing GitHub that GitHub is lacking in permission management in a few places. I therefore suggest that you do this development in https://github.com/KristjanESPERANTO/opening_hours.js for now. Feel free to merge pull requests (for example with git on the command line) that are open here into your branch or ask authors for changes. You can already submit reviews to pull requests. Please open a pull request that contains all your work or reuse #468. Similar how I did it in AMDmi3#14 ;-)

I will think about how to best give you access in a few days. This will need some thought.

For now, I have given you triage permission. In addition to read access that everyone has, it allows you to:

• Apply/dismiss labels
• Close, reopen, and assign all issues and pull requests
• Mark duplicate issues and pull requests
• Hide anyone's comments
• Move a discussion to a different category
• Lock and unlock discussions
• Individually convert issues to discussions
• Delete a discussion

Ref: Repository roles for an organization.

What I would be interested in terms of tooling is to automate the release process more. Things like

• https://pre-commit.com/
• commitizen

come to my mind. But you don’t have to use those if you prefer other tools.

What do you think about digitally signing git commits? I think it is helpful in that it allows you to build an online identity based on cryptography. Its a good trade-off between developer privacy and a long term identity in times of XZ project takeover.

Happy hacking 👌