Paul Querna wrote: > [snip] > I have mixed feelings about embedding vendor names in our filenames, or > API names. (gdata vs google vs some-generic-standard-paths-name) >
Yes, that is a concern. Is there an alternative naming approach that would work better? I honestly do not know. > But, otherwise, I think it generally makes sense, as long as the vendor > is good about publishing how their extension works in a publicly > accessible document. > We can make a stable, publicly accessible document a minimum requirement for allowing any vendor-specific extension code into the project. - James
