Alex, thank you so much for the effort.

Could I use this thread to clarify a couple of points I read about the Blog
we have there on[1].
Do tell me if this is off-topic, I will create a new thread.

1. Who is responsible? I imagine the task would be to update the site and
ensure blog posts are published.
2. Frequency of blog posts? This needs to be agreed on by us.
3. Topics - What topics we want to have there.
4. Do we want to review the blog posts before publishing?

Here are my 2c for the points:
1.We need to find a volunteer.
2. Imho we need to do blog posts every release + some extra guides (
bi-weekly or monthly ).
3. Topics - release posts, guides
4. I would suggest employing the same approach we have for any code
contribution. Send a PR and have 2 reviews from comitters.

Of course, this should be voted on, but I would like to hear other opinions.

Dominik


[1] https://infra.apache.org/project-blogs



On Mon, 29 Jan 2024 at 21:56, Alex Porcelli <a...@porcelli.me> wrote:

> We have a placeholder website already alive: https://kie.apache.org/ -
> the source code is available here [1]
>
>
> [1] - https://github.com/apache/incubator-kie-website
>
> On Mon, Jan 29, 2024 at 12:23 PM Alex Porcelli <a...@porcelli.me> wrote:
> >
> > For tracking purposes: https://issues.apache.org/jira/browse/INFRA-25438
> >
> > On Sat, Jan 27, 2024 at 8:33 AM Paolo Bizzarri <pibi...@gmail.com>
> wrote:
> > >
> > > Hi Alex,
> > >
> > > that is great!
> > >
> > > Let me know if you need help on completing the website.
> > >
> > > Regards
> > >
> > > Paolo
> > >
> > > On Fri, Jan 26, 2024 at 10:34 PM Alex Porcelli <porce...@apache.org>
> wrote:
> > >
> > > > Quick update, starting working on a KIE website.
> > > >
> > > > I’ll reach out to infra to have the proper config in place.
> > > >
> > > > I forked fury website and started to adjust.
> > > >
> > > > It’s expected to be minimal, but we’ll have the download links :)
> > > >
> > > > Regards,
> > > > Alex
> > > >
> > > >
> > > > On Fri, Jan 26, 2024 at 5:08 AM Christofer Dutz <
> christofer.d...@c-ware.de
> > > > >
> > > > wrote:
> > > >
> > > > > That would be cool.
> > > > >
> > > > > Chris
> > > > >
> > > > >
> > > > > Von: Luca Molteni <lmolt...@redhat.com>
> > > > > Datum: Freitag, 26. Januar 2024 um 09:32
> > > > > An: dev@kie.apache.org <dev@kie.apache.org>
> > > > > Betreff: Re: What's the status of the Project website?
> > > > >
> > > > >
> > > > > > On 25 Jan 2024, at 16:08, Christofer Dutz <
> christofer.d...@c-ware.de>
> > > > > wrote:
> > > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > I would probably ask you to double-check this with Infra.
> > > > > > Cause usually we like to serve our projects websites from our
> infra.
> > > > > > There have been cases, where projects had their websites on WP
> and then
> > > > > the person running the server dropped off the project and
> everything was
> > > > > gone.
> > > > > > So I do think it’s a requirement to have the sources for the
> website
> > > > > under Apache source control.
> > > > > >
> > > > > > There’s currently a discussion on the Incubator General list
> about the
> > > > > exact same thins (The Apache Wayang podling is asking for help
> with their
> > > > > website).
> > > > > > Here one project pointed out having built their website with
> > > > > https://docusaurus.io/
> > > > > > Others at apache use a lot of Django and other pythony stuff …. I
> > > > prefer
> > > > > the Maven Site Plugin.
> > > > >
> > > > > +1 to this, I’m all for having static blogs under version control
> rather
> > > > > than using Wordpress.
> > > > >
> > > > > We could use the original blog.kie.org <http://blog.kie.org/>
> content
> > > > and
> > > > > migrate it to whatever static generator ASF prefers.
> > > > >
> > > > > Luca
> > > > >
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscr...@kie.apache.org
> > > > > For additional commands, e-mail: dev-h...@kie.apache.org
> > > > >
> > > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@kie.apache.org
> For additional commands, e-mail: dev-h...@kie.apache.org
>
>

Reply via email to