FOSS public instance issueshttps://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues2020-08-06T06:48:38Zhttps://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/14Hosting downloads on this instance2020-08-06T06:48:38ZMatti PicusHosting downloads on this instanceCurrently the canonical place to find PyPy downloads is https://bitbucket.org/pypy/pypy/downloads/. Will there be a similar option to host downloads here or should we search for an alternative?
Also, I see on gitlab.com there is an opti...Currently the canonical place to find PyPy downloads is https://bitbucket.org/pypy/pypy/downloads/. Will there be a similar option to host downloads here or should we search for an alternative?
Also, I see on gitlab.com there is an option for a repo to have a wiki. Will that be enabled on the FOSS instances?
Updated 08-2020: removed wiki from the title since it is now supportedhttps://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/18Precisions about the help acknowledgement2020-05-03T21:10:01ZGeorges RacinetPrecisions about the help acknowledgementBoth the original announcement and [README](README.md) have this:
> acknowledge the help on their official web page by inserting links and logos to Clever Cloud and Octobus at the appropriate place, e.g, on the page that provides the de...Both the original announcement and [README](README.md) have this:
> acknowledge the help on their official web page by inserting links and logos to Clever Cloud and Octobus at the appropriate place, e.g, on the page that provides the development instructions.
Questions originally posted by @mattip
- do we provide a template ?
- Is this a pre-condition or do we have to verify in 4 weeks that the project(s) have implemented this?https://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/19favicon are missing2020-03-10T09:14:35ZPierre-Yves Davidfavicon are missingSince the `https://dev.heptapod.net/` to `https://foss.heptapod.net/` migration, the favicon are missing,
The main one is now working, but the subone does not: For example:
https://foss.heptapod.net/assets/ci_favicons/favicon_status_pe...Since the `https://dev.heptapod.net/` to `https://foss.heptapod.net/` migration, the favicon are missing,
The main one is now working, but the subone does not: For example:
https://foss.heptapod.net/assets/ci_favicons/favicon_status_pending-5ecc554aa46a62bdb293a698e37f1fa6e2eda95f130ef8a311a5d800147ba257.icohttps://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/23Project group policy2020-02-13T22:22:08ZGeorges RacinetProject group policyWhat should be the target group for a project that's requesting to be hosted here? In any case, agreeing on the target group should be in the HR task lists.
We already have several Hosting Requests for projects that are on Bitbucket sid...What should be the target group for a project that's requesting to be hosted here? In any case, agreeing on the target group should be in the HR task lists.
We already have several Hosting Requests for projects that are on Bitbucket side in the personal space of their maintainer. Do we want to do the same on Heptapod?
Technically, it should be possible to do the same on Heptapod but
- I'm not sure we can use the `Bitbucket Importer` special user for that, we'd probably need to import somewhere else first, and then transfer to the personal namespace (untested at this point)
- We don't really support personal projects, in the sense of the user being able to create new projects at will in their personal space. Does it introduce confusion about that to import projects that meet the requirements there?https://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/25Please import TortoiseHg and its related collateral2020-07-17T14:26:57ZMatt HarbisonPlease import TortoiseHg and its related collateral## 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
TortoiseHg is a popular cross platform GUI for Mercurial. @marmoute confirmed on IRC and on the mailing list that this would be eligible (though the number of dependencies is a bit surprising).
The main repo for the app is here:
https://bitbucket.org/tortoisehg/thg/
The repos for doing Windows builds are here:
https://bitbucket.org/tortoisehg/thg-build
https://bitbucket.org/tortoisehg/thg-winbuild
There are a couple of other repos that I'm not familiar with here:
https://bitbucket.org/account/user/tortoisehg/projects/PROJ
I think the "files" one was just a hack so they wouldn't hide the downloads page.
In addition, setup.py in thg-build clones the following list of repos, some of which are now hosted on Heptapod, some (e.g. keyring) are in progress:
https://bitbucket.org/tortoisehg/thg-build/src/default/repolist.txt
I'm not the maintainer, but the discussion is here:
https://groups.google.com/d/msg/thg-dev/4U0fy2MfURQ/n9RJknnxAwAJ
In addition to the repos, we should probably archive the previous builds (maybe on m-s.o if there's no ability/space to host random files here), because they are basically impossible to recreate:
https://bitbucket.org/tortoisehg/files/downloads/
## 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/27Setup clonebundles2020-02-12T14:10:41ZPierre-Yves DavidSetup clonebundlesOnce heptapod/heptapod#189 will be done, we should use it for FOSS, it will creatly help scalability by diverging traffic to a separated instance.Once heptapod/heptapod#189 will be done, we should use it for FOSS, it will creatly help scalability by diverging traffic to a separated instance.https://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/28LFS setup2020-02-12T14:22:24ZPierre-Yves DavidLFS setupWhen the work in heptapod/heptapod#191 will done, it would make sense to have some LFS option available on `https://foss.heptapod.net/When the work in heptapod/heptapod#191 will done, it would make sense to have some LFS option available on `https://foss.heptapod.net/https://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/29Gather statistic about client connecting to the instance2020-02-12T14:24:35ZPierre-Yves DavidGather statistic about client connecting to the instanceOnce heptapod/heptapod#190 is done we should gather statistic about the client connecting the foss.heptapod.net (like, hg version, repository format, etc).Once heptapod/heptapod#190 is done we should gather statistic about the client connecting the foss.heptapod.net (like, hg version, repository format, etc).https://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/34add a link to request developer status2020-02-17T16:35:36ZMatti Picusadd a link to request developer statusUntil there are personal forks, only developers can issue merge requests which increases drive-by contributor's friction: they need to find the "request access" link on the pypy group to get access to the pypy project.
We would like to p...Until there are personal forks, only developers can issue merge requests which increases drive-by contributor's friction: they need to find the "request access" link on the pypy group to get access to the pypy project.
We would like to publish a link in our external documentation to the "request access" link, currently https://foss.heptapod.net/groups/pypy/-/group_members/request_access, but it needs some authentication to work.https://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/48Migrate ZILF repos from Bitbucket2020-09-21T17:22:19ZTara McGrewMigrate ZILF repos from Bitbucket## Description of the projects to be hosted
ZILF is an open source tool chain for the Zork Implementation Language, used to write interactive fiction (text adventure games). The source code for Infocom's classic adventure games was uplo...## Description of the projects to be hosted
ZILF is an open source tool chain for the Zork Implementation Language, used to write interactive fiction (text adventure games). The source code for Infocom's classic adventure games was uploaded to GitHub in 2019, but with the original tools still missing, ZILF is the only known way to compile them.
The tools are licensed under GPL v3. The runtime library, to be incorporated into newly written games, is licensed under a BSD-alike license.
It's currently hosted on Bitbucket, at https://bitbucket.org/jmcgrew/zilf/, with a decade of change history and binary releases.
Some dependencies are also hosted at Bitbucket:
* https://bitbucket.org/jmcgrew/zil-editor-support
* https://bitbucket.org/jmcgrew/zlr
* https://bitbucket.org/zilf/vscode-zil-language
* https://bitbucket.org/zilf/zil-docs
Hosting support will be acknowledged where appropriate if this request is accepted.
## 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.
- [ ] 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.https://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/63VisualHg22020-07-17T10:35:41ZDmitry PopovVisualHg2## Description of the projects to be hosted
- Project Name: VisualHg2 (hermian - new name)
- Project URL: https://bitbucket.org/lmn/visualhg2
- Project Maintainers: Dmitry Popov
- Project License: GNU General Public License (GPL) (v2.0)...## Description of the projects to be hosted
- Project Name: VisualHg2 (hermian - new name)
- Project URL: https://bitbucket.org/lmn/visualhg2
- Project Maintainers: Dmitry Popov
- Project License: GNU General Public License (GPL) (v2.0)
VisualHg2 is a fork of VisualHG, a Visual Studio extension for TortoiseHg/Mercurial integration.
While the project is not under active development, it still might be relevant for Mercurial/Visual Studio community however small it may be. The extension was not published officially to the Visual Studio Marketplace and never got a user base. Looking at the similar extensions currently available, I assume it could gain some user attention even today. VisualHG was hosted on CodePlex, now archived (https://archive.codeplex.com/?p=visualhg) and is available on GitHub (https://github.com/BerndSchrader/VisualHG). The project is abandoned and the forks that continue to appear never get any further than supporting a new Visual Studio version, which is sad. VisualHg2 was thought as a more radical improvement, considering both user experience and the quality of code.
Berndt Schrader, the author and maintainer of the original VisualHG, abandoned the project long ago, returning to it a couple of times after I contacted him in 2013, just to release the extension to the Marketplace. He approved of the changes I made, but with the code largely rewritten, he declined the merge and asked me to change the name. I didn't come up with another name and didn't release it, as I decided to stay underground.
I understand that this project doesn't quite meet the criteria for free hosting, but migrating a Mercurial tool code to a git repository is something I'd really like to avoid.
If the project is approved, I'll release the extension officially, acknowledging the help by Octobus and Clever Cloud. However, in that case I'll need to change the name of the project, as Berndt wished, and "hermian" seems like an OK name to me.
Thank you for your attention and, as a person who uses hg every day, I'd like to thank you for keeping Mercurial alive.
### 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
- [ ] officially released (not released to Visual Studio Marketplace)
## Post approval maintainer task list:
See [README](README.md#maintainer-task-list-for-the-import-to-happen)
for explanations.
- [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
- [ ] Add the Octobus and Clever cloud acknowledgement at the selected place.
- [ ] Communicate about the migration to help others to aware of the options
(for example on mastodon, twitter, bitbucket thread, mailing list, …)https://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/64Pull errors in CI2020-05-27T10:28:14ZGeorges RacinetPull errors in CII get a few errors in CI on this instance these days, in which pulling the source failed, for example https://foss.heptapod.net/heptapod/heptapod-shell/-/jobs/76572.
The message is always `abort: error: Try again`.
Usually (always?) a ...I get a few errors in CI on this instance these days, in which pulling the source failed, for example https://foss.heptapod.net/heptapod/heptapod-shell/-/jobs/76572.
The message is always `abort: error: Try again`.
Usually (always?) a retry is enough
At this point I don't whether it's instance specific or a general Heptapod issue. So far, I don't know which component is producing that message.https://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/67roadmap for foss.heptapod.net - allow traditional workflows2020-06-02T08:53:45ZMatti Picusroadmap for foss.heptapod.net - allow traditional workflowsIs there a public roadmap for the short-term goals of foss.heptapod.net where we could get an idea of where the project is heading? My top concerns is to allow a workflow that does not require using topic branches (i.e. a traditional for...Is there a public roadmap for the short-term goals of foss.heptapod.net where we could get an idea of where the project is heading? My top concerns is to allow a workflow that does not require using topic branches (i.e. a traditional fork/MR workflow). This is a major break with other code hosting sites and makes the barrier for getting involved in our projects that much higher.https://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/68Hosting request for Magic Lantern (firmware add-on for Canon DSLRs)2020-09-22T09:18:50ZAlexHosting request for Magic Lantern (firmware add-on for Canon DSLRs)## Description of the projects to be hosted
- Project Name: Magic Lantern
- Project URL: https://bitbucket.org/hudson/magic-lantern, https://www.magiclantern.fm
- Project Maintainers: a1ex (a1ex@magiclantern.fm), g3gg0 (ml@g3gg0.de)
- P...## Description of the projects to be hosted
- Project Name: Magic Lantern
- Project URL: https://bitbucket.org/hudson/magic-lantern, https://www.magiclantern.fm
- Project Maintainers: a1ex (a1ex@magiclantern.fm), g3gg0 (ml@g3gg0.de)
- Project License: GPLv2
Hi, we are looking for a new home for the source code repository of Magic Lantern, which is currently hosted on Bitbucket (Mercurial). Magic Lantern is relatively well-known among Canon DSLR users; it was started back in 2009 by Trammell Hudson (https://trmm.net/Magic_Lantern_firmware) and adds several features, developed from scratch, to camera firmware. It runs on top of camera's operating system (DryOS), fully usable on most DIGIC 4 and 5 EOS cameras at the time of writing, and there are porting efforts for both newer (DIGIC 6/7/8) and older (DIGIC 2/3) models.
The "obvious" choice for moving the repository would have been Github/Gitlab, but we prefer to keep the Mercurial workflow. We have already tried to convert our repository to Git using various tools (hg-git, hg-fast-export, git-hg, git-hg-again), unfortunately with only partial success. Main issue: the conversion does not keep Mercurial changeset IDs (referenced in many places in our documentation and technical discussions). There are also a few corner cases with unusual branch names that were generated by Bitbucket when users contributed small changes via their web interface.
We are here at the suggestion of @antocuni from the PyPy project (already hosted here). After researching things a bit and noticing your (well, Octobus') activities in archiving existing Bitbucket content, alongside with Software Heritage, Heptapod came on top of my choices for a new Mercurial host. I also appreciate the ability to import Bitbucket data, including issues and open pull requests, and the option to login with Bitbucket and Github credentials - hopefully this should make the transition a lot easier for existing contributors.
I understand there will be a change in workflow, as personal forks are not supported, but I'm sure we'll figure it out. I still have to research things a bit before importing the currently-pending changes from other contributors (which are stored in their personal forks for now).
As for the group name, I'm not sure what to suggest, as there are not many camera firmware projects around, and most of them are not hosted on Bitbucket anyway. However, we do have a few related projects, such as MlRawViewer, MLVFS, MLV App, Switch, ml-focus-pixels, ufraw-mod and others, which are standalone repositories (some of them use Git, others Mercurial). So, a group name like "magic-lantern" might be appropriate, if you ask me.
Thanks for considering!
P.S. Right before noticing your Bitbucket archiving project, I have started my own small-scale backup of currently-available Mercurial repositories on Bitbucket (plain "hg clone" followed by tar archive). If you think it could be useful (e.g. for cross-checking the list of repositories or available changesets), kindly let me know where's the best place to discuss this further.
### 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] Heptapod / Bitbucket accounts link
- [ ] Reviewing [Heptapod workflow](https://heptapod.net/pages/faq.html#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. [ some issues missing; reported below ]
- [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. [ error merging MR #963 ]
- [ ] 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.
- [X] Communicate about the migration to help others to aware of the options [ [on our forum](https://www.magiclantern.fm/forum/index.php?topic=24420.msg228034#msg228034); initial suggestion [here](https://www.magiclantern.fm/forum/index.php?topic=24420.msg227797#msg227797) ]https://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/71Import libgf2 and jlibgf2 repositories for GF(2^n) finite field computation i...2020-06-28T22:27:08ZJason SachsImport libgf2 and jlibgf2 repositories for GF(2^n) finite field computation in Python and Java## Description of the projects to be hosted
The following are Python and Java libraries for computation in finite fields GF(2^n); I wrote a series of articles on embeddedrelated.com that explain some of the mathematics behind finite fie...## Description of the projects to be hosted
The following are Python and Java libraries for computation in finite fields GF(2^n); I wrote a series of articles on embeddedrelated.com that explain some of the mathematics behind finite fields and it utilizes the libgf2 library. (see https://www.embeddedrelated.com/showarticle/1070.php)
- Project Name: libgf2
- Project URL: https://bitbucket.org/jason_s/libgf2/src/default/
- Project Maintainers: Jason Sachs
- Project License: Apache
- Project Name: jlibgf2
- Project URL: https://bitbucket.org/jason_s/jlibgf2/src/default/
- Project Maintainers: Jason Sachs
- Project License: Apache
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] Heptapod / Bitbucket accounts link
- [x] Reviewing [Heptapod workflow](https://heptapod.net/pages/faq.html#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
- [ ] Add the Octobus and Clever cloud acknowledgement at the selected place.
- [ ] Communicate about the migration to help others to aware of the options
(for example on mastodon, twitter, bitbucket thread, mailing list, …)https://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/72Set hook `pretxnclose.heptapod_check_publish=` on two isa-afp repos2021-02-04T21:03:19ZGerwin KleinSet hook `pretxnclose.heptapod_check_publish=` on two isa-afp reposNot sure if this is the right place to ask, but I'd like to set
```
[hooks]
pretxnclose.heptapod_check_publish=
```
for the the two repositories [isa-afp/af-devel](http://foss.heptapod.net/isa-afp/afp-devel) and [isa-afp/afp-testboard]...Not sure if this is the right place to ask, but I'd like to set
```
[hooks]
pretxnclose.heptapod_check_publish=
```
for the the two repositories [isa-afp/af-devel](http://foss.heptapod.net/isa-afp/afp-devel) and [isa-afp/afp-testboard](http://foss.heptapod.net/isa-afp/afp-testboard).
According to the FAQ, this should allow people in the `Developer` role to push directly to the default branch, which is something we'd like (`Maintainer` rights are too much, and not all logicians and mathematicians are that firm in version control and installing an extension for topics).
If I've understood correctly, this needs to happen on the server side to which we don't have access on the foss instance. Is that something you could do for us or should I be using some API/setting that I haven't found yet?Georges RacinetGeorges Racinethttps://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/74Commit messages autoclose not working2020-07-10T13:06:37ZCharlieCCommit messages autoclose not workingThis may just be me getting used to the setup but I'm used to closing/resolving issues via the commit message but this isn't happening so far. I looked at the regex and it looks correct and it looks active. I wonder if it's related to mu...This may just be me getting used to the setup but I'm used to closing/resolving issues via the commit message but this isn't happening so far. I looked at the regex and it looks correct and it looks active. I wonder if it's related to multiline commit messages, as I normally put the command in a separate line.https://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/75Hosting pages2023-02-22T19:45:38ZMatti PicusHosting pagesIs there any chance we could get something like github pages? I see [gitlab supports the feature](https://docs.gitlab.com/ee/user/project/pages/). I would like to do something like [this blog](https://www.varrazzo.com/blog/) for PyPy, wh...Is there any chance we could get something like github pages? I see [gitlab supports the feature](https://docs.gitlab.com/ee/user/project/pages/). I would like to do something like [this blog](https://www.varrazzo.com/blog/) for PyPy, which is hosted via [this repo](https://github.com/dvarrazzo/www.varrazzo.com) and uses issues and [utterance bot](https://github.com/dvarrazzo/www.varrazzo.com/issues/9) for discussions. That would drive people to sign up for heptapod to comment.https://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/77Hosting request for grin32020-08-04T09:15:17ZRaffaele SalmasoHosting request for grin3## Description of the projects to be hosted
- Project Name: grin3
- Project URL: https://github.com/rsalmaso/grin3.git (was: https://bitbucket.org/rsalmaso/grin3)
- Project Maintainers: Raffaele Salmaso
- Project License: BSD
Please ex...## Description of the projects to be hosted
- Project Name: grin3
- Project URL: https://github.com/rsalmaso/grin3.git (was: https://bitbucket.org/rsalmaso/grin3)
- Project Maintainers: Raffaele Salmaso
- Project License: BSD
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
- [ ] currently hosted on Bitbucket
- [X] was 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.
- [ ] Hosting Request assignee has repository membership on Bitbucket
- [ ] Heptapod / Bitbucket accounts link
- [ ] Reviewing [Heptapod workflow](https://heptapod.net/pages/faq.html#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.
- [ ] Communicate about the migration to help others to aware of the options
(for example on mastodon, twitter, bitbucket thread, mailing list, …)https://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/80Discoverability and search2021-07-11T12:46:13ZMatti PicusDiscoverability and searchEven when I specify heptapod, google/duckduckgo do not show me heptapod/pypy/pypy when I search for "pypy +heptapod". I would expect it to be the top result by now. Is there some robot.txt blocking the site? Try it with a clean browser.Even when I specify heptapod, google/duckduckgo do not show me heptapod/pypy/pypy when I search for "pypy +heptapod". I would expect it to be the top result by now. Is there some robot.txt blocking the site? Try it with a clean browser.