[development] Jaza's modules are up for adoption
victorkane at gmail.com
Mon Jan 22 10:46:20 UTC 2007
I have offered to help on the Import / Export API. I will be using it
extensively on several projects, have written scripts to get around
its shortcomings, etc.
I am currently analyzing it from a data and control flow point of view.
I have ample software engineering, xml, etc., knowledge, but I am not
yet an expert in Drupal, for which reason it would be foolhardy for me
to offer to maintain it on my own.
Whoever does take the responsibility, however, can count on my active
assistance, and in time, I could maintain it when my Drupal knowledge
deepens with experience and practice.
Whoever that lucky person is, please get in touch with me.
On 1/21/07, Jeremy Epstein <jazepstein at gmail.com> wrote:
> Hi all,
> I am currently the primary (and the only) CVS maintainer of 4 contrib
> 3. Import / Export API <http://drupal.org/project/importexportapi>
> Status: 4.7 version only, is reasonably stable, and has some outstanding bugs.
> Description: this was my Summer of Code 2006 project. It's a massive
> module, and one that I managed to bring up to a stable and usable (and
> quite well-documented) level during SoC, but that I certainly wouldn't
> consider finished by any means. Needs a lot of TLC, and is seeking a
> maintainer who is prepared to give it all their love. In particular,
> needs to be upgraded to Drupal 5, needs serious UI improvement (the UI
> needs a lot more development, and ideally needs to be moved to a
> separate project), needs VERY serious performance improvement
> (currently the memory overhead makes dealing with large datasets quite
> hard - probably the underlying architecture needs serious improvement
> in order to fix this), and needs a number of new features (e.g.
> validation and error-reporting of import data, proper processing
> callbacks to handle special operations for various entities, etc). The
> amount of code is large, and the complexity is high. But it's all
> quite high-quality, and also quite well-documented, so this should
> make the module easier to grok.
> > Many thanks,
> Jeremy Epstein - GreenAsh
More information about the development