-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document PURL community meetings #384
Labels
PURL community
Messaging and communication of PURL and its adopters
Comments
johnmhoran
added a commit
that referenced
this issue
Jan 27, 2025
Reference: #384 Signed-off-by: John M. Horan <[email protected]>
pombredanne
added a commit
that referenced
this issue
Jan 28, 2025
Add 2025-01-22 PURL community meetings minutes #384
@pombredanne Unless you suggest otherwise, I'll keep this issue open and use it to create a new branch and PR each time we have a new set of minutes to prepare and push, e.g., today's branch will be |
johnmhoran
added a commit
that referenced
this issue
Feb 5, 2025
Reference: #384 Signed-off-by: John M. Horan <[email protected]>
johnmhoran
added a commit
that referenced
this issue
Feb 20, 2025
Reference: #384 Signed-off-by: John M. Horan <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'll create a new "meetings" folder to hold the
.md
-format minutes of the new PURL community meetings and push the minutes of our 2025-01-22 meeting.The text was updated successfully, but these errors were encountered: