Beancount Migration to Github

[Martin Blais]

Dear Beancount users,

The Beancount repository and issue tracker has been migrated to Github, at this location:

    http://github.com/beancount/beancount

This is now the official location for Beancount source code, for further development, and for filing any new tickets and issues.

Moving forward I will push all further development there.

Original documentation sources remain in Google Docs but there's an official dump of the documents to Markdown maintained by Kirill Goncharov in the Github beancount org, here:

    http://beancount.github.io/docs

Details:

- All issues from the Bitbucket repository have been migrated to Github issues on that project. Attachments are missing but I've saved them manually to a file.

- Pull requests from BitBucket have been moved to Git branches with name "pr<number>_<user>_<name>".

- Closed Mercurial branches have been saved as tags under the name "archive/<branch-name>"

- The BitBucket repository remains there just so that links to source code from mailing-list threads keep working until BitBucket removes it, and to be able to link back to original issue tickets if needed. I've erased the README and replaced it with a message about the new location on the landing page of that repository. I will not be updating that repository anymore.

Special thanks to Martin Michlmayr, Kirill Goncharov and Dominik Aumayr for figuring out most of the details to make this happen smoothly. This wouldn't have happened so quickly without your input.

I've also moved all my other OSS projects to Github. It's a sad day for Mercurial. It's an unfortunate fact that Mercurial on BitBucket never took off nearly to the same extent; nevertheless I'm grateful to BitBucket for hosting this project and my other ones for free for all these years. On the other hand, I'm excited to see what new opportunities the extra visibility might bring; everyone knows Github and already has an account there. I've been making some progress on a foundation for v3 which will likely take advantage of this. I'll be following up with a document about what the next version will look like.

Cheers!

[Zhen Cheng]

Thanks for your work, it's really nice seeing beancount on Github.

[Stefano Zacchiroli]

On Fri, May 22, 2020 at 05:56:33PM -0400, Martin Blais wrote:
> The Beancount repository and issue tracker has been migrated to Github, at
> this location:

[...]

> Special thanks to Martin Michlmayr, Kirill Goncharov and Dominik Aumayr for
> figuring out most of the details to make this happen smoothly. This
> wouldn't have happened so quickly without your input.

Great work. Thanks a lot to bot you personally and all the people who
have helped to make this happen.

Cheers
--
Stefano Zacchiroli . za...@upsilon.cc . upsilon.cc/zack . . o . . . o . o
Computer Science Professor . CTO Software Heritage . . . . . o . . . o o
Former Debian Project Leader & OSI Board Director . . . o o o . . . o .
« the first rule of tautology club is the first rule of tautology club »

[Stefano Zacchiroli]

Hi again Martin,

On Fri, May 22, 2020 at 05:56:33PM -0400, Martin Blais wrote:

> The Beancount repository and issue tracker has been migrated to Github, at
> this location:

as far as I can tell from:

https://travis-ci.org/github/beancount/beancount/pull_requests

CI builds are not enabled for pull requests. Can you enable them?

It's gonna help both you and PR submitters in shortening feedback loops,
I think. To enable them all that should be needed is going here:

https://travis-ci.org/github/beancount/beancount/settings

and flipping the switch "Build pushed pull requests" (there's also
"Build pushed branches", but that concerns only the people with direct
push access).

Thanks for considering,

[Martin Blais]

On Sat, May 23, 2020 at 11:53 AM Stefano Zacchiroli <za...@upsilon.cc> wrote:

Hi again Martin,

On Fri, May 22, 2020 at 05:56:33PM -0400, Martin Blais wrote:
> The Beancount repository and issue tracker has been migrated to Github, at
> this location:

as far as I can tell from:

  https://travis-ci.org/github/beancount/beancount/pull_requests

CI builds are not enabled for pull requests. Can you enable them?

I agree, but "Build pushed pull requests" is already enabled.

I changed the settings this morning so it's possible previous PRs haven't been built.

I disabled "build pushed branches" because most branches aren't clean in that way at the moment.

  

It's gonna help both you and PR submitters in shortening feedback loops,
I think. To enable them all that should be needed is going here:

  https://travis-ci.org/github/beancount/beancount/settings

and flipping the switch "Build pushed pull requests" (there's also
"Build pushed branches", but that concerns only the people with direct
push access).

Thanks for considering,
Cheers
--
Stefano Zacchiroli . za...@upsilon.cc . upsilon.cc/zack . . o . . . o . o
Computer Science Professor . CTO Software Heritage . . . . . o . . . o o
Former Debian Project Leader & OSI Board Director  . . . o o o . . . o .
« the first rule of tautology club is the first rule of tautology club »

--
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 beancount+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/20200523155310.hxufpc4fg5praz5v%40upsilon.cc.

[Stefano Zacchiroli]

On Sat, May 23, 2020 at 11:57:43AM -0400, Martin Blais wrote:
> I agree, but "Build pushed pull requests" is already enabled.
> I changed the settings this morning so it's possible previous PRs haven't
> been built.

Yup, it was indeed a race condition between my request here and you
enabling it. All is good now.

Thanks!

[TRS-80]

On 2020-05-22 17:56, Martin Blais wrote:
> Dear Beancount users,
> The Beancount repository and issue tracker has been migrated to
> Github

I know you were against it for a long time, but as you correctly point
out it seems "everyone" is on GitHub nowadays. Not my preference
either, but what can you do.

Hopefully, lowering of friction will enable better/more
co-operation/contribution, perhaps even making your maintainership
easier?

Thanks again for all your work over all these years, Martin. Cheers!

TRS-80

[Martin Blais]

On Thu, Jul 2, 2020 at 2:06 PM TRS-80 <trs...@isnotmyreal.name> wrote:

On 2020-05-22 17:56, Martin Blais wrote:
> Dear Beancount users,
> The Beancount repository and issue tracker has been migrated to
> Github

I know you were against it for a long time, but as you correctly point
out it seems "everyone" is on GitHub nowadays.  Not my preference
either, but what can you do.

Hopefully, lowering of friction will enable better/more
co-operation/contribution, perhaps even making your maintainership
easier?

Actually, now that we're a couple of months into it, here's my reaction to the move. I'd used Github a fair bit in read-only mode before, just cloning repos and sending the occasional patch to other projects, but I'm finding that after deeper experience with it, today's Github is better than BitBucket (I'm not sure this was the case originally when I created the repo). Today it clearly is.

Here are some of the things I really like about Github:

- The tag-based, unstructured labeling system for tickets is a much simpler, more flexible way to organize issues than the more fixed system in BitBucket. It's faster to make changes to large numbers of tickets and the UI is well-designed, does not require page reloads most of the time. And with some name conventions and if one's okay to live with the potential missing label of a particular category (e.g. priority) it covers all the use cases. It takes it within reach to handle a very large number of tickets--I had more or less abandoned being able to do this in BitBucket, it would have taken too long, was too slow to work with. I've relabeled a lot of the tickets and will be processing them; I created three types of labels: Px (P0, P1, P2, P3) for priorities, categories/component (as previously) and a few "status-related" / resolution tickets, e.g. wontfix. I use color codes to distinguish them. I'm hoping to be able to get on top of all the tickets eventually.

- Phone integration! I merged my first PR shortly after moving the repo over while still emerging from sleep. Picked up my phone, clicked on a link, did some code review, merged it. That was simply amazing. For really simple PRs that's a really great option.

- PRs and Issues in a single namespace instead of two separate ones totally makes sense. I can easily refer to a PR or Issue with #xxx anywhere and it links. Love it. Github is more flat than BitBucket, and I think it hits the sweet spot in that sense.

- Git itself remains with some occasional annoyances, but I think if you work very regularly with it you learn to avoid the pitfalls and because all the refs are dynamically changeable you can always find a way to fix things (if you've got refs preserving all the code you want to avoid getting garbage collected). I've had to learn a few tricks I didn't know lately and I'll admit that it does come with more flexibility I can leverage than Mercurial, e.g., the ability to merge just some other commits from another PR, for instance, by changing refs. I'm learning to like it, maybe even love it.

- Finally, and the biggest benefit, really is that more people have been sending PRs and eager to get involved.  It's nice now, many related repos under a single organization umbrella with ACLs and such, I really like that.

Overall, no regrets, this is a plus.

I've been writing a plan document for a v3 rewrite which I'll share soon (big changes).

The plan includes changes that will make it easier to collaborate and for me to maintain things going forward.

 

Thanks again for all your work over all these years, Martin.  Cheers!

Thank you! :-)

 

TRS-80

--
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 beancount+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/299941d3d649f3e629fc3b079e236486%40isnotmyreal.name.