--
You received this message because you are subscribed to the Google Groups "akara" group.
To post to this group, send email to ak...@googlegroups.com.
To unsubscribe from this group, send email to akara+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/akara?hl=en.
Folks, this answer is relevant to this thread, and the other ones on Amara.This week has been crazy as I battle deadlines and prepare for a big trip to Geneva, to present and refine a system we're preparing for the WHO. And yes, that software uses Amara and Akara. I just haven't had the time to work on docs as I'd promised, nor even to keep up with email, as you can see from my late response here.The bottom line is that unfortunately, It's been really hard to find the time to do the usual project leader stuff for Amara and Akara, including advocacy. My time is far too packed in *using* them, including in some very high profile projects. See:So if the ultimate test of any software (open source or no) is "did it scratch the creator's itch?" then Amara and Akara have passed that with flying colors, and there is a bright future for these. But that's only my perspective (and maybe also that of Mark Baker, who also uses Akara heavily). That said, I freely admit these projects need work. Amara needs work on tests and docs. Akara's tests are in pretty good shape, but it needs help with docs. I'm seriously considering the port of both of these to both PyPy and Python 3.3+, the former because I think it will allow us to eliminate the C code and still boost performance, and the latter because Unicode support has finally been revamped (*long* overdue in Python). But even this is a tricky matter considering that PyPy is inching towards Python 3.x support, but not quite there yet.So I think the only way I can answer the question about whether anyone else should use Amara and Akara is to say:I use them. They work very well for me. I acknowledge they also still need work (and I'm grateful for any help in that work), and I am still committed to them, both in minor fixes and improvements as well as in major evolution, but I'm dealing with limited bandwidth to donate to open source software. You'll have to make your own decision based on that input.I'm sure everyone will have dozens of suggestions for breaking the logjam, but please couple any such points with concrete ideas that are compatible with the reality of my limited time, for now (as a company Zepheira is working on developments that might help my workload in the future).
My plans are to give some time to Amara/Akara projects this summer, so
I could work on docs and test and maybe (Sylvain? ) Amara could grow
to a beta release.
Dear Uche,
Before we get too much in the weeds about schedules and goals and resources, I just want to point out two things that this project has going for it.
First, there is already a lot of energy around this project. In addition to many people using this code in production, one person is adding HTML processing and web scraping support, and Uche himself is talking about a port to PyPy and Python 3.3+. These are huge undertakings for such a small community. Building this level of commitment and excitement is one of the hardest things in growing a software community.
Second, in getting volunteer work, you usually have to provide (very) little structure in order to get a large return. Capturing the development energy outlined above in a few small paragraphs in the Progress section of the website could bring out a lot of developer help from companies or individuals who initially were scared off by the alpha designation. A few minutes spent describing in broad terms what help we are looking for could pay off in spades. Since it’s such little work, it’s worth a shot before we worry ourselves with really major changes to this project.
Just some thoughts,
Rocco