Folks, I'm happy to announce that we now have an experimental Gitlab instance for Wine development. Many thanks to everybody who worked on setting this up, notably Arkadiusz Hiler, Derek Lesho, Jeremy Newman and Jeremy White. You can find it at: https://gitlab.winehq.org You should be able to register an account and start playing with it. Currently it contains projects for the main Wine tree, the WineHQ tools, and the WineHQ website. You should be able to fork any of these trees and submit merge requests. We have added a mail gateway that will take merge requests and comments posted on Gitlab, and forward them to wine-devel, so that the full project activity will still be visible on the mailing list. Most actions can also be accomplished from the command line, with the help of tools like https://github.com/profclems/glab or https://github.com/zaquestion/lab. There's also a wine-demo project that you can use as a playground to test sending merge requests or debug your scripts without messing up the real project. wine-demo activity is not forwarded to wine-devel, so feel free to make mistakes there. Note that no decision has been made to switch to Gitlab yet. This is still an experiment, and if it turns out that it doesn't work for us, we'll scrap it and try something else. That said, I do think that it has the potential to be a very nice improvement, so I'll ask everybody to give it a chance. Please try it to see if it can be made to fit with your workflow, and report what works/doesn't work for you. I'll send a separate email to describe what I expect that the final workflow would look like. Looking forward to your feedback... -- Alexandre Julliard julliard(a)winehq.org
On 4/25/22 12:01, Alexandre Julliard wrote:
Folks,
I'm happy to announce that we now have an experimental Gitlab instance for Wine development. Many thanks to everybody who worked on setting this up, notably Arkadiusz Hiler, Derek Lesho, Jeremy Newman and Jeremy White.
You can find it at: https://gitlab.winehq.org
You should be able to register an account and start playing with it. Currently it contains projects for the main Wine tree, the WineHQ tools, and the WineHQ website. You should be able to fork any of these trees and submit merge requests.
We have added a mail gateway that will take merge requests and comments posted on Gitlab, and forward them to wine-devel, so that the full project activity will still be visible on the mailing list. Most actions can also be accomplished from the command line, with the help of tools like https://github.com/profclems/glab or https://github.com/zaquestion/lab.
There's also a wine-demo project that you can use as a playground to test sending merge requests or debug your scripts without messing up the real project. wine-demo activity is not forwarded to wine-devel, so feel free to make mistakes there.
Note that no decision has been made to switch to Gitlab yet. This is still an experiment, and if it turns out that it doesn't work for us, we'll scrap it and try something else.
That said, I do think that it has the potential to be a very nice improvement, so I'll ask everybody to give it a chance. Please try it to see if it can be made to fit with your workflow, and report what works/doesn't work for you.
I'll send a separate email to describe what I expect that the final workflow would look like.
Looking forward to your feedback...
To clarify, this is "effective immediately", i.e. right now patches submitted either via gitlab or via wine-devel will be reviewed and committed, right?
Is it possible to add support for logging in with GitHub or main GitLab account? For example, https://gitlab.gnome.org/ has those options.
Biswapriyo Nath <nathbappai(a)gmail.com> writes:
Is it possible to add support for logging in with GitHub or main GitLab account? For example, https://gitlab.gnome.org/ has those options.
I've enabled GitHub logins, can someone verify that it works? If it works we can add other providers. -- Alexandre Julliard julliard(a)winehq.org
I get „your account is pending approval from your Gitlab administrator „, there I think it works.
Am 26.04.2022 um 11:50 schrieb Alexandre Julliard <julliard(a)winehq.org>:
Biswapriyo Nath <nathbappai(a)gmail.com> writes:
Is it possible to add support for logging in with GitHub or main GitLab account? For example, https://gitlab.gnome.org/ has those options.
I've enabled GitHub logins, can someone verify that it works? If it works we can add other providers.
-- Alexandre Julliard julliard(a)winehq.org
I get same error as following. "Your account is pending approval from your GitLab administrator and hence blocked. Please contact your GitLab administrator if you think this is an error."
Alexandre Julliard <julliard(a)winehq.org> writes:
Biswapriyo Nath <nathbappai(a)gmail.com> writes:
Is it possible to add support for logging in with GitHub or main GitLab account? For example, https://gitlab.gnome.org/ has those options.
I've enabled GitHub logins, can someone verify that it works? If it works we can add other providers.
I've now added Gitlab.com and Google providers. For people who would like to use this but have already created an account, you can connect it under Edit Profile / Account / Social sign-in. -- Alexandre Julliard julliard(a)winehq.org
Zebediah Figura <zfigura(a)codeweavers.com> writes:
On 4/25/22 12:01, Alexandre Julliard wrote:
Folks, I'm happy to announce that we now have an experimental Gitlab instance for Wine development. Many thanks to everybody who worked on setting this up, notably Arkadiusz Hiler, Derek Lesho, Jeremy Newman and Jeremy White. You can find it at: https://gitlab.winehq.org You should be able to register an account and start playing with it. Currently it contains projects for the main Wine tree, the WineHQ tools, and the WineHQ website. You should be able to fork any of these trees and submit merge requests. We have added a mail gateway that will take merge requests and comments posted on Gitlab, and forward them to wine-devel, so that the full project activity will still be visible on the mailing list. Most actions can also be accomplished from the command line, with the help of tools like https://github.com/profclems/glab or https://github.com/zaquestion/lab. There's also a wine-demo project that you can use as a playground to test sending merge requests or debug your scripts without messing up the real project. wine-demo activity is not forwarded to wine-devel, so feel free to make mistakes there. Note that no decision has been made to switch to Gitlab yet. This is still an experiment, and if it turns out that it doesn't work for us, we'll scrap it and try something else. That said, I do think that it has the potential to be a very nice improvement, so I'll ask everybody to give it a chance. Please try it to see if it can be made to fit with your workflow, and report what works/doesn't work for you. I'll send a separate email to describe what I expect that the final workflow would look like. Looking forward to your feedback...
To clarify, this is "effective immediately", i.e. right now patches submitted either via gitlab or via wine-devel will be reviewed and committed, right?
Yes. Merge requests may take more time to go in though, since the tooling on my side is still a work in progress. -- Alexandre Julliard julliard(a)winehq.org
Is the mail gateway set up correctly? It looks like there's been at least one patch posted to Gitlab that hasn't come through: https://gitlab.winehq.org/wine/wine/-/merge_requests/1
On 4/25/22 14:40, Zebediah Figura wrote:
Is the mail gateway set up correctly? It looks like there's been at least one patch posted to Gitlab that hasn't come through:
No, there have been some teething pains with shifting away from wine-demo. Working on it; will hopefully start working... Cheers, Jeremy
participants (5)
-
Alexandre Julliard -
Biswapriyo Nath -
Jeremy White -
Robert Wilhelm -
Zebediah Figura