SES Canonical Home

[Kris Kowal]

I have an ambition to make SES accessible to the Node community.

This would involve adding a Node module entry-point, a package.json
file, and publishing it to NPM. Ideally, it would also involve adding
a README.markdown and posting it to Github as well, since that’s where
the Node community hangs.

This raises two issues. How can I submit upstream changes, and what is
the canonical repository for SES and friends?

From a brief conversation with Mark, it seems that the canonical
location is in flux, since ES5-Lab and Caja have forked revisions,
with the Caja version being more advanced. In both cases, it is
effectively a submodule. I propose that it have a home of its own.
This also entrains the issue of which repositories are covered by the
Google Vulnerability Rewards Program. Mark has made a home for Dr. SES
on Google Code with Git, which is a candidate. I like the idea of
using Git since it makes mirroring on Github trivial. I also advocate
making the home on Github since that’s where the developer community
lives.

Kris Kowal

[๏̯͡๏ Jasvir Nagra]

hi Kris,

We're super stoked about this idea and especially about anything we can do to make the integration with node possible and secure.  This also brings to head some concerns we've had about maintaining multiple (some stale) copies of ses.  Give us a couple of days to consolidate and I'll update this thread with how I reckon we should proceed with making the ses portion easily available on github while still being able to receive patches from the community and security updates in a timely fashion.

jas