On Thu, Jul 2, 2020 at 2:06 PM TRS-80 <[email protected]> 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beancount/299941d3d649f3e629fc3b079e236486%40isnotmyreal.name > . > -- 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/CAK21%2BhNL2ZM-Luw4AAvkjFLecZ1%2BWx95xXmyuNip5dk0JzdaQA%40mail.gmail.com.
