One of the points of concern, which you had noted in your mail, was the availability of source code. Since extensions are 3rd party (and, I may be wrong here), how can it be made binding that the source code be available ?
On Mon, Apr 6, 2009 at 5:03 PM, Martin Hollmichel <[email protected]> wrote: > Extensions should: > > * be localized A couple of points: - which l10n infrastructure would be used - who manages the l10n of the appropriate extension ie. is it more ad-hoc need based or, projectized > * documented, online help available Any special reason to not explicitly mandate off-line help ? > * QAd, Feature must be complete and without serious bugs What would be considered as a 'stop ship' or, 'block release' for an extension ? > * consistent with the UI of the core product and other bundled > extensions The latter part puts a demand on extension provides to collaborate based on some Interface Guidelines. Do such guidelines already exist specific to extensions ? > * does not need limited UI resources, and is not considered core > functionality at the same time > * a11y compliant Any specific test cases that can check for a11y compliance ? -- You see things; and you say 'Why?'; But I dream things that never were; and I say 'Why not?' - George Bernard Shaw Sent from Pune, MH, India --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
