tor, 28,.04.2005 kl. 08.42 +0100, skrev Michael Ross (PCT North West): > If that is going to be the best solution then that may be the best way to go > (not sure our budget along could stretch to that though, so we would be > looking for additional sponsors). > > From my point of view, if its functionality matches what we have now as well > the other bits and pieces that have already been mentioned, that > aesthetically it works the same way (retraining staff is and expensive and > time consuming business), that its code is based on a platform that it can > evolve with and that migrating from one to the other can be made relatively > simple, then this might be the best all round solution. > > What would you all think of a completely rewritten Aegir - Aegir 2.0?
Hmm, your users mainly use the topic/article part, then I got a suggestion: 1. Make a new "Aegir AIS" style that makes AIS look like aegir. 2. Make a new "base content" component that handles topics that have noe defined component (for migration of existing data). 3. Start defining what other parts of Aegir are most sorely needed and migrate them over bit by bit. Tarjei > Mike. > > > -----Original Message----- > From: Torben Nehmer [mailto:[EMAIL PROTECTED] > Sent: 28 April 2005 08:26 > To: [email protected] > Subject: Re: [midgard-user] Future Aegir Development > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > - --Michael Ross (PCT North West) wrote on 2005-04-28 09:22: > > I agree that everything should be under one roof so to speak - a complete > > administration and editing package. For Aegirs future development (and > > survival), it must keep up to date with the state of Midgard/MidCom to > > enable future developments to be made easily. Developments at the moment > > seem to be like trying to get a square peg into a round hole rather than > an > > easy blending of the base Midgard/Midcom platform. > > As far as I know the Aegir codebase, it is not possible to integrate it > directly > and, which is most important, cleanly into MidCOM. MidCOM is its own > framework, > and the only thing Aegir can do is *duplicate* the functionality. Unless you > do > a complete rewrite you cannot *integrate* with the functionality, which is a > very important (and nasty) difference. > > Exactly this is the reason why I propose to simply drop Aegir to a > Maintain/Bugfix only state and to build a new solution on top of MidCOM, > which > makes real use of the framework, instead of trying to rebuild what is > already there. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Tarjei Huse <[EMAIL PROTECTED]> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
