You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The hackathon will take place at the [Orangerie](https://www.designersfactory.com/orangerie/) at [Grellingerstrasse 75, 4052 Basel](https://goo.gl/maps/PY9tarrnA2S2). The nearest international airports are `BSL` and `ZRH`.
22
23
23
24
---
24
25
25
-
The hackathon will take place at the [Orangerie](https://www.designersfactory.com/orangerie/) at [Grellingerstrasse 75, 4052 Basel](https://goo.gl/maps/PY9tarrnA2S2). The nearest international airports are `BSL` and `ZRH`.
We will have two documentathons; during these, each of us will work to improve the documentation on some helix component they did not write themselves:
66
+
### Goals
40
67
41
-
* What is the api of that component
42
-
* Why was it build?
43
-
* What is it good for?
44
-
* What should it not be used for?
45
-
* Are there any caveats to using that module?
68
+
> What are you planning to show at the end of the week?
46
69
47
-
The goal of this event is to improve the documentation, share knowledge of parts of helix and reduce the truck factor in the helix team.
70
+
* Refine our on-call policy (see [here](https://github.com/adobe/project-helix/pull/382) for initial discussion)
71
+
* Discuss and work on next UI iteration with @kamendola
72
+
* Where and how do we document Helix?
73
+
* Improve Developer Experience for devs new to Helix, see [helix-cli/711](https://github.com/adobe/helix-cli/issues/711) (@stefan-guggisberg, @rofe, ...)
74
+
* Integration with project management tools (@bdelacretaz), looking at parallels with similar work that I'm doing for assets management.
75
+
* Discuss cold-start timing issues and expectations (@meryllblanchet@dunguyen@tripodsan@davidnuescheler)
48
76
49
77
#### Breakouts
50
78
@@ -71,12 +99,11 @@ Come up with specific areas for an overall Roadmap (inclusive of helix pages) an
71
99
Roadmaps should be specific, try to include who is most suited to perform the tasks, what needs to be done and how hard the task is.
72
100
Come up with a documented development plan, who does what?
73
101
74
-
75
102
##### Breakout #2: Operations
76
103
77
104
Proposed Time: Wednesday 14h-16h
78
105
79
-
Moderated by ?Rofe & Alex?
106
+
Moderated by Rofe
80
107
81
108
Some ideas for the breakout...
82
109
@@ -97,6 +124,19 @@ Some ideas for the breakout...
97
124
*Goal:*
98
125
Come up with a documented plan, and assign responsibilities to implement a plan.
99
126
127
+
##### Breakout #3: Documentation
128
+
129
+
We plan to have two documentathons; during these, each of us will work to improve the documentation on some helix component they did not write themselves:
130
+
131
+
* What is the api of that component
132
+
* Why was it build?
133
+
* What is it good for?
134
+
* What should it not be used for?
135
+
* Are there any caveats to using that module?
136
+
137
+
*Goal:*
138
+
Improve the documentation, share knowledge of parts of helix and reduce the truck factor in the helix team.
139
+
100
140
101
141
### Lodging
102
142
@@ -110,44 +150,6 @@ Recommended hotels for our out-of-town visitors:
110
150
-[Radisson Blu](https://www.radissonblu.com/en/hotel-basel) modern 4-star hotel in the city center (22 min walk, or 5 min by tram #14 + 7 min walk)
111
151
-[Hotel Euler](https://www.hoteleuler.ch/en/) century-old 4-star hotel at the train station (19 min walk, or 4 min by tram #14 + 8 min walk)
112
152
113
-
### Goal
114
-
115
-
> What are you planning to show at the end of the week?
116
-
117
-
* Refine our on-call policy (see [here](https://github.com/adobe/project-helix/pull/382) for initial discussion)
118
-
* Discuss and work on next UI iteration with @kamendola
119
-
* Where and how do we document Helix?
120
-
* Improve Developer Experience for devs new to Helix, see [helix-cli/711](https://github.com/adobe/helix-cli/issues/711) (@stefan-guggisberg, @rofe, ...)
121
-
* Integration with project management tools (@bdelacretaz), looking at parallels with similar work that I'm doing for assets management.
122
-
* Discuss cold-start timing issues and expectations (@meryllblanchet@dunguyen@tripodsan@davidnuescheler)
0 commit comments