> > If you'd prefer to move it (I didn't know it was possible to move a repo > across users) you can wait, if I have Owner ACLs I'd be happy to make that > happen. >
Yes, I would prefer transfer as it preserves issues, watchers and stars. Let's wait for Dominik's response. Strange. Maybe there's something hardcoded in the generator? > I don't know. It says that `beancount.tools` is a module that has no attribute `sheets_upload` (full traceback: https://github.com/xuhcc/beancount-docs/issues/14). On Wednesday, May 20, 2020 at 10:11:35 PM UTC+3, Martin Blais wrote: > > On Wed, May 20, 2020 at 2:35 PM Kirill Goncharov <[email protected] > <javascript:>> wrote: > >> I'd love for you to move that repo under " >>> http://github.com/beancount/docs"; if you don't mind, that would be >>> ideal. >>> >> >> Sure, I'll rename it. >> >> According to the GitHub documentation >> <https://help.github.com/en/github/administering-a-repository/transferring-a-repository>, >> >> I need a permission to create repositories in organization in order to >> initiate the transfer. Can you grant me such permission? >> > > I'm not able to grant at the moment, I'm merely a Member of the org; I > just asked Dominik if he'll promote me to Owner. > In any case, I've created an empty repo here: > https://github.com/beancount/docs > Are you able to push it over that (along with the history)? > > If you'd prefer to move it (I didn't know it was possible to move a repo > across users) you can wait, if I have Owner ACLs I'd be happy to make that > happen. > > > >> >> Feel free to stick your name in the generated docs somewhere as the >>> maintainer and get some credit for all that nice work. Alternatively, I >>> have a credits file somewhere in the source repo that I can convert to a >>> Google doc, that would be an easy way to make this appear in your generated >>> docs. >>> >> >> We have a history of commits, I think that's enough. >> >> >>> At a quick glance, I notice Dominik's has a full index in the API >>> reference, and not a hierarchical one (not sure this matters): >>> https://aumayr.github.io/beancount-docs-static/api_reference/index.html >>> >> >> I didn't found a way to build such an index automatically with mkdocs. >> > > No worries. > > > >> Also your API reference is missing the "projects" subdirectory. >>> >> >> This subdirectory is not present in the beancount package downloaded from >> PyPI. >> Also, the documentation generator fails to read 'tools' subdirectory, I >> can't figure out why. But I added documentation pages for 'loader', >> 'prices' and 'web' which were missing. >> > > Strange. Maybe there's something hardcoded in the generator? > > > >> >> On Wednesday, May 20, 2020 at 6:13:07 PM UTC+3, Martin Blais wrote: >>> >>> On Wed, May 20, 2020 at 6:34 AM Kirill Goncharov <[email protected]> >>> wrote: >>> >>>> >After I refresh the code and migrate the tickets, I'd love to >>>> integrate Kirill's .md docs >>>> >>>> How would you like to do that? >>>> >>>> I think it's better to keep the parser and resulting markdown files in >>>> a separate repo unless there's a compelling reason to do otherwise, as >>>> this >>>> allows frequent updates (I currently do re-parsing once a week). >>>> That being said, I would happily transfer my beancount-docs repo to >>>> https://github.com/beancount/ organization and add you as collaborator. >>>> >>> >>> Come to think of it, this makes the most sense. This way there's no need >>> to pepper the code repo with documentation updates. >>> >>> I'd love for you to move that repo under " >>> http://github.com/beancount/docs"; if you don't mind, that would be >>> ideal. >>> It would make a https://beancount.github.io/docs/ root for that >>> documentation site, which is a pretty nice URL. >>> >>> Two more things: >>> - Feel free to stick your name in the generated docs somewhere as the >>> maintainer and get some credit for all that nice work. Alternatively, I >>> have a credits file somewhere in the source repo that I can convert to a >>> Google doc, that would be an easy way to make this appear in your generated >>> docs. >>> >>> - Your conversikon seems like it covers all of the static docs generated >>> by Dominik, here: >>> https://aumayr.github.io/beancount-docs-static/ >>> <https://aumayr.github.io/beancount-docs-static/api_reference/index.html> >>> Is this correct? Does it cover everything that is there? >>> At a quick glance, I notice Dominik's has a full index in the API >>> reference, and not a hierarchical one (not sure this matters): >>> https://aumayr.github.io/beancount-docs-static/api_reference/index.html >>> Also your API reference is missing the "projects" subdirectory. >>> >>> Let me know if I help with anything to make this happen, >>> >>> >>> >>> >>> >>>> On Tuesday, May 19, 2020 at 4:57:14 PM UTC+3, Martin Blais wrote: >>>>> >>>>> On Tue, May 19, 2020 at 5:28 AM Martin Michlmayr <[email protected]> >>>>> wrote: >>>>> >>>>>> * Martin Blais <[email protected]> [2020-05-18 04:24]: >>>>>> > Martin: Did you want to go beyond this and create a mapping? >>>>>> >>>>>> I have a mapping now for some users. For quite a few people I cannot >>>>>> find a mapping. I think once we've done the migration, we can update >>>>>> the BitBucket issues and let them know about the move to GitHub. >>>>> >>>>> >>>>> >>>>>> Anyway, I emailed some people asking for their GitHub username, so >>>>>> please give me a few days. >>>>>> >>>>> >>>>> SGTM, I'll wait for your mapping and then I'll test it with >>>>> git-remote-hg. >>>>> Thanks a lot for your help and thanks to Kirill Goncharov for figuring >>>>> out the issues migration. >>>>> >>>>> I re-ran the hg-fast-export conversion and git-remote-hg ones last >>>>> night to see if there's any benefit to using one vs. the other. >>>>> The former fails with an exception; the latter works well. It'll be a >>>>> git-remote-log conversion. >>>>> I diffed all the heads of branches to make sure nothing's lost; seems >>>>> to have worked perfectly. >>>>> I also spot-checked some of the per-branch logs, they also fine. >>>>> The tags are also present and matching. >>>>> >>>>> There are a few final relatively easy things I need to figure out: >>>>> >>>>> - I have some repo lying around with local changes that needs to get >>>>> merged before I make the final conversion. I'll merge those changes in hg >>>>> and reimport. >>>>> >>>>> - Mercurial has the concept of "closing" a branch (typically when it >>>>> gets merged). This results over time in a large set of "inactive" and a >>>>> smaller set of "active" branches. The conversion merely creates branches, >>>>> for both active and inactive ones. The git-remote-hg docs mention "Closed >>>>> branches are not supported; they are not shown and you can’t close or >>>>> reopen. Additionally in certain rare situations a synchronization issue >>>>> can >>>>> occur (Bug #65)." I want to figure a way to keep the branch refs / >>>>> history >>>>> yet have them not show up in the list of branches (so that the little >>>>> github menu doesn't show all these closed branches as if they were work >>>>> in >>>>> progress). I think I may use a tag in under archive/ like some people do >>>>> to >>>>> differentiate those from tags for released versions. >>>>> >>>>> - Dominik Aumayr created the github.com/beancount/beancount >>>>> repository originally and gave me admin rights. While I'm able to pull >>>>> the >>>>> output of a fresh git-remote-hg conversion on top of that repo (with a >>>>> minor merge on a tags file), I'd prefer to empty it or remove it and >>>>> recreate it from scratch with the latest version of the git-remote-hg >>>>> converter. Is this going to cause problems? I suspect I would not since >>>>> I >>>>> can pull the recent conversion on top, the checksums are probably the >>>>> same >>>>> and the repos would be compatible. Have you done that before? I wonder if >>>>> it's easiest to delete and recreate the repo project in github (does >>>>> github >>>>> make that possible or if I delete the repo would the beancount/beancount >>>>> name be unavailable forever?). >>>>> >>>>> After I refresh the code and migrate the tickets, I'd love to >>>>> integrate Kirill's .md docs and ask if people can remove other static >>>>> docs >>>>> to there's only one copy out there and change all pointers to the repo. >>>>> >>>>> >>>>> >>>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Beancount" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/beancount/fac47049-267d-4205-88f3-6e030e7d2039%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/beancount/fac47049-267d-4205-88f3-6e030e7d2039%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Beancount" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/beancount/bbc6da8c-20a5-4c0d-9292-ce9a112b8c99%40googlegroups.com >> >> <https://groups.google.com/d/msgid/beancount/bbc6da8c-20a5-4c0d-9292-ce9a112b8c99%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/a5714ee2-852a-4a19-acba-26c5c1ab6fc3%40googlegroups.com.
