Skip to content

Commit 462e683

Browse files
committed
Merge BPD Events and Sponsored Events pages
1 parent be7c3fb commit 462e683

File tree

107 files changed

+2219
-37
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

107 files changed

+2219
-37
lines changed

.issues/.sync/config.json

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
{
2+
"repository": {
3+
"owner": "BlackPythonDevs",
4+
"repo": "blackpythondevs.github.io"
5+
},
6+
"sync": {
7+
"last_full_pull": "2026-01-09T15:22:57.5743Z"
8+
}
9+
}

.issues/.sync/issue_types.json

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
{
2+
"issue_types": [
3+
{
4+
"id": "IT_kwDOCJKUFs4BNcjg",
5+
"name": "Bug",
6+
"description": "An unexpected problem or behavior"
7+
},
8+
{
9+
"id": "IT_kwDOCJKUFs4BNcji",
10+
"name": "Feature",
11+
"description": "A request, idea, or new functionality"
12+
},
13+
{
14+
"id": "IT_kwDOCJKUFs4BNcje",
15+
"name": "Task",
16+
"description": "A specific piece of work"
17+
}
18+
],
19+
"synced_at": "2026-01-09T15:22:57.5743Z"
20+
}

.issues/.sync/labels.json

Lines changed: 201 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,201 @@
1+
{
2+
"labels": [
3+
{
4+
"name": "a11y",
5+
"color": "C822A6"
6+
},
7+
{
8+
"name": "announcement",
9+
"color": "65EAAD"
10+
},
11+
{
12+
"name": "automated issue",
13+
"color": "F244E0"
14+
},
15+
{
16+
"name": "automated pr",
17+
"color": "ededed"
18+
},
19+
{
20+
"name": "backlog",
21+
"color": "A9DD9A"
22+
},
23+
{
24+
"name": "blog post",
25+
"color": "9E889B"
26+
},
27+
{
28+
"name": "bug",
29+
"color": "d73a4a"
30+
},
31+
{
32+
"name": "conference",
33+
"color": "D87148"
34+
},
35+
{
36+
"name": "conference_accepted",
37+
"color": "71846D"
38+
},
39+
{
40+
"name": "conference_approved",
41+
"color": "7FA733"
42+
},
43+
{
44+
"name": "content",
45+
"color": "ACC446"
46+
},
47+
{
48+
"name": "css",
49+
"color": "2794D2"
50+
},
51+
{
52+
"name": "data",
53+
"color": "E1961B"
54+
},
55+
{
56+
"name": "dependencies",
57+
"color": "052215"
58+
},
59+
{
60+
"name": "design",
61+
"color": "5853F8"
62+
},
63+
{
64+
"name": "design_change",
65+
"color": "12BFBB"
66+
},
67+
{
68+
"name": "devcontainer",
69+
"color": "1CB5A8"
70+
},
71+
{
72+
"name": "documentation",
73+
"color": "0075ca"
74+
},
75+
{
76+
"name": "duplicate",
77+
"color": "cfd3d7"
78+
},
79+
{
80+
"name": "enhancement",
81+
"color": "a2eeef"
82+
},
83+
{
84+
"name": "epic",
85+
"color": "b60205"
86+
},
87+
{
88+
"name": "events",
89+
"color": "134F9E"
90+
},
91+
{
92+
"name": "github actions",
93+
"color": "2D9AED"
94+
},
95+
{
96+
"name": "good first issue",
97+
"color": "7057ff"
98+
},
99+
{
100+
"name": "hacktoberfest-accepted",
101+
"color": "AB296E"
102+
},
103+
{
104+
"name": "help wanted",
105+
"color": "008672"
106+
},
107+
{
108+
"name": "high priority",
109+
"color": "B60205"
110+
},
111+
{
112+
"name": "hold",
113+
"color": "834137"
114+
},
115+
{
116+
"name": "i18n",
117+
"color": "1FEC6C"
118+
},
119+
{
120+
"name": "idea",
121+
"color": "15B86C"
122+
},
123+
{
124+
"name": "infrastructure",
125+
"color": "4E0B08"
126+
},
127+
{
128+
"name": "invalid",
129+
"color": "e4e669"
130+
},
131+
{
132+
"name": "javascript",
133+
"color": "74E221"
134+
},
135+
{
136+
"name": "leadership summit",
137+
"color": "8E8FB7"
138+
},
139+
{
140+
"name": "more-thought",
141+
"color": "4FCFC6"
142+
},
143+
{
144+
"name": "partnerships",
145+
"color": "93B826"
146+
},
147+
{
148+
"name": "performance",
149+
"color": "2684FF"
150+
},
151+
{
152+
"name": "playwright",
153+
"color": "193BE3"
154+
},
155+
{
156+
"name": "python",
157+
"color": "7B6C1B"
158+
},
159+
{
160+
"name": "question",
161+
"color": "d876e3"
162+
},
163+
{
164+
"name": "report",
165+
"color": "ededed"
166+
},
167+
{
168+
"name": "responsiveness",
169+
"color": "772001"
170+
},
171+
{
172+
"name": "ruby",
173+
"color": "EDFB22"
174+
},
175+
{
176+
"name": "security",
177+
"color": "0D6780"
178+
},
179+
{
180+
"name": "swahili",
181+
"color": "E56133"
182+
},
183+
{
184+
"name": "testing",
185+
"color": "77D2FA"
186+
},
187+
{
188+
"name": "translation",
189+
"color": "9ADB5C"
190+
},
191+
{
192+
"name": "typo",
193+
"color": "aaaaaa"
194+
},
195+
{
196+
"name": "wontfix",
197+
"color": "ffffff"
198+
}
199+
],
200+
"synced_at": "2026-01-09T15:22:57.5743Z"
201+
}

.issues/.sync/milestones.json

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
{
2+
"milestones": [
3+
{
4+
"title": "PyCon Sprints 2025",
5+
"due_on": "2025-05-20T00:00:00Z",
6+
"state": "open"
7+
}
8+
],
9+
"synced_at": "2026-01-09T15:22:57.5743Z"
10+
}

.issues/.sync/originals/10.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
---
2+
title: Create a membership map
3+
labels:
4+
- enhancement
5+
- hacktoberfest-accepted
6+
state: open
7+
state_reason: null
8+
synced_at: 2026-01-07T18:48:39.087581Z
9+
info:
10+
author: kjaymiller
11+
created_at: 2023-10-03T14:54:13Z
12+
updated_at: 2024-10-10T18:22:07Z
13+
---
14+
15+
I'm not sure the easiest way to do this but I think we can figure it out together.
16+
17+
I've seen plenty of communities that have maps that highlight where their members are. While I don't think we need to be hyper specific I think a file that has a counter showing what countries people are from could be interesting. It would be nice to tie this into registration but I think that would be over-compilcating things a bit.
18+
19+
Perhaps we can start with some form (Google forms/Microsoft Forms) and then use that data to create a heatmap
20+
21+
I've done this with Elasticsearch, Google Maps, and with Azure Maps, we could also use a more open mapping tool.

.issues/.sync/originals/112.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
---
2+
title: "Add website translation for Hausa "
3+
labels:
4+
- translation
5+
assignees:
6+
- bhantsi
7+
projects:
8+
- Black Python Devs Planning
9+
state: open
10+
state_reason: null
11+
synced_at: 2026-01-07T18:48:39.088267Z
12+
info:
13+
author: bhantsi
14+
created_at: 2023-10-29T10:58:07Z
15+
updated_at: 2024-03-08T13:54:09Z
16+
---

.issues/.sync/originals/281.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
---
2+
title: "\U0001F4A1[IDEA] - Use Playwright to Create a screenshot of the built page changes"
3+
labels:
4+
- backlog
5+
- idea
6+
- playwright
7+
- testing
8+
state: open
9+
state_reason: null
10+
synced_at: 2026-01-07T18:48:39.088472Z
11+
info:
12+
author: kjaymiller
13+
created_at: 2024-03-18T14:56:04Z
14+
updated_at: 2024-10-05T23:38:40Z
15+
---
16+
17+
This would be really cool and something we could definitely talk about at events.
18+
19+
When a change is made I would love to see an attachment that includes a zip of the playwright recording with a quick review of pages to test. This could be modified by GitHub tags (index that looks for tags and runs tests and review based on what is included)

.issues/.sync/originals/344.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
---
2+
title: Add a section on the Conferences page to consider being sponsored and having your conference added to the Black Python Devs Website
3+
labels:
4+
- content
5+
projects:
6+
- Black Python Devs Planning
7+
state: open
8+
state_reason: null
9+
synced_at: 2026-01-07T18:48:39.088705Z
10+
info:
11+
author: kjaymiller
12+
created_at: 2024-06-29T19:52:47Z
13+
updated_at: 2024-06-29T19:53:08Z
14+
---
15+
16+
Currently, we don't have a user friendly way to talk about sponsoring us. Here are some things that I would like to consider adding to our website in the conferences sections.
17+
18+
BELOW THE LIST of conferences
19+
20+
- [ ] A link to our prospectus (in development)
21+
- [ ] A quick outline of the types of sponsorships we offer.
22+
- [ ] Community Sponsor (Tickets for Local Black Python Developers)
23+
- [ ] Commitment Sponsor (Multi-year commitment to increase engagement of Black Python Developers in the local community)

.issues/.sync/originals/386.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
title: "[QUESTION] Can the conferences link be closed once conference item has been created"
3+
labels:
4+
- help wanted
5+
assignees:
6+
- kjaymiller
7+
projects:
8+
- Black Python Devs Planning
9+
state: open
10+
state_reason: null
11+
synced_at: 2026-01-07T18:48:39.088921Z
12+
info:
13+
author: kjaymiller
14+
created_at: 2024-08-23T18:09:43Z
15+
updated_at: 2024-10-04T17:57:33Z
16+
---
17+
18+
We have conferences that are open issues and have been for months. Is the code that is responsible for reading the yaml only looking for open issues?
19+
20+
If so it would be nice to modify this to look for all issues (Perhaps filter by tags like `conference` `-proccessed`)

.issues/.sync/originals/401.md

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
---
2+
title: Make local development significantly easier
3+
labels:
4+
- help wanted
5+
projects:
6+
- Black Python Devs Planning
7+
state: open
8+
state_reason: null
9+
synced_at: 2026-01-07T18:48:39.089122Z
10+
info:
11+
author: kjaymiller
12+
created_at: 2024-08-29T13:15:57Z
13+
updated_at: 2024-12-31T14:24:07Z
14+
---
15+
16+
I'm not sure why but I am completely unable to run this project outside of a devcontainer or codespace.
17+
18+
I'm not sure if it's issues with my local Ruby setup or not.
19+
20+
I'm open to different suggestions on this but the more we force folks to use codespaces then we limit their contribution based on what they are willing to pay for.
21+
22+
### Suggestions
23+
24+
#### Diagram
25+
26+
We need a diagram of the infrastructure to better understand the different tools that we're using.
27+
28+
- [x] #402
29+
30+
#### Dockerfile
31+
32+
Beauty of a dockerfile is that it can be the source for the codespace (we don't have access to the existing codespace dockerfile so we'd likely need to start over. It also means that we can implement this across operating systems as well.
33+
34+
#### Make or Invoke
35+
36+
I don't have a preference on this but we should make it simple to `setup`, `test`, `lint` and `run` services regardless of the language.
37+
38+
I would probably be more comfortable with invoke since it's python code but if someone knows enough about make to make it easy to follow I wouldn't mind.

0 commit comments

Comments
 (0)