Migration from bitbucket nmsdk
## Description of the projects to be hosted
* Project Name: Neuro Modeler
* Project URL: https://bitbucket.org/aicommunity/workspace/projects/nmsdk
* Project Maintainers: Alexab
* Project License: New BSD 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
- [ ] officially released
## Post approval maintainer task list:
See [README](README.md#maintainer-task-list-for-the-import-to-happen)
for explanations.
- [ ] 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
- [ ] 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, …)
/label ~"Hosting Request"
issue