October Meeting #109

Open
opened 2026-02-17 11:46:53 -06:00 by GiteaMirror · 7 comments
Owner

Originally created by @bcoe on GitHub (Sep 25, 2020).

Proposal

I would like to suggest that we have our first monthly meeting in October, where:

  1. start to figure out some governance for this project.
  2. divide up some of the work triaging Pull Requests, and commenting on issues.

This issue will be updated with a Hangout link, agenda, and a date/time once we can agree on one.

Call to action

Join the conventional commits channel in this chat room if you're interested in joining the meeting; and we can pick a time.

Originally created by @bcoe on GitHub (Sep 25, 2020). ## Proposal I would like to suggest that we have our first monthly meeting in October, where: 1. start to figure out some governance for this project. 2. divide up some of the work triaging Pull Requests, and commenting on issues. This issue will be updated with a Hangout link, agenda, and a date/time once we can agree on one. ## Call to action Join the conventional commits channel in [this chat room](http://devtoolscommunity.herokuapp.com/) if you're interested in joining the meeting; and we can pick a time.
GiteaMirror added the process label 2026-02-17 11:46:53 -06:00
Author
Owner

@damianopetrungaro commented on GitHub (Sep 25, 2020):

Created a conventional-commits workspace as well: https://join.slack.com/t/newworkspace-x8l1674/shared_invite/zt-hiebz1qv-EhTZI5kIx6IIcbMc459W3A

@damianopetrungaro commented on GitHub (Sep 25, 2020): Created a conventional-commits workspace as well: https://join.slack.com/t/newworkspace-x8l1674/shared_invite/zt-hiebz1qv-EhTZI5kIx6IIcbMc459W3A
Author
Owner

@damianopetrungaro commented on GitHub (Sep 25, 2020):

@conventional-commits/committee FYI ☝️

@damianopetrungaro commented on GitHub (Sep 25, 2020): @conventional-commits/committee FYI ☝️
Author
Owner

@bcoe commented on GitHub (Sep 25, 2020):

As a potential date, I'd like to suggest, Friday, October 9th, 10AM - 11AM PDT.

@bcoe commented on GitHub (Sep 25, 2020): As a potential date, I'd like to suggest, **Friday, October 9th, 10AM - 11AM PDT**.
Author
Owner

@ghermeto commented on GitHub (Sep 28, 2020):

I can make it

@ghermeto commented on GitHub (Sep 28, 2020): I can make it
Author
Owner

@wesleytodd commented on GitHub (Sep 29, 2020):

I can also attend (or atleast will make it happen).

@damianopetrungaro would you consider using the tooling slack? I just hesitate to have even more slacks 🤣. I am not opposed, but seems like it fits well within the domain of tooling, or is this because you don't want to be so JS focused (edit: which is a very valid concern)?

@wesleytodd commented on GitHub (Sep 29, 2020): I can also attend (or atleast will make it happen). @damianopetrungaro would you consider using the tooling slack? I just hesitate to have *even more slacks* 🤣. I am not opposed, but seems like it fits well within the domain of tooling, or is this because you don't want to be so JS focused (edit: which is a very valid concern)?
Author
Owner

@damianopetrungaro commented on GitHub (Sep 29, 2020):

@wesleytodd I am cool with that, but conventional commits it's not a tooling for JS, or at least not anymore :P

It is a language agnostic specification :)

That's the main reason why I created it, also to have a non-JS place where to discuss things :D

Fun fact: I never wrote JS code for real, only played a couple times locally 😂

@damianopetrungaro commented on GitHub (Sep 29, 2020): @wesleytodd I am cool with that, but conventional commits it's not a tooling for JS, or at least not anymore :P It is a language agnostic specification :) That's the main reason why I created it, also to have a non-JS place where to discuss things :D Fun fact: I never wrote JS code for real, only played a couple times locally 😂
Author
Owner

@wesleytodd commented on GitHub (Sep 29, 2020):

Cool, at first I didn't think about that as I was writing my comment, so added it at the end. I agree completely that this is lang agnostic and that reason makes perfect sense for why we need another slack workspace.

@wesleytodd commented on GitHub (Sep 29, 2020): Cool, at first I didn't think about that as I was writing my comment, so added it at the end. I agree completely that this is lang agnostic and that reason makes perfect sense for why we need another slack workspace.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/conventionalcommits.org#109