Re: NonGNU ELPA and release frequency

[Antoine Kalmbach]

Ivan Yonchovski <yyoncho@gmail.com> writes:

>
>> Each package will be developed in a repo somewhere else.  Some will be
>> on Savannah.  Some will be elsewhere (but insisting that maintenance
>> not require running nonfree JS code).
>
> So, if someone wants to be in NonGNU elpa should not be using github? If
> this is the case then why it is fine for ELPA package to be in github
> but it won't be fine for NonGNU ELPA?

I suppose maintenance here means that the work required by the NonGNU
ELPA maintainers means running nonfree JS. As far as I know, the only
nonfree JS for Github is needed during the signup process, but pulling
from upstream repositories hosted on Github requires no JS, and even
browsing Github works with LibreJS, the signup process is the
problematic part.

For reference, `grep -c github` on
http://elpa.gnu.org/packages/archive-contents returns 82, so a
significant amount of external packages in GNU ELPA list Github as their
:url. 

-- 
Antoine Kalmbach