Re: [asterisk-dev] issues-archive.asterisk.org is now available for preview

[George Joseph]

On Sun, Aug 27, 2023 at 11:49 AM  wrote:

> On 8/4/2023 9:48 AM, George Joseph wrote:
> >
> > > We've done a dump of all the ASTERISK-* issues and their
> > attachments
> > > from the issues.asterisk.org 
> >  Jira
> > > instance and made them available at
> > > https://issues-archive.asterisk.org. It'll be a few days before
> > Google
> > > gets around to indexing the entire site so the search bar isn't
> > > working yet but you can browse the issues right now. When the
> > search
> > > is fully working we'll announce it on the asterisk-users list as
> > well.
> >
>
> Something I noticed in the past few days...
> issues.asterisk.org used to redirect to issues-archive.asterisk.org, but
> now redirects to GitHub, so issues.asterisk.org links no longer work
> properly. I'm assuming this wasn't intentional - just wanted to make you
> aware of it! Didn't seem like there was a good GitHub repo for this
> metaissue...
>
> I'm thinking maybe it was intended that the root domain
> issues.asterisk.org itself redirect to GitHub, and anything with a path
> redirect to issues-archive, but that's just speculation on my part.
>

Correct.  Should be fixed now.
-- 
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

Re: [asterisk-dev] issues-archive.asterisk.org is now available for preview

[Joshua C. Colp]

On Fri, Aug 4, 2023 at 2:38 PM  wrote:

> On 8/4/2023 9:48 AM, George Joseph wrote:
> > We've done a dump of all the ASTERISK-* issues and their attachments
> > from the issues.asterisk.org  Jira
> > instance and made them available at
> > https://issues-archive.asterisk.org. It'll be a few days before Google
> > gets around to indexing the entire site so the search bar isn't
> > working yet but you can browse the issues right now.  When the search
> > is fully working we'll announce it on the asterisk-users list as well.
> >
> > Take a look.
> Looks good on the surface to me. My main concern was patch attachments
> being preserved and it looks like they are.
>
> Just curious, how large is the export exactly? Certain things in JIRA
> were helpful like being able to filter issues by a keyword to "open",
> i.e. things which had and have not yet been resolved. The Google Search
> will help with indexing content but not with filtering, I'd think. If
> it's not too large, do you think this would be better suited to allowing
> folks to download an archive and then be able to use tools like grep to
> find the issues they want?
>
> I don't know that the hosted archives needs to do this, I suspect very
> few people would have any need for being able to do that, and I don't
> want to add any work for anyone here.
>
> Side question, more on the legal side. When everything was on JIRA, I
> think the policy was that any patches on JIRA could be taken through
> code review by anyone else, so long as the uploader had signed the CLA.
> Now that it is on GitHub, and there is a new CLA, and most people have
> not resigned the CLA for patches from the past ~20 years, how does this
> affect patches in the JIRA archive? Since the CLA was valid when they
> were provided to the project, can they still be taken through code
> review by anyone else? What is the status of such patches? Thanks.
>

All contributions need to be under the new CLA. The previous signed CLA is
no longer valid, even though the changes may have been submitted using it.
Original authors can use the archive site to get their old patches if they
want and submit under the new CLA.

-- 
Joshua C. Colp
Asterisk Project Lead
Sangoma Technologies
Check us out at www.sangoma.com and www.asterisk.org
-- 
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

Re: [asterisk-dev] issues-archive.asterisk.org is now available for preview

[asterisk]

On 8/4/2023 9:48 AM, George Joseph wrote:


> We've done a dump of all the ASTERISK-* issues and their
attachments
> from the issues.asterisk.org 
 Jira
> instance and made them available at
> https://issues-archive.asterisk.org. It'll be a few days before
Google
> gets around to indexing the entire site so the search bar isn't
> working yet but you can browse the issues right now. When the
search
> is fully working we'll announce it on the asterisk-users list as
well.



Something I noticed in the past few days...
issues.asterisk.org used to redirect to issues-archive.asterisk.org, but 
now redirects to GitHub, so issues.asterisk.org links no longer work 
properly. I'm assuming this wasn't intentional - just wanted to make you 
aware of it! Didn't seem like there was a good GitHub repo for this 
metaissue...


I'm thinking maybe it was intended that the root domain 
issues.asterisk.org itself redirect to GitHub, and anything with a path 
redirect to issues-archive, but that's just speculation on my part.


--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-dev

Re: [asterisk-dev] issues-archive.asterisk.org is now available for preview

[Joshua C. Colp]

On Fri, Aug 4, 2023 at 4:14 PM George Joseph  wrote:




>
>>
>> I don't know that the hosted archives needs to do this, I suspect very
>> few people would have any need for being able to do that, and I don't
>> want to add any work for anyone here.
>>
>> Side question, more on the legal side. When everything was on JIRA, I
>> think the policy was that any patches on JIRA could be taken through
>> code review by anyone else, so long as the uploader had signed the CLA.
>> Now that it is on GitHub, and there is a new CLA, and most people have
>> not resigned the CLA for patches from the past ~20 years, how does this
>> affect patches in the JIRA archive? Since the CLA was valid when they
>> were provided to the project, can they still be taken through code
>> review by anyone else? What is the status of such patches? Thanks.
>>
>
> I'll have to let Josh answer that one.
>

The patches can not be taken as-is, the creator has to sign the new CLA.
All old signatures are no longer valid.

-- 
Joshua C. Colp
Asterisk Project Lead
Sangoma Technologies
Check us out at www.sangoma.com and www.asterisk.org
-- 
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

Re: [asterisk-dev] issues-archive.asterisk.org is now available for preview

[George Joseph]

On Fri, Aug 4, 2023 at 11:38 AM  wrote:

> On 8/4/2023 9:48 AM, George Joseph wrote:
> > We've done a dump of all the ASTERISK-* issues and their attachments
> > from the issues.asterisk.org  Jira
> > instance and made them available at
> > https://issues-archive.asterisk.org. It'll be a few days before Google
> > gets around to indexing the entire site so the search bar isn't
> > working yet but you can browse the issues right now.  When the search
> > is fully working we'll announce it on the asterisk-users list as well.
> >
> > Take a look.
> Looks good on the surface to me. My main concern was patch attachments
> being preserved and it looks like they are.
>
> Just curious, how large is the export exactly? Certain things in JIRA
> were helpful like being able to filter issues by a keyword to "open",
> i.e. things which had and have not yet been resolved. The Google Search
> will help with indexing content but not with filtering,


Actually I may be able to customize the search results to be just a list.
If I have time next week, I'll take a look.


> I'd think. If
> it's not too large, do you think this would be better suited to allowing
> folks to download an archive and then be able to use tools like grep to
> find the issues they want?
>

235M uncompressed without attachments
41M in tarball
https://issues-archive.asterisk.org/asterisk-issue-archive.tar.gz

4.7G uncompressed attachments
They will not be made available as an archive.
If you want, you can simply munge the links to them in your local copy of
the html to point to the online versions.


>
> I don't know that the hosted archives needs to do this, I suspect very
> few people would have any need for being able to do that, and I don't
> want to add any work for anyone here.
>
> Side question, more on the legal side. When everything was on JIRA, I
> think the policy was that any patches on JIRA could be taken through
> code review by anyone else, so long as the uploader had signed the CLA.
> Now that it is on GitHub, and there is a new CLA, and most people have
> not resigned the CLA for patches from the past ~20 years, how does this
> affect patches in the JIRA archive? Since the CLA was valid when they
> were provided to the project, can they still be taken through code
> review by anyone else? What is the status of such patches? Thanks.
>

I'll have to let Josh answer that one.
-- 
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

Re: [asterisk-dev] issues-archive.asterisk.org is now available for preview

[asterisk]

On 8/4/2023 9:48 AM, George Joseph wrote:
We've done a dump of all the ASTERISK-* issues and their attachments 
from the issues.asterisk.org  Jira 
instance and made them available at 
https://issues-archive.asterisk.org. It'll be a few days before Google 
gets around to indexing the entire site so the search bar isn't 
working yet but you can browse the issues right now.  When the search 
is fully working we'll announce it on the asterisk-users list as well.


Take a look.
Looks good on the surface to me. My main concern was patch attachments 
being preserved and it looks like they are.


Just curious, how large is the export exactly? Certain things in JIRA 
were helpful like being able to filter issues by a keyword to "open", 
i.e. things which had and have not yet been resolved. The Google Search 
will help with indexing content but not with filtering, I'd think. If 
it's not too large, do you think this would be better suited to allowing 
folks to download an archive and then be able to use tools like grep to 
find the issues they want?


I don't know that the hosted archives needs to do this, I suspect very 
few people would have any need for being able to do that, and I don't 
want to add any work for anyone here.


Side question, more on the legal side. When everything was on JIRA, I 
think the policy was that any patches on JIRA could be taken through 
code review by anyone else, so long as the uploader had signed the CLA. 
Now that it is on GitHub, and there is a new CLA, and most people have 
not resigned the CLA for patches from the past ~20 years, how does this 
affect patches in the JIRA archive? Since the CLA was valid when they 
were provided to the project, can they still be taken through code 
review by anyone else? What is the status of such patches? Thanks.


--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-dev

[asterisk-dev] issues-archive.asterisk.org is now available for preview

[George Joseph]

We've done a dump of all the ASTERISK-* issues and their attachments from
the issues.asterisk.org Jira instance and made them available at
https://issues-archive.asterisk.org.  It'll be a few days before Google
gets around to indexing the entire site so the search bar isn't working yet
but you can browse the issues right now.  When the search is fully working
we'll announce it on the asterisk-users list as well.

Take a look.


-- 
George Joseph
Asterisk Software Developer
Sangoma Technologies
Check us out at www.sangoma.com and www.asterisk.org
-- 
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev