You go, Michael. :-) I know how much time it takes to get something to work in your spare time.
That reduces the amount of time spent on someone else's mess to nil. BTW: Speaking of spending free time on non-paying gigs; I'm almost done with the re-factor of my message passing core "Dendrite". Whenever you're the designer, programmer and project manager it's really difficult to force yourself not to implement that one last cool feature or patch and bottle up the release. Jim Burnes On Sat, Jan 30, 2010 at 7:06 AM, Michael Sparks <[email protected]> wrote: > Hi, > > > Last year I fought the above branch for many months seeking to make it > something that a) worked b) was usable. > > I have decided, regretfully, to cease spending any of my time on it. > > Rationale: > * In practical terms it was sucking up far too much of my time, since > the > code was non-idiomatic for either python or Kamaelia. > > * It didn't work, and still largely doesn't work. > > * It provided no way of testing the system as a whole, nor in part. > > * It was not documented, or where documentation was included it was > either > unclear, patchy or wrong. (no docs are better than broken docs) > > * The approach taken to inclusion of a seperately library appeared to be > copy and paste, rather than wrap and use. Thereby making the code > significantly more fragile. This goes rather heavily against > Kamaelia's > approach of modularity. > > * The coding style is extremely monolithic, rather than modular. Kamaelia > systems are generally testable in small fragments. > > Crucially though: > * The original developer dumped the code and ignored it. (This isn't > necessarily a problem for code that is documented and works, if the > code is useful enough - see above on this point). > > * The original branch proposer did not assist in fixing the code, nor > documenting it. > > * It is largely code for its own sake - it has no user & no potential > user. > > For these reasons I'm rejecting the branch. > > I should have done this 4 months ago when I actually stopped working on > fighting this branch, but like many people I don't like giving up on > something. > > Also, as many people know, much of my development of Kamaelia itself as a > project is now done in my own time, so the time I have to fight LARGE > branches > which don't work, aren't documented, aren't maintained, and don't have a > developer taking ownership of their own code, is minimal. > > As a result, I've decided that the potential benefits of working with this > code > to get it working are outweight by the time cost incurred (to me, > personally) > of doing so. > > I'm sorry to the original developer who will read this and probably be > disappointed, but if you don't care enough to make your code work > and use it, I don't have to either. > > Regards, > > > Michael. > > -- > You received this message because you are subscribed to the Google Groups > "kamaelia" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<kamaelia%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/kamaelia?hl=en. > > -- You received this message because you are subscribed to the Google Groups "kamaelia" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/kamaelia?hl=en.
