Permission to enabling Travis temporarily to add string_decoder

[mcollina]

May I do it? Are there a set of things I need to worry about when doing so?

Repo: https://github.com/nodejs/string_decoder
Issue: nodejs/string_decoder#5
Projects we are testing on travis: https://travis-ci.org/nodejs

I know @Fishrock123 has done this in the past, and we are running several builds on travis.

Ref #68

cc @joyeecheung.

[mcollina]

Another approach we can agree on is that I move the repo to my personal profile, enable it, and then move it back. For #68 to work Travis needs to be enabled externally.

[joyeecheung]

Both SGTM.

[bnoordhuis]

IIRC, Travis wants private (or was it write?) access to the organization. We moved most of the sensitive repos out of the org but e.g. nodejs/security is still a thing.

[targos]

nodejs/security moved to nodejs-private. There is only one sensitive repo left in this organization: the moderation repo.

Edit: there is also nodejs/members

[mcollina]

Do you prefer?

1. enable Travis / set up repo / disable Travis 🎉
2. move repo to github.com/mcollina, set up repo, move repo back to github.com/nodejs 👍

[mcollina]

Alternatively, can someone from @nodejs/build set up a CI environement identical to the one of readable-stream?

(also readable-stream Travis integration is broken as well).

[Trott]

Closing stuff that has been inactive for more than a year in this repo, but if someone plans on picking this up, just go ahead and re-open! No strong opinions from me. Just tidying.