Tom Morris

We require developers to respect licenses and intellectual property rights and only submit code that they own or have the rights to. The DCO is a lightweight mechanism for them...

Given the current design, the scope of this operation is all rows in the project. Because of they way the operation works, sometimes putting the split value into an existing...

I've reverted the title and labels given the change in focus. Documentation is now in OpenRefine/openrefine.org#308

When I adjusted the labels, I also removed the "Good First Issue" label. @dauinh if you were being guided by that label, you may want to reconsider. From an implementation...

One other wrinkle is that the current behavior will reuse empty cells in the current record to split into in lieu of adding a new row. We need to decide...

@wetneb What do you think of this proposal? Any preference for how the numeric range is divided? In addition to the two options above (10^3 and 2^5), we also have...

@wetneb The project metadata already includes both the creation time and the last updated time. This is intended to provide a hint to the user in case the metadata is...

I've adapted this to the `master` branch and split it into two pieces: API (#6796) & Implementation (#6797) which supersede this PR. Thanks again for your contribution @karindev ! I've...

> This is a request to implement that command into the core product using the same implementation as currently in the gokbutils That implementation uses [MassRowChange](https://github.com/OpenRefine/OpenRefine/tree/6ba044c4e39d49b0dd4221f4b9a9328e5c71117c/main/src/com/google/refine/model/changes) which is a pretty...

That looks great. I didn't review in detail, but it looks like it is basically done except for the addition of unit tests which doesn't seem like enough work to...