Mainstream hosting versus rolling our own: availability for mashups?

One interesting thing to say about the Ohloh service is that it demonstrates the difference in consequences between using mainstream project hosting and rolling our own project hosting infrastructure in JA-SIG.

Projects hosted on dev.java.net are indexed and included in the visibility in ohloh.net, whereas by squirreling our code out into our own ja-sig.org infrastructure, our code isn't available for first pass indexing.
This is not the end of the world, of course -- presumably ohloh can and will eventually get around to indexing Sakai and uPortal, but the CAS Modules and Spring project and so forth show up immediately, thereby getting better visibility in these mashups, or even just when someone searches dev.java.net or sourceforge.

Sakai is present on dev.java.net but there's no code there so Sakai's ohloh.net entry is dopey by default.

uPortal isn't even on the radar at ohloh.net because it's not on one of the hosts being indexed. So if you search for opensource portals there, uPortal won't even show up.

Job Opportunity at BU

BU's School of Management is now taking applications for a Senior Software Engineer position (see entry 3175/G256 on the university's IT jobs page).

We're especially interested in the sort of facility that comes from healthy experience in open source endeavors, so it seems fitting to circulate the announcement here. Feel free to contact me for any further details:
clayf AT bu.edu.

As posted on sakai-announce.