>> Hi Jose, >> >> On Sat, Mar 08, 2025 at 02:17:52PM +0100, Jose E. Marchesi wrote: >>> > Since you already have a fork on the (experimental) forge we could >>> > also move your fork under https://forge.sourceware.org/gcc that way >>> > you can experiment with merge requests if you like. Even if all your >>> > patches still go to the algol68 list first. >>> >>> I am all for continuing using the forge if it is useful for the >>> experiment. >> >> I think it would. Also I think it would be fun to have one of the >> oldest language frontends use the most modern development environments >> :) > > :) > >>> Let's see. Right now the resources we are using are: >>> >>> Website: https://gcc.gnu.org/wiki/Algol68FrontEnd >>> Mailing list: algo...@gcc.gnu.org >>> Bugzilla: https://gcc.gnu.org/bugzilla >>> Git repo: https://forge.sourceware.org/jemarch/a68-gcc (branch a68) >>> >>> If I understand you suggestion right, we would simply move the git repo >>> to: >>> >>> https://forge.sourceware.org/gcc/algol68 (branch a68) >> >> Yes. To do that you should become a member/owner of the gcc >> organization. https://forge.sourceware.org/org/gcc An existing >> member/owner should be able to accept you. >> https://forge.sourceware.org/org/gcc/members > > Ok. I have asked in IRC. Hopefully someone can add my user to that > list.
This is done. >> Then you can move your repository/fork to the gcc organization by >> going to the existing repository Settings at >> https://forge.sourceware.org/jemarch/algol68/settings Scroll down to >> "Danger zone" and click on "Transfer ownership" The new owner would be >> gcc. It does need to be accepted by one of the gcc Owners. > > Note that the repo is currently named jemarch/a68-gcc, but I see all the > repos under the gcc organization start with "gcc": > > gcc-mirror > gcc-wwwdocs-mirror > gcc-TEST > gcc-wwwdocs-TEST > > Probably it is a good idea to be consistent, so I will move the > jemach/a68-gcc repo to gcc/a68-gcc and then rename it to gcc/gcc-a68. This is also done. The transfer and rename worked perfectly well. The forge is even able to redirect from jemarch/a68-gcc to gcc/gcc-a68 by itself. >> Now you can setup a Team inside the gcc organization of people who >> help maintain this repository. You can do this by either creating a >> list of colaborators or pick an existing gcc team at >> https://forge.sourceware.org/gcc/algol68/settings/collaboration > > Which one is the default group of people who can admin the repo? The > members of the gcc organization? jwakely created a Team in the gcc organization to administer the gcc/gcc-a68 repo. >> (BTW. This would also be a good time to set the Default branch to >> a68.) > > Good idea. I just did that in jemarch/a68-gcc > >>> Then people could fork it, send patch series based on their forks to be >>> reviewed in the mailing list, get feedback, do corrections, rinse and >>> repeat. Then when the series has been OKed a PR can be made and the >>> maintainer just merges it. Is this the idea? >> >> Yes, that would be the traditional email workflow extended to the >> forge. Note that (very unforge like) you (the algol68 team members) >> can also directly push to the repository through ssh sidestepping >> creating a merge request if that is how you want to do things. > > Sounds good! > >>> Is it possible to get emails sent to the mailing list when merges >>> happen, merge requests are issued, etc? >> >> People can get emails by clicking the "Watch" button on the >> repository. > > I think thats probably enough for now. If somebody sends a merge > request via the web, some admin can contact the person asking her to > send a patch series to the mailing list for review. > >> We could try creating a "fake" account that has the mailinglist as >> email address. But I am a little hesitant experimenting with "fake" >> users. It might be good if the owner of a repo could add an email >> address to the Watch list. Maybe this should be a new feature request >> to Forgejo.
