Hey folks. I thought I would open a discussion about fedoraplanet and possibly some plans for it.
Right now:
fedoraplanet.org runs on people02.fedoraproject.org (aka fedorapeople). To add a blog/rss feed you have to login there and edit your .planet file, then scripting pulls all those .planet files and tries to fetch all the feeds and then serves them up at http://fedoraplanet.org. It uses a app called 'venus' to do this. venus is written in very old python2 and very very dead upstream.
We run into the following problems with it:
* Sometimes it gets stuck and just stops processing until it's killed. * It's serving on a http site, which causes people to ask us to make it https, but that would just change the errors because many feeds it pulls are still http since they were added back before letsencrypt existed. * We have a handy 'website' field in our new account system, but aren't using it at all. * The .planet parsing is poor, any number of things can cause it to break.
We have two open tickets on it: - https://pagure.io/fedora-infrastructure/issue/10383 (upgrade to pluto, a ruby based, but maintained thing) - https://pagure.io/fedora-infrastructure/issue/10490 ( planet not served via ssl) Which I am just going to close now.
So, I can think of a number of options and would love everyone who has thoughts on it to chime in:
1. Do nothing. Venus "works" and .planet files are cool and retro.
2. Switch to pluto and use account system 'website' fields of contributors. We could likely shove it in openshift and serve it directly from there to avoid fedorapeople entirely. (This would likely break anyone who has multiple feeds in there)
3. Switch to something better/bigger. I would think (although I don't know) that there might be something that would not only aggregate rss feeds for contributors, but perhaps mastodon/twitter/whatever also.
4. Planets are old and tired, just drop the entire thing. People can maintain their own rss lists.
5. Planets are old and tired, just drop the entire thing. But also, get our social media people to maintain contributor / interesting lists. ie, the fedoraproject twitter account could maintain a list of 'fedora contributors' and 'fedora packagers' or whatever.
6. Switch to pluto as in 2, but also setup some curators. Have a 'firehose' of all feeds, but the main fedora planet would be just curated things that are known to be related to fedora and not off topic or unrelated.
6. Get someones (not it!) to take in all the twitter/facebook/mastodon/blog posts/rss feeds and post some kind of curated round up every week or something.
7. Your brilliant idea here!
So, thoughts? this is not at all urgent, but we should end up doing something with it sometime. :)
kevin
On Wed, Mar 2, 2022 at 7:29 AM Kevin Fenzi kevin@scrye.com wrote:
Hey folks. I thought I would open a discussion about fedoraplanet and possibly some plans for it.
Right now:
fedoraplanet.org runs on people02.fedoraproject.org (aka fedorapeople). To add a blog/rss feed you have to login there and edit your .planet file, then scripting pulls all those .planet files and tries to fetch all the feeds and then serves them up at http://fedoraplanet.org. It uses a app called 'venus' to do this. venus is written in very old python2 and very very dead upstream.
We run into the following problems with it:
- Sometimes it gets stuck and just stops processing until it's killed.
- It's serving on a http site, which causes people to ask us to make it
https, but that would just change the errors because many feeds it pulls are still http since they were added back before letsencrypt existed.
- We have a handy 'website' field in our new account system, but aren't
using it at all.
- The .planet parsing is poor, any number of things can cause it to
break.
We have two open tickets on it:
- https://pagure.io/fedora-infrastructure/issue/10383 (upgrade to pluto, a ruby based, but maintained thing)
- https://pagure.io/fedora-infrastructure/issue/10490 ( planet not served via ssl) Which I am just going to close now.
So, I can think of a number of options and would love everyone who has thoughts on it to chime in:
Do nothing. Venus "works" and .planet files are cool and retro.
Switch to pluto and use account system 'website' fields of
contributors. We could likely shove it in openshift and serve it directly from there to avoid fedorapeople entirely. (This would likely break anyone who has multiple feeds in there)
- Switch to something better/bigger. I would think (although I don't
know) that there might be something that would not only aggregate rss feeds for contributors, but perhaps mastodon/twitter/whatever also.
- Planets are old and tired, just drop the entire thing. People can
maintain their own rss lists.
#4 here has my vote -- i personally stopped reading RSS feeds daily on July 1, 2013. Also, not sure what value the planet provides to the community. its a bit of a hit and miss firehose sometimes.
--ryanlerch
- Planets are old and tired, just drop the entire thing.
But also, get our social media people to maintain contributor / interesting lists. ie, the fedoraproject twitter account could maintain a list of 'fedora contributors' and 'fedora packagers' or whatever.
- Switch to pluto as in 2, but also setup some curators. Have a
'firehose' of all feeds, but the main fedora planet would be just curated things that are known to be related to fedora and not off topic or unrelated.
- Get someones (not it!) to take in all the
twitter/facebook/mastodon/blog posts/rss feeds and post some kind of curated round up every week or something.
- Your brilliant idea here!
So, thoughts? this is not at all urgent, but we should end up doing something with it sometime. :)
kevin _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro... Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Dne 01. 03. 22 v 22:28 Kevin Fenzi napsal(a):
So, I can think of a number of options and would love everyone who has thoughts on it to chime in:
Thank you for kicking this off.
- Switch to pluto and use account system 'website' fields of
contributors. We could likely shove it in openshift and serve it directly from there to avoid fedorapeople entirely. (This would likely break anyone who has multiple feeds in there)
+1
But I would either rename the website field to RSSfeed or add new column with this name.
In my case the website is
but the RSS feed point to (just one category of my blog)
http://miroslav.suchy.cz/blog/archives/fedora/index.html
- Planets are old and tired, just drop the entire thing. People can
maintain their own rss lists.
-1
People can maintain their list, but it require effort. And sooner or later you give up.
And I get nice feedback on my post almost every time it is propagated by Planet.
- Planets are old and tired, just drop the entire thing.
But also, get our social media people to maintain contributor / interesting lists. ie, the fedoraproject twitter account could maintain a list of 'fedora contributors' and 'fedora packagers' or whatever.
-1 see above.
- Switch to pluto as in 2, but also setup some curators. Have a
'firehose' of all feeds, but the main fedora planet would be just curated things that are known to be related to fedora and not off topic or unrelated.
I am afraid of that "curated" as it requires "somebody".
- Get someones (not it!) to take in all the
twitter/facebook/mastodon/blog posts/rss feeds and post some kind of curated round up every week or something.
-1
let use the manpower somewhere else.
Miroslav
On Wed, Mar 02, 2022 at 10:38:08AM +0100, Miroslav Suchý wrote:
Dne 01. 03. 22 v 22:28 Kevin Fenzi napsal(a):
So, I can think of a number of options and would love everyone who has thoughts on it to chime in:
Thank you for kicking this off.
- Switch to pluto and use account system 'website' fields of
contributors. We could likely shove it in openshift and serve it directly from there to avoid fedorapeople entirely. (This would likely break anyone who has multiple feeds in there)
+1
+1 from me, too. Planet is very valuable window into our community.
But I would either rename the website field to RSSfeed or add new column with this name.
In my case the website is http://miroslav.suchy.cz/ but the RSS feed point to (just one category of my blog) http://miroslav.suchy.cz/blog/archives/fedora/index.html
I have similar situation. New field for ATOM/RSS field would be preferably.
- Switch to pluto as in 2, but also setup some curators. Have a
'firehose' of all feeds, but the main fedora planet would be just curated things that are known to be related to fedora and not off topic or unrelated.
-1 for curators. It won't scale. But maybe prune some non-people feeds (for example, but not limited to, Bodhi releases feed).
On Tue, Mar 01, 2022 13:28:07 -0800, Kevin Fenzi wrote:
Hey folks. I thought I would open a discussion about fedoraplanet and possibly some plans for it.
Hello,
- Do nothing. Venus "works" and .planet files are cool and retro.
- Switch to pluto and use account system 'website' fields of
contributors. We could likely shove it in openshift and serve it directly from there to avoid fedorapeople entirely. (This would likely break anyone who has multiple feeds in there)
+1 but with caveats:
I think folks do use multiple feeds sometimes, for example to add the blogs of our Outreachy candidates who may not always be CLA+1 right away. Adding folks to a group is not hard though (the Join SIG happily gives people membership to our FAS group if required, and there's also wikiedit). So we can do this, and just make sure everyone knows.
- Planets are old and tired, just drop the entire thing. People can
maintain their own rss lists.
-1
The planet is the only place where one can keep up with what community folks are doing---not just Fedora related, but generally in their lives. Folks share whatever they wish to share, and that's very important for us to know more about folks we do so much with.
(Generally, I think we need to give the planet more visibility---make sure everyone is aware that they can add their feeds there, and maybe also add links to the planet in other places like start.fp.o etc. to make it less of a "hidden" community resource.)
- Planets are old and tired, just drop the entire thing.
But also, get our social media people to maintain contributor / interesting lists. ie, the fedoraproject twitter account could maintain a list of 'fedora contributors' and 'fedora packagers' or whatever.
-1
Looks like too much manual work? I also note that not all community members use Twitter etc. so we end up in "what platform should the community use/promote" territory..
- Switch to pluto as in 2, but also setup some curators. Have a
'firehose' of all feeds, but the main fedora planet would be just curated things that are known to be related to fedora and not off topic or unrelated.
+0
I think just letting people share what they wish is fine. That way folks self curate what they think should go to the planet and when something goes against the CoC etc., it gets flagged. The current signal to noise ratio isn't too bad. I tend to skim titles quickly and only read posts that are relevant.
Are the curators going to be humans? That's more work that'll need to be done. Automated curators would work (keywords based?) but they may take some time setting up initially?
- Get someones (not it!) to take in all the
twitter/facebook/mastodon/blog posts/rss feeds and post some kind of curated round up every week or something.
-1
Dunno who'll do this, and how this will be done in the long run.
- Your brilliant idea here!
So, thoughts? this is not at all urgent, but we should end up doing something with it sometime. :)
Thanks for moving this along.
The Neuro SIG is using Pluto for our two planets already with a rather basic set up[1,2] and it works quite well for our very simple use case. @nerdsville helped with the migration for us, and from what I know, they're interested in helping out with migrating the Fedora planet too.
[1] https://neuroblog.fedoraproject.org/planet-neuroscientists/ [2] https://neuroblog.fedoraproject.org/planet-neuroscience/
On Wed, Mar 02, 2022 at 10:18:58AM +0000, Ankur Sinha wrote:
The planet is the only place where one can keep up with what community folks are doing---not just Fedora related, but generally in their lives. Folks share whatever they wish to share, and that's very important for us to know more about folks we do so much with.
It's so selective, though -- the set of people who blog about what they're doing isn't representative of the community. I mean, even if we made people more aware of it, it's not going to make more people into bloggers.
I'm interested in the idea of something more grand that can incorporate multiple other kinds of sources. Maybe something that'd make me use mastodon for real finally. :)
I think just letting people share what they wish is fine. That way folks self curate what they think should go to the planet and when something goes against the CoC etc., it gets flagged. The current signal to noise ratio isn't too bad. I tend to skim titles quickly and only read posts that are relevant.
I'd like to see it a little more focused. Having it be _whatever_ opens us up to potential trouble.
Plus there are some feeds which someone clearly set up many years ago and just plain have nothing relevant anymore ever. That's not a problem in the same sense, but does decrease the value.
On Wed, Mar 02, 2022 13:34:49 -0500, Matthew Miller wrote:
On Wed, Mar 02, 2022 at 10:18:58AM +0000, Ankur Sinha wrote:
The planet is the only place where one can keep up with what community folks are doing---not just Fedora related, but generally in their lives. Folks share whatever they wish to share, and that's very important for us to know more about folks we do so much with.
It's so selective, though -- the set of people who blog about what they're doing isn't representative of the community. I mean, even if we made people more aware of it, it's not going to make more people into bloggers.
Is there one platform that is representative of the community though?
I'm interested in the idea of something more grand that can incorporate multiple other kinds of sources. Maybe something that'd make me use mastodon for real finally. :)
If there is a tool that can aggregate data from multiple sources, and the work necessary to set it up and maintain it isn't a blocker, that would be a good way to go.
I think just letting people share what they wish is fine. That way folks self curate what they think should go to the planet and when something goes against the CoC etc., it gets flagged. The current signal to noise ratio isn't too bad. I tend to skim titles quickly and only read posts that are relevant.
I'd like to see it a little more focused. Having it be _whatever_ opens us up to potential trouble.
It isn't quite _whatever_ even now. "The Planet is a place for expression of many ideas related to the Fedora Project". Whatever platform is used, it'll have to be quite advanced to filter posts based on criteria that someone sets up to keep the output feed focused enough.
Plus there are some feeds which someone clearly set up many years ago and just plain have nothing relevant anymore ever. That's not a problem in the same sense, but does decrease the value.
Is this a platform issue either though? Irrespective of what we use, we'll have outdated input sources that will need to be cleaned up from time to time. We've just never had a policy in place for a planet clean up.
On Wed, Mar 02, 2022 at 09:16:29PM +0000, Ankur Sinha wrote:
It's so selective, though -- the set of people who blog about what they're doing isn't representative of the community. I mean, even if we made people more aware of it, it's not going to make more people into bloggers.
Is there one platform that is representative of the community though?
Wouldn't that be nice?!
This presents a nice opportunity to put forth an idea that Ben surely knew would be coming at some point: Discourse has an RSS polling plugin! https://meta.discourse.org/t/configure-the-discourse-rss-polling-plugin/1563...
We could set up a category specifically for aggregated blog posts. (Probably with replies disabled — although you could reply-as-new-linked-topic into a different categegory.)
This isn't _just_ "Matthew loves discourse and is looking at it as a hammer to hit all nails". It's also a way to help pull different threads together in once central place, so that there _is_ eventually a representative platform.
I think just letting people share what they wish is fine. That way folks self curate what they think should go to the planet and when something goes against the CoC etc., it gets flagged. The current signal to noise ratio isn't too bad. I tend to skim titles quickly and only read posts that are relevant.
I'd like to see it a little more focused. Having it be _whatever_ opens us up to potential trouble.
It isn't quite _whatever_ even now. "The Planet is a place for expression of many ideas related to the Fedora Project". Whatever platform is used, it'll have to be quite advanced to filter posts based on criteria that someone sets up to keep the output feed focused enough.
I think the filter would be: ask people to use feed categories on their blogs as a requirement for setting it up, and if we notice that being misused, disconnect that blog.
Plus there are some feeds which someone clearly set up many years ago and just plain have nothing relevant anymore ever. That's not a problem in the same sense, but does decrease the value.
Is this a platform issue either though? Irrespective of what we use, we'll have outdated input sources that will need to be cleaned up from time to time. We've just never had a policy in place for a planet clean up.
It's partly a platform issue because of the self-service nature. The Discourse plugin requires admin configuration, which has its own downsides, but means that people can flag the posts and an admin handle it like any kind of moderation. With Planet, removing something from an administrative point of view is a lot of process (and interrupt-driven infrastructure team work).
On Thu, Mar 03, 2022 at 12:23:57PM -0500, Matthew Miller wrote:
On Wed, Mar 02, 2022 at 09:16:29PM +0000, Ankur Sinha wrote:
It's so selective, though -- the set of people who blog about what they're doing isn't representative of the community. I mean, even if we made people more aware of it, it's not going to make more people into bloggers.
Is there one platform that is representative of the community though?
Wouldn't that be nice?!
This presents a nice opportunity to put forth an idea that Ben surely knew would be coming at some point: Discourse has an RSS polling plugin! https://meta.discourse.org/t/configure-the-discourse-rss-polling-plugin/1563...
We could set up a category specifically for aggregated blog posts. (Probably with replies disabled — although you could reply-as-new-linked-topic into a different categegory.)
This isn't _just_ "Matthew loves discourse and is looking at it as a hammer to hit all nails". It's also a way to help pull different threads together in once central place, so that there _is_ eventually a representative platform.
...snip...
yeah, I don't like the idea of 800 tickets to add 800 blogs (ok, I am sure it will be far less, but still).
Otherwise I don't hate the idea off hand. I think it could have some advantages like allowing the community to comment on some post together instead of comments going to the remote blog that no one goes back to notice there are comments on.
kevin
On Mon, Mar 21, 2022 at 01:30:07PM -0700, Kevin Fenzi wrote:
This isn't _just_ "Matthew loves discourse and is looking at it as a hammer to hit all nails". It's also a way to help pull different threads together in once central place, so that there _is_ eventually a representative platform.
...snip...
yeah, I don't like the idea of 800 tickets to add 800 blogs (ok, I am sure it will be far less, but still).
And I don't know how well it would even scale to 800 actual blogs.
If there really is that much interest, though, it'd be worthwhile setting up some automation — or maybe asking Discourse support to do a bulk first-setup from the console side.
Otherwise I don't hate the idea off hand. I think it could have some advantages like allowing the community to comment on some post together instead of comments going to the remote blog that no one goes back to notice there are comments on.
Let's keep it on the table, then. :)
On Thu, 24 Mar 2022 at 09:00, Matthew Miller mattdm@fedoraproject.org wrote:
On Mon, Mar 21, 2022 at 01:30:07PM -0700, Kevin Fenzi wrote:
This isn't _just_ "Matthew loves discourse and is looking at it as a
hammer to
hit all nails". It's also a way to help pull different threads
together in
once central place, so that there _is_ eventually a representative
platform.
...snip...
yeah, I don't like the idea of 800 tickets to add 800 blogs (ok, I am sure it will be far less, but still).
And I don't know how well it would even scale to 800 actual blogs.
I have counted about 80 different blogs since January. Most of them have a 1 post per every three months so maybe at most 100 counting a short tail.
If there really is that much interest, though, it'd be worthwhile setting up some automation — or maybe asking Discourse support to do a bulk first-setup from the console side.
Otherwise I don't hate the idea off hand. I think it could have some advantages like allowing the community to comment on some post together instead of comments going to the remote blog that no one goes back to notice there are comments on.
Since I don't generally allow posts on my blog in the first place since 99% of them have been spam or worse.. having a 'curated' place where people could comment is ok with me.
Let's keep it on the table, then. :)
-- Matthew Miller mattdm@fedoraproject.org Fedora Project Leader _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro... Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On Tue, Mar 1, 2022 at 4:28 PM Kevin Fenzi kevin@scrye.com wrote:
Hey folks. I thought I would open a discussion about fedoraplanet and possibly some plans for it.
Thanks for starting this discussion, Kevin!
We've had some moderation issues with Planet over the years and a lot of the content is not relevant to Fedora. If it were to go away, I could live with it. Personally, I'd rather see much of the Fedora-related content on Planet end up on the Community Blog instead. That said, it does provide *some* value to the community (and the non-Fedora content is interesting and isn't necessarily something I'd see otherwise) so I'm not going to actively advocate for shutting it down.
- Do nothing. Venus "works" and .planet files are cool and retro.
-1. I don't want to endorse making someone go kick the process on a regular basis. And running EOL software seems un-great.
- Switch to pluto and use account system 'website' fields of
contributors. We could likely shove it in openshift and serve it directly from there to avoid fedorapeople entirely. (This would likely break anyone who has multiple feeds in there)
+1 with caveats. It should be a separate field, IMO, because "website" and "RSS feed of my blog" are not necessarily the same thing. Like some others, my feed in Planet is for a specific tag to avoid spamming Planet with all of the other baloney I write about. But I also have a static website that I'd rather point people to when I say "this is my website".
Do we have a rough count of how many people have multiple feeds in their .planet file? I didn't even know that was supported! In general, I'd rather break that for a few people than maintain the status quo. If it's a non-trivial number of people, maybe we can come up with a way to have the account system support multiple values in the RSS field?
- Switch to something better/bigger. I would think (although I don't
know) that there might be something that would not only aggregate rss feeds for contributors, but perhaps mastodon/twitter/whatever also.
-1. People can add their social media account's RSS feed now if they want, but I don't think we want to encourage that. I feel bad enough for the people who follow me on Twitter, nevermind subjecting everyone subscribing to Planet to it. :-)
- Planets are old and tired, just drop the entire thing. People can
maintain their own rss lists.
0. (see reasoning in my opening comments)
- Planets are old and tired, just drop the entire thing.
But also, get our social media people to maintain contributor / interesting lists. ie, the fedoraproject twitter account could maintain a list of 'fedora contributors' and 'fedora packagers' or whatever.
- Switch to pluto as in 2, but also setup some curators. Have a
'firehose' of all feeds, but the main fedora planet would be just curated things that are known to be related to fedora and not off topic or unrelated.
- Get someones (not it!) to take in all the
twitter/facebook/mastodon/blog posts/rss feeds and post some kind of curated round up every week or something.
-1. Active curation takes a lot of effort, and we don't seem to have that available (particularly not in a sustained way). Maybe someday in the future, but we are not yet living in this particular future.
On Wed, Mar 02, 2022 at 01:16:27PM -0500, Ben Cotton wrote: ...snip...
Do we have a rough count of how many people have multiple feeds in their .planet file? I didn't even know that was supported! In general, I'd rather break that for a few people than maintain the status quo. If it's a non-trivial number of people, maybe we can come up with a way to have the account system support multiple values in the RSS field?
So, some (interesting) stats.
802 users have .planet files. (Unsure how many of these are active)
Of those 802 users, 65 have more than 1 rss feed in their .planet file.
The most is pingou with 5. ;)
kevin
On Tue, 1 Mar 2022 at 16:29, Kevin Fenzi kevin@scrye.com wrote:
Hey folks. I thought I would open a discussion about fedoraplanet and possibly some plans for it.
Right now:
fedoraplanet.org runs on people02.fedoraproject.org (aka fedorapeople). To add a blog/rss feed you have to login there and edit your .planet file, then scripting pulls all those .planet files and tries to fetch all the feeds and then serves them up at http://fedoraplanet.org. It uses a app called 'venus' to do this. venus is written in very old python2 and very very dead upstream.
We run into the following problems with it:
- Sometimes it gets stuck and just stops processing until it's killed.
- It's serving on a http site, which causes people to ask us to make it
https, but that would just change the errors because many feeds it pulls are still http since they were added back before letsencrypt existed.
- We have a handy 'website' field in our new account system, but aren't
using it at all.
- The .planet parsing is poor, any number of things can cause it to
break.
We have two open tickets on it:
- https://pagure.io/fedora-infrastructure/issue/10383 (upgrade to pluto, a ruby based, but maintained thing)
- https://pagure.io/fedora-infrastructure/issue/10490 ( planet not served via ssl) Which I am just going to close now.
So, I can think of a number of options and would love everyone who has thoughts on it to chime in:
Do nothing. Venus "works" and .planet files are cool and retro.
Switch to pluto and use account system 'website' fields of
contributors. We could likely shove it in openshift and serve it directly from there to avoid fedorapeople entirely. (This would likely break anyone who has multiple feeds in there)
I would like to go for 2 but with the caveat Ben put that it uses a different field. However I also realize it is a lot of work and there are not a lot of active blog writers anymore.
Hi everyone. I was taking a look at this and trying to migrate Fedora Planet to pluto and have some questions.
Some things in pluto are not done yet, for example getting the author is something marked as "to be done" in the documentation https://feedreader.github.io/#planet-planet--pluto---template-cheatsheet-1 and even some pluto standard templates are still a WIP (https://github.com/orgs/planet-templates/repositories). Even with those limitations, I searched if there was a way to get the same info we have using venus, but nothing seems to work. Fedora Planet and its sub planets have their own distinct template, but not being able to "translate" every variable to pluto or changing to any standard pluto template, would make a lot of changes in the website.
The Neuro SIG used a standard pluto template called forty and did some customization. Should we do the same with Fedora Planet? Could we keep Fedora Planet with venus for now and just work to put it in openshift? Or should we follow any other path Kevin proposed?
On Thu, Jul 21, 2022 at 11:45:31AM -0000, Pedro Moura wrote:
Hi everyone. I was taking a look at this and trying to migrate Fedora Planet to pluto and have some questions.
Some things in pluto are not done yet, for example getting the author is something marked as "to be done" in the documentation https://feedreader.github.io/#planet-planet--pluto---template-cheatsheet-1 and even some pluto standard templates are still a WIP (https://github.com/orgs/planet-templates/repositories). Even with those limitations, I searched if there was a way to get the same info we have using venus, but nothing seems to work. Fedora Planet and its sub planets have their own distinct template, but not being able to "translate" every variable to pluto or changing to any standard pluto template, would make a lot of changes in the website.
I think we are open to changes here as long as they are reasonable ones. Not having author is pretty major sounding though. ;(
Can any of the neuro folks provide some help here?
The Neuro SIG used a standard pluto template called forty and did some customization. Should we do the same with Fedora Planet?
Yeah, thats fine as long as we can still have things like author and such. Perhaps it would be worth trying to get it to do a few feeds and we can all look at it?
Could we keep Fedora Planet with venus for now and just work to put it in openshift?
I don't think we want to do that. We should wait for pluto before moving to openshift.
Or should we follow any other path Kevin proposed?
I'd say perhaps try and get pluto working with just a few feeds and we can see how it looks like? Then, we can work on the part where it pulls the feeds from the account system, then after that, we can look at putting it in openshift.
Just my thoughts...
kevin
On Wed, Jul 27, 2022 11:26:34 -0700, Kevin Fenzi wrote:
On Thu, Jul 21, 2022 at 11:45:31AM -0000, Pedro Moura wrote:
Hi everyone. I was taking a look at this and trying to migrate Fedora Planet to pluto and have some questions.
Some things in pluto are not done yet, for example getting the author is something marked as "to be done" in the documentation https://feedreader.github.io/#planet-planet--pluto---template-cheatsheet-1 and even some pluto standard templates are still a WIP (https://github.com/orgs/planet-templates/repositories).
Could you clarify what is meant by the "author"? The name of the blog/site? That's given by `item.feed.title`, see here:
https://github.com/neurofedora/planet-neuroscientists/blob/master/neuroscien...
Even with those limitations, I searched if there was a way to get the same info we have using venus, but nothing seems to work. Fedora Planet and its sub planets have their own distinct template, but not being able to "translate" every variable to pluto or changing to any standard pluto template, would make a lot of changes in the website.
I think we are open to changes here as long as they are reasonable ones. Not having author is pretty major sounding though. ;(
Can any of the neuro folks provide some help here?
The Neuro SIG used a standard pluto template called forty and did some customization. Should we do the same with Fedora Planet?
Yeah, thats fine as long as we can still have things like author and such. Perhaps it would be worth trying to get it to do a few feeds and we can all look at it?
Yeh, our template is a rather simple customisation of one of the examples.
I remember we'd also looked into OpenSUSE's planet instance, which is a more complex deployment (uses Jekyll etc. IIRC). That may be a better starting point?
https://github.com/openSUSE/planet-o-o https://planet.opensuse.org/
The name of the blog/site? That's given by `item.feed.title`, see here:
https://github.com/neurofedora/planet-neuroscientists/blob/master/neurosc...
I remember we'd also looked into OpenSUSE's planet instance, which is a more complex deployment (uses Jekyll etc. IIRC). That may be a better starting point?
https://github.com/openSUSE/planet-o-o https://planet.opensuse.org/
Thanks! This tip and openSUSE repo really helped. I was able to get the author, picture and do a work around to get the fas name. It seems we can keep the templates as they are in Fedora Planet and just change it so pluto can build them.
Sharing what I've done so far: - Fedora Planet didnt had a repo, so I created one here https://github.com/fedora-infra/planet - Everything was pushed on dev branch for now - Put Fedora Planet in a container - Changed only the index template of people's planet. Fedora Planet has about 7 "planets", each "planet" has about 7 distinct html templates, they're slightly similar tho. So the mission now would be changing those html templates to erb templates so pluto can build them.
I'd like to keep working on this, but also would like to hear from you all: - What do you think how this is going so far? - Any suggestions or anything I should have done? - Can I keep working on this?
Regards, Pedro Moura
On Wed, Aug 10, 2022 20:39:18 -0000, Pedro Moura wrote:
Thanks! This tip and openSUSE repo really helped. I was able to get the author, picture and do a work around to get the fas name.
Ah, great. Glad that was helpful :)
<snip>
I'd like to keep working on this, but also would like to hear from you all:
- What do you think how this is going so far?
- Any suggestions or anything I should have done?
I think that's great progress :)
My only request would be: could you add instructions in the README on how to test this out with the container etc.? We can then also play around with it and help out wherever possible.
On Wed, Aug 10, 2022 at 08:39:18PM -0000, Pedro Moura wrote:
The name of the blog/site? That's given by `item.feed.title`, see here:
https://github.com/neurofedora/planet-neuroscientists/blob/master/neurosc...
I remember we'd also looked into OpenSUSE's planet instance, which is a more complex deployment (uses Jekyll etc. IIRC). That may be a better starting point?
https://github.com/openSUSE/planet-o-o https://planet.opensuse.org/
Thanks! This tip and openSUSE repo really helped. I was able to get the author, picture and do a work around to get the fas name. It seems we can keep the templates as they are in Fedora Planet and just change it so pluto can build them.
Sharing what I've done so far:
- Fedora Planet didnt had a repo, so I created one here https://github.com/fedora-infra/planet
- Everything was pushed on dev branch for now
- Put Fedora Planet in a container
- Changed only the index template of people's planet. Fedora Planet has about 7 "planets", each "planet" has about 7 distinct html templates, they're slightly similar tho. So the mission now would be changing those html templates to erb templates so pluto can build them.
I don't think it has to be 100% exactly the same... just close...
I'd like to keep working on this, but also would like to hear from you all:
- What do you think how this is going so far?
- Any suggestions or anything I should have done?
- Can I keep working on this?
I think you're doing great. ;)
Once you have it generating pages, might be good to publish those somewhere and everyone can look and see how it looks?
kevin
Hi everyone,
We have been migrating those templates to erb files and was noticed some differences. people02.fedoraproject.org has templates for each sub-planet of fedora planet, but some of them are not being used in prod. Summer-coding and Security are examples of sub-planets that have different templates that are not used in prod, css is different too.
Should we apply the same templates for all the planets? If yes, the repo https://gitlab.com/fedora/websites-apps/themes/fedora-planet-theme has the templates for "people" planet, which are the templates that seems to be in prod. Should we be pushing in that repo instead?
Pedro Moura
On Tue, Aug 23, 2022 at 12:46:04AM -0000, Pedro Moura wrote:
Hi everyone,
We have been migrating those templates to erb files and was noticed some differences. people02.fedoraproject.org has templates for each sub-planet of fedora planet, but some of them are not being used in prod. Summer-coding and Security are examples of sub-planets that have different templates that are not used in prod, css is different too.
Should we apply the same templates for all the planets? If yes, the repo https://gitlab.com/fedora/websites-apps/themes/fedora-planet-theme has the templates for "people" planet, which are the templates that seems to be in prod. Should we be pushing in that repo instead?
Well, we did at one point have those 'sub planets' defined for various teams. If you go to: http://fedoraplanet.org/ and look at the top there's a drop down for 'sub planets'. I am not sure they are really used, but they also all seem to have the same templates/apperance? (At least from what I can tell).
So, I would say, get it working with the base one and we can adjust the other ones later.
We could reuse that repo I guess... it looks like almost all the work there was done by Ryan Lerch, we could ask him...
kevin
Hi everyone,
We had help to migrate those venus templates to pluto. :) The container is similar to what we have in production, but some blogs are responding with 404 while building pluto. You can check how it is here https://github.com/fedora-infra/planet So, would like to ask the opinion of you all. - Is it good? - Is it missing anything? - Is there anything we should improve? - Should we move to OCP already?
Pedro
On Fri, 2 Dec 2022 at 12:10, Pedro Moura pmoura@redhat.com wrote:
Hi everyone,
We had help to migrate those venus templates to pluto. :) The container is similar to what we have in production, but some blogs are responding with 404 while building pluto. You can check how it is here https://github.com/fedora-infra/planet So, would like to ask the opinion of you all.
- Is it good?
- Is it missing anything?
- Is there anything we should improve?
- Should we move to OCP already?
Cool. What blogs responded with a 404? And where can people see how it looks in staging?
Pedro _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro... Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On Sat, Dec 3, 2022 at 12:22 PM Stephen Smoogen ssmoogen@redhat.com wrote:
Cool. What blogs responded with a 404?
A lot of blogs are responding with errors, not only 404. I could come up with a list and share it here
And where can people see how it looks in staging?
I haven't deployed in staging yet, but I could deploy it in stg OCP if it's ok :)
-- Stephen Smoogen, Red Hat Automotive Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro... Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Pedro Moura
He/Him/His
Software Engineer
Red Hat https://www.redhat.com/
pmoura@redhat.com https://www.redhat.com/
On Sat, Dec 3, 2022 at 12:22 PM Stephen Smoogen <ssmoogen(a)redhat.com> wrote:
Cool. What blogs responded with a 404?
Here is a list of blogs that respond with an error during the build:
http://blog.fubar.dk/?feed=rss2 : *** error - fetch HTTP - 404 Not Found http://domsch.com/blog/?feed=rss2&tag=fedora : *** error - fetch HTTP - 404 Not Found http://www.dragonsreach.it/category/justfedora/feed/ : *** error - fetch HTTP - 404 Not Found http://mribeirodantas.github.io/ato.xml : *** error - fetch HTTP - 404 Not Found http://stef.thewalter.net/feeds/posts/default/-/security/?alt=rss : *** error - fetch HTTP - 404 Not Found https://amitosh.in/feed/fedora.xml<*** error - fetch HTTP - 404 Not Found http://sarupbanskota.github.io/feed.fedora.xml : *** error - fetch HTTP - 404 Not Found http://github.com/mapleoin/maplepink/raw/master/ftp/tag/fedora-summer-coding... : *** error - fetch HTTP - 404 Not Found http://devel.adityapatawari.com/category/FSC/feed/ : *** error - fetch HTTP - 522
Also, some other blogs were disabled on `.ini` files because they were breaking the build. Follow that list below:
http://dailypackage.fedorabook.com/index.php?/feeds/index.rss2 http://www.redhatmagazine.com/category/fedora/feed http://www.projetofedora.org/rss.xml http://www.fedora-tunisia.org/?q=atom/feed http://www.braincache.de/wp/category/fedora-design/feed http://sarupbanskota.github.io/feed.fedora.xml http://jefvanschendel.nl/blog/index.atom http://www.ryanlerch.org/blog/?feed=rss2 http://feeds.feedburner.com/Karl-tux-stadtFedora-design
Regards, Pedro Moura He/Him/His Software Engineer Red Hat <https://www.redhat.com/ pmoura(a)redhat.com https://www.redhat.com/
On Fri, Dec 02, 2022 at 04:31:55PM -0000, Pedro Moura wrote:
Hi everyone,
We had help to migrate those venus templates to pluto. :) The container is similar to what we have in production, but some blogs are responding with 404 while building pluto. You can check how it is here https://github.com/fedora-infra/planet So, would like to ask the opinion of you all.
- Is it good?
- Is it missing anything?
- Is there anything we should improve?
- Should we move to OCP already?
I finally got around to trying this... and I couldn't quite get it working.
It built ok, but then I ran it and got the default httpd web page on port 80. Is the content under something ?
Likely it's me not being very container savvy... but perhaps you could go through the steps again on how to build/run it and where the content will be?
But yeah, given that you have it pulling things, we should definitely look at bringing it up in staging so everyone can help out and check it.
kevin
Hi Kevin,
I have been helping Pedro a little with this (and will try to continue to do so, if I can).
I finally got around to trying this... and I couldn't quite get it working.
It built ok, but then I ran it and got the default httpd web page on port 80. Is the content under something ?
Likely it's me not being very container savvy... but perhaps you could go through the steps again on how to build/run it and where the content will be?
Hmm, I know I made some Dockerfile changes, but the following works for me, and brings me straight to a working instance of the planet site:
podman build -t fedora-infra/planet:dev . && \ podman run --rm -it -p 8080:80 fedora-infra/planet:dev && \ xdg-open http://localhost:8080
Are you sure that you're looking at port 8080 in your browser, or might you be looking at port 80, and somehow have httpd running separately from the container? Otherwise, it sounds like something has gone wrong during your "podman build" step. If you hit that problem again, could you upload the image that you built to quay.io or somewhere like that, and the build logs to somewhere that I could see them too?
But yeah, given that you have it pulling things, we should definitely look at bringing it up in staging so everyone can help out and check it.
+1, it would be great to get it coughing and wheezing in staging to get eyes on it. There are a few things that I think still need to be done to make it great. For example, I don't think the build-planets.sh should be run as part of the image build. Assuming this will run in an OpenShift/k8s cluster, I think we'd be better off looking at something like a pod with 2 containers with a shared persistent volume: one container would run httpd, serving the planet from that disk (read-only), and the other would periodically run the script to scan the feeds and update the contents on disk.
Where would the best place to create such tasks/proposals be...issues in that GitHub project? It's been quite a while since I've been involved in anything around Fedora, so I'm not really sure how/where things are done nowadays!
Ger.
On Sat, Jan 21, 2023 at 12:09:34AM -0000, Gerard Ryan wrote:
Hi Kevin,
Hello.
I have been helping Pedro a little with this (and will try to continue to do so, if I can).
Great!
I finally got around to trying this... and I couldn't quite get it working.
It built ok, but then I ran it and got the default httpd web page on port 80. Is the content under something ?
Likely it's me not being very container savvy... but perhaps you could go through the steps again on how to build/run it and where the content will be?
Hmm, I know I made some Dockerfile changes, but the following works for me, and brings me straight to a working instance of the planet site:
podman build -t fedora-infra/planet:dev . && \ podman run --rm -it -p 8080:80 fedora-infra/planet:dev && \ xdg-open http://localhost:8080
Huh. Now this works here too... I am not sure what I did wrong. ;(
Are you sure that you're looking at port 8080 in your browser, or might you be looking at port 80, and somehow have httpd running separately from the container? Otherwise, it sounds like something has gone wrong during your "podman build" step. If you hit that problem again, could you upload the image that you built to quay.io or somewhere like that, and the build logs to somewhere that I could see them too?
Yeah, I was definitely looking at 8080... not sure. ;(
But yeah, given that you have it pulling things, we should definitely look at bringing it up in staging so everyone can help out and check it.
+1, it would be great to get it coughing and wheezing in staging to get eyes on it. There are a few things that I think still need to be done to make it great. For example, I don't think the build-planets.sh should be run as part of the image build. Assuming this will run in an OpenShift/k8s cluster, I think we'd be better off looking at something like a pod with 2 containers with a shared persistent volume: one container would run httpd, serving the planet from that disk (read-only), and the other would periodically run the script to scan the feeds and update the contents on disk.
Yes, I think that model is right...
Where would the best place to create such tasks/proposals be...issues in that GitHub project? It's been quite a while since I've been involved in anything around Fedora, so I'm not really sure how/where things are done nowadays!
So, I talked with Pedro last week and we thought setting up a communishift instance for this would be a good first step. You all can then get it all working as you like in openshift there and then exporting the config to staging should be easy. :0)
I setup Pedro as manager of the communishift-planet group, so he should be able to add you and then you should have access to the project.
Thats to you (and Pedro!) for working on this.
kevin
Dear colleagues,
I would like to share some updates and ask for suggestions regarding the Fedora Planet.
As some of you may already know, Fedora Planet was deployed on CommuniShift with the blogs hard-coded. Additionally, we are working on some significant changes that affect the process of adding new blogs to the Fedora Planet.
Instead of users having to SSH and create a .planet file to add their blogs, the idea would be simply add their blogs to Fedora Accounts. The fields in Fedora Accounts should be available in FasJSON, and we are using this API to create the files for each planet so Pluto can build them.
I wrote a Python script, just for now, that creates planet build files using the "website" field in FasJSON and brute-force directories to find RSS feeds (not the best solution, but I'll get there), this script classifies in which planet a particular blog will be added based on which group the user is in (i.e. if the user is in design fedora account group, then will be added to design planet). However, this could bring some issues to the users like showing an article not related to the corresponding planet. Additionally, a user also may have tags in their blog that correspond to a particular planet, such as security, design, fedora, etc. Because of those issues, I talked to Kevin about adding an RSS field in Fedora Accounts (noggin) that would allow the user to add links to the planets they want and also get rid of that brute-force solution. I created an issue about it here: https://github.com/fedora-infra/noggin/issues/1155
Is it the best approach? Are those planets still being used? Also, is it okay to let users freely add some link that will appear in Fedora planet? Maybe creating a group for people that wish to add their blog on Fedora Planet would help to improve the security about the last one?
The container build also needs some improvement, as Pluto breaks due to the misconfiguration of some feeds, such as "error: This is not well-formed XML Missing end tag for 'meta' (got 'head')" and "error: undefined method `rss_version' for nil:NilClass". Maybe adding a condition in that Python script checking those feeds would solve it. Additionally, due to queries to FasJSON, Kerberos login is required. Probably, there will be a service account to automate this process for prod, but for now during container build in CommuniShift, I don't know how to automate this part.
Thank you in advance for your time, and looking forward to your suggestions.
Best regards,
Pedro Moura
On Mon, Jan 23, 2023 at 3:28 PM Kevin Fenzi kevin@scrye.com wrote:
On Sat, Jan 21, 2023 at 12:09:34AM -0000, Gerard Ryan wrote:
Hi Kevin,
Hello.
I have been helping Pedro a little with this (and will try to continue
to do so, if I can).
Great!
I finally got around to trying this... and I couldn't quite get it working.
It built ok, but then I ran it and got the default httpd web page on port 80. Is the content under something ?
Likely it's me not being very container savvy... but perhaps you could go through the steps again on how to build/run it and where the content will be?
Hmm, I know I made some Dockerfile changes, but the following works for
me, and brings me straight to a working instance of the planet site:
podman build -t fedora-infra/planet:dev . && \ podman run --rm -it -p 8080:80 fedora-infra/planet:dev && \ xdg-open http://localhost:8080
Huh. Now this works here too... I am not sure what I did wrong. ;(
Are you sure that you're looking at port 8080 in your browser, or might
you be looking at port 80, and somehow have httpd running separately from the container? Otherwise, it sounds like something has gone wrong during your "podman build" step. If you hit that problem again, could you upload the image that you built to quay.io or somewhere like that, and the build logs to somewhere that I could see them too?
Yeah, I was definitely looking at 8080... not sure. ;(
But yeah, given that you have it pulling things, we should definitely look at bringing it up in staging so everyone can help out and check
it.
+1, it would be great to get it coughing and wheezing in staging to get
eyes on it. There are a few things that I think still need to be done to make it great. For example, I don't think the build-planets.sh should be run as part of the image build. Assuming this will run in an OpenShift/k8s cluster, I think we'd be better off looking at something like a pod with 2 containers with a shared persistent volume: one container would run httpd, serving the planet from that disk (read-only), and the other would periodically run the script to scan the feeds and update the contents on disk.
Yes, I think that model is right...
Where would the best place to create such tasks/proposals be...issues in
that GitHub project? It's been quite a while since I've been involved in anything around Fedora, so I'm not really sure how/where things are done nowadays!
So, I talked with Pedro last week and we thought setting up a communishift instance for this would be a good first step. You all can then get it all working as you like in openshift there and then exporting the config to staging should be easy. :0)
I setup Pedro as manager of the communishift-planet group, so he should be able to add you and then you should have access to the project.
Thats to you (and Pedro!) for working on this.
kevin _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro... Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On Wed, Apr 5, 2023 at 6:05 PM Pedro Moura pmoura@redhat.com wrote:
Instead of users having to SSH and create a .planet file to add their blogs, the idea would be simply add their blogs to Fedora Accounts. The fields in Fedora Accounts should be available in FasJSON, and we are using this API to create the files for each planet so Pluto can build them.
That seems like a nice improvement in usability.
Is it the best approach? Are those planets still being used? Also, is it okay to let users freely add some link that will appear in Fedora planet? Maybe creating a group for people that wish to add their blog on Fedora Planet would help to improve the security about the last one?
I don't think an additional group is necessary, but we should probably tie it to agreeing to the FPCA at a minimum. Maybe we can require membership in at least one group instead of adding a specific group? We have historically had the occasional problem with inappropriate content in Planet, but generally it hasn't been an issue. We can address those issues as they come up.
On Thu, Apr 06, 2023 at 12:22:59PM -0400, Ben Cotton wrote:
On Wed, Apr 5, 2023 at 6:05 PM Pedro Moura pmoura@redhat.com wrote:
Instead of users having to SSH and create a .planet file to add their blogs, the idea would be simply add their blogs to Fedora Accounts. The fields in Fedora Accounts should be available in FasJSON, and we are using this API to create the files for each planet so Pluto can build them.
That seems like a nice improvement in usability.
Is it the best approach? Are those planets still being used? Also, is it okay to let users freely add some link that will appear in Fedora planet? Maybe creating a group for people that wish to add their blog on Fedora Planet would help to improve the security about the last one?
I don't think an additional group is necessary, but we should probably tie it to agreeing to the FPCA at a minimum. Maybe we can require membership in at least one group instead of adding a specific group? We have historically had the occasional problem with inappropriate content in Planet, but generally it hasn't been an issue. We can address those issues as they come up.
Oh, I forgot to reply to this part, but currently planet feeds are taken from ~/.planet files on fedorapeople.org. So, in order to do that you have to have access there (ie, be in more than one non cla group).
We should definitely keep this in the new setup. The ipa group "contributor" I think exposes this. So, we should make sure only people in that group are enabled.
Finally, yeah, it might be good to have a blocklist file in case we need to block someone, but I guess we could just remove their feed from their account? but then they could add it back in, so...
kevin
On Thu, Apr 6, 2023 at 3:45 PM Kevin Fenzi kevin@scrye.com wrote:
Finally, yeah, it might be good to have a blocklist file in case we need to block someone, but I guess we could just remove their feed from their account? but then they could add it back in, so...
I figure it's going to be either spam or CoC violations. The spam case is going to be something where the person probably isn't putting much effort into it and mostly blocked by the "contributor" group requirement anyway, so I'm not really concerned there. The CoC violation case is more complex, but I figure if someone has their feed forcibly removed from the planet, they're probably getting their account put in timeout for a while anyway. I assume they wouldn't be able to log in while their account is suspended? So having a blocklist is nice, but not something we'd need immediately. I hope.
Is the current url available to look at? Just to see what it looks like as a test?
Yes, it is. I forgot to share the link here it is: https://planet-communishift-planet.apps.fedora.cj14.p1.openshiftapps.com
This version has the blogs hard coded and the profile pics from the links that I got from venus (the feed reader we were using before pluto) Now the python script uses libravatar to get profile pics and periodically create planet.ini files to build planets. I did not push to the repo yet.
Finally, yeah, it might be good to have a blocklist file in case we need to block someone, but I guess we could just remove their feed from their account? but then they could add it back in, so...
We have a `ìgnore_users` list in ansible repo planet role. Maybe we can reuse the idea
Pedro Moura
he/him/his
Software Engineer
Red Hat https://www.redhat.com
pmoura@redhat.com https://www.redhat.com
On Thu, Apr 6, 2023 at 6:20 PM Ben Cotton bcotton@redhat.com wrote:
On Thu, Apr 6, 2023 at 3:45 PM Kevin Fenzi kevin@scrye.com wrote:
Finally, yeah, it might be good to have a blocklist file in case we need to block someone, but I guess we could just remove their feed from their account? but then they could add it back in, so...
I figure it's going to be either spam or CoC violations. The spam case is going to be something where the person probably isn't putting much effort into it and mostly blocked by the "contributor" group requirement anyway, so I'm not really concerned there. The CoC violation case is more complex, but I figure if someone has their feed forcibly removed from the planet, they're probably getting their account put in timeout for a while anyway. I assume they wouldn't be able to log in while their account is suspended? So having a blocklist is nice, but not something we'd need immediately. I hope.
-- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro... Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On Thu, Apr 06, 2023 at 12:22:59PM -0400, Ben Cotton wrote:
On Wed, Apr 5, 2023 at 6:05 PM Pedro Moura pmoura@redhat.com wrote:
Instead of users having to SSH and create a .planet file to add their blogs, the idea would be simply add their blogs to Fedora Accounts. The fields in Fedora Accounts should be available in FasJSON, and we are using this API to create the files for each planet so Pluto can build them.
That seems like a nice improvement in usability.
One thing to keep in mind is that from time to time people are having multiple blogs in their .planet.ini. We could check on fedorapeople how often this happens, and from there see if we need to keep that feature.
Pierre
On Thu, Apr 06, 2023 at 12:22:59PM -0400, Ben Cotton wrote:
One thing to keep in mind is that from time to time people are having multiple blogs in their .planet.ini. We could check on fedorapeople how often this happens, and from there see if we need to keep that feature.
Pierre
Not very often. There are currently 789 users who have added their blogs to the Fedora Planet directory. However, the last updates to the .planet were as follows:
- 12 made last year (mostly in the beginning of the year) - 20 made in 2021 - 25 made in 2020
The rest were updated prior to 2020, and there have been no updates made by any user this year. It's worth noting that some users have more than one blog listed in that file.
On Wed, Apr 12, 2023 at 07:44:13PM -0000, Pedro Moura wrote:
On Thu, Apr 06, 2023 at 12:22:59PM -0400, Ben Cotton wrote:
One thing to keep in mind is that from time to time people are having multiple blogs in their .planet.ini. We could check on fedorapeople how often this happens, and from there see if we need to keep that feature.
Pierre
Not very often. There are currently 789 users who have added their blogs to the Fedora Planet directory. However, the last updates to the .planet were as follows:
- 12 made last year (mostly in the beginning of the year)
- 20 made in 2021
- 25 made in 2020
The rest were updated prior to 2020, and there have been no updates made by any user this year.
It's worth noting that some users have more than one blog listed in that file.
This is what I was pointing out, sorry if I wasn't clear :)
Pierre
On Wed, Apr 05, 2023 at 07:04:54PM -0300, Pedro Moura wrote:
Dear colleagues,
I would like to share some updates and ask for suggestions regarding the Fedora Planet.
Hey Pedro. Thanks for updating everyone. :)
As some of you may already know, Fedora Planet was deployed on CommuniShift with the blogs hard-coded. Additionally, we are working on some significant changes that affect the process of adding new blogs to the Fedora Planet.
Instead of users having to SSH and create a .planet file to add their blogs, the idea would be simply add their blogs to Fedora Accounts. The fields in Fedora Accounts should be available in FasJSON, and we are using this API to create the files for each planet so Pluto can build them.
I wrote a Python script, just for now, that creates planet build files using the "website" field in FasJSON and brute-force directories to find RSS feeds (not the best solution, but I'll get there), this script classifies in which planet a particular blog will be added based on which group the user is in (i.e. if the user is in design fedora account group, then will be added to design planet). However, this could bring some issues to the users like showing an article not related to the corresponding planet. Additionally, a user also may have tags in their blog that correspond to a particular planet, such as security, design, fedora, etc. Because of those issues, I talked to Kevin about adding an RSS field in Fedora Accounts (noggin) that would allow the user to add links to the planets they want and also get rid of that brute-force solution. I created an issue about it here: https://github.com/fedora-infra/noggin/issues/1155
Is it the best approach? Are those planets still being used? Also, is it okay to let users freely add some link that will appear in Fedora planet? Maybe creating a group for people that wish to add their blog on Fedora Planet would help to improve the security about the last one?
I'm interested to hear from others if those subplanets are much used anymore. :)
IMHO, we should probibly just try and make things as simple as possible to start with. I'd say we could even drop the subplanets unless people are really using them/expecting them anymore.
But I guess lets see?
Is the current url available to look at? Just to see what it looks like as a test?
The container build also needs some improvement, as Pluto breaks due to the misconfiguration of some feeds, such as "error: This is not well-formed XML Missing end tag for 'meta' (got 'head')" and "error: undefined method `rss_version' for nil:NilClass". Maybe adding a condition in that Python
Yeah, the current planet script gets a ton of errors from places. It's pretty anoying. We definitely need to handle errors by passing on to the next feed when we get them or something.
script checking those feeds would solve it. Additionally, due to queries to FasJSON, Kerberos login is required. Probably, there will be a service account to automate this process for prod, but for now during container build in CommuniShift, I don't know how to automate this part.
Yeah, in real clusters we can just have ansible get a service keytab for that, but there's no easy way to do that in communishift.
Thank you in advance for your time, and looking forward to your suggestions.
Thanks for bringing things up.
I'm hoping for more input too...
kevin
I'm interested to hear from others if those subplanets are much used anymore. :)
IMHO, we should probibly just try and make things as simple as possible to start with. I'd say we could even drop the subplanets unless people are really using them/expecting them anymore.
Given that there are no frequent updates on .planet, I also believe we could drop the subplanets.
Additionally, a list could be implemented on Noggin where users could add multiple blog links, considering the fact that some users have more than one blog and later query those links from FASjson to build planet.
Furthermore, I wonder if we should close the old issue, which requests the migration of Venus to Pluto, and create a new one explaining the current goal of changing the process of Fedora Planet and deploying it on OCP.
Please let us know your thoughts on these proposals. We look forward to working together to improve the Fedora Planet platform.
On Wed, Apr 12, 2023 at 09:16:51PM -0000, Pedro Moura wrote:
I'm interested to hear from others if those subplanets are much used anymore. :)
IMHO, we should probibly just try and make things as simple as possible to start with. I'd say we could even drop the subplanets unless people are really using them/expecting them anymore.
Given that there are no frequent updates on .planet, I also believe we could drop the subplanets.
Yeah, hopefully. It might be possible to reach out to those groups... design, security? They have irc rooms, we could try asking there? (I don't recall all the subplanets we have...)
Additionally, a list could be implemented on Noggin where users could add multiple blog links, considering the fact that some users have more than one blog and later query those links from FASjson to build planet.
yeah, that sounds reasonable to me. Will require noggin changes tho.
Furthermore, I wonder if we should close the old issue, which requests the migration of Venus to Pluto, and create a new one explaining the current goal of changing the process of Fedora Planet and deploying it on OCP.
We could, but it's really just a continuation of that...
Please let us know your thoughts on these proposals. We look forward to working together to improve the Fedora Planet platform.
Hopefully we will get some more feedback soon. :)
kevin
Yeah, hopefully. It might be possible to reach out to those groups... design, security? They have irc rooms, we could try asking there?
Due to time zone differences and the possibility of some users not seeing my message on IRC, I created a survey with 3 questions to gather data on the use of subplanets on Fedora Planet. I have sent the survey to the devel, design, and desktop mailing lists. I did this because some mailing lists that would represent subplanet groups don't exist or don't have subscribers.
If you in the infrastructure list would like to respond as well, it would help us make a more informed decision. Please find the link to the survey below. I will keep the form open until April 24th at 12 UTC.
Link: https://forms.gle/FGxkAoiMSQKdC7o39
Thank you for your time and participation.
Best regards, Pedro
On Fri, Apr 14, 2023 at 07:22:57PM -0300, Pedro Moura wrote:
Yeah, hopefully. It might be possible to reach out to those groups... design, security? They have irc rooms, we could try asking there?
Due to time zone differences and the possibility of some users not seeing my message on IRC, I created a survey with 3 questions to gather data on the use of subplanets on Fedora Planet. I have sent the survey to the devel, design, and desktop mailing lists. I did this because some mailing lists that would represent subplanet groups don't exist or don't have subscribers.
Might be worth sending it to devel-announce, or maybe even announce? They should be low(er) traffic and high(er) attention.
Pierre
Or maybe if we know who are those users, we can contact them directly.
Michal
On 17. 04. 23 10:06, Pierre-Yves Chibon wrote:
On Fri, Apr 14, 2023 at 07:22:57PM -0300, Pedro Moura wrote:
Yeah, hopefully. It might be possible to reach out to those groups... design, security? They have irc rooms, we could try asking there?
Due to time zone differences and the possibility of some users not seeing my message on IRC, I created a survey with 3 questions to gather data on the use of subplanets on Fedora Planet. I have sent the survey to the devel, design, and desktop mailing lists. I did this because some mailing lists that would represent subplanet groups don't exist or don't have subscribers.
Might be worth sending it to devel-announce, or maybe even announce? They should be low(er) traffic and high(er) attention.
Pierre _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro... Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Thanks for the suggestions :)
Just sent to announce mailing list. We could get planet users and send to them directly, but them would have an opinion only of those who are posting their blogs there and sending in announce we might have an opinion of those who are using planet also to read?
Pedro Moura
he/him/his
Software Engineer
Red Hat https://www.redhat.com
pmoura@redhat.com https://www.redhat.com
On Mon, Apr 17, 2023 at 6:01 AM Michal Konecny mkonecny@redhat.com wrote:
Or maybe if we know who are those users, we can contact them directly.
Michal
On 17. 04. 23 10:06, Pierre-Yves Chibon wrote:
On Fri, Apr 14, 2023 at 07:22:57PM -0300, Pedro Moura wrote:
Yeah, hopefully. It might be possible to reach out to those groups... design, security? They have irc rooms, we could try asking there?
Due to time zone differences and the possibility of some users not
seeing
my message on IRC, I created a survey with 3 questions to gather data on the use of subplanets on Fedora Planet. I have sent the survey to the devel, design, and desktop mailing lists. I did this because some
mailing
lists that would represent subplanet groups don't exist or don't have subscribers.
Might be worth sending it to devel-announce, or maybe even announce? They should be low(er) traffic and high(er) attention.
Pierre _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to
infrastructure-leave@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro... Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On 2023-04-18 15:07, Pedro Moura wrote:
Thanks for the suggestions :)
Just sent to announce mailing list. We could get planet users and send to them directly, but them would have an opinion only of those who are posting their blogs there and sending in announce we might have an opinion of those who are using planet also to read?
Random thought: does the http server have any metrics or logs that could be counted to give an indication of how many requests there are for each feed (including the main one) over a period of time?
infrastructure@lists.fedoraproject.org
-
Ankur Sinha -
Ben Cotton -
Gerard Ryan -
Kevin Fenzi -
Matthew Miller -
Michal Konecny -
Miroslav Suchý -
Pedro Moura -
Pedro Moura -
Pierre-Yves Chibon -
Ryan Lerch -
Stephen Smoogen -
Tomasz Torcz