> Personally, I would prefer a simple method, whereby we can specify a feature > and simple tick boxes of which containers support it. And keep adding as > issues are brought up. > That is a non-contentious approach. > > The contentious part is then to classify which ones are 'requirements for > compliance', but would help for 3rd Party container developers as well as > standard component writers. > IMHO, after a large portion of the list has been established, I think we > should just go through the list, and place a majority vote on each one, > provided that each PMC member can be consistent in their own personal > preference (LCD, Merlin-only, Drop-Legacy, or whatever). > When new issues are brought up, they are treated in the same manner.
+1 Whatever is "ticked off" for every container would represent the initial requirements for compatibility. Jonathan Hawkes --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
