Planet is not a commonly understood word outside the hacker culture. Thus change the title from "Planet TDF" to "LibreOffice Community Blogs" and have blogs.libreoffice.org redirect to planet.documentfoundation.org (or vice versa, if simple to do). for reference (from #libreoffice-dev): 16:55 <@mmeeks> Sweetshark: I suspect that the libreoffice planet is another victim of the unhelpful 'TDF' parallel brand. 16:55 <@mmeeks> Sweetshark: planet.libreoffice.org is where I'd look for it ;-) 17:12 <@Sweetshark> mmeeks: nah not really. its because we neither link to it from either libreoffice.org and documentfoundation.org. We only have the TDF blog in there. 17:13 <@Sweetshark> mmeeks: fwiw, I now added the planet to the TDF blog, my blog and in the default header on the TDF wiki and the wiki frontpage. 17:13 <@mmeeks> Sweetshark: you don't think the huge title: "The Document Foundation Planet" 17:13 <@mmeeks> Sweetshark: makes it just a bit harder to find it when you search for "LibreOffice Planet" ? ;-) 17:13 * mmeeks thinks it is yet-another slam-dunk example of the folly of dual-branding ;-) 17:14 <@Sweetshark> mmeeks: if you are talking about the general population, they dont have a clue what a "planet" is in the first place. 17:14 < tml_> Sweetshark: +1 17:14 <@Sweetshark> mmeeks: hence I called it "LibreOffice community blogs" in my links. 17:15 <@Sweetshark> mmeeks: but yeah: having the title changed and maybe "blogs.libreoffice.org" redircting to it cant hurt either. 17:20 <@Sweetshark> mmeeks: and https://www.libreoffice.org/default/ ONLY featured the 'official blog' -- not the community. Same with libreoffice.de. I understand that having a community member rant syndicated there directly might be ... unfortunate. But a link to the planet itself cant hurt (...). 17:20 <@Sweetshark> (strangely they also have a "twitter" section featuring ... a big whitespace.) 17:25 <@Sweetshark> mmeeks: and again: the urgent problem has little to nothing to do with the TDF/LibreOffice branding. After all, if you google for "documentfoundation" you wont find the planet on the first two pages either. and nobody bothers beyond that. 17:26 <@Sweetshark> mmeeks: OTOH "planet libreoffice" finds the TDF planet as first hit. QED: nothing to do with the LO/TDF dual brand and everything with underlinking and 'planet' being geekspeak (adding links should be fixed by now, so the rename is what remains)
Renaming it is an easy task - but then we have confusion between blog.documentfoundation.org and blogs.libreoffice.org, not really improving the situation. I rather prefer then blog.libreoffice.org (for the current TDF blog) and planet.libreoffice.org or blogplanet.libreoffice.org (for the current TDF planet) - thoughts?
(In reply to comment #1) > Renaming it is an easy task - but then we have confusion between > blog.documentfoundation.org and blogs.libreoffice.org, not really improving > the situation. hmm true > I rather prefer then blog.libreoffice.org (for the current TDF blog) and > planet.libreoffice.org or blogplanet.libreoffice.org (for the current TDF > planet) - thoughts? blog.libreoffice.org for the official TDF blog seems nice to me instead of {blog,}planet.libreoffice.org I would prefer communityblogs.libreoffice.org though -- as said: "planet" is not common vocabulary.
Sounds ok to me Is this highly urgent? Otherwise, I propose we do a general rebranding/renaming campaign, and handle all of that in a row instead of individually...
(In reply to comment #3) > Sounds ok to me > Is this highly urgent? no, explicitly used a bugzilla issue so this can be done sometime in the long run without falling through the cracks.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: *Test to see if the bug is still present on a currently supported version of LibreOffice (4.4.1 or later) https://www.libreoffice.org/download/ *If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior *If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT *Update the version field *Reply via email (please reply directly on the bug tracker) *Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-04-18
Ticket moved to redmine, see https://redmine.documentfoundation.org/issues/1551