Fedora package social networking

Fedora Community v2 Package Profile Thumbnail
So we’ve been talking about a reincarnation of Fedora Community (the app).
Stuff to take note of:

  • Yes, it looks like Facebook. (As my coworker Partha likes to remind me, Fedora had the white lowercase f on blue first. 🙂 )
  • The main navbar for the package is directly under its name & summary. Additional information about the package is available via nav items along the right sidebar, but what we thought was the most important we put in the main navbar. What do you think about which is most important and which is not?
  • In the main navbar we have:
    • Bugs – this will be somewhat like the current bugs tab in Fedora Community.
    • Contents – this will be like running rpm -ql on the package; it will list out all the files it includes.
    • Changelog – a changelog of the package, similar to what Fedora Community has now.
    • Sources – this will show patches we’ve applied if any, the spec file, the git repo for source, the tarball, maybe diffs. (SRPM should be available here too I think.)
    • Relationships – requires / dependences / provides / obsoletes / etc. information. Maybe like this mockup, but less crappy. Also this tab will let you know which package is dating which. I hear inkscape and blender have gotten engaged!
  • There’s a section for upstream information, but we’re not quite sure how we’ll get all of that. There is an XML based format called dope (sp?) that some upstreams use, so maybe that will be involved.
  • A per-package events stream!

There’s more ideas here; see for yourself.
What do you think?


  1. Andre Costa

    It looks very good, nice work =) Sometimes I find it confusing to grab testing or unstable RPMs from Koji, maybe this page will ease this process. Also, it’ll be good to have a central point from which I can contact the package owners, download new (or old) versions, go to upstream site etc. BTW: in case there are multiple owners, will there be a way to contact them all at once? If not one of the owners might end up receiving much more messages than the others… (unless this is expected, of course).

  2. While I have yet to actively use Fedora on my computer (moving from the linux-introducing Ubuntu to Debian seemed easier at the time), I am constantly impressed with the design aspect of Fedora regarding new contributions.
    The http://fedoraproject.org/ website, the “Your Life on Fedora” user stories, as well as the easy to understand areas where you can get involved. Compelled to action, I submitted a font to Máirín via e-mail and received a quick and kind response.
    This is another example where I think you’re doing things right. It looks great, it makes sense, and it makes me care — and want to care more with action. Congrats!
    My two cents from the outside.

  3. FWIW, in openSUSE, we’ve developed some stuff to fetch latest upstream versions. This definitely needs re-working, but this an area where we could collaborate easily — and it wouldn’t be too hard to add more metadata (like git, svn, etc. URL).
    I’m willing to work with other distros on this. Note that at this time, we don’t have information about that many packages, but it wouldn’t be too hard to crowdsource this.
    There’s also a similar thing done by Debian to watch for new upstream versions, but we didn’t invest enough time to merge the efforts. Yet.

  4. I like it.
    IMHO the upstream information is VERY important, because it’s deeply tied with the bug information. After all, Fedora is a distribution, and it’s very likely that a bug need to be fixed somewhere else.

  5. Till Maas

    Instead of raw relationships it would be nice to have these mapped to other packages. E.g. have an easy way to navigate to other packages that require the current package or provide a dependency for the current package.
    Also I noticed that the “latest build” information is only interesting, if it is there for all active branches.
    In the active release overview it would be nice to also mark whether updates are already marked to be moved to stable or testing.

  6. Pingback: » Source view in Fedora Packages Máirín Duffy

  7. Pingback: Source view in Fedora Packages « Fedora Tutorials « 123linux tutorials

  8. Pingback: Package categories… what do you think? « Máirín Duffy

  9. Pingback: Announcing Fedora Packages (and Fedora Tagger!) « Máirín Duffy

Leave a Reply to Michael Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.