[development] API module namespace reservation

Peter Wolanin pwolanin at gmail.com
Fri Aug 31 02:35:43 UTC 2007

This discussion is a bit pointless unless you can elaborate on what
your new module might be doing.

As killes said - if you really think you want it, create a project,
commit some skeleton/"hello world" code, and get back to use when you
have something meaningful to share.


On 8/30/07, Daniel F. Kudwien <news at unleashedmind.com> wrote:
> > Modules are good because they are modular. What is the advantage of putting 6 into one?
> The existent modules do not share the same data, although all of them deal with the same kind of information. AFAIK, most of them implement their own forms to fetch and output similar data and do not interoperate with other modules. Thus, an API(-like) module would not only reserve the generic namespace but also introduce a shared, extensible dataset.
> That was the good news. The bad news is, that there is no code and I will not have time to actually do something within the next weeks, which in turn is the (hopefully reasonable) cause for my question.
> sun

More information about the development mailing list