or
or
By clicking below, you agree to our terms of service.
New to HackMD? Sign up
Syntax | Example | Reference | |
---|---|---|---|
# Header | Header | 基本排版 | |
- Unordered List |
|
||
1. Ordered List |
|
||
- [ ] Todo List |
|
||
> Blockquote | Blockquote |
||
**Bold font** | Bold font | ||
*Italics font* | Italics font | ||
~~Strikethrough~~ | |||
19^th^ | 19th | ||
H~2~O | H2O | ||
++Inserted text++ | Inserted text | ||
==Marked text== | Marked text | ||
[link text](https:// "title") | Link | ||
 | Image | ||
`Code` | Code |
在筆記中貼入程式碼 | |
```javascript var i = 0; ``` |
|
||
:smile: | ![]() |
Emoji list | |
{%youtube youtube_id %} | Externals | ||
$L^aT_eX$ | LaTeX | ||
:::info This is a alert area. ::: |
This is a alert area. |
On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?
Please give us some advice and help us improve HackMD.
Syncing
xxxxxxxxxx
Nest with Fedora 2022 Infrastructure and Releng BARCAMP
schedule
2022-07-06 14UTC to 16:30UTC
14:00 to 14:15UTC - introductions and barcamp voting
14:16 to 15:00UTC - first block of discussions
15:00 to 15:15UTC - break
15:16 to 16:00UTC - second block of discussions
16:01 to 16:30UTC - revisting/roundup/smaller topics
discussion blocks - total 90min available, how shall we divide it. Please place an X where you prefer.
9 10min?
Votes:
6 15min?
Votes: XXX
3 30min?
Votes:
Discussion proposals:
Votes will be made until 14:15UTC. At that point the highest voted will be discussed first, then the next, etc.
Example talk - facilitator name / note taker name
description/more info
Votes: X
Notes:
5 year plans - Kevin Fenzi (nirik) / (mobrien)
I'd like to talk about where people see infrastructure going in the next 5 years? what will change? what can we do to be ready for it? Are there things we should focus on more? Is it all too volitle to tell? How about 3years? a year?
Votes: XXXXXX
Notes:
Questions:
Ideas:
Continuously updated infrastructure - roll to latest every 6 months
How to handle Fedora Infra Tech Debt? (zlopez) / ?
As a Fedora Infra we accumulated plenty of Tech Debt during the years, some is more pressing, some not that much. I will share the current list of Tech debt we have and would like to discuss how should we address this or if you think anything is missing on the list.
Votes: XXXX
Notes: There’s a lot of tech debt. We have a spreadsheet.
https://mobrien.fedorapeople.org/CPE Fedora_CentOS Tech Debt Matrix.ods
Ideas/Comments:
Questions:
How should Fedora Infra approach apps that we don't want to maintain? (zlopez) / ?
Three years ago we decided to get rid of some of the services we owned at that time. The reason for this was to better focus on the services that are critical for Fedora. Everything was explained in the blogpost, but we still have those apps around and community is using them, but there isn't anyone who actually maintains them. How we should approach this?
Votes: XXX
Notes:
Questions:
Onboarding Improvement ideas (nirik) / (mobrien)
What can we do to improve our infra and releng onboarding? How can we be more welcoming? How can we get folks thru the 'a few changes' into a regular contributor? Can we do it without taking up tons of time from folks that are currently really busy?
Votes: XXXXXXXX
Notes:
Current onboarding: onboard during weekly meeting or mailing list. We add them to our fi-apprentice group which allows them read only ssh access to a number of servers which allows them to look around. We have docs which need work. Suggest some easy tickets to new users or a ticket which may be of interest to them. Not clear to jump from apprentice to higher access levels. We generally avoid direct mentoring mostly due to not enough mentors.
We should check on Openshfit metric access and if we can improve metrics and log accessibility
Infra as code is integrated strongly by wide use of Ansible
Provide some method to grant people titles within the community such as a "Fedora DevOps" or similar. Badges may help here
Permissions are hard to get and possibly to strict. Is it possible to grant access quicker? Possibly a more fine grained level.
How can community people help without access. Help with docs, attend meetings and ask questions. Tell us what knowledge you'd like to share
In chat - Maybe "proven packagers" can be approved also as "apprentice" by default?
Questions:
Ways to improve communication (mobrien) / (zlopez)
Should we use mailing lists/ irc / discourse or something else. What are the best ways to communicate changes, discuss ideas or encourage new community engagement?
Votes: XXXX
Notes:
Questions:
Questions and Answers (perhaps) (nirik) / ?
Questions from anyone on any infra topics.
Votes:
notes: