> 1) install pygump on moof.apache.org I'd love to see/support this.
> 2) initiate the burocratic process to get Gump as a Top Level Domain > > [I volunteer to help that process] > > What do you think? I'm no expert on what makes a TLP, and can see why Stefan doesn't see a need for a small community of active users, but maybe Gump is bigger than we think. Developing Gump (code) is one thing, acting as an admin (maintaining servers/metadata) is another, but the true Gump community are those folk -- plus all those who maintain their own metadata, and/or react to the results/nags/feeds, and read/reference the output pages. [BTW: A satisfied smile came to my face to see Antoine recently reference a 'Full Project Dependees' section I'd added only a little while before. That is exactly what Gump ought communicate for us.] In short, I think we are a larger community than the gump mailinglist archives might show. I'd love to see Gump 'open up' to more uses (e.g. work with forrestbot, work with non build scripts) and maybe it needs to be reborn in order for folks to see that potential/opening. I don't know if being in Jakarta has limited it, but it might've. I think Gump is a social experiment of interconnecting metadata about projects/communities, and I'd love it to explore/reach that potential. I guess none of this needs to be a TLP, but then again, maybe it does. I'll let wiser folks than I figure that out. I really want gump.apache.org -- for an official presence (if only to send relayed nag e-mails from the inside & host an interactive WWW interface) -- but I sure hope that doesn't limit the distributed network of gump servers contributed by the community. There is value in that also. regards, Adam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
