Yeah, this is part of what I want JabberForge to present in the end user interaction with it. It should allow for easy browsing of the projects and their status. The end user shouldn't be busied with the development details unless they really want to be.
--temas On Wed, Dec 05, 2001 at 08:54:26AM +0000, David Sutton wrote: > Hello, > > On Tue, 2001-12-04 at 16:40, Robert Norris wrote: > > I had been thinking of implementing some sort of repository for server > > components (or getting something added to JabberCentral, much like their > > clients directory), including this sort of information, but I'm going to > > wait and see how JabberForge will go - it may very well be able to help > > with this sort of thing. > > > > Rob. > > That was similar to my line of thinking too. There is already an area > listing available transports, but is a little sparce on information and > needs updating. To be honest tho, that really should be the > responsibility of the transport maintainer, which is why an architecture > like JabberForge is vital in many ways. > > David > > _______________________________________________ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev -- Thomas Muldowney email/jabber: [EMAIL PROTECTED]
msg03491/pgp00000.pgp
Description: PGP signature
