Migrate beancount away from Bitbucket
Hello,
we are looking into options to migrate beancount
away from Bitbucket, that, as you most probably know, will remove its mercurial support really soon.
Description of the projects to be hosted
beancount
is a double-entry bookkeeping computer language that lets you define financial transaction records in a text file, read them in memory, generate a variety of reports from them, and provides a web interface. It is licensed under the GPLv2. It is a successful project with a fairly large user base. Latest version is 2.2.3 released on 2019‑08‑29. Martin Blais, creator and maintainer of beancount
is rather busy lately, thus I volunteered to explore foss.heptapod.net as a possible repository hosting solution.
http://furius.ca/beancount/ https://bitbucket.org/blais/beancount
The plan is to migrate the main development repository here, probably under a beancount
project.
I don't see a problem with adding acknowledgements to Octobus Clever Cloud on the project webpage.
-
Free / Open Source -
main development repositories -
agreement to acknowledge where appropriate the help provided by Octobus and Clever Cloud by hosting on foss.heptapod.net -
currently hosted on Bitbucket -
officially released
Post approval maintainer task list:
See README for explanations.
-
Hosting Request assignee has repository membership on Bitbucket -
Heptapod / Bitbucket accounts link -
Reviewing Heptapod workflow
Post import maintainer task list:
-
Clone the project afresh from foss.heptapod.net. -
Check that the repository looks good: branches are as expected in the clone and the web interface, with no wild
branches unless there are known multiple heads. -
Check that issues are imported, and notably that all open issues are there. Watch for attachments etc. -
Check that Pull Requests are imported, and in particular take a close look at the resulting open Merge Requests - they should be backed by a topic. Make sure you can navigate these in the fresh clone. -
Check that against foss.heptapod.net, hg outgoing
andhg incoming
from a prior clone are as expected -
Add the Octobus and Clever cloud acknowledgement at the selected place.