Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

synerbi transition: #614

Closed
14 of 21 tasks
paskino opened this issue Apr 3, 2020 · 29 comments
Closed
14 of 21 tasks

synerbi transition: #614

paskino opened this issue Apr 3, 2020 · 29 comments

Comments

@paskino
Copy link
Contributor

paskino commented Apr 3, 2020

See https://github.com/orgs/SynerBI/projects/1#card-35844051


  • website update existing or new from scratch?,
  • mailing lists (@KrisThielemans),
  • github organisation
  • zenodo (with David and Ben),
  • ccppetmr@stfc.ac.uk?
  • slack (@paskino)
  • hub.docker.com (@casperdcl)
  • ccp.petmr.devel email (we will leave this as-is. too much work)
    • @ccp-petmr-codebot user,
    • youtube user
    • slack admin
    • JISCMAIL admin
    • googlegroups admin,
    • github-stats owner and fixes
  • travis
  • codacy
  • coverage
  • coverall
    what else?
  • ResearchGate
  • ResearchFish (not necessary. this is managed by UKRI. we have no control)

Name: www.ccpsynerbi.ac.uk. Others SyneRBI.

Contacts page needs to be kept in sync!

@paskino
Copy link
Contributor Author

paskino commented Apr 6, 2020

I am not the owner of the slack channel and cannot rename it. Who may be?

@KrisThielemans
Copy link
Member

KrisThielemans commented Apr 6, 2020

I am not the owner of the slack channel and cannot rename it. Who may be?

not me

@KrisThielemans
Copy link
Member

Note somewhat confusing to have checklists here and in https://github.com/SynerBI/SIRF/projects/4#card-35657657. The latter is more up-to-date at present. I suggest to keep it that way (but tick off here as well)

@rijobro
Copy link
Contributor

rijobro commented Apr 6, 2020

I am not the owner of the slack channel and cannot rename it. Who may be?

Not me either.

image

@casperdcl
Copy link
Member

I am not the owner of the slack channel and cannot rename it. Who may be?

Me neither

@casperdcl
Copy link
Member

NVM the bot seems to have admin access (Kris/Edo you should have the credentials). Or I can change it... what do you want it changed to?

Currently:

Name: CCP PETMR
URL: ccppetmr

Maybe consider just SIRF/sirf?

@casperdcl
Copy link
Member

P.S. @paskino I made both of us admins now; @KrisThielemans I made you owner.

@KrisThielemans
Copy link
Member

thanks. Sadly I have no idea what NVM is... sorry!

@casperdcl
Copy link
Member

nvm=nevermind :) don't know why I capitalised it. Anyway you should be able to change things using your own account now.

@KrisThielemans
Copy link
Member

:-) so... which bot are you talking about then? (I'm clearly on top of all this!)

@casperdcl
Copy link
Member

image

@KrisThielemans
Copy link
Member

sorry @casperdcl I still have no clue...

@rijobro
Copy link
Contributor

rijobro commented Apr 6, 2020

looks like a screenshot from slack

@casperdcl
Copy link
Member

on a related note I created a more appropriate ord-wide project https://github.com/orgs/SynerBI/projects rather than rely on the current repo-specific projects

@KrisThielemans
Copy link
Member

While hunting for why some Travis jobs failed, I found that the github-stats fail
https://travis-ci.org/github/SynerBI/SIRF-SuperBuild/jobs/672298976#L1660 with HTTP Error 404: NOT FOUND. @casperdcl is this related to the transition? By the way, is there some (very brief) doc on the github-stats anywhere?

@KrisThielemans
Copy link
Member

HDF5 jobs are failing because we try to download from https://www.ccpsynerbi.ac.uk/sites/www.ccpsynerbi.ac.uk/files/downloads/hdf5-1.10.1.tar.gz which doesn't exist yet

@casperdcl
Copy link
Member

github-stats

Yes I saw they are failing (but at least not causing jobs to fail)

HDF5

Any reason we're not hosting that on github? We can easily add that as a release asset or even in a separate repo. Both would provide direct download URLs.

@KrisThielemans
Copy link
Member

@paskino @evgueni-ovtchinnikov can you please update the contacts page to be in sync with the above? Example: slack is now synerbi.slack.com. github org changes, ResearchGate changed (maybe not URL). zenodo not yet. check the checklist!

@casperdcl
Copy link
Member

Zenodo would require a new release but it should "just work" with no further configuration.

@KrisThielemans
Copy link
Member

HDF5

Any reason we're not hosting that on github? We can easily add that as a release asset or even in a separate repo. Both would provide direct download URLs.

Clearly, ideally we don't host his stuff ourselves. In the past, we've had trouble with the HDF5 and FFTW websites being accessible, hence this lousy work-around.

Putting it on github is probably a better idea. I don't really want to have a repo with the source of HDF5 and FFTW though. Those projects aren't in great shape as far as version tracking goes etc, and it'd lead us astray.

I have no idea about "release assets". If this can be done with minimal maintenance effort, it'd be great. We'd probably need help though... (I'm hoping that the synerbi website will be up soon.)

casperdcl added a commit to SyneRBI/assets that referenced this issue Apr 8, 2020
@casperdcl
Copy link
Member

Just created a repo SynerBI/assets with a release tag SynerBI/assets@latest which we can freely update with more binaries in future (using https://github.com/SynerBI/assets/releases/edit/latest).

So we can now use this URL instead:

https://github.com/SynerBI/assets/releases/download/latest/hdf5-1.10.1.tar.gz

Note that if you do a trace on this URL you'll notice that the file is actually hosted on AWS.

casperdcl added a commit to SyneRBI/SIRF-SuperBuild that referenced this issue Apr 8, 2020
@KrisThielemans
Copy link
Member

excellent. thanks!

@paskino @evgueni-ovtchinnikov are there any other files (e.g. FFTW) that need to be there? Please do so, and add a commit at SyneRBI/SIRF-SuperBuild#372

@KrisThielemans
Copy link
Member

I've added codacy https://app.codacy.com/gh/SyneRBI.

I've also expanded our check-list again. @casperdcl maybe you can tick a few off that you've already done.

paskino added a commit to SyneRBI/SIRF-SuperBuild that referenced this issue Apr 24, 2020
* update github repos to synerbi

* CCPPETMR => SynerBI

* ccppetmr.ac.uk => ccpsynerbi.ac.uk

* mostly docker ccppetmr => synerbi

* minor revert touching CHANGES

* update hdf5 URL

- see SyneRBI/SIRF#614 (comment)

* docker: correct org name

* update headers

* further updates of string SynerBI to SyneRBI

* Update version_config.cmake

* formely => formerly

* SynerBI => SyneRBI

* added to CHANGES.md and fix typos in comments

* fixed project name

Co-authored-by: Casper da Costa-Luis <casper.dcl@physics.org>
Co-authored-by: Casper da Costa-Luis <imaging@caspersci.uk.to>
@KrisThielemans
Copy link
Member

also badges in README #708. Probably same for the the superbuild.

@KrisThielemans
Copy link
Member

@casperdcl I need some advice I'm afraid.

I don't understand what happened that we don't have any yml config files, nor really what I have to do. Would you be able to help?

@casperdcl
Copy link
Member

doesn't look like .coverage is being generated (at least not in the expected location). TL;DR travis logs (after ctest passes):

$ pushd ../SIRF
$ codecov
    Error running `['/usr/bin/python2', '-m', 'coverage', 'xml', '-i']`: Command '['/usr/bin/python2', '-m', 'coverage', 'xml', '-i']' returned non-zero exit status 1
    - Ignored: [Errno 2] No such file or directory: '/home/travis/build/SyneRBI/SIRF/coverage.xml'
Error: No coverage report found
$ coveralls
coverage.misc.CoverageException: Data file '/home/travis/build/SyneRBI/SIRF/.coverage' doesn't seem to be a coverage data file: Couldn't use data file '/home/travis/build/SyneRBI/SIRF/.coverage': no such table: coverage_schema

@KrisThielemans
Copy link
Member

SuperBuild badges sorted

@paskino
Copy link
Contributor Author

paskino commented Feb 11, 2021

Shall we close this @KrisThielemans ?

@KrisThielemans
Copy link
Member

coverage and coveralls have their own issues I believe.

I guess we're not fixing the owner nor the email address.

so yes, let's close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants