> From: Peter Donald [mailto:[EMAIL PROTECTED] > > On Sat, 15 Mar 2003 00:09, Leo Sutic wrote: > > Unlikely in the sense that we're getting rid of parts of Avalon that
> > are out of scope. > > yep - Why add a dependency on something scheduled to be culled ? As a stepping stone to Commons CLI. 1. Keep deps inside Apache. 2. Switch to Commons CLI. There appears to be no technical reasons not to to the switch. Your objections have been largely invalidated since they were made - Commons CLI has evolved. > > So, I don't get this maintenance part. If I leave it in a > stable state > > - and coder X goes in a breaks it, shouldn't then coder X fix it? > > They should fix it (but history shows that does not happen). However you > should also be monitoring the change and making sure all the changers done by > coder X do not inadverantly break something (ie coder X may not know > something is broken) and if coderX skimps on some of the work (docs, unit > tests, etc) then you have to be willing to step up and do something about it. What you're asking me to do is to monitor the Phoenix project. That is impossible - I don't use Phoenix, nor do I intend to. Unless I test the project every day, I can not be a good monitor and would not do my duty according to you, and according to my idea of responsibility. What I offered to you was help in making a change that I believe is beneficial to Avalon as a whole - I did not offer to become a Phoenix developer. /LS --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
