We need to impose a feature freeze and get the .2 release out. There are a lot of great ideas coming now but we can't incorporate them all into the .2 release.
My role includes collecting all the ideas and helping you reach consensus on their priority for order in which they should be added. Plists certainly deserve consideration. Benjk has a *lot* of excellent points about both plists and the APIs available to implement them. Plists could reduce errors and better define choices for a lot of the basic configuration options. So far nobody that is directly opposed has spoken up. Some other good points have been made about real-time and LDAP and "user objects". These ideas keep popping up. Has anybody given much consideration to what a user object should encompass? Have you written it down anywhere to share? :) I think we all *think* we know what a user should include but somebody should try to write it down so we can give it further consideration. A user may need to be stored in LDAP, relationally or as a flat-file record and be flexible enough to adapt to future needs. We should start considering these questions now in case somebody reaches this point in their branch or wants to run with it. -Nate _______________________________________________ Openpbx-dev mailing list [email protected] http://lists.openpbx.org/mailman/listinfo/openpbx-dev
