Andrew, Great!
I'll see if I can kick off the migration today and start 2018 on a high note! Thanks for all the hard work! -Bill On Mon, Jan 1, 2018 at 6:23 AM, Andrew Featherstone < andrew.featherst...@cantab.net> wrote: > Done. > > On 29 December 2017 at 17:28, Bill Deegan <b...@baddogconsulting.com> > wrote: > >> Can you send a pull request to scons/tigris-to-github ? >> >> On Fri, Dec 29, 2017 at 3:37 AM, Andrew Featherstone < >> andrew.featherst...@cantab.net> wrote: >> >>> I've just check this morning that it's able to work with an >>> organization's repos and not just an individual's. If you don't want to >>> solicit feedback on the users' mailing list, then the next step is to >>> perform the migration. So, to move things forward: >>> >>> 1. Clone my repo. >>> 2. Call python tigris2github.py and answer the questions. >>> >>> So it'd be something like this: >>> >>> > python .\tigris2github.py >>> GitHub username: ajf58 >>> GitHub Password: >>> GitHub repository for issues: scons/scons >>> GitHub repository for attachments: scons/tigris-issue-attachments >>> >>> As mentioned previously, it'll take a couple of hours to churn through >>> everything due to the rate limiting of GitHub. >>> >>> Cheers, >>> Andrew >>> >>> On 28 December 2017 at 22:12, Bill Deegan <b...@baddogconsulting.com> >>> wrote: >>> >>>> Yes. Sorry I didn't see the link in the existing markup. >>>> That looks good to me. >>>> So to move forward (migrate bugs to scons/scons and attachments to >>>> scons/tigris-issue-attachements/ ) what do I need to do? >>>> >>>> Thanks, >>>> Bill >>>> >>>> On Thu, Dec 28, 2017 at 12:56 PM, Andrew Featherstone < >>>> andrew.featherst...@cantab.net> wrote: >>>> >>>>> Hi Bill, >>>>> >>>>> I'm not sure I follow you. The issue numbers and the Tigris >>>>> 'attachment IDs' (used as the folder names) aren't the same value. Where >>>>> issues have attachments they are reffered to in the issue by name, and the >>>>> URL is included in the Markdown. As an example, see >>>>> https://github.com/ajf58/tigris-sandbox/issues/6, which has an >>>>> attachment found at https://github.com/ajf58/tigri >>>>> s-issue-attachments/blob/master/190/bug6.zip. >>>>> >>>>> Have I understood your question correctly? >>>>> >>>>> Andrew >>>>> >>>>> On 28 December 2017 at 20:33, Bill Deegan <b...@baddogconsulting.com> >>>>> wrote: >>>>> >>>>>> Can you add to the github bug a link to the github attachment repo >>>>>> where appropriate? >>>>>> (so you don't have to go look for the repo and then the issue number >>>>>> folder.) >>>>>> >>>>>> On Thu, Dec 28, 2017 at 11:51 AM, Daniel Moody <dmoody...@gmail.com> >>>>>> wrote: >>>>>> >>>>>>> I think it's awesome, looks great fully support moving forward with >>>>>>> this! Good work! >>>>>>> >>>>>>> On Dec 28, 2017 2:36 PM, "Andrew Featherstone" < >>>>>>> andrew.featherst...@cantab.net> wrote: >>>>>>> >>>>>>>> Hi All, >>>>>>>> >>>>>>>> Any comments or feedback on this? >>>>>>>> >>>>>>>> Regards, >>>>>>>> Andrew >>>>>>>> >>>>>>>> >>>>>>>> On 17 December 2017 at 18:58, Bill Deegan < >>>>>>>> b...@baddogconsulting.com> wrote: >>>>>>>> >>>>>>>>> Great work! >>>>>>>>> I'll try and set aside some time to review it this week. >>>>>>>>> >>>>>>>>> -Bill >>>>>>>>> >>>>>>>>> On Sat, Dec 16, 2017 at 6:44 PM, Andrew Featherstone < >>>>>>>>> andrew.featherst...@cantab.net> wrote: >>>>>>>>> >>>>>>>>>> Hi All, >>>>>>>>>> >>>>>>>>>> I've been working on how we can migrate the Tigris issues to >>>>>>>>>> GitHub. You can see the output of this at >>>>>>>>>> https://github.com/ajf58/tigris-sandbox/issues, To ensure that >>>>>>>>>> we're not relying on issue attachments being hosted at Tigris, which >>>>>>>>>> looks >>>>>>>>>> to be deserted by its owners (no tweets since 2013 >>>>>>>>>> https://twitter.com/tigrisdotorg?lang=en, for example), the >>>>>>>>>> issue attachments are also migrated to GitHub ( >>>>>>>>>> https://github.com/ajf58/tigris-issue-attachments). The source >>>>>>>>>> code used for doing this can be found at >>>>>>>>>> https://github.com/ajf58/tigris-to-github. >>>>>>>>>> >>>>>>>>>> I think the next steps are: >>>>>>>>>> >>>>>>>>>> 1. Members of this list review the format of the migrated >>>>>>>>>> issues and offer feedback. >>>>>>>>>> 2. Act on feedback. >>>>>>>>>> 3. Get feedback on the scons-user mailing list. >>>>>>>>>> 4. Migrate issues to https://github.com/SCons/scons >>>>>>>>>> >>>>>>>>>> The migration process takes ~2 hours currently. This is largely >>>>>>>>>> due to the rate limits GitHub imposees on their REST API. GitHub >>>>>>>>>> allows >>>>>>>>>> temporary restrictions to be imposed on the repo, so we can do that >>>>>>>>>> while >>>>>>>>>> the migration takes place. >>>>>>>>>> >>>>>>>>>> Thoughts? >>>>>>>>>> >>>>>>>>>> Cheers, >>>>>>>>>> Andrew >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Scons-dev mailing list >>>>>>>>>> Scons-dev@scons.org >>>>>>>>>> https://pairlist2.pair.net/mailman/listinfo/scons-dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Scons-dev mailing list >>>>>>>>> Scons-dev@scons.org >>>>>>>>> https://pairlist2.pair.net/mailman/listinfo/scons-dev >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Scons-dev mailing list >>>>>>>> Scons-dev@scons.org >>>>>>>> https://pairlist2.pair.net/mailman/listinfo/scons-dev >>>>>>>> >>>>>>>> >>>>>>> _______________________________________________ >>>>>>> Scons-dev mailing list >>>>>>> Scons-dev@scons.org >>>>>>> https://pairlist2.pair.net/mailman/listinfo/scons-dev >>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Scons-dev mailing list >>>>>> Scons-dev@scons.org >>>>>> https://pairlist2.pair.net/mailman/listinfo/scons-dev >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Scons-dev mailing list >>>>> Scons-dev@scons.org >>>>> https://pairlist2.pair.net/mailman/listinfo/scons-dev >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Scons-dev mailing list >>>> Scons-dev@scons.org >>>> https://pairlist2.pair.net/mailman/listinfo/scons-dev >>>> >>>> >>> >>> _______________________________________________ >>> Scons-dev mailing list >>> Scons-dev@scons.org >>> https://pairlist2.pair.net/mailman/listinfo/scons-dev >>> >>> >> >> _______________________________________________ >> Scons-dev mailing list >> Scons-dev@scons.org >> https://pairlist2.pair.net/mailman/listinfo/scons-dev >> >> > > _______________________________________________ > Scons-dev mailing list > Scons-dev@scons.org > https://pairlist2.pair.net/mailman/listinfo/scons-dev > >
_______________________________________________ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev