On Mar 11, 2025, Richard Stallman <r...@gnu.org> wrote: > However, it also requires the user to have per own repo which is > accessible over the net. That would tend to force the user to set up > per own server (not easy), or use a service comparable to github.
It's not that hard, really. Jami sets up and shares a GIT repository for each conversation. It would be really cool if we could encourage people who wanted to share code but who don't have their own server to start a GNU Jami conversation, and push the code there. I wonder if Jami can share arbitrary git repos, or if it's limited to a narrow set of git repos that Jami creates and manages itself. > What about github-style centrally handled pull requests? In terms of > how they distribute the users' proposed changes, do they work like the > mailing list, or like pre-github pull requests? github hosts users' repositories, and AFAIK pull requests point at them. >> Taking pull requests from committers through git hooks would make our >> repositories contain the submissions from committers. They're >> presumably under an agreement about what they can and must not push >> there. The risks are no different from those that current committers >> face. > Since I do NOT understand any of these proposals in any detail, > it is hard for me to tell whether you are describing one proposal > in multiple ways. > For instance, is "through git hooks" another way of describing this > option? >> 2. Some projects introduced code reviews integrated with git, so that >> frequent contributors (with write access to the repository, but not >> blanket commit privileges, > I suspect yes, but I can't be sure. Those weren't exactly proposals, but various potential meanings of 'pull requests', that needed clarification on what precise feature was being requested of Savannah. But yeah, there's a large overlap between that code-review pull-request model and the git hooks that could be used to create and maintain a PR database by detecting pushes to branches that abide by certain branch-name conventions. This requires submitters to already have git push privileges, so it's not a general pull request feature. OTOH, account creation for submission of bugs (or PRs) *could* grant push privileges onto such branches, or perhaps onto a separate repository created to this end. There are many ways to go about it, and I wasn't (yet) trying to suggest how to go about implementing it before knowing what it was that was being asked for. -- Alexandre Oliva, happy hacker https://blog.lx.oliva.nom.br/ Free Software Activist FSFLA co-founder GNU Toolchain Engineer Learn the truth about Richard Stallman at https://stallmansupport.org/
