heptapod issueshttps://foss.heptapod.net/groups/heptapod/-/issues2020-01-07T17:51:38Zhttps://foss.heptapod.net/heptapod/heptapod/-/issues/11Support ssh access to Mercurial repository2020-01-07T17:51:38ZGeorges RacinetSupport ssh access to Mercurial repository**Problem**
HTTPS access always ask for a password, and automated processes need to be able to identify with an SSH key.
Current version of heptapod allows ssh access to the Git repository, but writing to it is discouraged, and thi...**Problem**
HTTPS access always ask for a password, and automated processes need to be able to identify with an SSH key.
Current version of heptapod allows ssh access to the Git repository, but writing to it is discouraged, and this ability will be disabled by #17 as we don't know what will be broken if we do git changes and push them via git.
**Task description**
Enable the SSH gateway towards the Mercurial repositoryVersion 0.8.0https://foss.heptapod.net/heptapod/heptapod-runner/-/issues/11hg id is unavailable during CI/CD2023-01-05T14:29:06ZDavid Kane Schillingerhg id is unavailable during CI/CDI think this is more a question than a bug report or feature request so I'm hoping this is the right place to ask.
When running `hg id --id` in one of my CI configurations, I get the error:
`abort: repository requires features unknown ...I think this is more a question than a bug report or feature request so I'm hoping this is the right place to ask.
When running `hg id --id` in one of my CI configurations, I get the error:
`abort: repository requires features unknown to this Mercurial: sparserevlog!`
According to https://www.mercurial-scm.org/wiki/MissingRequirement `hg>=4.7` is required for `sparserevlog`.
I use the revision ID to easily verify that the deployed version of an app is exactly the revision I'm expecting.
Would we be able to upgrade `hg` on the runner to a version `>=4.7`?
If not, is it possible to easily parse out the revision from another `hg` command?
EDIT: `hg --version` returns `4.0`https://foss.heptapod.net/heptapod/omnibus-heptapod/-/issues/11latesttag is not enough2020-10-15T11:29:21ZGeorges Racinetlatesttag is not enoughAfter a merge from the stable branch to the main one, if `.hgtags` was merged, then it's possible that `hg log -r. -T {lattesttag}` returns the tag that has originally been set on the stable branch.
This is what happens in the build for...After a merge from the stable branch to the main one, if `.hgtags` was merged, then it's possible that `hg log -r. -T {lattesttag}` returns the tag that has originally been set on the stable branch.
This is what happens in the build for !7, whose resulting Debian package version is `0.16.1-1%2B4hg.72b78dcde4f0`, instead of starting with the expected `0.17.0~~pre` Of course that can't happen for a tagged release.
We should filter more agressively (we already consider only those tags that start with `heptapod-`), perhaps infering the wished prefix from the current content of `HEPTAPOD_VERSION`.Georges RacinetGeorges Racinethttps://foss.heptapod.net/heptapod/hgitaly/-/issues/11Bump protocol, at least to GitLab 13.32022-01-26T15:18:33ZGeorges RacinetBump protocol, at least to GitLab 13.3Currently the main development branch of Heptapod is based on GitLab 13.3, and it's quite possible that we bump to GitLab 13.4 for Heptapod 0.17.
But the Gitaly protocol we're using is older, dating back to GitLab 13.1 or even 12.x.Currently the main development branch of Heptapod is based on GitLab 13.3, and it's quite possible that we bump to GitLab 13.4 for Heptapod 0.17.
But the Gitaly protocol we're using is older, dating back to GitLab 13.1 or even 12.x.Heptapod 0.17.0Georges RacinetGeorges Racinethttps://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/54Hosting request for Trosnoth platform game2020-04-23T07:41:00ZJoshua D. BartlettHosting request for Trosnoth platform game## Description of the projects to be hosted
- Project Name: Trosnoth
- Project URL: https://trosnoth.org/
- Project Maintainers: Joshua D. Bartlett (@talljosh)
- Project License: GPLv2
This project meets all of the hosting criteria, in...## Description of the projects to be hosted
- Project Name: Trosnoth
- Project URL: https://trosnoth.org/
- Project Maintainers: Joshua D. Bartlett (@talljosh)
- Project License: GPLv2
This project meets all of the hosting criteria, including the priority criteria.
### Main criteria
- [x] **Free / Open Source**: published under GPLv2
- [x] **main development repositories**: this request is for the main Trosnoth repository
- [x] **agreement to acknowledge where appropriate the help provided by Octobus
and Clever Cloud by hosting on foss.heptapod.net**: if approved, I agree to acknowledge the help on the Trosnoth website on the development-related website pages
### Priority Criteria
- [x] **currently hosted on Bitbucket**: this repository is a Bitbucket refugee, currently hosted at https://bitbucket.org/talljosh/trosnoth/
- [x] **officially released**: Trosnoth 1.0 was released in 2009. The latest version was released in 2019, and the next release is still being developed.
## Post approval maintainer task list:
See [README](README.md#maintainer-task-list-for-the-import-to-happen)
for explanations.
- [x] Hosting Request assignee has repository membership on Bitbucket
- [x] Heptapod / Bitbucket accounts link
- [x] Reviewing Heptapod workflow
## Post import maintainer task list:
- [x] Clone the project afresh from foss.heptapod.net.
- [x] 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.
- [x] Check that issues are imported, and notably that all open issues are
there. Watch for attachments etc.
- [x] 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.
- [x] Check that against foss.heptapod.net, `hg outgoing` and `hg incoming`
from a prior clone are as expected
- [x] Add the Octobus and Clever cloud acknowledgement at the selected place.Georges RacinetGeorges Racinethttps://foss.heptapod.net/heptapod/heptapod/-/issues/12Filter out hg log when pushing2023-08-29T04:51:14ZGeorges RacinetFilter out hg log when pushing**Problem**
This is cosmetic, but it would be nice to not show the final user that we are (also) pusing to a git repo under the hood:
```
remote: pushing to git+ssh://git@localhost:org/project.git
```
Full log :
```
$ hg ...**Problem**
This is cosmetic, but it would be nice to not show the final user that we are (also) pusing to a git repo under the hood:
```
remote: pushing to git+ssh://git@localhost:org/project.git
```
Full log :
```
$ hg push forge
pushing to https://forge.example.org/org/project
searching for changes
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 1 changesets with 1 changes to 1 files
remote: pushing to git+ssh://git@localhost:org/project.git
remote: searching for changes
remote: adding objects
remote: added 1 commits with 1 trees and 1 blobs
```
There is even a case where there is a double remote output, like:
```
remote: remote: something
```
**Task description**
Enhance the remote output with a filter, which silences the normal git output, but still shows errors in order to facilitate investigation and debugging.https://foss.heptapod.net/heptapod/heptapod-runner/-/issues/12Run `hg recover`2022-01-18T13:54:05ZGeorges RacinetRun `hg recover`It can happen that we have interrupted pulls in our builds, leading to Mercurial needing `hg recover` before any subsequent pull can succeed. Here's an [example](https://foss.heptapod.net/octobus/mercurial-devel/-/jobs/68966).
In the ru...It can happen that we have interrupted pulls in our builds, leading to Mercurial needing `hg recover` before any subsequent pull can succeed. Here's an [example](https://foss.heptapod.net/octobus/mercurial-devel/-/jobs/68966).
In the runner context, we don't have an easy way to introspect the state of the repository and act accordingly. But `hg recover` is cheap if it has nothing to do, so we could run it systematically.https://foss.heptapod.net/heptapod/website/-/issues/12The website is not responsive?2020-06-15T14:54:51ZPierre AugierThe website is not responsive?The width of the page does not adapt to small screens (at least on mine phone, which is running UBports).
Note : same with https://octobus.net/The width of the page does not adapt to small screens (at least on mine phone, which is running UBports).
Note : same with https://octobus.net/https://foss.heptapod.net/heptapod/omnibus-heptapod/-/issues/12HGitaly service2020-10-15T11:28:51ZGeorges RacinetHGitaly serviceShould be easy, just a variation on work done for #10.
Could perhaps be backported to the 0.16 series, if the timing makes sense, but that's a stretch: it would make us rebuild Mercurial entirely for the Python 3.7 built by Omnibus (se...Should be easy, just a variation on work done for #10.
Could perhaps be backported to the 0.16 series, if the timing makes sense, but that's a stretch: it would make us rebuild Mercurial entirely for the Python 3.7 built by Omnibus (see #4).Heptapod 0.17.0Georges RacinetGeorges Racinethttps://foss.heptapod.net/heptapod/hgitaly/-/issues/12CommitService: implement CommitLanguages2023-09-04T20:59:00ZGeorges RacinetCommitService: implement CommitLanguagesThis is about programming or markup language detection, as opposed to natural languages.
It will be a tough one: in Gitaly, it is handled by the Ruby side, using the [GitHub linguist](https://github.com/github/linguist) gem, which could...This is about programming or markup language detection, as opposed to natural languages.
It will be a tough one: in Gitaly, it is handled by the Ruby side, using the [GitHub linguist](https://github.com/github/linguist) gem, which could well be very Git specific.
Including Ruby gems in HGitaly would be a pain (as it is with Gitaly actually, because of side effects between bundles), and it's not clear if could just feed diffs and files extracted from Mercurial programming to primitives purely about language detection.
On the other hand, using anything else will bring us visible changes in results that may be undesirable, and reimplementing everything is probably too much work in the short term.HGitaly2: fully nativeGeorges RacinetGeorges Racinethttps://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/59Hosting request for JavaHg and MercurialEclipse on Bitbucket2020-07-03T09:49:29ZAmenel VoglozinHosting request for JavaHg and MercurialEclipse on Bitbucket## Description of the projects to be hosted
**JavaHg**
- Project Name: JavaHg
- Project URL: https://bitbucket.org/aragost/javahg/
- Project Maintainers: Amenel Voglozin
- Project License: MIT
**MercurialEclipse**
- Project Name: Mer...## Description of the projects to be hosted
**JavaHg**
- Project Name: JavaHg
- Project URL: https://bitbucket.org/aragost/javahg/
- Project Maintainers: Amenel Voglozin
- Project License: MIT
**MercurialEclipse**
- Project Name: MercurialEclipse
- Project URL: https://bitbucket.org/mercurialeclipse/main
- Project Maintainers: Amenel Voglozin
- Project License: EPL 1.0
Please explain here why they meet our current criteria.
All details are in the [invitation announcement](https://heptapod.net/a-public-heptapod-for-free-and-open-source-software.html#a-public-heptapod-for-free-and-open-source-software)
To recapitulate, these are:
### Main criteria
- [x] Free / Open Source
- [x] main development repositories
- [x] agreement to acknowledge where appropriate the help provided by Octobus
and Clever Cloud by hosting on foss.heptapod.net
I have been the maintainer of JavaHg and MercurialEclipse for a few years at these official repositories. For instance, all plugins of JavaHg, which were in separate repositories, have been unified. Even though I can't assess the installed base and how wide their respective usage is, I believe it is essential that these two projects remain free and open source. Other obligations (and the lack of knowledge of Heptapod's existence) have prevented me from making this request sooner.
As can be seen in the projects, for instance in MercurialEclipse release notes, the acknowledgment of the help received is part of the projects' culture.
### Priority Criteria
- [x] currently hosted on Bitbucket
- [x] officially released
Both projects have been hosted on Bitbucket for a few years and all versions released in that time are publicly available within the repository (for JavaHg) or in a companion repository (<https://bitbucket.org/mercurialeclipse/update-site/>) for MercurialEclipse.
**NOTE**: versions of JavaHg since I took over as the maintainer cannot be found on Maven Central due to the original authors having lost their signing keys.
## Post approval maintainer task list:
See [README](README.md#maintainer-task-list-for-the-import-to-happen)
for explanations.
- [x] Hosting Request assignee has repository membership on Bitbucket
- [x] Heptapod / Bitbucket accounts link
- [x] Reviewing Heptapod workflow
## Post import maintainer task list:
- [x] Clone the project afresh from foss.heptapod.net.
- [x] 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.
- [x] 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.
- [x] Check that against foss.heptapod.net, `hg outgoing` and `hg incoming`
from a prior clone are as expected
- [x] Add the Octobus and Clever cloud acknowledgement at the selected place.
- [x] Communicate about the migration to help others to aware of the options
(for example on mastodon, twitter, bitbucket thread, mailing list, …)Georges RacinetGeorges Racinethttps://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/3Hosting request - mercurial_keyring, mercurial_update_version, …2020-06-27T22:48:14ZMarcin KasperskiHosting 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 n...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](https://heptapod.net/a-public-heptapod-for-free-and-open-source-software.html#a-public-heptapod-for-free-and-open-source-software)
To recapitulate, these are:
### Main criteria
- [x] Free / Open Source
- [x] main development repositories
- [x] agreement to acknowledge where appropriate the help provided by Octobus
and Clever Cloud by hosting on foss.heptapod.net
### Priority Criteria
- [x] currently hosted on Bitbucket
- [x] officially released
## Post approval maintainer task list:
See [README](README.md#maintainer-task-list-for-the-import-to-happen)
for explanations.
- [x] Hosting Request assignee has repository membership on Bitbucket
- [x] Heptapod / Bitbucket accounts link
- [x] Reviewing Heptapod workflow
## Post import maintainer task list:
- [x] Clone the project afresh from foss.heptapod.net.
- [x] 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.
- [x] 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.
- [x] Check that against foss.heptapod.net, `hg outgoing` and `hg incoming`
from a prior clone are as expected
- [x] Add the Octobus and Clever cloud acknowledgement at the selected place.Pierre AugierPierre Augierhttps://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/22Request hosting for the 'b' Mercurial extension2020-04-16T21:49:02ZMichael DiamondRequest hosting for the 'b' Mercurial extension## Description of the projects to be hosted
Please explain here why they meet our current criteria.
I was pointed to Heptapod by Pierre-Yves David after I [migrated my 'b' extension from BitBucket to GitHub](https://www.mercurial-scm.o...## Description of the projects to be hosted
Please explain here why they meet our current criteria.
I was pointed to Heptapod by Pierre-Yves David after I [migrated my 'b' extension from BitBucket to GitHub](https://www.mercurial-scm.org/wiki/bExtension?action=diff&rev1=9&rev2=10). I'd much rather keep it as a Mercurial repo, so it would be great to be able to host it here instead of GitHub.
**http://bitbucket.org/dimo414/b**
---
All details are in the [invitation announcement](https://heptapod.net/a-public-heptapod-for-free-and-open-source-software.html#a-public-heptapod-for-free-and-open-source-software)
To recapitulate, these are:
- [x] Free / Open Source
- [x] main development repositories
- [x] agreement to acknowledge where appropriate the help provided by Octobus
and Clever Cloud by hosting on foss.heptapod.net
- [x] currently hosted on Bitbucket
- [x] officially released
## Post approval maintainer task list:
See [README](README.md#maintainer-task-list-for-the-import-to-happen)
for explanations.
- [x] @gracinet repository membership on Bitbucket
- [x] Heptapod / Bitbucket accounts link
- [x] Reviewing Heptapod workflowGeorges RacinetGeorges Racinethttps://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/20Please add smart to the FOSS public instance2021-07-21T15:31:59ZChuck TuffliPlease add smart to the FOSS public instance## Description of the projects to be hosted
Please explain here why they meet our current criteria.
All details are in the [invitation announcement](https://heptapod.net/a-public-heptapod-for-free-and-open-source-software.html#a-public...## Description of the projects to be hosted
Please explain here why they meet our current criteria.
All details are in the [invitation announcement](https://heptapod.net/a-public-heptapod-for-free-and-open-source-software.html#a-public-heptapod-for-free-and-open-source-software)
To recapitulate, these are:
- [x] Free / Open Source
- [x] main development repositories
- [x] agreement to acknowledge where appropriate the help provided by Octobus
and Clever Cloud by hosting on foss.heptapod.net
- [x] currently hosted on Bitbucket
- [x] officially released
I am the creator and maintainer for smart (https://bitbucket.org/ctuffli/smart), an ISC licensed command line utility to retrieve SMART data from disk drives. The application is actively used in the FreeBSD community and has been packaged (sysutils/smart). All development is done in the BitBucket repository, but there is a read-only mirror on GitHub exclusively to simplify packaging.
## Post approval maintainer task list:
See [README](README.md#maintainer-task-list-for-the-import-to-happen)
for explanations.
- [x] @gracinet repository membership on Bitbucket
- [x] Heptapod / Bitbucket accounts link
- [x] Reviewing Heptapod workflowhttps://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/57Import openpyxl repository2021-04-06T15:10:38ZCharlieCImport openpyxl repository## Description of the projects to be hosted
- Project Name: openpyxl
- Project URL: https://bitbucket.org/openpyxl/openpyxl/src/default/
- Project Maintainers: Charlie Clark
- Project License: MIT
- Project Name: et_xmlfile
- Project U...## Description of the projects to be hosted
- Project Name: openpyxl
- Project URL: https://bitbucket.org/openpyxl/openpyxl/src/default/
- Project Maintainers: Charlie Clark
- Project License: MIT
- Project Name: et_xmlfile
- Project URL: https://bitbucket.org/openpyxl/et_xmlfile/src/default/
- Project Maintainers: Charlie Clark
- Project License: MIT
Please explain here why they meet our current criteria.
All details are in the [invitation announcement](https://heptapod.net/a-public-heptapod-for-free-and-open-source-software.html#a-public-heptapod-for-free-and-open-source-software)
To recapitulate, these are:
### Main criteria
- [x] Free / Open Source
- [x] main development repositories
- [x] agreement to acknowledge where appropriate the help provided by Octobus
and Clever Cloud by hosting on foss.heptapod.net
### Priority Criteria
- [x] currently hosted on Bitbucket
- [x] officially released
## Post approval maintainer task list:
See [README](README.md#maintainer-task-list-for-the-import-to-happen)
for explanations.
- [x] Hosting Request assignee has repository membership on Bitbucket
- [x] Heptapod / Bitbucket accounts link
- [ ] Reviewing Heptapod workflow
## Post import maintainer task list:
- [x] 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.
- [x] 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` and `hg incoming`
from a prior clone are as expected
- [x] Add the Octobus and Clever cloud acknowledgement at the selected place.Georges RacinetGeorges Racinethttps://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/42Hosting request for the Mercurial guest-repo extension.2020-05-26T10:23:36ZPierre-Yves DavidHosting request for the Mercurial guest-repo extension.The `guestrepo` extension is a small extension that aim at keeping track of compatible revision for a groupe of repository
All details are in the [invitation announcement](https://heptapod.net/a-public-heptapod-for-free-and-open-source-...The `guestrepo` extension is a small extension that aim at keeping track of compatible revision for a groupe of repository
All details are in the [invitation announcement](https://heptapod.net/a-public-heptapod-for-free-and-open-source-software.html#a-public-heptapod-for-free-and-open-source-software)
To recapitulate, these are:
- [x] Free / Open Source
- [x] main development repositories (Got other maintainer approval)
- [x] agreement to acknowledge where appropriate the help provided by Octobus
and Clever Cloud by hosting on foss.heptapod.net
- [x] currently hosted on Bitbucket
- [x] officially released
## Post approval maintainer task list:
See [README](README.md#maintainer-task-list-for-the-import-to-happen)
for explanations.
- [x] Hosting Request assignee has repository membership on Bitbucket
- [x] Heptapod / Bitbucket accounts link
- [x] Reviewing Heptapod workflow
## Post import maintainer task list:
- [x] Clone the project afresh from foss.heptapod.net.
- [x] 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.
- [x] Check that issues are imported, and notably that all open issues are
there. Watch for attachments etc.
- [x] 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.
- [x] Check that against foss.heptapod.net, `hg outgoing` and `hg incoming`
from a prior clone are as expected
- [x] Add the Octobus and Clever cloud acknowledgement at the selected place.Pierre-Yves DavidPierre-Yves Davidhttps://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/43Need new home for XEmacs2020-05-02T11:35:39ZMichael SperberNeed new home for XEmacs## Description of the projects to be hosted
XEmacs is an open-source project that has existed since 1998 or so.
For many years, it has been hosted on Bitbucket:
https://bitbucket.org/%7B3b4cf16a-308f-4e0a-a7cc-f0d363c12b0c%7D/
I requ...## Description of the projects to be hosted
XEmacs is an open-source project that has existed since 1998 or so.
For many years, it has been hosted on Bitbucket:
https://bitbucket.org/%7B3b4cf16a-308f-4e0a-a7cc-f0d363c12b0c%7D/
I request to move the development repositories as well
as the website repo over to Heptapod FOSS.
I'd be happy to put acknowledgements on the xemacs.org website.
To recapitulate, these are:
- [X] Free / Open Source
- [X] main development repositories
- [X] agreement to acknowledge where appropriate the help provided by Octobus
and Clever Cloud by hosting on foss.heptapod.net
- [X] currently hosted on Bitbucket
- [X] officially released
Your help would be much appreciated!
## Post approval maintainer task list:
See [README](README.md#maintainer-task-list-for-the-import-to-happen)
for explanations.
- [x] 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` and `hg incoming`
from a prior clone are as expected
- [ ] Add the Octobus and Clever cloud acknowledgement at the selected place.Georges RacinetGeorges Racinethttps://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/52hgview2020-04-14T08:29:47ZNicolas Chauvathgview## Description of the projects to be hosted
- Project Name: hgview
- Project URL: https://bitbucket.org/logilab/hgview
- Project Maintainers: Logilab and others
- Project License: GPL
Please explain here why they meet our current crite...## Description of the projects to be hosted
- Project Name: hgview
- Project URL: https://bitbucket.org/logilab/hgview
- Project Maintainers: Logilab and others
- Project License: GPL
Please explain here why they meet our current criteria.
hgview has been developed at Logilab's forge, then moved to bitbucket. We would like to move it to foss.heptapod.net in order to share it easily with more contributors. If our request is rejected, we will move hgview to the heptapod hosted at Logilab, but we think it would be better if it were not to rely on our hosting, since it will make it look less "mainstream".
All details are in the [invitation announcement](https://heptapod.net/a-public-heptapod-for-free-and-open-source-software.html#a-public-heptapod-for-free-and-open-source-software)
To recapitulate, these are:
### Main criteria
- [X] Free / Open Source
- [X] main development repositories
- [X] agreement to acknowledge where appropriate the help provided by Octobus
and Clever Cloud by hosting on foss.heptapod.net
### Priority Criteria
- [X] currently hosted on Bitbucket
- [X] officially released
## Post approval maintainer task list:
See [README](README.md#maintainer-task-list-for-the-import-to-happen)
for explanations.
- [x] Hosting Request assignee has repository membership on Bitbucket
- [ ] Heptapod / Bitbucket accounts link
- [ ] Reviewing Heptapod workflow
## Post import maintainer task list:
- [x] Clone the project afresh from foss.heptapod.net.
- [x] 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.
- [x] Check that issues are imported, and notably that all open issues are
there. Watch for attachments etc.
- [x] 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.
- [x] Check that against foss.heptapod.net, `hg outgoing` and `hg incoming`
from a prior clone are as expected
- [x] Add the Octobus and Clever cloud acknowledgement at the selected place.Pierre AugierPierre Augierhttps://foss.heptapod.net/heptapod/heptapod/-/issues/13menu Repository > {Graph,Contributors,Charts} seems broken2020-04-24T13:59:21ZGeorges Racinetmenu Repository > {Graph,Contributors,Charts} seems brokenthese menus give a 404 on our instance (based on 992dce5cd78)these menus give a 404 on our instance (based on 992dce5cd78)https://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/13Import process: untie from @gracinet personal bitbucket account2020-07-19T16:10:43ZGeorges RacinetImport process: untie from @gracinet personal bitbucket accountWe have this technical requirement of adding me, @gracinet, to the project members, so that it gets listed on the Bitbucket import page.
Obviously this is subpar and doesn't scale. Some ideas:
- make a true Bitbucket account for @bitbu...We have this technical requirement of adding me, @gracinet, to the project members, so that it gets listed on the Bitbucket import page.
Obviously this is subpar and doesn't scale. Some ideas:
- make a true Bitbucket account for @bitbucket_importer and share its password with all administrators of foss.heptapod.net
- change to membership by the heptapod_net team, if that's even possible (needs to be tested)
- adapt the import page to replace the filtering based on membership by filtering based on path of public projects. More recent GitLab versions have such a filter, but I think it's on top of the membership. We'd have to add an additional page to give the path before displaying.