As part of the GSoC involvement this year, I am requesting that a sub-domain gsoc.fedoraproject.org be set up and, a planet instance be made available to syndicate the blogs of the GSoC candidates for The Fedora Project.
For further reference/information, please feel free to ask {quaid|nman64}@fedoraproject.org
I read through the "GSoC-ers this year and their blogs" thread. Wasn't one of the points "Exposure to the greater community"? Why not just use planet.fedoraproject.org. People actually already goto and follow that planet. What compelling reason do people have to go to gsoc.fedoraproject.org besides the gsoc students?
Replying to [comment:1 mmcgrath]:
Umm...well, the Fedora+GSoC branding has never happened. And, giving the GSoC-ers a space of their own would probably encourage them to be a bit more relaxed and collegial than throwing them into the great cacophony of the Fedora Planet. Additionally, the single view of the GSoC blogs would also be helpful I guess. A separate planet for GSoC mentors and students makes some sense that way.
I'd leave the floor to quaid and nman64 now :)
The other thing I'd like to point out is straight fedorapeople integration would happen now, a gsoc.fedoraproject.org would likely happen at some point in time in the future.
I don't think we want Fedora GSoC students to not be on the Fedora planet; same with JBoss.org students and the JBoss.org planet. That fulfills the exposure to greater community.
One thing we have to consider is that JBoss.org students are not otherwise needing to use Fedora resources or get a Fedora account. If we want to encourage blogging that is not mandatory, it helps if we don't require a % of the students to step way out of their existing pathway.
Having one location where both projects are highlighted is good for Fedora, JBoss.org, and the students. They can be superstars without too much limelight on them.
For administrators, it is easier to watch one planet feed to provide the meta-oversight that Google expects from us. Easier than reading two massive planets to glean a few nuggets.
As for domain names, that is tricky. I was hoping we could get some Apache magic and co-branding so it would appear to be gsoc.{fedoraproject,jboss}.org depending on the source URL.
But now that is starting to sound like actual work ... :)
Replying to [comment:4 quaid]:
As for domain names, that is tricky. I was hoping we could get some Apache magic and co-branding so it would appear to be gsoc.{fedoraproject,jboss}.org depending on the source URL. But now that is starting to sound like actual work ... :)
How does something like http://planet.fedoraproject.org/gsoc/ work out in terms of work ? Is that a feasible option ?
Does this still need to be done?
Replying to [comment:6 mmcgrath]:
Yes please. In light of the Fedora Summer Coding effort, this (planet.fedoraproject.org/gsoc) is required to be put up. I am not too sure if all that is required for it to happen is a .planet.gsoc file in the fedorapeople home of the candidates, if that is so, then I guess we are all set.
All we perhaps need to do is work with the Design Team for a theme for the /gsoc planet.
Quaid, Nman can you confirm this is required? and we want /gsoc even though it's fsoc?
Neither "gsoc" nor "fsoc" are suitable. I am certain we will want to use something different, but I do not know what that will be. We do not call it "Fedora Summer of Code", since Google has trademarked "Summer of Code", and "fsc" (Fedora Summer Coding) does not seem quite right either. Maybe "summer".
Suggestions or opinions?
planet.fedoraproject.org/summer-coding
We're using the 'summer coding' fairly regularly, and it fits with how we do other similar branding.
I'm asking for help from someone at JBoss.org to at least get their branding right, if not some co-branding work. So, to start, let's put up the typical Fedora Planet skin, get that in a repo, and we can get someone from JBoss.org to help us tweak it for their sponsorship, etc.
Replying to [comment:10 quaid]:
planet.fedoraproject.org/summer-coding We're using the 'summer coding' fairly regularly, and it fits with how we do other similar branding.
Err yes. Summer coding. Sorry about the stupidity on my part in responding to the ticket but carrying forward the 'gsoc' part.
Just to be clear, we don't need any fancy redirects from e.g. "summer-coding.fedoraproject.org" (I want to save that kind of thing for an actual nicely done program page, cf. http://rubysoc.org).
We could use this as soon as possible. I'm unclear if this is a trivial or non-trivial task, I never heard definitively if the .planet file can handle multiple planet installations.
One final point from the discussions last year. This has gone from a nice-have to a must-have now that we are running our own program. We have a reporting obligation to sponsors, and a planet of the students' blogs is an important way we can get a regular overview of the health of the program as well as the individual projects. It allows mentors to read-up and cross-mentor each other - I can notice a problem in one area and help the mentor help the student to a solution. This is especially important where the mentors are not well-connected Fedora contributors already.
Done:
http://planet.fedoraproject.org/summer-coding/
To add new people to planet, the procedure is just like the old planet except for creating a .planet.summer-coding file. Let me know when you've added one and I'll remove myself, it's just sitting there right now as a place holder so the site actually comes up :)
Login to comment on this ticket.