-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Create docs directory so we can show it on packit.dev
And move the weekly-roles content there so we can add more generic content to this repository. Signed-off-by: Frantisek Lachman <[email protected]>
- Loading branch information
1 parent
f623b6b
commit 4f4679a
Showing
3 changed files
with
22 additions
and
19 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,20 +1,3 @@ | ||
# Weekly roles of the Packit team | ||
# Packit Agile Repository | ||
|
||
![Sharing responsibility in a team](./title.png) | ||
|
||
This repository handles the weekly rotating roles of the Packit team. | ||
Rotating roles represent work that needs to be done each week (e.g. releasing, | ||
monitoring, communicating with the users). They are described in [issues using the `roles` label](https://github.com/packit/weekly-roles/issues?q=is%3Aissue+is%3Aopen+label%3Aroles). | ||
These issues are automatically cloned every Friday and team members are assigned to them. | ||
|
||
The repository contains: | ||
|
||
1. `clone_roles.py` - script that does the cloning of the issues, assigning of the team members | ||
and closing the old ones | ||
2. `.github/workflows/rotate_roles.yaml` - Github action that runs the script periodically (each Friday) | ||
|
||
You can read more about the process in the following blog post series: | ||
|
||
- [How to run an open-source service?](https://medium.com/@laura.barcziova/how-to-run-an-open-source-service-fb3303240e69) | ||
- [Inception of rotating roles](https://medium.com/@laura.barcziova/inception-of-rotating-roles-9caf971b3096) | ||
- [Share team responsibilities efficiently](https://medium.com/@laura.barcziova/share-team-responsibilities-efficiently-9a202aad7bd0) | ||
This repository contains all the information and tooling for the agile practices of the Packit team. |
File renamed without changes
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
# Weekly roles of the Packit team | ||
|
||
![Sharing responsibility in a team](./img/title.png) | ||
|
||
This repository handles the weekly rotating roles of the Packit team. | ||
Rotating roles represent work that needs to be done each week (e.g. releasing, | ||
monitoring, communicating with the users). They are described in [issues using the `roles` label](https://github.com/packit/agile/issues?q=is%3Aissue+is%3Aopen+label%3Aroles). | ||
These issues are automatically cloned every Friday and team members are assigned to them. | ||
|
||
The repository contains: | ||
|
||
1. `clone_roles.py` - script that does the cloning of the issues, assigning of the team members | ||
and closing the old ones | ||
2. `.github/workflows/rotate_roles.yaml` - Github action that runs the script periodically (each Friday) | ||
|
||
You can read more about the process in the following blog post series: | ||
|
||
- [How to run an open-source service?](https://medium.com/@laura.barcziova/how-to-run-an-open-source-service-fb3303240e69) | ||
- [Inception of rotating roles](https://medium.com/@laura.barcziova/inception-of-rotating-roles-9caf971b3096) | ||
- [Share team responsibilities efficiently](https://medium.com/@laura.barcziova/share-team-responsibilities-efficiently-9a202aad7bd0) |