Create a pt_BR feed created on planet.fedoraproject.org/pt_BR
This new website needs to be fullfilled only with pt_BR content, need a RSS Feed only for pt_BR and should be integrated with maind planet.fedoraproject.org.
Below some e-mails with Infrastructure guys!!!
Rodrigo Menezes escreveu:
I'll fill the ticket right now. What I need? A Planet only in pt_BR and a working RSS for this pt_BR website. About URL, I can create a planeta.projetofedora.org and set this dub-domain to re-direct to planet.fedoraproject.org/pt_BR, no problems. I'm making some tests with Venus here, just to see how it works, can you provide the theme used in our Planet? Cheers, Rodrigo Menezes Karsten 'quaid' Wade escreveu: On Fri, 2008-07-18 at 19:44 -0400, Paul W. Frields wrote: We can aggregate the pt_BR stuff on the official Planet Fedora as well. Seth Vidal said he could make the new .planet file able to handle l10n. Not sure if the function is there, it might just be a stub right now. Rodrigo -- can you enter in an infrastructure ticket to have a pt_BR feed created on planet.fedoraproject.org/pt_BR? (Presuming that is a good URL.) https://fedorahosted.org/fedora-infrastructure Then we can find out from Seth how it can work, and recruit a web programmer to help, if needed. Once that is done, you can use it to populate a "mirror" planet on projetofedora.org. The people can use the existing system and quickly populate language-specific planets. Karsten
I'll fill the ticket right now.
What I need? A Planet only in pt_BR and a working RSS for this pt_BR website.
About URL, I can create a planeta.projetofedora.org and set this dub-domain to re-direct to planet.fedoraproject.org/pt_BR, no problems.
I'm making some tests with Venus here, just to see how it works, can you provide the theme used in our Planet?
Cheers,
Rodrigo Menezes
Karsten 'quaid' Wade escreveu:
On Fri, 2008-07-18 at 19:44 -0400, Paul W. Frields wrote: We can aggregate the pt_BR stuff on the official Planet Fedora as well. Seth Vidal said he could make the new .planet file able to handle l10n. Not sure if the function is there, it might just be a stub right now. Rodrigo -- can you enter in an infrastructure ticket to have a pt_BR feed created on planet.fedoraproject.org/pt_BR? (Presuming that is a good URL.) https://fedorahosted.org/fedora-infrastructure Then we can find out from Seth how it can work, and recruit a web programmer to help, if needed. Once that is done, you can use it to populate a "mirror" planet on projetofedora.org. The people can use the existing system and quickly populate language-specific planets. Karsten
On Fri, 2008-07-18 at 19:44 -0400, Paul W. Frields wrote:
We can aggregate the pt_BR stuff on the official Planet Fedora as well.
Seth Vidal said he could make the new .planet file able to handle l10n. Not sure if the function is there, it might just be a stub right now.
Rodrigo -- can you enter in an infrastructure ticket to have a pt_BR feed created on planet.fedoraproject.org/pt_BR? (Presuming that is a good URL.)
https://fedorahosted.org/fedora-infrastructure
Then we can find out from Seth how it can work, and recruit a web programmer to help, if needed.
Once that is done, you can use it to populate a "mirror" planet on projetofedora.org. The people can use the existing system and quickly populate language-specific planets.
We've had a request for this in the past. So first some questions.
1) Should we do this? 2) How do we do this?
In answering should, I need a little feedback from you. How much pt_BR content has been generated in the last month?
1) We are planning to do this for local websites, if we could do this as an integrated tool, perfect. If it's not possible, we'll create another agregator, a separeted one.
After FISL and before the new Account System, a lot of Ambassadors had their own website added in planet.fp.org, now only a few is there.
We want something to get all the comunity closer, doesn't matter if the person is an Ambassador or not, we want news about Fedora, if anyone write, we'll publish.
2) Good question, How can we create a separate agregator, that can sincronize with the main planet.fp.org?
Replying to [comment:2 rmenezes]:
This was one of the reasons I suggested Rodrigo file this ticket instead, so we don't proliferate planets for no reason.
What I'd like to see is a way to add your feed an arbitrary number of locales via the .planet file. Possibly the mere existence of a new locale causes it to be created on the next planet run? That would minimize admin work, v. having to get a request for every locale created.
This way people can add themselves (or not) to the main feed as well as any locales. For multi-lingualists, they could create a different feed for each language and put posts in that depending on the language, e.g.:
http://iquaid.org/feeds/es
Then I could write in Spanish, put it in that category, and arrange that to appear on the planet.fedoraproject.org/es page by putting the right stanza in my .planet file. Then we could communicate across languages without having to invade each other's language-specific areas with content in a different language.
What's the next step?
Messages through e-mail, just to be in the ticket:
seth vidal wrote:
The idea was that users can make a .planet.$something file in their homedir on fedorapeople.org. Then we can have a separate planet run grab up those files, compile them and use them. The code we have now can deal with that, we just need to decide which ones are needed and set up planet to know to grab them. How about a .planet.pt_BR? -sv
The idea was that users can make a .planet.$something file in their homedir on fedorapeople.org. Then we can have a separate planet run grab up those files, compile them and use them. The code we have now can deal with that, we just need to decide which ones are needed and set up planet to know to grab them.
How about a .planet.pt_BR?
-sv
Diego Búrigo Zacarão wrote:
Hello, +1 Make sence to me. Regards -- Diego Búrigo Zacarão
Hello,
+1 Make sence to me.
Regards
-- Diego Búrigo Zacarão
Ian Weller escreveu:
How about a lang= variable in the existing .planet file? :)
seth vidal escreveu:
doesn't work - many people post in mutliple languages and the point of the .planet.something option is so we can have arbitrary aggregation, not just language-based aggregation. -sv
doesn't work - many people post in mutliple languages and the point of the .planet.something option is so we can have arbitrary aggregation, not just language-based aggregation.
In my opinion a .planet.pt_BR is the best choice, this way a user can add himself as a pt_BR, english, spanish, as we wants.
More updates via e-mail:
Karsten 'quaid' Wade wrote:
Also let's us do: .planet.docs .planet.ambassadors .planet.art etc. Seth -- did you stop at the second dot? Or did you include tertiary filtering, e.g.: .planet.ambassadors.en_US ??? Karsten
Also let's us do:
.planet.docs .planet.ambassadors .planet.art
etc.
Seth -- did you stop at the second dot? Or did you include tertiary filtering, e.g.:
.planet.ambassadors.en_US
???
group has to be manually set up in the backend so going hog-wild doesn't really help us. More to the point it takes a bit of time to generate these feeds for each new one we have. So, segmenting it out to the nth degree has a cost. -sv the group is just anything that arbitrarily follows the .planet. Each
group has to be manually set up in the backend so going hog-wild doesn't really help us. More to the point it takes a bit of time to generate these feeds for each new one we have. So, segmenting it out to the nth degree has a cost.
the group is just anything that arbitrarily follows the .planet. Each
Updating ticket with e-mail conversation...
On Mon, 2008-07-21 at 13:27 -0700, Karsten 'quaid' Wade wrote:
Also let's us do: .planet.docs .planet.ambassadors .planet.art etc. Seth -- did you stop at the second dot? Or did you include tertiary filtering, e.g.: .planet.ambassadors.en_US
.planet.docs .planet.ambassadors .planet.art etc.
On Mon, 2008-07-21, Seth Vidal wrote:
the group is just anything that arbitrarily follows the .planet. Each group has to be manually set up in the backend so going hog-wild doesn't really help us. More to the point it takes a bit of time to generate these feeds for each new one we have. So, segmenting it out to the nth degree has a cost. -sv
the group is just anything that arbitrarily follows the .planet. Each group has to be manually set up in the backend so going hog-wild doesn't really help us. More to the point it takes a bit of time to generate these feeds for each new one we have. So, segmenting it out to the nth degree has a cost.
On Mon, 2008-07-21, Ian Weller wrote:
This is going to get very messy very fast. We can just ln -s them to the main .planet file if we want, right?
What's the nex step?
wow, this is old.
we have subplanets now.
Is this request still wanted?
I'm looking with friends from Brazil about this issue.
This ticket is no longer necessary.
Please close it.
Login to comment on this ticket.