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
short-description: Work needed around moving Quarkus to foundation and streamline open governance.
6
+
readme: |
7
+
<p>from Discussion at https://github.com/quarkusio/quarkus/discussions/43013</p>
8
+
<p>We started the move of Quarkus to a foundation <a href="https://quarkus.io/blog/quarkus-in-a-foundation/">earlier this year</a> and recently <a href="https://quarkus.io/blog/quarkus-moving-to-commonhaus/">set the direction</a> towards <a href="https://www.commonhaus.org/">CommonHaus</a> and during the summer break the CommonHaus council <a href="https://github.com/commonhaus/foundation/pull/183">approved our request</a> to join.</p>
9
+
<p>Thus, now the real work starts, and it's just fitting we set up a working group for the effort getting Quarkus to CommonHaus foundation.</p>
10
+
<h1>Goal</h1>
11
+
<p>Two parts</p>
12
+
<ul>
13
+
<li>setup Quarkus to have transparent and open governance</li>
14
+
<li>Go through the few but important requirements for a CommonHaus project.</li>
15
+
</ul>
16
+
<h1>Initial work items/questions:</h1>
17
+
<p>Current known list, but not limited to:</p>
18
+
<ul>
19
+
<li>identify design communication channels (i.e. #41973)</li>
20
+
<li>which repositories / code will move</li>
21
+
<li>impact (if any) on quarkiverse projects</li>
22
+
<li>how will trademarks work/change</li>
23
+
<li>identify running services and setup/maintain them (registry.quarkus.io, code.quarkus.io etc.)</li>
24
+
<li>add required metadata/files to the various repositories</li>
25
+
</ul>
26
+
<h1>Tracking</h1>
27
+
<p>We will use the working group board to track publicly all the known relevant work and questions.For the few exception cases where, for legal or personal constraints, the work must happen in private, we will post the outcome and results in public places (like a GitHub discussion of a GitHub issue tracked on the working group board).</p>
28
+
<h1>When will this working group be done?</h1>
29
+
<p>When Quarkus has an active working governance model in place and all major work items around setting up Quarkus at CommonHaus are completed - after that, its expected things will just be iteratively improved, and the dedicated working group will not be needed (others might start to continue more specific efforts).</p>
30
+
<p>The majority of the work must be done before the end of December 2024. The latest deadline for CommonHaus is April 2025, when the bootstrap period of CommonHaus ends.</p>
short-description: Allow Static Site Generation with Quarkus.
38
+
readme: |
39
+
<p>New initiative to allow Static Site Generation with Quarkus.</p>
40
+
<p>Quarkus already provides most of the pieces to create great web applications (https://quarkus.io/guides/web).</p>
41
+
<p>I recently added https://github.com/quarkiverse/quarkus-roq. It will allow generating a static website out of any Quarkus application (it starts the app, fetch all the configured pages and assets, generate a static website and stop), it already works but it is still very alpha.</p>
42
+
<p>What's missing? we now need to incrementally add the toolkit to ease the process of creating static content through Quarkus:</p>
43
+
<ul>
44
+
<li>Static Data</li>
45
+
<li>Markdown/Asciidoc and frontmatter</li>
46
+
<li>SEO</li>
47
+
<li>Image processing</li>
48
+
<li>Easy to configure routing</li>
49
+
</ul>
50
+
<p>This will allow to develop the content using Quarkus dev-mode, and then generate for Github Pages or similar when it's ready.</p>
51
+
<p>Bonus, everything added will benefit any "non-static" Quarkus app and any Static Quarkus app could also become non static.</p>
52
+
<p>This effort is now tracked using a "Working Group" project: https://github.com/orgs/quarkiverse/projects/6</p>
53
+
<p>This is a great opportunity to participate in fun effort and be involved with the Quarkus community, if anyone is interested in being a part of this, please reach out to me 🚀</p>
54
+
status: on track
55
+
last-activity: 2024-09-20
56
+
last-update: |
57
+
0.0.3 has been released, it is the MVP version and allowed to publish the Roq blog: https://quarkiverse.io/quarkus-roq/posts/2024-08-29-welcome-to-roq/
58
+
59
+
From now on, we start adding features incrementally, documenting.
short-description: Allow Static Site Generation with Quarkus.
59
-
readme: |
60
-
<p>New initiative to allow Static Site Generation with Quarkus.</p>
61
-
<p>Quarkus already provides most of the pieces to create great web applications (https://quarkus.io/guides/web).</p>
62
-
<p>I recently added https://github.com/quarkiverse/quarkus-roq. It will allow generating a static website out of any Quarkus application (it starts the app, fetch all the configured pages and assets, generate a static website and stop), it already works but it is still very alpha.</p>
63
-
<p>What's missing? we now need to incrementally add the toolkit to ease the process of creating static content through Quarkus:</p>
64
-
<ul>
65
-
<li>Static Data</li>
66
-
<li>Markdown/Asciidoc and frontmatter</li>
67
-
<li>SEO</li>
68
-
<li>Image processing</li>
69
-
<li>Easy to configure routing</li>
70
-
</ul>
71
-
<p>This will allow to develop the content using Quarkus dev-mode, and then generate for Github Pages or similar when it's ready.</p>
72
-
<p>Bonus, everything added will benefit any "non-static" Quarkus app and any Static Quarkus app could also become non static.</p>
73
-
<p>This effort is now tracked using a "Working Group" project: https://github.com/orgs/quarkiverse/projects/6</p>
74
-
<p>This is a great opportunity to participate in fun effort and be involved with the Quarkus community, if anyone is interested in being a part of this, please reach out to me 🚀</p>
75
-
status: on track
76
-
last-activity: 2024-09-12
77
-
last-update: |
78
-
0.0.3 has been released, it is the MVP version and allowed to publish the Roq blog: https://quarkiverse.io/quarkus-roq/posts/2024-08-29-welcome-to-roq/
79
-
80
-
From now on, we start adding features incrementally, documenting.
short-description: Work needed around moving Quarkus to foundation and streamline open governance.
105
-
readme: |
106
-
<p>from Discussion at https://github.com/quarkusio/quarkus/discussions/43013</p>
107
-
<p>We started the move of Quarkus to a foundation <a href="https://quarkus.io/blog/quarkus-in-a-foundation/">earlier this year</a> and recently <a href="https://quarkus.io/blog/quarkus-moving-to-commonhaus/">set the direction</a> towards <a href="https://www.commonhaus.org/">CommonHaus</a> and during the summer break the CommonHaus council <a href="https://github.com/commonhaus/foundation/pull/183">approved our request</a> to join.</p>
108
-
<p>Thus, now the real work starts, and it's just fitting we set up a working group for the effort getting Quarkus to CommonHaus foundation.</p>
109
-
<h1>Goal</h1>
110
-
<p>Two parts</p>
111
-
<ul>
112
-
<li>setup Quarkus to have transparent and open governance</li>
113
-
<li>Go through the few but important requirements for a CommonHaus project.</li>
114
-
</ul>
115
-
<h1>Initial work items/questions:</h1>
116
-
<p>Current known list, but not limited to:</p>
117
-
<ul>
118
-
<li>identify design communication channels (i.e. #41973)</li>
119
-
<li>which repositories / code will move</li>
120
-
<li>impact (if any) on quarkiverse projects</li>
121
-
<li>how will trademarks work/change</li>
122
-
<li>identify running services and setup/maintain them (registry.quarkus.io, code.quarkus.io etc.)</li>
123
-
<li>add required metadata/files to the various repositories</li>
124
-
</ul>
125
-
<h1>Tracking</h1>
126
-
<p>We will use the working group board to track publicly all the known relevant work and questions.For the few exception cases where, for legal or personal constraints, the work must happen in private, we will post the outcome and results in public places (like a GitHub discussion of a GitHub issue tracked on the working group board).</p>
127
-
<h1>When will this working group be done?</h1>
128
-
<p>When Quarkus has an active working governance model in place and all major work items around setting up Quarkus at CommonHaus are completed - after that, its expected things will just be iteratively improved, and the dedicated working group will not be needed (others might start to continue more specific efforts).</p>
129
-
<p>The majority of the work must be done before the end of December 2024. The latest deadline for CommonHaus is April 2025, when the bootstrap period of CommonHaus ends.</p>
0 commit comments