"I'm totally cool with the idea of code review for Gadgets & so forth, just not using Gerrit. We considered it for Scribunto (and heck, I wrote half of a proof of concept) but shot it down because the idea totally sucked."
Chad, can you expand on that statement. I've been toying for some time with writing something that allows documentation to be synced both ways. E.g. for hooks and variables and what not. My simplistic toy example had a 1:1 link but I've been trying to figure out how to make it more complex. (Ideally this would also allow documentation to be linked to a branch and thus we then have versioned documentation)
~Matt Walker Wikimedia Foundation Fundraising Technology Team
On Wed, Dec 11, 2013 at 11:21 AM, Chad innocentkiller@gmail.com wrote:
On Wed, Dec 11, 2013 at 11:04 AM, Jon Robson jdlrobson@gmail.com wrote:
Many a time I've talked about this I've hit the argument that gerrit is confusing to some users and is a barrier for development, but this is a terrible unacceptable attitude to have in my opinion. Our end users
deserve
a certain standard of code. I'm aware using a code review process can
slow
things down but I feel this is really essential. I for one greatly
benefit
from having every single piece of my code scrutinized and perfected
before
being consumed by a wider audience. If this is seen as a barrier, someone should investigate making it possible to send wiki edits to Gerrit to simplify that process.
Sending wiki edits to Gerrit for review? Absolutely not.
I'm totally cool with the idea of code review for Gadgets & so forth, just not using Gerrit. We considered it for Scribunto (and heck, I wrote half of a proof of concept) but shot it down because the idea totally sucked.
-Chad _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l