Re: [PATCH xf86-video-ati] Update README for gitlab migration
On 2018-11-18 9:22 p.m., Alan Coopersmith wrote: > Signed-off-by: Alan Coopersmith > --- > > Unlike the similar updates to the other Xorg project README's, this leaves > your bugzilla link in place, as well as the instructions to submit patches > to your mailing list instead of suggesting gitlab merge requests. Pushed, thanks Alan! -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer ___ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx
[PATCH xf86-video-ati] Update README for gitlab migration
Signed-off-by: Alan Coopersmith --- Unlike the similar updates to the other Xorg project README's, this leaves your bugzilla link in place, as well as the instructions to submit patches to your mailing list instead of suggesting gitlab merge requests. Makefile.am | 2 +- README | 25 - README.md | 19 +++ 3 files changed, 20 insertions(+), 26 deletions(-) delete mode 100644 README create mode 100644 README.md diff --git a/Makefile.am b/Makefile.am index b8d99f32..d14ed8f9 100644 --- a/Makefile.am +++ b/Makefile.am @@ -31,4 +31,4 @@ INSTALL: ChangeLog: $(CHANGELOG_CMD) -EXTRA_DIST = ChangeLog INSTALL +EXTRA_DIST = ChangeLog INSTALL README.md diff --git a/README b/README deleted file mode 100644 index bf7c6407.. --- a/README +++ /dev/null @@ -1,25 +0,0 @@ -xf86-video-ati - ATI/AMD Radeon video driver for the Xorg X server - -Patches and questions regarding this software should be directed at the -amd-gfx mailing list: - -https://lists.freedesktop.org/mailman/listinfo/amd-gfx - -Please submit bug reports to the Xorg bugzilla: - - https://bugs.freedesktop.org/enter_bug.cgi?product=xorg&component=Driver/Radeon - -The master development code repository can be found at: - -git://anongit.freedesktop.org/git/xorg/driver/xf86-video-ati - -https://cgit.freedesktop.org/xorg/driver/xf86-video-ati - -For patch submission instructions, see: - -https://www.x.org/wiki/Development/Documentation/SubmittingPatches - -For more information on the git code manager, see: - -https://wiki.x.org/wiki/GitPage - diff --git a/README.md b/README.md new file mode 100644 index ..7c9925c7 --- /dev/null +++ b/README.md @@ -0,0 +1,19 @@ +xf86-video-ati - ATI/AMD Radeon video driver for the Xorg X server +-- + +Patches and questions regarding this software should be directed at the +amd-gfx mailing list: + + https://lists.freedesktop.org/mailman/listinfo/amd-gfx + +Please submit bug reports to the Xorg bugzilla: + + https://bugs.freedesktop.org/enter_bug.cgi?product=xorg&component=Driver/Radeon + +The master development code repository can be found at: + + https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati + +For patch submission instructions, see: + + https://www.x.org/wiki/Development/Documentation/SubmittingPatches -- 2.15.2 ___ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx
Re: gitlab migration
On Mon, 2018-06-11 at 12:33 +0200, Michel Dänzer wrote: > As the maintainer of xf86-video-amdgpu and -ati, I'm fine with migrating > these to GitLab for Git and patch review. > > However, I'm not sure what to do about bugs/issues. My first thought was > to allow creating new issues in GitLab and disable creating new reports > in Bugzilla, but not to migrate existing reports from Bugzilla. However, > it still happens fairly often that a report is initially filed against > the Xorg drivers, even though it's actually an issue in the X server, > Mesa or the kernel (old habits die hard...). Therefore, I'm inclined to > stick to Bugzilla until at least the X server and Mesa have moved to > GitLab for issue tracking, to hopefully allow moving such misfiled issues. I've hacked up the migration script to allow moving individual issues by bug number instead of matching a whole product/component [1]. This has already been useful to sort out some of the junkdrawer components like App/Other. Running the script does require someone with supercow powers on both sides, but I'm happy to do so as needed. With that in mind, I think it may be time to enable issues and merge requests for xserver, and disable the remaining (server) bz components for new issues. Any objections? [1] - https://gitlab.freedesktop.org/freedesktop/bztogl/merge_requests/1 - ajax ___ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx
Re: gitlab migration
> "DS" == Daniel Stone writes: DS> No need to test; it's guaranteed to fail since we require Recaptcha DS> for login due to massive spam issues. Which is of course grossly unethical and malicious and should never be used by any site, under any circumstances. If some sort of captcha is ever desired, it always must be something which works with non-ecmacsipt, TUI browsers. A simple math question with a simple html text box for the answer is OK. Or a technical question specific to the given project. But never goog's malicious crap. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6 ___ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx
Re: gitlab migration
Daniel Stone : > > Hi Sylvain, > > On 12 June 2018 at 13:38, wrote: > > On Tue, Jun 12, 2018 at 12:34:31PM +0100, Daniel Stone wrote: > >> GitLab has a pretty comprehensive and well-documented API which might > >> help if you don't want to use a web browser. There are also clients > >> like 'lab': https://gitlab.com/zaquestion/lab which provide a good CLI > >> interface. > > > > Those "web APIs" usually require the use of an heavy javascript browser for > > authentification or "app authorization". > > > > That said, I could not even create an account with a noscript/xhtml basic > > browser (if you want to test that, install the famous noscript module with > > an > > empty "white list" in firefox or chromium, or use lynx or links or w3m). > > No need to test; it's guaranteed to fail since we require Recaptcha > for login due to massive spam issues. Have you tested whether Chinese or Russian users can login or sign up? Asking because Recaptcha was blocked for quite a long time by Russian authorities. Cannot test the situation myself now, because I emigrated several months ago. -- Alexander E. Patrakov ___ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx
Re: gitlab migration
Daniel Stone : > > Hi Alexander, > > On 12 June 2018 at 14:53, Alexander E. Patrakov wrote: > > Daniel Stone : > >> > That said, I could not even create an account with a noscript/xhtml basic > >> > browser (if you want to test that, install the famous noscript module > >> > with an > >> > empty "white list" in firefox or chromium, or use lynx or links or w3m). > >> > >> No need to test; it's guaranteed to fail since we require Recaptcha > >> for login due to massive spam issues. > > > > Have you tested whether Chinese or Russian users can login or sign up? > > Asking because Recaptcha was blocked for quite a long time by Russian > > authorities. > > We do have active users from both countries currently. Great, thanks for confirmation! -- Alexander E. Patrakov ___ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx
Re: gitlab migration
On 2018-06-12 01:35 PM, Daniel Stone wrote: > On 11 June 2018 at 11:33, Michel Dänzer wrote: >> On 2018-06-08 08:08 PM, Adam Jackson wrote: >>> I'd like us to start moving repos and bug tracking into gitlab. >>> Hopefully everyone's aware that gitlab exists and why fdo projects are >>> migrating to it. If not, the thread about Mesa's migration provides >>> some useful background: >>> >>> https://lists.x.org/archives/mesa-dev/2018-May/195634.html >>> >>> This should be mostly mechanical, except for moving some of the older >>> junk into the archive and deciding which drivers _not_ to move yet (I >>> imagine intel has some of its processes hooked up to bz, for example). >> >> As the maintainer of xf86-video-amdgpu and -ati, I'm fine with migrating >> these to GitLab for Git and patch review. >> >> However, I'm not sure what to do about bugs/issues. My first thought was >> to allow creating new issues in GitLab and disable creating new reports >> in Bugzilla, but not to migrate existing reports from Bugzilla. However, >> it still happens fairly often that a report is initially filed against >> the Xorg drivers, even though it's actually an issue in the X server, >> Mesa or the kernel (old habits die hard...). Therefore, I'm inclined to >> stick to Bugzilla until at least the X server and Mesa have moved to >> GitLab for issue tracking, to hopefully allow moving such misfiled issues. > > One thing some Mesa people said during that discussion is that they > like the ability to move issues between Mesa and the kernel, which > won't be possible if they're on split systems. So I probably wouldn't > hold my breath for that to be honest. Then I'd rather not use GitLab issues for these drivers at all either for the time being. The same argument applies to xserver as well, but I won't stand in the way of migrating that to GitLab issues. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer ___ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx
Re: gitlab migration
Hi Alexander, On 12 June 2018 at 14:53, Alexander E. Patrakov wrote: > Daniel Stone : >> > That said, I could not even create an account with a noscript/xhtml basic >> > browser (if you want to test that, install the famous noscript module with >> > an >> > empty "white list" in firefox or chromium, or use lynx or links or w3m). >> >> No need to test; it's guaranteed to fail since we require Recaptcha >> for login due to massive spam issues. > > Have you tested whether Chinese or Russian users can login or sign up? > Asking because Recaptcha was blocked for quite a long time by Russian > authorities. We do have active users from both countries currently. Cheers, Daniel ___ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx
Re: gitlab migration
On Tue, Jun 12, 2018 at 01:41:55PM +0100, Daniel Stone wrote: > Hi Sylvain, > > On 12 June 2018 at 13:38, wrote: > > On Tue, Jun 12, 2018 at 12:34:31PM +0100, Daniel Stone wrote: > >> GitLab has a pretty comprehensive and well-documented API which might > >> help if you don't want to use a web browser. There are also clients > >> like 'lab': https://gitlab.com/zaquestion/lab which provide a good CLI > >> interface. > > > > Those "web APIs" usually require the use of an heavy javascript browser for > > authentification or "app authorization". > > > > That said, I could not even create an account with a noscript/xhtml basic > > browser (if you want to test that, install the famous noscript module with > > an > > empty "white list" in firefox or chromium, or use lynx or links or w3m). > > No need to test; it's guaranteed to fail since we require Recaptcha > for login due to massive spam issues. Why is this captcha not noscript/xhtml basic friendly? (You could use also netsurf browser which has some static css support) regards, -- Sylvain ___ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx
Re: gitlab migration
Hi Sylvain, On 12 June 2018 at 13:38, wrote: > On Tue, Jun 12, 2018 at 12:34:31PM +0100, Daniel Stone wrote: >> GitLab has a pretty comprehensive and well-documented API which might >> help if you don't want to use a web browser. There are also clients >> like 'lab': https://gitlab.com/zaquestion/lab which provide a good CLI >> interface. > > Those "web APIs" usually require the use of an heavy javascript browser for > authentification or "app authorization". > > That said, I could not even create an account with a noscript/xhtml basic > browser (if you want to test that, install the famous noscript module with an > empty "white list" in firefox or chromium, or use lynx or links or w3m). No need to test; it's guaranteed to fail since we require Recaptcha for login due to massive spam issues. Cheers, Daniel ___ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx
Re: gitlab migration
On Tue, Jun 12, 2018 at 12:34:31PM +0100, Daniel Stone wrote: > Hi Sylvain, > It looks like Mutt is mangling email addresses - I've fixed Michel's. > > On 11 June 2018 at 14:30, wrote: > > On Mon, Jun 11, 2018 at 12:33:52PM +0200, Michel Dänzer wrote: > >> Adding the amd-gfx list, in cases somebody there has concerns or other > >> feedback. > > > > For feedback: > > I attempted a migration on gitlab of my repos but I was blocked because it's > > not noscript/xhtml basic browser friendly. > > > > I was successfull with launchpad.net (which has now git support). > > > > I did not test if the issue system was noscript/xhtml basic friendly though. > > GitLab has a pretty comprehensive and well-documented API which might > help if you don't want to use a web browser. There are also clients > like 'lab': https://gitlab.com/zaquestion/lab which provide a good CLI > interface. Hi, Those "web APIs" usually require the use of an heavy javascript browser for authentification or "app authorization". That said, I could not even create an account with a noscript/xhtml basic browser (if you want to test that, install the famous noscript module with an empty "white list" in firefox or chromium, or use lynx or links or w3m). regards, -- Sylvain ___ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx
Re: gitlab migration
Hi Michel, On 11 June 2018 at 11:33, Michel Dänzer wrote: > On 2018-06-08 08:08 PM, Adam Jackson wrote: >> I'd like us to start moving repos and bug tracking into gitlab. >> Hopefully everyone's aware that gitlab exists and why fdo projects are >> migrating to it. If not, the thread about Mesa's migration provides >> some useful background: >> >> https://lists.x.org/archives/mesa-dev/2018-May/195634.html >> >> This should be mostly mechanical, except for moving some of the older >> junk into the archive and deciding which drivers _not_ to move yet (I >> imagine intel has some of its processes hooked up to bz, for example). > > As the maintainer of xf86-video-amdgpu and -ati, I'm fine with migrating > these to GitLab for Git and patch review. > > However, I'm not sure what to do about bugs/issues. My first thought was > to allow creating new issues in GitLab and disable creating new reports > in Bugzilla, but not to migrate existing reports from Bugzilla. However, > it still happens fairly often that a report is initially filed against > the Xorg drivers, even though it's actually an issue in the X server, > Mesa or the kernel (old habits die hard...). Therefore, I'm inclined to > stick to Bugzilla until at least the X server and Mesa have moved to > GitLab for issue tracking, to hopefully allow moving such misfiled issues. One thing some Mesa people said during that discussion is that they like the ability to move issues between Mesa and the kernel, which won't be possible if they're on split systems. So I probably wouldn't hold my breath for that to be honest. Cheers, Daniel ___ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx
Re: gitlab migration
Hi Sylvain, It looks like Mutt is mangling email addresses - I've fixed Michel's. On 11 June 2018 at 14:30, wrote: > On Mon, Jun 11, 2018 at 12:33:52PM +0200, Michel Dänzer wrote: >> Adding the amd-gfx list, in cases somebody there has concerns or other >> feedback. > > For feedback: > I attempted a migration on gitlab of my repos but I was blocked because it's > not noscript/xhtml basic browser friendly. > > I was successfull with launchpad.net (which has now git support). > > I did not test if the issue system was noscript/xhtml basic friendly though. GitLab has a pretty comprehensive and well-documented API which might help if you don't want to use a web browser. There are also clients like 'lab': https://gitlab.com/zaquestion/lab which provide a good CLI interface. Cheers, Daniel ___ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx
Re: gitlab migration
On Mon, Jun 11, 2018 at 12:33:52PM +0200, Michel Dänzer wrote: > Adding the amd-gfx list, in cases somebody there has concerns or other > feedback. For feedback: I attempted a migration on gitlab of my repos but I was blocked because it's not noscript/xhtml basic browser friendly. I was successfull with launchpad.net (which has now git support). I did not test if the issue system was noscript/xhtml basic friendly though. -- Sylvain ___ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx
Re: gitlab migration
On 2018-06-08 08:08 PM, Adam Jackson wrote: > I'd like us to start moving repos and bug tracking into gitlab. > Hopefully everyone's aware that gitlab exists and why fdo projects are > migrating to it. If not, the thread about Mesa's migration provides > some useful background: > > https://lists.x.org/archives/mesa-dev/2018-May/195634.html > > This should be mostly mechanical, except for moving some of the older > junk into the archive and deciding which drivers _not_ to move yet (I > imagine intel has some of its processes hooked up to bz, for example). As the maintainer of xf86-video-amdgpu and -ati, I'm fine with migrating these to GitLab for Git and patch review. However, I'm not sure what to do about bugs/issues. My first thought was to allow creating new issues in GitLab and disable creating new reports in Bugzilla, but not to migrate existing reports from Bugzilla. However, it still happens fairly often that a report is initially filed against the Xorg drivers, even though it's actually an issue in the X server, Mesa or the kernel (old habits die hard...). Therefore, I'm inclined to stick to Bugzilla until at least the X server and Mesa have moved to GitLab for issue tracking, to hopefully allow moving such misfiled issues. Adding the amd-gfx list, in cases somebody there has concerns or other feedback. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer ___ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx
