googlearchive / caja

Caja is a tool for safely embedding third party HTML, CSS and JavaScript in your website.
Apache License 2.0
1.13k stars 113 forks source link

How do I contribute a CL? #1970

Open erights opened 9 years ago

erights commented 9 years ago

https://github.com/google/caja/wiki/ContributingCode is obsolete. It still speaks in terms of myvn which is no longer relevant since the switch to github.

kpreid commented 9 years ago

Okay, so we need to update the instructions and create a replacement for myvn. It is possible to use tools/appspot.py directly to do code reviews.

I have been carefully executing a minimum-changes-from-svn workflow, but I'm open to suggestions as to making it more git-ish. The things I didn't want to lose, but don't fit all that well with standard git workflows, is the code review information in the message for every commit, and the linearity of history.

In the absence of such changes, here is what a new myvn-analogue would do, I think:

This would be sufficient to handle the workflow I've been doing manually since the migration. The docs would be updated to explain the above.

I specifically do not want to do GitHub pull requests by themselves because from what I've seen, Rietveld is superior to GitHub's code review support, and I find a lot of value in avoiding unnecessarily nonlinear history. However, we should be able to accept contributions which are in the form of pull requests, which suggests a new myvn feature:

jfparadis commented 8 years ago

Keith:

I've submitted three pull requests (and more are coming). However, I just assumed a standard process, and just noticed last night this note about using an analogous process to myvn.

Would you prefer to get those three pull requests in a single one? Anything other request?

kpreid commented 8 years ago

jfparadis, pull requests are fine for little things from non-members — just don't expect them to get merged unmodified.

Regarding your own pull requests, please sign the Google CLA like the bot comment said.