GNOME Bugzilla – Bug 629990
Make news.gnome.org a redirect to www.gnome.org/news
Last modified: 2017-08-31 10:26:51 UTC
From bug 625728 "It's called http://news.gnome.org and is so boring that no one even knows about it." Lets look into how we can make news.gnome.org interesting. The must be some really cool projects feed out there.
Please assign this to me
I don't really understand the goal of the bug, to be honest. Why not just file a bug for each feed we should add?
well, you can close it if you want. I was thinking this could be a bug with lots of dependencies on it on cool feeds. Hard to tell when this is resolved though.
Ah, well, I'm fine having dependencies and all... Let's try :-)
From time to time I propose the creation of a GNOME universe like Gentoo people do. In Gentoo, Universe Gentoo is an aggregation of weblog articles on all topics written by the Gentoo community. For a more refined aggregation of Gentoo-related topics only, they have Planet Gentoo. Maybe we can left GNOME planet as it is (it will be our "universe") and redirect the GNOME related posts to news.gnome.org (our "planet" in the Gentoo comparison) Just my 2 cents
Juanjo: That would is a different bug I think. This is about http://news.gnome.org, our projects feed.
Andread: My idea was to include informative GNOME posts on news.gnome.org. Only few post on planet.gnome.org meet this condition. news.gnome.org is boring because it doesn't include too much "human ready" entries (sort of articles or posts). But if we talk of articles, we are on the territory of GNOME journal and if talk of posts we're talking about planet.gnome.org. Maybe we can rethink about our communication channels, even more if we take into account new media channels like gnome tv, and the targets we want to go -- insiders to the project, downstreams projects, hobbysts, press, etc --. After some toughts in general terms we can implement better communication channels that we can take maintain. So, I think is relevant to ask "Which is supposed to be the news.gnome.org readers" ?
s/Andead/Andreas/
I agree that we need more humanness on news.gnome.org. Either the author's voice needs to come through on the posts or we need to make the project news about users or developers.
FWIW, I always thought that authors/maintainers should take care of blogging themselves about their projects and let P.G.O be the hub for all that information, in that regard, News is boring by design in that is mainly meant to be used for release notes.
No offense to anyone, but has this changed in any way over the last three years? From my point of view, it is still quite "boring" in that it does not offer anything which is not already available by subscribing to mailing lists (which is kinda essential for community members) and p.g.o.
I've come to agree with the last two comments. I wonder if we should just retire it.
Sure. Do we point news.gnome.org to www.gnome.org/news in that case?
(In reply to comment #13) > Sure. Do we point news.gnome.org to www.gnome.org/news in that case? Makes sense.
(In reply to comment #14) > (In reply to comment #13) > > Sure. Do we point news.gnome.org to www.gnome.org/news in that case? > > Makes sense. Indeed. Who wants to inform the world (foundation-announce and/or p.g.o) about this change? I can do it if no one else wants to do it desperately.
Currently news.gnome.org is (still) a planet that aggregates www.gnome.org news items, but also the devel-announce and foundation-announce lists (although the list aggregation is broken). Effectively this means news.gnome.org only has www.gnome.org/news content. The way I understand the previous comments, the plan was to have a redirect though. Is this how we want to handle this? If so, this should me reassigned to sysadmins.
(In reply to Alexandre Franke from comment #16) ... > The way I understand the previous comments, the plan was to have a redirect > though. Is this how we want to handle this? That sounds right. > If so, this should me reassigned > to sysadmins. Makes sense.
Done. [1] [1] https://infrastructure.gnome.org/browse/puppet/commit/?id=13dc596
+ [2]. [2] https://infrastructure.gnome.org/browse/puppet/commit/?id=5f9e844