Hosting request - mercurial_keyring, mercurial_update_version, …
Replying to https://heptapod.net/heptapod-as-a-bitbucket-replacement.html I would like to host my set of Mercurial extensions. Complete list and short descriptions:
https://mekk.bitbucket.io/mercurial.html
If possible, it would be nice to copy also issues (esp. mercurial_keyring has some).
Question: what about new code? I have some ideas for the future…
Description of the projects to be hosted
- Project Name:
- Project URL:
- Project Maintainers:
- Project License:
Please explain here why they meet our current criteria.
All details are in the invitation announcement
To recapitulate, these are:
Main criteria
-
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
Priority Criteria
-
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.