As always I don't know if I'm writing in the correct place. But anyway. I found by chance an interview to @mattdm talking about the relation between CentOS Stream and Fedora on zdnet (it was not the first time I read an article about Fedora just by chance) and I had an idea. What about a press review? (Actually I don't know if it is the correct wording in English). A place (a web page? a newsletter?) where we collect (and most importantly, publicize) valuable articles talking about Fedora all around the web. Obviously it should be a collective and distributed effort between community members, and not a one person in charge.
like fedora planet but with notices from nonaffiliated sites?
I like the idea :)
How about Monthly Fedora Community Newsletter ?
Exactly. People can suggest articles (via a pagure ticket?) that after a fast review (I don't think that it is useful to link everything, trolling and cospiracy included) can be placed in a web page or as said by @nasirhm we could create a newsletter. The downside of the newsletter is that people should subscribe to it, while a web page could be more open. Mmm, maybe a monthly "Fedora in the press" post in the community blog could also work?
@nasirhm My idea: using pagure to handle a json file (or the like). Submit issues (proposals, mentions, corrections) and PR to the json file. Then write a (Python) script (good work for newcomers) that get such json and build a web page (and RSS feed). This is a POC. https://pagure.io/fedorapressreview <- the pagure repository with the json file and the Python script. https://gitlab.com/alciregi/fedorapressreview/ <- using a gitlab pipeline [1], the script is downloaded and invoked together with the json file, and a gitlab page is generated (no RSS at the moment): https://alciregi.gitlab.io/fedorapressreview/
Then we could include the RSS in the fedora planet.
[1] https://gitlab.com/alciregi/fedorapressreview/-/blob/master/.gitlab-ci.yml
If we could use a space in the Fedora infrastructure instead of gitlab it could be better (does pagure has pipelines/CI/CD?)
@nasirhm My idea: using pagure to handle a json file (or the like). Submit issues (proposals, mentions, corrections) and PR to the json file.
Sounds Awesome.
So, Will it be like the following (Please excuse my drawing skills):
<img alt="pagure-fedora-press-review.png" src="/fedora-commops/issue/raw/files/26efeef8c4cdd3313a880fba48cf6a3f8ffac077553476f9b480550a938b7ccf-pagure-fedora-press-review.png" />
here's some information about Pagure CI: https://docs.pagure.org/pagure/usage/pagure_ci_jenkins.html
Something like Jenkins can be integrated with Pagure for the task.
I wonder how will we make sure that the article added in the repo is good and abides by out Code Of Conduct ?
Mmm. Not really. My idea is. The json file containing the links to the articles and other info (source, date, description) is maintained on pagure. An article should be proposed via a ticket on pagure or directly via a PR to the json file. The article has to be reviewed and the PR reviewed as well and accepted. Obviously the articles/links have to be of interest to the community, following the CoC, of valuable content.
Then. The Python script (running on gitlab/whatever or on Fedora infra) periodically (cron style or triggered by an event) pick such json file and create a static page and an rss feed.
What about just collecting these up for a regular Magazine article?
It could be an idea. Btw, having something to code could be more compelling for newcomers. :-) In any case we still need a place where to collect the content, and someone that evaluate and approve the proposed links.
The problem with coding something is then it needs to live somewhere, and be maintained. So I'm biased towards using tools we already have. Not to rain on your idea, though — I think the concept is great.
Fedora Marketing used to collect media coverage and share it around. I think this is a good task for CommOps, or for a reinvigorated Marketing, or both. I guess my suggestion would be to decide on a cadence, and then use a pagure ticket or taiga board to collect and review links for each period.
Yes, maintenance :-/ Let's wait some additional input and thoughts.
On May 16th, 2024, this repository was migrated from Pagure to GitLab, including all closed and open issues. This Pagure repository is being retired and set to read-only. We are committed to reviewing tickets on GitLab that are still open to determine whether or not they should be moved to the team's active planning repository.
If you want this issue to be followed up in 2024, please comment on the corresponding GitLab issue and let us know you are still interested in seeing it completed or implemented.
See the repository below for the imported issues:
https://gitlab.com/fedora/commops/archive/
This specific issue can be found below:
https://gitlab.com/fedora/commops/archive/-/issues/224
Metadata Update from @jflory7: - Issue close_status updated to: moved - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.