Hi all, Sorry for late response, but I wanted others to say first.
I tend to agree that ESME should head for Attic. I feel partially it's my fault - I haven't been able to dedicate ESME as much time as it deserved and as you probably expected from me (while I tried to do so). But my situation is similar to Ethan's and Vassil's - I have two-year-old son and other projects in may daily work, both these things take significant amount of my time. As for current status of ESME - well, from my point of view it's not outdated that much - Lift 2.5 is still RC (it would require quite a big amount of changes though) and I think migration from Scala 2.9.x to 2.10.x is not a showstopper. On the other hand, work only to keep current technology stack up-to-date is not enough. And, as Vassil has already noticed, there's no any active user base of ESME (at least I'm not aware of one... well, maybe besides Jack who is rather developer as far as I understand). It's hard to for me to figure out the reason of it - probably because I joined the project rather late. Hope fork will breathe new life into ESME. Personally, I learned a lot from you guys and appreciate it very much. ESME was good entry point to Scala ecosystem and Lift framework for me too. It was really interesting to participate in mailing list discussion and, honestly, I will miss this communication. At the end, I believe it was worth our efforts and ESME will remain in history as first Apache Software Foundation Scala project, the project I proud to be part of. With kind regards, Vladimir 2013/4/20 Vassil Dichev <[email protected]> > Hi, > > I wanted to take some time to reply, so I didn't reply right away. > > I agree with Dick, Ethan and Anne- it's not likely that we'll find the > time to keep on pushing ESME forward. It has been painful to see > Dick's reports with no progress month after month. I think that if we > haven't found the time for one year, it's not likely that this will > happen in the near future either. So for me retiring ESME is an > expected outcome. > > Of course, as others mentioned, since it is open-source, it is always > possible to revive a project. However note that many components are > outdated already- there have been a couple of Scala releases since the > last ESME commit, Lift is a couple of versions ahead, and most > Twitter-compatibility is outdated- we don't even support OAuth. > > There's also the problem of motivation. Scratching an itch is one > part, but one of the biggest motivators in open-source projects is > having a healthy community of users. I haven't heard requests from > users of ESME for about a year. So of course at least my personal time > is better spent with my 2 kids (and yeah, this is a huge time sink). > > On a positive note, working on ESME has been very beneficial. It > helped me learn Scala and Lift and I'm currently working with social > networks in my day job. I'm sure that the experience has been valuable > for all of us and I'm happy to have worked with all of you. I'm sure > that when the time is right, the ideas might live a second life in > another project. > > Best wishes, > Vassil > -- Best Regards, Vladimir Ivanov
