Ted,
Thank you for being open to these ideas and encouraging ways for coding environments appealing to contributors to work together.
I would be wary of allowing any elements of the project to begin finding new or additional platforms to call home - maintaining the process in one place should be a priority over allowing additional forks to be scattered around various development environments; even with callbacks to help close issues, refer them to existing groups, etc.
Personally, I would encourage any targeted development or forks performed elsewhere to be submitted into the GitLab repository maintained by the Inkscape project, by the author(s) of such work, even if can or does exist elsewhere as a matter of preference.
Best,
Nathan
Sent from my iPhone
On Jun 10, 2022, at 8:41 AM, Ted Gould ted@gould.cx wrote:
K, it seems like there is stuff we need to setup, but people are generally happy with the idea of trying it out. I'll try to figure out the details in the next bit (baseball tournament this weekend, see how far the kid's team goes to how much time I have 😉)
Ted
On Jun 8 2022, at 10:48 pm, Ted Gould ted@gould.cx wrote: Howdy folks,
I was looking at our repo on Github, and frankly, I like it. But, I know for some employers they're rating potential employees on their Github profiles (I don't agree with this, but it happens) and so not having the commits in Github reduces the exposure for that work. This probably effects our "interns" from Google SoC and Outreachy the most.
For reference: https://github.com/inkscape/inkscape The problem we've had in the past is that when we had the repo on Github, people would fork it and create Pull Requests that no one would see or triage. Which would frustrate folks (understandably) and look poor on the project.
The idea that I had is that we take the Inkscape repo, and we make a branch "github" that has the same README and graphic that is currently up on Github. We push the full Inkscape repo, but then set the default visible branch to the "github" branch. So anyone going to the repository sees exactly the same thing.
Github doesn't seem to have a mechanism for disabling PRs, or forks. So we're relying on people actually reading the text. But I was curious what folks thought about the idea.
Ted _______________________________________________ Inkscape Devel mailing list -- inkscape-devel@lists.inkscape.org To unsubscribe send an email to inkscape-devel-leave@lists.inkscape.org