The issue seems to be with unauthenticated requests. Try signing into
GitHub first, then open another tab and try to sign the CLA.
On Fri, Apr 28, 2023 at 9:35 AM George Joseph wrote:
> On Fri, Apr 28, 2023 at 9:32 AM Shloime Rosenblum <
> shloimerosenb...@gmail.com> wrote:
>
>> [image:
https://github.com/asterisk/asterisk/pulls
Please refresh yourself by reading
https://wiki.asterisk.org/wiki/display/AST/Code+Contribution
again. There have been a few minor changes.
--
George Joseph
Asterisk Software Developer
Sangoma Technologies
Check us out at www.sangoma.com and
All Asterisk issues should now be reported at
https://github.com/asterisk/asterisk/issues
The previous issue system at https://issues.asterisk.org remains in
read-only mode for reference but will eventually be replaced with a
searchable archive.
--
It is working now
On Fri, Apr 28, 2023 at 11:55 AM George Joseph wrote:
> The issue seems to be with unauthenticated requests. Try signing into
> GitHub first, then open another tab and try to sign the CLA.
>
>
> On Fri, Apr 28, 2023 at 9:35 AM George Joseph wrote:
>
>> On Fri, Apr 28, 2023
> "GJ" == George Joseph writes:
GJ> Sorry about this guys. It appears that the cla-assistant GitHub app has an
GJ> issue if you try to sign using just the organization. If you sign for a
GJ> specific repository, it'll work and it'll be valid for the entire
GJ> organization. So use...
GJ>
now it worked.
too much malicious ecmascript...
-JimC
--
James Cloos OpenPGP: 0x997A9F17ED7DAEA6
--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-dev mailing list
To UNSUBSCRIBE or
You can get a head start and sign the new Contributor License Agreement at
any time...
https://oss-cla.sangoma.com/asterisk
--
George Joseph
Asterisk Software Developer
Sangoma Technologies
Check us out at www.sangoma.com and www.asterisk.org
--
Hello,
to save me (and probably other people) trying to parse that agreement again
some time:
Is this an identical agreement as the one signed in the old process (on
gerrit/Jira etc..)? Or were some changes here done.
Thanks,
Henning
From: asterisk-dev On Behalf Of George
Joseph
Sent:
Good now :)
On 2023-04-28 10:40 a.m., George Joseph wrote:
OK, sorry. You have to add the slash at the end :)
https://oss-cla.sangoma.com/asterisk/
Stupid reverse proxy.
On Fri, Apr 28, 2023 at 8:16 AM George Joseph wrote:
You can get a head start and sign the new Contributor License
On Fri, Apr 28, 2023 at 9:32 AM Shloime Rosenblum <
shloimerosenb...@gmail.com> wrote:
> [image: image.png]
>
>
It's always something. Let me see if I can increase the limits.
> On Fri, Apr 28, 2023 at 11:19 AM George Joseph
> wrote:
>
>> Sorry about this guys. It appears that the
[image: image.png]
On Fri, Apr 28, 2023 at 11:19 AM George Joseph wrote:
> Sorry about this guys. It appears that the cla-assistant GitHub app has
> an issue if you try to sign using just the organization. If you sign for a
> specific repository, it'll work and it'll be valid for the entire
>
Hello,
It's 404.
Sylvain
On 2023-04-28 10:16 a.m., George Joseph wrote:
You can get a head start and sign the new Contributor License
Agreement at any time...
https://oss-cla.sangoma.com/asterisk
--
George Joseph
Asterisk Software Developer
Sangoma Technologies
Check us out at
OK, sorry. You have to add the slash at the end :)
https://oss-cla.sangoma.com/asterisk/
Stupid reverse proxy.
On Fri, Apr 28, 2023 at 8:16 AM George Joseph wrote:
> You can get a head start and sign the new Contributor License Agreement at
> any time...
> https://oss-cla.sangoma.com/asterisk
Now it gives:
Error
There is no CLA to sign for asterisk/asterisk
(API rate limit exceeded for 44.208.69.1. (But here's the good news:
Authenticated requests get a higher rate limit. Check out the documentation for
more details.))
From: asterisk-dev On Behalf Of George
Joseph
Sent:
On Fri, Apr 28, 2023 at 11:44 AM Henning Westerholt wrote:
> Hello,
>
>
>
> to save me (and probably other people) trying to parse that agreement
> again some time:
>
>
>
> Is this an identical agreement as the one signed in the old process (on
> gerrit/Jira etc..)? Or were some changes here
Yeah sorry. One minute.
On Fri, Apr 28, 2023 at 8:19 AM Sylvain Boily wrote:
> Hello,
>
> It's 404.
>
> Sylvain
>
> On 2023-04-28 10:16 a.m., George Joseph wrote:
>
> You can get a head start and sign the new Contributor License Agreement at
> any time...
>
On Fri, Apr 28, 2023 at 11:47 AM Joshua C. Colp wrote:
> On Fri, Apr 28, 2023 at 11:44 AM Henning Westerholt wrote:
>
>> Hello,
>>
>>
>>
>> to save me (and probably other people) trying to parse that agreement
>> again some time:
>>
>>
>>
>> Is this an identical agreement as the one signed in
Sorry about this guys. It appears that the cla-assistant GitHub app has an
issue if you try to sign using just the organization. If you sign for a
specific repository, it'll work and it'll be valid for the entire
organization. So use...
https://oss-cla.sangoma.com/asterisk/asterisk
If that
18 matches
Mail list logo
