Re: Midgard in the sky with ... PEAR?

Hi, everyone,

In nutshell, what I am looking for is: - Some discussion on whether we are welcome around here ;) - are Midgard-specific modules welcome? - should PEAR have a Midgard category? - or the Midgard community have a separate PEAR server users can configure as a secondary source? (if PEAR tools allow)

I'm a newbie to the PEAR community, so if my opinions are not accurate, that's why. Having said that, it seems to me that classes submitted to PEAR ought to have some level of generic-ness to them. E.g., when it comes to content management and delivery, there are sure to be many things common to Midgard and (e.g.) Drupal, PHPNuke/Postnuke, and so on, such as:

    user authentication
    page-level protections
    revision control
    hierarchical representations (e.g. categories of content)
    etc.

Some of these items are covered by current PEAR classes ("Auth" and "Tree" come to mind) but others are not (content storage and revision control). Perhaps one way to start would be to abstract content-management kinds of stuff into a foundation class or set of classes that anybody can use; Midgard could then extend and enhance the foundational class(es) for its own purposes, as could Drupal or RandomProjectX. Hope this makes sense. (Please note that I do not speak for PEAR; list-readers, please correct me if I am wrong.) -- pmj