[meego-packaging] rejections FAQ - un-spectacle package isn't allowed

[fathi.boudra at Nokia.com]

>>> Ok, lets start and we should move this to the wiki:
>>> - spectacle is not mandatory
>>> - spectacle is recommended for simple packages
>>> - packager should not change packaging format randomly.
>>>  - You need to be the main maintainer
>>>  - You need to have a valid reason why not to use the yaml format
>>
>> Do you mean:
>> - main maintainer and valid reason
> 
> Yes. Because "main" maintainers change all the time and you are not the
> owner of the package even if you are the maintainer.

It isn't so good then.
I don't see so much turnovers in the responsibility of a package.

What about rule precedence question?
> Let's say a maintainer/packager provides YAML files for most packages ;),
> it means on the next package update round, you don't have a choice anymore.
>
> The package have been spectaclified and the maintainer/packager has enforced
> spectacle usage. Which rule take precedence?

Cheers,

Fathi