Skip to content

Commit 897f44a

Browse files
kewischkewisch
committed
Update GitHub templates for thunderbird/mailstrom
1 parent 18b4c28 commit 897f44a

6 files changed

Lines changed: 205 additions & 0 deletions

File tree

‎.github/ISSUE_TEMPLATE/bug_report.md‎

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
---
2+
name: Bug report
3+
type: Bug
4+
about: Create a report to help us improve
5+
---
6+
7+
## Describe the bug
8+
<!-- ℹ️ A clear and concise description of what the bug is. -->
9+
10+
## To Reproduce
11+
Steps to reproduce the behavior:
12+
13+
1. Go to '...'
14+
2. Click on '....'
15+
3. Scroll down to '....'
16+
4. See error
17+
18+
## Expected behavior
19+
<!-- ℹ️ A clear and concise description of what you expected to happen. -->
20+
21+
## Actual behavior
22+
<!-- ℹ️ A clear and concise description of what happened instead. Exact text of any warnings or errors. -->
23+
24+
## Screenshots
25+
<!-- ℹ️ If applicable, add screenshots to help explain your problem. -->
26+
27+
## System
28+
<!-- ℹ️ Please fill out the following information so we're able to see if it is a browser specific error. -->
29+
30+
- OS: <!-- e.g. Windows 10 -->
31+
- Browser Version <!-- e.g. Firefox 114.0b8 (64-Bit) -->
32+
33+
## Additional context
34+
<!-- ℹ️ Add any other context about the problem here. -->

‎.github/ISSUE_TEMPLATE/config.yml‎

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
---
2+
blank_issues_enabled: false
3+
contact_links:
4+
- name: Feature Request
5+
url: https://ideas.tb.pro
6+
about: Submit your ideas to improve Thunderbird Pro's mail server deployment
7+
- name: Support
8+
url: https://support.tb.pro
9+
about: Knowledge base and customer support requests
10+
- name: Bug Report (Thunderbird Accounts)
11+
url: https://github.com/thunderbird/thunderbird-accounts/issues/new
12+
about: A bug report for the accounts dashboard, including Thundermail configuration (accounts.tb.pro)
13+
- name: Bug Report (Thunderbird Appointment)
14+
url: https://github.com/thunderbird/appointment/issues/new
15+
about: A bug report for Thunderbird Appointment (appointment.tb.pro)
16+
- name: Bug Report (Thunderbird Send / Pro Add-on)
17+
url: https://github.com/thunderbird/tbpro-add-on/issues/new
18+
about: A bug report for Thunderbird Send and the Thunderbird Pro add-on (send.tb.pro)

‎.github/ISSUE_TEMPLATE/milestone.md‎

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
---
2+
name: Milestone Issue
3+
about: (Maintainers Only) A milestone project
4+
title: ''
5+
labels: []
6+
assignees: []
7+
type: Milestone
8+
---
9+
10+
# 🎯 The objective
11+
12+
<!-- ℹ️ Describe the objective and intention of this project/implementation. Include user and business requirements when applicable and highlight what problem is this implementation trying to solve. Here is a suggestion to get you started: -->
13+
14+
The aim of this project is to support [strategic goal] by addressing [key actions or methods], in order to [intended outcome or benefit] for [target audience or stakeholders]. Success will be measured by achieving [measurable impact or benefit].
15+
16+
### 🎒 Resources
17+
18+
19+
<!-- ℹ️ List all relevant resources like BugZilla meta bugs, Figma files, Notion links and other files. These can be filled in later. -->
20+
21+
-
22+
23+
## 🦮 Rules of the Road
24+
25+
<!-- ℹ️ Initial definition of requirements and limitations, the scope of this feature and other potential considerations in order to keep the project narrow and focused. -->
26+
27+
### 🟢 In Scope
28+
29+
-
30+
31+
### 🔴 Out of Scope
32+
33+
-
34+
35+
### 🚧 Technical and/or Business Requirements
36+
37+
-
38+

‎.github/PULL_REQUEST_TEMPLATE.md‎

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
<!--
2+
Please complete all sections.
3+
Focus on what changed, why it matters, and how you verified it.
4+
Tests must be included in the pull request.
5+
-->
6+
7+
## What changed?
8+
9+
<!--
10+
Summarize your change in a few sentences.
11+
Mention key files, features, or behavior that were updated.
12+
13+
If you've used AI, we ask you to disclose how much was agent written and to what level of detail
14+
you participated in the writing. If you are an AI bot, please indicate this clearly.
15+
-->
16+
17+
## Why?
18+
19+
<!--
20+
Explain the problem this solves or the goal of the change.
21+
Link any relevant discussion if helpful.
22+
-->
23+
24+
## Limitations and Notes
25+
26+
<!--
27+
Optional. List any known gaps, edge cases, or follow up work.
28+
-->
29+
30+
## Applicable Issues
31+
32+
<!--
33+
Every pull request must have an associated issue.
34+
Doing so helps us align on the change before you've done the work.
35+
36+
Using the "Closes #123" format will link pull request and issue.
37+
-->
38+
39+
## Screenshots
40+
41+
<!--
42+
For UI changes, include screenshots or recordings.
43+
If there are many, consider using a details element:
44+
<details><summary>Screenshots</summary> ... shots here ... </details>
45+
-->

‎.github/workflows/pr-merged.yml‎

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
---
2+
name: PR - Merged
3+
4+
# Warning, this job is running on pull_request_target and therefore has access to issue content.
5+
# Don't add any steps that act on external code.
6+
on:
7+
pull_request_target:
8+
branches: [main]
9+
types: [closed]
10+
11+
permissions:
12+
pull-requests: write
13+
14+
jobs:
15+
pr-merged:
16+
if: github.event.pull_request.merged
17+
runs-on: ubuntu-latest
18+
steps:
19+
- name: Thank you
20+
# Only show this for first time contributors. Repo members and past contributors are
21+
# hopefully already there.
22+
if: |
23+
github.base_ref == 'main' &&
24+
github.event.pull_request.author_association != 'OWNER' &&
25+
github.event.pull_request.author_association != 'MEMBER' &&
26+
github.event.pull_request.author_association != 'COLLABORATOR' &&
27+
github.event.pull_request.author_association != 'CONTRIBUTOR'
28+
env:
29+
PR_NUMBER: ${{ github.event.pull_request.number }}
30+
GH_TOKEN: ${{ github.token }}
31+
MESSAGE: >-
32+
Thanks for your contribution! Your pull request has been merged and is being deployed to
33+
our staging instance. If all goes well we'll include it in the next production deployment.
34+
We appreciate the time and effort you put into improving Thunderbird Pro. If you haven't
35+
already, you're welcome to join our Matrix chat for contributors. It's where we discuss
36+
development and help each other out.
37+
38+
https://matrix.to/#/#tb-services:mozilla.org
39+
40+
Hope to see you there! 🌩️🐦🚀
41+
run: |
42+
gh pr comment "$PR_NUMBER" --repo "$GITHUB_REPOSITORY" --body "$MESSAGE"

‎CODE_OF_CONDUCT.md‎

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# Code of Conduct
2+
3+
It is our intention that our repository remains a useful tool for reporting and commenting on bugs, feature requests, and tasks for the Thunderbird community. No single contributor's work outweighs the importance of civility and professionalism in the Thunderbird community.
4+
5+
In order to keep our repository a useful, inclusive place we have guidelines which, by using this repository, you agree to follow. In addition, your participation on this repository is also subject to the [Mozilla Community Participation Guidelines](https://www.mozilla.org/about/governance/policies/participation/).
6+
7+
Violations of the Code of Conduct or the [Mozilla Community Participation Guidelines](https://www.mozilla.org/about/governance/policies/participation/) are grounds for restrictions or bans on this repository.
8+
9+
## Guidelines
10+
11+
### Commenting
12+
13+
1. **No abusing people**. Constant and intense critique is one of the reasons we build great products. It's harder to fall into group-think if there is always a healthy amount of dissent. We want to encourage vibrant debate inside of the Thunderbird community, we want you to disagree with us, and we want you to effectively argue your case. However, we require that in the process, you criticize things, not people. Examples of things include: interfaces, algorithms, and schedules. Examples of people include: developers, designers, and users. Attacking or encouraging attacks on a person may result in you being banned from this organization.
14+
2. **No obligation**. "Open Source" is not the same as "the developers must do my bidding." Everyone here wants to help, but no one else has any obligation to fix the bugs you want fixed. Therefore, you should not act as if you expect someone to fix a bug by a particular date or release. Aggressive or repeated demands will not be received well and will almost certainly diminish the impact of and interest in your suggestions.
15+
3. **No spam**. Posting comment spam will lead to the ban of your account from our organization.
16+
4. **No pointless comments**. Limit comments on a bug to information which will help with resolving it. Unless requested, additional "I see this too" or "It works for me" comments are unnecessary. Constructive conversations unrelated to the topic of the bug should go in the appropriate discussion forum.
17+
5. **No private email**. Do not send comments on bugs by private email to users; no one else can read them if you do that, and they'll be missed and/or ignored. If an attachment is too big for GitHub, add a comment giving the file size and contents and ask what to do.
18+
19+
### Changing Fields or labels
20+
21+
1. **No changing other people's bugs**. Unless you are the bug assignee, please never change the label fields. If you notice any inconsistencies with the labels, do not change the fields of bugs you do not own and add a comment instead, suggesting the change.
22+
2. **Accept decisions with grace**. If another project contributor has marked a bug as **Closed** or **Not Planned**, then it is not planned. Filing another duplicate of it does not change this. Unless you have further evidence to support reopening a bug, do not post a comment arguing that a bug resolved as **Closed** or **Not Planned** should be reopened.
23+
24+
## Responding to Violations
25+
26+
If you find a user violating the Code of Conduct or the [Mozilla Community Participation Guidelines](https://www.mozilla.org/about/governance/policies/participation/) in comments on bugs, please report the bug to a core develoepr.
27+
28+
To report incidents follow the [How to Report Violations of the Community Participation Guidelines](https://www.mozilla.org/about/governance/policies/participation/reporting/).

0 commit comments

Comments
 (0)