From Fedora Project Wiki
#!rst =========================== Developer Social Networking =========================== Just because your wife thinks you talk to "the little people who live in the computer" doesn't mean you don't have a social life. It's just that your community is on the other side of a set of keyboards and wires from you. Like any other social animal, you want to keep in touch with the day to day events of your community. In other words, you want to be up on the latest gossip. There's a couple ways to achieve that. There's IRC, email, and other forms of instantaneous communication. There's blogging, web pages, and other forms of semi-static content. There's package builds, changes to programs, and other semi-interesting things that are being done by the people you're interested in. So how do you find out about these? How do you organize them? How do you make new friends? How do you come to understand your existing friends better? These are the things that social networking sites in general address. A Fedora Social Networking site could do these things for Fedora Developers or it could take a different tack. Other sites cover the range of social networking very well. Perhaps there's more value in providing Fedora Events and aggregating those events with events from other sites to provide a complete experience. .. contents:: ------ Events ------ * CVS Commits * Package Builds * Push from updates * Changes to owner information * Groups that your friends belong to * Email messages * Blog postings ------------------------------------- Subjects (Things to watch for events) ------------------------------------- * Friends * Packages * CVS Repository * Hosted projects * out of Fedora Information (blogs..) * Mailing lists * Fedora Weekly News -------- Services -------- * Notification server that can generate per-user RSS, send emails, etc for users about events. Events should be category based so that a user can watch "all package events which concern kernel" * Central page (in FAS2) that a user can use to view the events going on around them. * Tying SIGs to FAS2 groups and from there to content concerning SIG member actions. * Ability to see what similarities and differences you have to your friends (... Like what groups/packages do we have in common, which ones are different?) * summaries and graphs (% patches accepted into the package; % Fedora contribution in subproject) * Collaborative whiteboard (a la gobby)