#423 Find out how your Fedora system really feels (with the linux-mcp-server!)
Closed: published by rlengland. Opened by duffy.

Article introducing the linux-mcp-server and how to use it to work with your Fedora system with the open source AI tool Goose as well as an open source licensed model (gpt-oss:20b.)

Would love to publish first week of Dec ASAP. Will create draft in wordpress shortly.


Issue tagged with: article

Metadata Update from @rlengland:
- Issue tagged with: needs-series

Metadata Update from @rlengland:
- Issue assigned to rlengland

Metadata Update from @rlengland:
- Issue assigned to duffy (was: rlengland)

@duffy Please let us know when you have the article ready for review/publication by leaving a comment on this ticket to that effect.

We will aim for the first week of December

Metadata Update from @rlengland:
- Issue tagged with: needs-image

@duffy Three questions:
1) Is this article ready for the editors to review?
2) I see it has the "needs-series" flag is set. What article should this one be "teamed" with?
3) Do you have any suggestions about images that might be used for the feature image.

@duffy Can you give us a status/response on the previous questions, please?

Metadata Update from @rlengland:
- Custom field preview-link adjusted to https://fedoramagazine.org/?p=42773&preview=true

Metadata Update from @rlengland:
- Issue untagged with: needs-image, needs-series

@duffy @briansmith I've added a featured image, added a "teaser" paragraph before the introduction that some web pages will pick up from the article, and changed some "code" font stylings to "preformatted" per the magazine standard.

Now would be a good time to review the article to ensure that I haven't, inadvertently, modify anything.

Let us know, via comments on this ticket, that you approve or need modifications made so we can move forward with scheduling publication. Feel free to make any changes/additions necessary.

Thank you.

@duffy @briansmith
:-( I just discovered an image in the media for the WP Magazine instance
https://fedoramagazine.org/wp-admin/upload.php?item=42814
that appears to be for this article. I will gladly use it but it is not the proper aspect ratio to fit the magazine requirements. We conform to 1890x800 pixels and that image is 1008x427 pixels.

Is there a chance that it can be resized?

@duffy @briansmith
Never mind I've taken care of it.

:-( I just discovered an image in the media for the WP Magazine instance
https://fedoramagazine.org/wp-admin/upload.php?item=42814
that appears to be for this article. I will gladly use it but it is not the proper aspect ratio to fit the magazine requirements. We conform to 1890x800 pixels and that image is 1008x427 pixels.

Is there a chance that it can be resized?

@duffy @briansmith
Still hoping that one of you can provide a final review and "all-clear" so we can schedule your article.

@rlengland I just did a thorough review and it's looking good and Brian is on board as well. I modified the opening summary you wrote (thank you!) to make it slightly more Fedora-focused :) This should be ready for publishing now.

@rlengland Oh I forgot a couple things:

  • thanks for fixing the image! I created it based on the SVG template in the git repo for fedora magazine images. I have the SVG but didn't check it into the repo. Is that repo still current and would you like the SVG committed? https://pagure.io/fedoramagazine-images
  • we don't need a series for this, im not sure how that needs-series flag got triggered - apologies for confusion on that!

@duffy Thank you very much for the review. I'll schedule this for 10 Dec.
If you have time to check the image into that repo that would great!

Thanks for the effort you and Brian put into the article.

Metadata Update from @rlengland:
- Custom field editor adjusted to rlengland
- Custom field image-editor adjusted to duffy
- Custom field publish adjusted to 2025-12-10

Metadata Update from @rlengland:
- Custom field editor adjusted to @rlengland (was: rlengland)
- Custom field image-editor adjusted to @duffy (was: duffy)

Issue status updated to: Closed (was: Open)
Issue close_status updated to: published

Metadata