Hi, I have been using James and watching development for sometime, what I think is really missing from the project is 'Branding'.
What I mean by this is that the James project needs a clear high level vision of what it does, how it does it, where it is going and how it getting there, this vision needs to be kept independent of its implementation. To some extent I think this is what the Avalon framework encourages, design lead by role, i.e. people need first and foremost be able to use James. A lot of developer discussion is focused on implementation details, however without a clear statement of intent design can become difficult as there are no clear targets to reach. My point is that James is a peice of software, for it to be taken up and used more widely it need to become a product as well. Its basic seperation of concerns, product specification and software implementation. Simon ----- Original Message ----- From: "Noel J. Bergman" <[EMAIL PROTECTED]> To: "James Users List" <server-user@james.apache.org> Sent: Friday, March 25, 2005 3:32 PM Subject: RE: Gateway Authentication > > There seems to be only one active developer: he is > > working on JamesNG, trying to migrate away from the > > Avalon beast. > > Actually, no. Development outside of the ASF infrastructure is not > development. I'd be fairly happy to see him as an active developer, working > with the others. > > > if the dart-throwers were burning up their keyboards cranking > > out new features, integrating submitted patches, making more > > than typo-level fixes to the website, figuring out a versioning > > strategy, or at the very least read up on lightweight containers > > etc. > > Lightweight containers is a fairly low priority compared to the many > features that are pending. > > Personally, I've been home less than 20 days so far this year, weekends > included, and including mornings like today when I am just packing to leave > for another 6-8 weeks straight. I'd love to have time to spend in SVN, > which is one of my highest unfulfilled priorities. Maybe tomorrow ... > > --- Noel > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
