Pitch Summary: This article builds on my previous Fedora Magazine piece, “Writing Docs with Kate”, and explores how Kate’s advanced editing features can support quality assurance (QA) for lightweight data pipelines.
Instead of tackling full-scale orchestration or IaC (infrastructure as Code) tooling, I focus on how analysts and engineers can design, validate, and document data workflows—such as ETL (Extract, transform, and load) scripts or cron-based pipelines—using Kate as a practical, Fedora-native editor.
Key highlights include:
This follow-up continues the theme of “developer writing for real-world execution,” focusing on how Kate supports both clarity and correctness in technical documentation and code-driven processes.
The article will walk through a real-world example of building and validating a data pipeline using open-source tools on Fedora, showing how Kate helps improve documentation quality, testability, and repeatability.
@rlengland Thanks again, Richard — both for the idea you shared in the Docs Matrix room the other day, and for accepting my pitch so promptly. I'm currently engaged in another project, so I expect to work on a well-polished draft sometime after September 2025.
I would like to inform you in advance that the draft will be delayed longer than expected. I have a lot of work to do due to data-related testing and my portfolio work.
Data preprocessing using R Studio and the numerous R packages involved are complex, and I anticipate making progress on this toward the end of the year. Since I am continuously engaged in data-related work, I will ensure the article has depth. Rather than rushing to publish basic content in Fedora Magazine, I will take the time to conduct my own tests and create original content that cannot be found elsewhere, hoping that the effort will be worthwhile.
Thanks Hank. I'm sure the Fedora Magazine readers will appreciate your dedication.
Due to the need to establish a data analysis-optimized workflow for this project, I've decided to change the primary development tool from the initially planned general text editor (Kate) to RStudio. This adjustment will be reflected in the final article.
By shifting to RStudio, I aim to focus less on environment configuration and more on efficient data transformation and accurate model building, ultimately improving the quality and clarity of the project presented in the magazine.
The new title would be 'R-Powered ETL on Fedora: A Complete Open Source Data Analysis Pipeline'.
Thank you for the update. We are looking forward to your contribution.
For future reference, apropos the title change to ‘R-Powered ETL on Fedora: A Complete Open Source Data Analysis Pipeline’, here is a updated description:
A first draft is ready for your review. The new title that reflects the latest test and data source and optimized for SEO.
Creating Data Analysis Pipelines using DuckDB and RStudio
https://fedoramagazine.org/?p=42781&preview=1&_ppp=bee5ddef05
Metadata Update from @hankuoffroad: - Custom field preview-link adjusted to https://fedoramagazine.org/?p=42781&preview=1&_ppp=bee5ddef05
@hankuoffroad I will start the review of the article soon but noticed that the featured image is 816 × 612 pixels and we need it to be 1890 x 800. If you want to scale and trim it great otherwise I will see what I can do. Thanks.
Cropped and scaled image attached
Overlay text: Data Analysis Pipelines using DuckDB and RStudio
Metadata Update from @rlengland: - Custom field preview-link adjusted to https://fedoramagazine.org/?p=42781&preview=1 (was: https://fedoramagazine.org/?p=42781&preview=1&_ppp=bee5ddef05)
Installation instructions for RStudio Desktop/a last review are done December 8. No intermittent changes made from 09:00 UTC Dec 8. The article is now ready for editorial review. The draft was reviewed with the Data Working Group.
Metadata Update from @rlengland: - Custom field image-editor adjusted to rlengland - Issue untagged with: needs-image
I was wondering if there is a target publication date. I personally think the week of December 15th would be ideal to catch readers before the year-end break. Does that work for the editorial team?
Metadata Update from @hankuoffroad: - Custom field publish adjusted to 2025-12-15
@hankuoffroad this article is next on my to-do list and that week is my aim.
Metadata Update from @rlengland: - Custom field editor adjusted to rlengland - Custom field image-editor adjusted to hankuoffroad (was: rlengland)
@hankuoffroad I've completed editing. The magazine standard is to use "preformatted" text rather than "Inline code" so I modified those, linked the images to the image in WP so when selected the open in a new page. and did the same for the other links. Text editing was done for sentence length and passive voice. I also slightly modified your first paragraph so it might draw potential reader in.
I think it would be good for you to do a final review before I commit the schedule for 15 Dec. If I don't hear back from you by 14 Dec. I will proceed with the schedule.
Thanks for you hard work.
@rlengland I forgot the formatting in WP. Thanks for your help with it and text editing. I was so stuck on the technical part, and as a result, sentence length was out of control. Looks good. It is good to go. Many thanks.
@hankuoffroad I, too, suffer from not only long sentences, but periodic ones as well. My poor wife has often had to correct me. :-) Scheduled for 15 Dec. Thanks for you hard work.