On Mon, 2010-04-12 at 13:05 +0200, Andreas Rottmann wrote: > Derick Eddington <[email protected]> writes: > > > On Sun, 2010-04-11 at 21:23 +0200, Andreas Rottmann wrote: > > > >> I'd also appreciate thoughts about how to _name_ the libraries inside > >> the collections. I think someone (Derick?) has mentioned using (ported > >> ...) for third-party code ported to R6RS, and I'm fine with that, but > >> would like to hear other suggestions as well. > > > > Yeah, I suggested (ported ---) for community-maintained ported > > libraries. I like it because a top-level namespace is needed, because > > it's not proper to name them like (irregex) unless the author blesses > > that particular R6RS port, and "ported" describes the nature of the > > collection. > > > I agree, besides the "single collection" point I detailed in my other > mail.
In my mind, "collection" only means libraries in the same namespace. Maybe a better term is needed. > > LaunchPad has the facilities for the coordination, but I don't care if > > somewhere else is used, we just need proper facilities for > > coordinating. > > > I'm not a big fan of bzr, and would rather use something git-based (like > gitorious or github); OK, if the place has project home pages, bug reporting / issue tracking, and team-assisting organization (I'm not familiar with those places). I've been wanting a reason to get more familiar with Git. > I've already a "dorodango" project on > gitorious, and we could use repositories below that for each > package. Suggestions welcome! I don't think things usually distributed via Dorodango should be under it. They're independent and could be distributed without it, so a separate project makes more sense to me. -- : Derick ----------------------------------------------------------------
