Re: License statement as a prerequisite for gerrit account
> Personally, I would think the most efficient thing would be to just > have it be a checkbox on the account registration screen. Similar to > the "I agree to the terms and conditions" statement that everyone just > acknowledges without reading on any other website. Note that Gerrit already has such a feature: https://gerrit-review.googlesource.com/Documentation/config-cla.html If we still want to keep the license statements on the Mailing List, we could use the Gerrit Contributor agreement feature with the agreement saying "I sent my license statement to the mailing list". This way we have some automated check in gerrit, and still have the license statements on the public Mailing List. Regards Samuel ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: License statement as a prerequisite for gerrit account
Every license statement I see on this list follows the provided template, so regex matching that should be trivial. Matching the email address to accounts in gerrit or bugzilla would probably work for some large percentage of cases, but you could reasonably expect there to be some cases where someone registered for a gerrit account with one email address, and sent their license statement to the mailing list from another one. Personally, I would think the most efficient thing would be to just have it be a checkbox on the account registration screen. Similar to the "I agree to the terms and conditions" statement that everyone just acknowledges without reading on any other website. John wrote: Would it be possible to script? Looping over messages in the mailing list would not be hard to script, finding bugzilla tickets from a corresponding email that the script has not modified yet would not be hard, but it might be tricky to identify that a given message /is/ a valid license statement. If you could figure that out, though, having the bot/script update tickets with a link to the assignee's license statement would make this much less of an issue, in my opinion. On 3/29/21 9:24 AM, Eike Rathke wrote: Hi, On Sunday, 2021-03-28 02:36:49 -0700, julien2412 wrote: I noticed several times some patches on gerrit for which authors hadn't send yet their license statement. Of course when asking, the license statement is provided but to avoid to miss it and risk some legal problem, thought it could be relevant to make license statement as prerequisite for a gerrit account. Maybe not a prerequisite for a gerrit account (contributors want that quickly to push a change and you don't want their hard disk die before ;-), but a prerequisite for being able to merge a change. Often enough when I spot a new name at a change I look up the dev statement and if not found mention that during review, but I'm also guilty not thinking of or asking only after merging. Eike ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: License statement as a prerequisite for gerrit account
Would it be possible to script? Looping over messages in the mailing list would not be hard to script, finding bugzilla tickets from a corresponding email that the script has not modified yet would not be hard, but it might be tricky to identify that a given message /is/ a valid license statement. If you could figure that out, though, having the bot/script update tickets with a link to the assignee's license statement would make this much less of an issue, in my opinion. On 3/29/21 9:24 AM, Eike Rathke wrote: Hi, On Sunday, 2021-03-28 02:36:49 -0700, julien2412 wrote: I noticed several times some patches on gerrit for which authors hadn't send yet their license statement. Of course when asking, the license statement is provided but to avoid to miss it and risk some legal problem, thought it could be relevant to make license statement as prerequisite for a gerrit account. Maybe not a prerequisite for a gerrit account (contributors want that quickly to push a change and you don't want their hard disk die before ;-), but a prerequisite for being able to merge a change. Often enough when I spot a new name at a change I look up the dev statement and if not found mention that during review, but I'm also guilty not thinking of or asking only after merging. Eike ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: License statement as a prerequisite for gerrit account
Hi, On Sunday, 2021-03-28 02:36:49 -0700, julien2412 wrote: > I noticed several times some patches on gerrit for which authors hadn't send > yet their license statement. > Of course when asking, the license statement is provided but to avoid to > miss it and risk some legal problem, thought it could be relevant to make > license statement as prerequisite for a gerrit account. Maybe not a prerequisite for a gerrit account (contributors want that quickly to push a change and you don't want their hard disk die before ;-), but a prerequisite for being able to merge a change. Often enough when I spot a new name at a change I look up the dev statement and if not found mention that during review, but I'm also guilty not thinking of or asking only after merging. Eike -- GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A signature.asc Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
License statement as a prerequisite for gerrit account
Hello, I noticed several times some patches on gerrit for which authors hadn't send yet their license statement. Of course when asking, the license statement is provided but to avoid to miss it and risk some legal problem, thought it could be relevant to make license statement as prerequisite for a gerrit account. Any thoughts here? Julien -- Sent from: http://document-foundation-mail-archive.969070.n3.nabble.com/Dev-f1639786.html ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: Gerrit Account
On Sat, Feb 22, 2020 at 5:09 PM ahmed El-Shreif wrote: > I have account on gerrit from last year. I tried to login again now and the > website says that no account match this. FYI: this was dealt with in #tdf-infra the same day... ciao Christian ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
Gerrit Account
Hello all, I have account on gerrit from last year. I tried to login again now and the website says that no account match this. So I make new account with same mail : aelshre...@gmail.com When I try to login now I got these messages: Forbidden / Server Error How could I access my account to start contributing again? This is my account on gerrit: https://gerrit.libreoffice.org/q/owner:aelshreif7%2540gmail.com Thanks, Ahmed ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
