Skip to content

Commit

Permalink
Initial commit
Browse files Browse the repository at this point in the history
  • Loading branch information
jmertic authored Jan 3, 2023
0 parents commit 93bdb6c
Show file tree
Hide file tree
Showing 11 changed files with 311 additions and 0 deletions.
38 changes: 38 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
---
name: Bug report
about: Create a report to help us improve
title: ''
labels: ''
assignees: ''

---

**Describe the bug**
A clear and concise description of what the bug is.

**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

**Expected behavior**
A clear and concise description of what you expected to happen.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Desktop (please complete the following information):**
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]

**Smartphone (please complete the following information):**
- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]

**Additional context**
Add any other context about the problem here.
20 changes: 20 additions & 0 deletions .github/ISSUE_TEMPLATE/feature_request.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
---
name: Feature request
about: Suggest an idea for this project
title: ''
labels: ''
assignees: ''

---

**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

**Describe the solution you'd like**
A clear and concise description of what you want to happen.

**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.

**Additional context**
Add any other context or screenshots about the feature request here.
22 changes: 22 additions & 0 deletions .github/ISSUE_TEMPLATE/meeting.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
# [COMMUNITY NAME] Working Group Meeting - <%= date.toFormat("MMMM d, yyyy") %>

## Attendance

- [ ] Person A, Afflilation
- [ ] Person B, Afflilation
...

## Agenda

Extracted from **<%= agendaLabel %>** labelled issues and pull requests from **<%= owner %>/<%= repo %>** prior to the meeting.

<%= agendaIssues.map((i) => {
return `* ${i.title} [#${i.number}](${i.html_url})`
}).join('\n') %>

## Action Items


## Notes

## Chat
29 changes: 29 additions & 0 deletions .github/PULL_REQUEST_TEMPLATE/pull_request_template.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
# Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes # (issue)

## Type of change

Please delete options that are not relevant.

- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
- [ ] This change requires a documentation update

# How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

# Checklist:

- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings
- [ ] I have added tests that prove my fix is effective or that my feature works
- [ ] New and existing unit tests pass locally with my changes
- [ ] Any dependent changes have been merged and published in downstream modules
16 changes: 16 additions & 0 deletions .github/workflows/build_agenda.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
name: Build Agenda for meetings
on:
issues:
types: [labeled, unlabeled]
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: wesleytodd/meeting-maker@v0
with:
token: ${{ secrets.GITHUB_TOKEN }}
schedules: 2020-04-22T16:00:00.0Z/P2W # first occurance of the meeting and recurrance schedule
createWithin: P2D # create agenda within 2 days of the meeting
issueTitle: "WG Meeting <%= date.toFormat('yyyy-MM-dd') %>"
labels: meeting
agendaLabel: meeting-agenda
18 changes: 18 additions & 0 deletions .github/workflows/send_agenda.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
name: Send meeting agenda to email list
on:
issues:
types: [labeled]
pull_request:
types: [labeled]
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: timheuer/issue-notifier@v1
env:
SENDGRID_API_KEY: ${{ secrets.SENDGRID_API_KEY }}
with:
fromMailAddress: '[email protected]'
toMailAddress: '[MAILING LIST EMAIL]'
subject: '[COMMUNITY NAME] Working Group meeting agenda for today'
labelsToMonitor: 'meeting'
1 change: 1 addition & 0 deletions CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
All participants agree to abide by the Code of Conduct available at https://github.com/openmainframeproject/tac/blob/master/CODE_OF_CONDUCT.md. Please contact [email protected] to report any violations or concerns.
15 changes: 15 additions & 0 deletions INSTRUCTIONS.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
# Instructions for using this template

1) Review and update (README.md) with the working group name, and other details as approved by the TAC
2) To enable creating meeting agendas from GitHub issues, follow steps 3-5.
3) In the [meeting agenda template](.github/ISSUE_TEMPLATE/meeting.md), update `[COMMUNITY NAME]` and add the working groups members under the ['Attendance' section](.github/ISSUE_TEMPLATE/meeting.md#attendance).
4) Set the meeting date and time, along with the cadence in the [build agenda workflow](.github/workflows/build_agenda.yml) in the key `schedules:` that specifies a ISO-8601 interval. Examples for repeating:

```
# start 2020-04-22 at 16:00, repeat every 2 weeks
schedules: 2020-04-22T16:00:00.0Z/P2W
# start 2020-04-22 at 16:00, repeat every 7 days
schedules: 2020-06-22T16:00:00.0Z/P7D
```
5) In the [send agenda workflow](.github/workflows/send_agenda.yml), update `[COMMUNITY NAME]` and `[MAILING LIST EMAIL]`.
6) Any items with the label `meeting` will be added to the agenda automatically when it is built the day prior to the meeting.
Loading

0 comments on commit 93bdb6c

Please sign in to comment.