On 8/31/21 6:20 PM, sebb wrote:
It is not the goal of the tool to make editing source files easy or even
possible. It's a code analysis tool. Sure, it could link to the file in
the target repository, which may be what you're asking for. But it's not
intended to be a remediation tool.
The easier you make it for projects, the more likely they are to use
it and persuade others to do the same.
I am only suggesting providing links to the Git repo files.
Assuming that the tool has local checkouts of the repo, that should
not be hard to do.
At present not even the Github source repos listed at the head of the
page are linked, and they are already URLs.
I feel like this misses a pretty important aspect of this: It is *NOT*
easy to change these words. Any tools that we provide that encourage
people to simply s/foo/bar/ across a code base are going to create huge
problems.
Consider, for example, the doc that we've provided here:
https://inclusivenaming.org/language/implementation-path/
In particular, there are some word changes that BREAK EVERYTHING.
Encouraging people to do that via a simple click-and-commit interface
would be a HUGE disservice to those projects.
Furthermore, those projects know far better than we do how to make
changes to their code. They know their CI systems. They know their
functional tests, their beta process, their deprecation cycle. It would
be presumptuous for us to provide a tool that says "click this button to
make all of these change!" (Yes, I am exaggerating for effect. Yes, I
know you're not suggesting that.)
Yes, OF COURSE we can improve the tool. Nobody is suggesting that it's a
perfect solution. But trying to make it into a remediation tool is not a
goal, and I seriously question whether it should be a goal, now or ever.
As for "that should not be hard to do", I welcome your advice in how we
would do that, as I wasn't able to figure it out. It was, in fact, hard
to do. Note that this tool is used across many git solutions - it's not
*just* Github. Any solution must work for all possible Git hosting
solutions.
--
Rich Bowen - rbo...@rcbowen.com
@rbowen
