A new archive, halfway between GNU ELPA and MELPA

[Stefan Monnier]

>> > Coming to a conclusion about that broad question would be work.  If
>> > someone wants to set up and maintain an alternate archive, it would be
>> > useful to do that work.  Until then, we don't need an answer.
>> So, I will have to keep recommending the use of MELPA, I guess.
>> Creating such a new archive without knowing beforehand if it will be
>> accepted in the default value of `package-archive` is much too risky.
> Richard didn't say you actually had to _create_ a new archive, he said
> you (or someone else) just needs to say they _intend_ to, and describe
> the details.

Then I guess we misunderstood each other:

I do want to setup and maintain such an archive, and I'm pretty sure
several other people would be interested in helping.
That's why I asked the question in the first place.

So here's the question again:

What would be required of a new ELPA archive for it be acceptable in the
default value of `package-archives`, given the following following main
constraints:
- It would not require copyright paperwork.
- It would not impose our own coding conventions and would hence happily
  accept `s.el`.
- The understanding that it will significantly reduce the incentive for
  authors to include their package in GNU ELPA.


        Stefan