mirror of
https://github.com/mfocko/blog.git
synced 2024-11-22 13:03:47 +01:00
Fix formatting of talks and add QEcamp23 (#9)
This commit is contained in:
commit
b8ae08bb37
1 changed files with 86 additions and 47 deletions
|
@ -4,58 +4,97 @@ import Layout from "@theme/Layout";
|
||||||
import Talk, { TalkMetadata } from "../components/talks/Talk";
|
import Talk, { TalkMetadata } from "../components/talks/Talk";
|
||||||
|
|
||||||
const talks: TalkMetadata[] = [
|
const talks: TalkMetadata[] = [
|
||||||
{
|
{
|
||||||
title: "Packit: RPM integration, all in one",
|
title: "Shift Left Testing with Packit and Testing Farm",
|
||||||
description: (
|
description: (
|
||||||
<>
|
<>
|
||||||
Do you want to automate how you build and test your RPM packages?
|
<p>
|
||||||
Do you maintain any package in Fedora and want to automate the
|
In today's fast-paced software development landscape, ensuring the
|
||||||
releases? Or are you just interested in CI/CD on GitHub or GitLab,
|
quality and reliability of upstream contributions is crucial. The
|
||||||
Fedora and integration of upstream projects with RPM-based Linux
|
traditional approach of testing at the end of the development cycle is
|
||||||
distributions? In this session, we are going to deep-dive into
|
no longer sufficient. To address this challenge, we present "Shift
|
||||||
features of Packit that can help you do your day-to-day job.
|
Left Your Testing with Packit and Testing Farm", a talk that
|
||||||
</>
|
introduces two powerful tools designed to simplify and enhance the
|
||||||
),
|
testing process for the upstream contributions.
|
||||||
events: [
|
</p>
|
||||||
{
|
|
||||||
name: "DevConf.cz",
|
<p>
|
||||||
location: "Brno, Czechia",
|
Packit and Testing Farm provide a dead simple way to build and test
|
||||||
date: new Date(2023, 5, 17),
|
your upstream contributions against both public or internal Red Hat
|
||||||
},
|
testing infrastructure. In this talk, we will explore the capabilities
|
||||||
{
|
of both tools and demonstrate how they can be seamlessly integrated
|
||||||
name: "DevConf.cz Mini",
|
into your development workflow.
|
||||||
location: "Brno, Czechia",
|
</p>
|
||||||
date: new Date(2023, 2, 31),
|
|
||||||
},
|
<p>
|
||||||
],
|
In addition to the current capabilities, we will share our plans for
|
||||||
recordingURL: "https://www.youtube.com/watch?v=FxhXzgxWO18",
|
Packit and Testing.
|
||||||
slidesURL: "https://static.sched.com/hosted_files/devconfcz2023/37/DevConf.cz%20June%202023%20Packit%20talk-1.pdf",
|
</p>
|
||||||
},
|
</>
|
||||||
|
),
|
||||||
|
events: [
|
||||||
|
{
|
||||||
|
name: "QEcamp23",
|
||||||
|
location: "virtual",
|
||||||
|
date: new Date(2023, 10, 19),
|
||||||
|
},
|
||||||
|
],
|
||||||
|
},
|
||||||
|
{
|
||||||
|
title: "Packit: RPM integration, all in one",
|
||||||
|
description: (
|
||||||
|
<>
|
||||||
|
Do you want to automate how you build and test your RPM packages? Do you
|
||||||
|
maintain any package in Fedora and want to automate the releases? Or are
|
||||||
|
you just interested in CI/CD on GitHub or GitLab, Fedora and integration
|
||||||
|
of upstream projects with RPM-based Linux distributions? In this
|
||||||
|
session, we are going to deep-dive into features of Packit that can help
|
||||||
|
you do your day-to-day job.
|
||||||
|
</>
|
||||||
|
),
|
||||||
|
events: [
|
||||||
|
{
|
||||||
|
name: "DevConf.cz",
|
||||||
|
location: "Brno, Czechia",
|
||||||
|
date: new Date(2023, 5, 17),
|
||||||
|
},
|
||||||
|
{
|
||||||
|
name: "DevConf.cz Mini",
|
||||||
|
location: "Brno, Czechia",
|
||||||
|
date: new Date(2023, 2, 31),
|
||||||
|
},
|
||||||
|
],
|
||||||
|
recordingURL: "https://www.youtube.com/watch?v=FxhXzgxWO18",
|
||||||
|
slidesURL:
|
||||||
|
"https://static.sched.com/hosted_files/devconfcz2023/37/DevConf.cz%20June%202023%20Packit%20talk-1.pdf",
|
||||||
|
},
|
||||||
];
|
];
|
||||||
|
|
||||||
const title = "Talks";
|
const title = "Talks";
|
||||||
const description = "Featured talks I presented on various events.";
|
const description = "Featured talks I presented on various events.";
|
||||||
|
|
||||||
export default function Talks(): JSX.Element {
|
export default function Talks(): JSX.Element {
|
||||||
return (
|
return (
|
||||||
<Layout title={title} description={description}>
|
<Layout title={title} description={description}>
|
||||||
<main className="container container--fluid margin-vert--lg">
|
<main className="container container--fluid margin-vert--lg">
|
||||||
<h1>{title}</h1>
|
<h1>{title}</h1>
|
||||||
<p>{description}</p>
|
<p>{description}</p>
|
||||||
|
|
||||||
<div className="row">
|
<div className="row">
|
||||||
{talks.map((talkData) => (
|
{talks.map((talkData) => (
|
||||||
<Talk key={talkData.title} {...talkData} />
|
<Talk key={talkData.title} {...talkData} />
|
||||||
))}
|
))}
|
||||||
</div>
|
</div>
|
||||||
|
|
||||||
<hr/>
|
<hr />
|
||||||
<p>
|
<p>
|
||||||
Credits to <a href="https://kosiec.dev/" target="_blank">
|
Credits to{" "}
|
||||||
Paweł Kosiec</a> for implementing his own React components
|
<a href="https://kosiec.dev/" target="_blank">
|
||||||
for talks.
|
Paweł Kosiec
|
||||||
</p>
|
</a>{" "}
|
||||||
</main>
|
for implementing his own React components for talks.
|
||||||
</Layout>
|
</p>
|
||||||
);
|
</main>
|
||||||
|
</Layout>
|
||||||
|
);
|
||||||
}
|
}
|
Loading…
Reference in a new issue