conventional-commits / meta Goto Github PK

Can we use the Verified domains feature under our org Settings to verify the conventionalcommits.org domain.

@wesleytodd and I would be able to meet a bit earlier, which could be better for European folks.

@wesleytodd a day other than Friday would potentially be better, (@bcoe would be open to Thursday or Wednesday, with a preference for Thursday).

@byCedric, @damianopetrungaro, @eemeli.

Hey, i just left the org before few weeks because of that.
Is it big deal for you guys or not? I really don't find much sense in 2FA and disabled in most of the places. It definitely isn't "more secure", in reality, it might even be more insecure because it's easier to get 2FA code than breaking some huge random generated password.

In anyway, if you don't want to consider that, re-invite me again and I'll sadly activate it.. ;/

Since there was no tracking issue with the details I figured I would make this. Feel free to edit as we have more details (like a zoom link).

Agenda:

• Governance
• Future plans

Date: Friday October 9th
Time: 1pm EST

Notes: https://hackmd.io/do0DS1BnRgWgv4LYpckzsw

It seems to me that since the spec lives here, so should the parser. Thoughts?

Having separate issues and history from the monorepo where it lives today would be helpful for me, as I have been struggling to find the right place to start contributing, and don't really care to touch all those project specific configuration packages which live together in the monorepo.

I would be happy to extract just the git history from that directory so we can maintain the references, but it would mean loosing the related issues and any open PRs. IMO, this is a fine tradeoff for a better future, but it is one downside of doing this.

FWIW, I would also like to look at pulling out the other "foundational" packages like git-raw-commits and git-semver-tags but those don't make as much sense to move to this org, so figured I would start by asking about the parser.

Hey, i just left the org before few weeks because of that.
Is it big deal for you guys or not? I really don't find much sense in 2FA and disabled in most of the places. It definitely isn't "more secure", in reality, it might even be more insecure because it's easier to get 2FA code than breaking some huge random generated password.

In any way, if you don't want to consider that, re-invite me again and I'll sadly re-activate it... ;/

I want to be part of the org and already created huge work on that topic in last months, so I can transfer a couple of my repos here.

parse-commit-message v3 is on its way too. From now on, it can be called "conventional commits utils" for sure. It can parse, stringify and validate (both objects and strings) against the specification.

I also created git-commits-since, recommended-bump and detect-next-version as part of the greater good in automation.

We should have some policy files for this repo, like SECURITY.md, CoC.md, and Contributing.md. I can create a .github repo and just push some standard ones there if folks are good with it. Would help keep those from being duplicated in all the repos.

cc @bcoe @damianopetrungaro @byCedric