profile
viewpoint

nushell/nushell 8764

A new type of shell

hpcng/singularity 1794

Singularity: Application containers for Linux

datalad/datalad 210

Keep code, data, containers under control with git and git-annex

nuest/ten-simple-rules-dockerfiles 41

Ten Simple Rules for Writing Dockerfiles for Reproducible Data Science

buildtesters/buildtest 29

HPC System and Software Testing Framework

good-labs/awesome-governance 14

A curated list of awesome governance resources

good-labs/greater-good-affirmation 10

An affirmation that your open source community exists for the greater good.

mgoubran/MIRACL 10

Multi-modal Image Registration And Connectivity anaLysis

macshine/coupling 8

Matlab and Python scripts for calculating functional coupling between time series data

nipy/nipy.github.com 6

Main website for the Neuroimaging in Python community

issue commentvsoch/django-oci

'jit' for JWT token

You could, but clearing the cache is an easier mechanism that does not require a server (or container) restart.

ad-m

comment created time in 4 minutes

issue commentvsoch/django-oci

'jit' for JWT token

The jit is stored in a cache with the same expiration as the token itself. If a registry wants to revoke all tokens they can simply clear that cache.

ad-m

comment created time in 8 minutes

issue commentvsoch/django-oci

Goals of projects

Sounds good! No worries about getting involved, I am good :)

ad-m

comment created time in 28 minutes

issue commentvsoch/django-oci

Goals of projects

Thanks for your thoughts! It’s ok if we disagree. Have a good day!

ad-m

comment created time in 35 minutes

issue commentvsoch/django-oci

Figure out optimal upload/download strategy

Thanks for the feedback! If we have a storage backend with signed urls for upload/download, the core registry running on Django (but offloading to that storage) I don't think would be an issue. But you are totally right that the filesystem storage, for example running alongside the action, might be too much.

vsoch

comment created time in an hour

issue commentvsoch/django-oci

Goals of projects

I think someone already asked this on Twitter, and I'm happy to reference that and provide more context. First, the tweet:

https://twitter.com/vsoch/status/1316055385388642309

And to state again for the issue - basically, the research use case (where researchers that might want to create a custom registry) are not developers, but are comfortable with Python and associated frameworks). The typical OCI registry that I see is in GoLang, with the exception of Quay which is quite substantial to set up. A research group should be empowered to deploy an OCI registry alongside their custom Django app, with many options for customization for their needs.

Next is the plugin aspect - this isn't a "registry in a box" (although I plan to make one for an example) but rather a plugin. It fits nicely alongside existing or custom Django projects that might warrant it. It comes with customization of storage backends, authentication, rate limits, content types, and pretty much anything that you might want. I am not discouraged that there are many other OCI registries out there - if I am a Django developer and I want OCI support it should be easy.

ad-m

comment created time in 2 hours

issue commentvsoch/django-oci

Figure out optimal upload/download strategy

Agreed! For Singularity Hub, for example, we just generate signed URLs for Google Storage and offload there, same with the Minio backend for Singularity Registry Server (both are not OCI, however, hence why I'm creating this module). You are correct that Django + Python tends to be a bottle neck - the use case is less a huge industry registry, and more a smaller research-oriented one that serves many fewer requests.

vsoch

comment created time in 2 hours

issue commentvsoch/django-oci

Anticipated bug: different repositories with blobs with the same digest

The actual query wouldn't be hard, it would just find blobs not linked to any image manifest. But currently, it makes no effort to check or cleanup, since it's a module intended for someone else to add to their Django project, I suspect they might want to have control over some cleanup strategy, however it might be done. The current storage is alongside the registry on the filesystem, but it's setup to allow for implementation of different storage backends, meaning you could imagine cloud storage, or something like Minio, and you can imagine the cleanup strategy would also vary based on that. So my thinking is that I'd first want to finish the module to add a few basic default (frontend interface) views, and then implement more storage backends. When those are done, I'm going to implement an example registry that uses it, and there I'm thinking it would be good to include some examples of cleanup. I might implement it on the level of the example, or if appropriate, could add it back here. So if you can provide what you have in mind that would give me a good start.

vsoch

comment created time in 2 hours

push eventvsoch/django-oci

vsoch

commit sha 055248833b06df3b9d6b29e6aa985f97500dfa0d

missing import Signed-off-by: vsoch <vsochat@stanford.edu>

view details

push time in 3 hours

issue commentvsoch/django-nginx-upload

Upload page 503 Service Temporarily Not Available

It's likely related to your operating system, and versions of Docker and docker-compose - I've had different results on different OS in personal experience. Glad it all worked out with the manual commands, feel free to close the issue if it's resolved.

vathyamodot

comment created time in 3 hours

PR opened vsoch/django-oci

Add/ratelimit

This pull request will add django rate-limit to close #19.

+46 -11

0 comment

9 changed files

pr created time in 3 hours

push eventvsoch/django-oci

vsoch

commit sha ccc010444792bedd3a787d59abe53ca32a127753

adding missing class Signed-off-by: vsoch <vsochat@stanford.edu>

view details

push time in 3 hours

push eventvsoch/django-oci

vsoch

commit sha 57aebdc29a34bfa5c5ff01e8f6ab81fb05a0d3b7

dont ratelimit patch Signed-off-by: vsoch <vsochat@stanford.edu>

view details

push time in 3 hours

push eventvsoch/django-oci

vsoch

commit sha ca2a6b88afa68d1a4d7a58ee3e524658ba8a3622

adding ratelimit to install deps Signed-off-by: vsoch <vsochat@stanford.edu>

view details

push time in 3 hours

create barnchvsoch/django-oci

branch : add/ratelimit

created branch time in 3 hours

issue commentvsoch/django-nginx-upload

Upload page 503 Service Temporarily Not Available

the command listed below is creating the directory as it is. Not creating sub folders.

It depends on having a bash shell, if you have something different or Windows you need to adjust for your needs. The migrations are done in the run_uwsgi.sh script, which is the container entrypoint: https://github.com/vsoch/django-nginx-upload/blob/master/run_uwsgi.sh. If this script isn't hit then there is something different or erroneous about your setup.

vathyamodot

comment created time in 3 hours

issue commentopencontainers/distribution-spec

WWW-Authenticate & discovery authentication server

Thanks again for all the good discussion, I think we're good https://vsoch.github.io/django-oci/docs/getting-started/auth.

ad-m

comment created time in 3 hours

issue closedvsoch/django-oci

Add user authentication

The registry currently has no understanding of users / authentication, so we will want to add that at some level.

closed time in 3 hours

vsoch

issue commentvsoch/django-oci

Add user authentication

Authentication is added https://twitter.com/vsoch/status/1321191305624498177

vsoch

comment created time in 3 hours

push eventvsoch/django-oci

vsoch

commit sha 69f424178ee5eb395302f14c2cb756718b8db4f8

updating manifest Signed-off-by: vsoch <vsochat@stanford.edu>

view details

vsoch

commit sha ec4a873bf8c8302b43771d5e49573bdc93a68c55

adding auth to docs navigation Signed-off-by: vsoch <vsochat@stanford.edu>

view details

push time in 3 hours

push eventvsoch/django-oci

Vanessasaurus

commit sha a59614869ae5da7028f12d688c8b9b3af60f13e4

Add/authentication (#18) * freezing work to add auth * start of work to add authentication, need to update conformance tests * finishing up updating tests to include auth * forgot to install pyjwt * finish up work to add authentication and docs Signed-off-by: vsoch <vsochat@stanford.edu>

view details

push time in 3 hours

PR merged vsoch/django-oci

Add/authentication

This PR will add a "docker style OAuth2" authentication to django oci. The things I'd still like to do include:

  • update settings in the options.md with newly added
  • write up the auth.md page with an example of using reggie (and link from reggie page)
  • clean up docstrings / args for functions
+913 -142

0 comment

29 changed files

vsoch

pr closed time in 3 hours

delete branch vsoch/oci-python

delete branch : test/auth

delete time in 3 hours

push eventvsoch/oci-python

Vanessasaurus

commit sha e168029864277e2dfe3ca7a6a903eca8687d3f53

small tweaks to fix parsing of www-authentication header (#12) * small tweaks to fix parsing of www-authentication header * formatting Signed-off-by: vsoch <vsochat@stanford.edu>

view details

push time in 3 hours

PR merged vsoch/oci-python

small tweaks to fix parsing of www-authentication header

Signed-off-by: vsoch vsochat@stanford.edu

+31 -40

0 comment

3 changed files

vsoch

pr closed time in 3 hours

issue openedvsoch/django-oci

Add view ratelimits with defaults

The user should be able to set rate limits for django OCI endpoints, or disable entirely (and not need the dependency).

created time in 3 hours

push eventvsoch/django-oci

vsoch

commit sha ac4ab29b8c66c9b323c59636678526a61e7a4db2

finish up work to add authentication and docs Signed-off-by: vsoch <vsochat@stanford.edu>

view details

push time in 3 hours

push eventvsoch/oci-python

vsoch

commit sha 28d5dd79d2f54cbf06c83455132d05a077aeb8c1

formatting Signed-off-by: vsoch <vsochat@stanford.edu>

view details

push time in 3 hours

PR opened vsoch/oci-python

small tweaks to fix parsing of www-authentication header

Signed-off-by: vsoch vsochat@stanford.edu

+29 -40

0 comment

3 changed files

pr created time in 3 hours

create barnchvsoch/oci-python

branch : test/auth

created branch time in 3 hours

issue commentvsoch/django-nginx-upload

Upload page 503 Service Temporarily Not Available

Yes the instruction to create them is clearly stated in the README

https://github.com/vsoch/django-nginx-upload#usage

The second error message above suggests that you did not create the database, e.g., you didn't do the migrations. Again, I can't comment on the changes that you made, but I can say that the original version, clearly following the instructions, should work.

vathyamodot

comment created time in 4 hours

issue commentexpfactory/expfactory-docker

Save to Filesystem as automatic fallback

As long as you start and finish the measurement before the save, it shouldn't, theoretically.

tfeige91

comment created time in 4 hours

issue commentexpfactory/expfactory-docker

Forwarding to current port

That means you have something else running on port 80, perhaps another container? Or nginx / apache on your host? What is your goal here - to run two different experiment servers at once on the same host? if you want to do that, you need to map each container to a different port on the host, e.g.,

80:3001 # map the container's internal port 80 to 3001 on your host
80:3002 # map the container's internal port 80 to 3002 on your host
tfeige91

comment created time in 4 hours

issue commentvsoch/django-nginx-upload

Upload page 503 Service Temporarily Not Available

It’s hard for me to debug with changes I don’t know, but I’d check if you exposed the port, and made sure to update the Nginx.conf, and also verify the temporary upload folders exist in /tmp.

vathyamodot

comment created time in 5 hours

push eventyeastphenome/yeastphenome.org

vsoch

commit sha 4da5cc650dc61490a266a1a14b983d33fda5250e

refactoring gene explorer to look like others Signed-off-by: vsoch <vsochat@stanford.edu>

view details

Vanessasaurus

commit sha b2215c435ec51ef10ae511c3bd5616b77351b560

Merge pull request #42 from yeastphenome/refactor/gene-explorer refactoring gene explorer to look like others

view details

push time in 5 hours

delete branch yeastphenome/yeastphenome.org

delete branch : refactor/gene-explorer

delete time in 5 hours

PR merged yeastphenome/yeastphenome.org

refactoring gene explorer to look like others

This PR will refactor the gene explorer to look like the others! Namely, the user is allowed to search for known tags (with autocomplete) or a random string, and a table of results is presented. I tested by searching for just SR, and I got a whole table of results.

Signed-off-by: vsoch vsochat@stanford.edu

+510 -206

0 comment

6 changed files

vsoch

pr closed time in 5 hours

PR opened yeastphenome/yeastphenome.org

refactoring gene explorer to look like others

This PR will refactor the gene explorer to look like the others! Namely, the user is allowed to search for known tags (with autocomplete) or a random string, and a table of results is presented. I tested by searching for just SR, and I got a whole table of results.

Signed-off-by: vsoch vsochat@stanford.edu

+510 -206

0 comment

6 changed files

pr created time in 5 hours

create barnchyeastphenome/yeastphenome.org

branch : refactor/gene-explorer

created branch time in 6 hours

issue commentexpfactory/expfactory-docker

Forwarding to current port

Yes that's correct! Any port that you use from inside the container needs:

EXPOSE <port>
EXPOSE 3391

But since each container is isolated, what you really should care about are the ports you map to on the host (the second in the mapping). Using port 80 inside each of the containers should work best unless you are doing some significant change to services in the container that require running the expfactory server on another port.

tfeige91

comment created time in 6 hours

issue commentsnakemake/snakemake

default remote prefix duplicated for checkpoint output on cloud

I agree! @johanneskoester was on fire this morning :) :fire:

aryarm

comment created time in 8 hours

delete branch stanford-rc/recommend-o-matic

delete branch : updates/october-27

delete time in 8 hours

push eventstanford-rc/recommend-o-matic

Vanessasaurus

commit sha 18c8d53d6fdf43df9e3e175218f00aade51bc00a

updating recommend-o-matic with updated data, generation script, and … (#1) * updating recommend-o-matic with updated data, generation script, and tooltips * running black Signed-off-by: vsoch <vsochat@stanford.edu>

view details

push time in 8 hours

PR merged stanford-rc/recommend-o-matic

updating recommend-o-matic with updated data, generation script, and …

Per request of the recommend-o-matic team, this pull request will:

  • update data for questions and resources
  • add tooltips if defined
  • add ordering for questions

Signed-off-by: vsoch vsochat@stanford.edu

+87 -134

0 comment

6 changed files

vsoch

pr closed time in 8 hours

PR opened stanford-rc/recommend-o-matic

updating recommend-o-matic with updated data, generation script, and …

Per request of the recommend-o-matic team, this pull request will:

  • update data for questions and resources
  • add tooltips if defined
  • add ordering for questions

Signed-off-by: vsoch vsochat@stanford.edu

+87 -134

0 comment

6 changed files

pr created time in 8 hours

push eventstanford-rc/recommend-o-matic

vsoch

commit sha 670b819e9d34d4858fe39180c71bc8b3e4fed5d4

running black Signed-off-by: vsoch <vsochat@stanford.edu>

view details

push time in 8 hours

create barnchstanford-rc/recommend-o-matic

branch : updates/october-27

created branch time in 8 hours

issue commentsnakemake/snakemake

default remote prefix duplicated for checkpoint output on cloud

hey @aryarm ! We just merged a PR that at least can handle the redundant name for standard runs, would you care to test, and also check for the checkpoint case? If you find the issue for checkpoint, please provide a simple example to reproduce with the current master.

aryarm

comment created time in 8 hours

issue commentsnakemake/snakemake

MissingOutputException with directory and GS remote provider

hey @CowanCS1 ! We just merged a PR into master to address directories on GLS - would you care to test it out?

eric-czech

comment created time in 8 hours

pull request commentsnakemake/snakemake

Test/gls directory output

Thank you to you! I really appreciate the help, and I'm so glad you like the idea of adding the development container build for the test - it's going to make it hugely easier for developers that want it.

vsoch

comment created time in 8 hours

issue commentopencontainers/distribution-spec

WWW-Authenticate & discovery authentication server

Thanks to you both! I didn’t mean to suggest this should be part of the spec, I was just generally asking for advice.

ad-m

comment created time in 9 hours

pull request commentsnakemake/snakemake

Test/gls directory output

Okay I’ll rebuild and try again when I officially wake up, still before 6am here :)

vsoch

comment created time in 12 hours

pull request commentsnakemake/snakemake

Test/gls directory output

Would it be feasible for PRs to build and push a development image, built from the codebase being tested directly? Of course named by something like the commit. Then of course delete it / clean up after.

vsoch

comment created time in 12 hours

delete branch USRSE/usrse.github.io

delete branch : add-umich-job

delete time in 12 hours

push eventUSRSE/usrse.github.io

Ian Cosden

commit sha 8395be81f6affcbddbe31c63fdb580171db6b2bb

Update jobs.yml (#316)

view details

push time in 12 hours

PR merged USRSE/usrse.github.io

Add Michigan job

Adds University of Michigan job posted in slack.

cc @usrse-maintainers

+2 -0

0 comment

1 changed file

cosden

pr closed time in 12 hours

PullRequestReviewEvent

pull request commentsnakemake/snakemake

Test/gls directory output

There is no way the tests could pass because they are using an older container, What I typically have to do is specify --container-image with a container I just built and pushed for the branch.

vsoch

comment created time in 13 hours

issue commentexpfactory/expfactory-docker

Save to Filesystem as automatic fallback

I could see doing that on the experiment level - currently the data is submit to save on task finish, https://github.com/expfactory-experiments/breath-counting-task/blob/master/index.html#L63 so you would just create an experiment that submits to /save for a different jspsych callback function.

tfeige91

comment created time in 13 hours

issue commentexpfactory/expfactory-docker

Forwarding to current port

For both of those, you mapped to port 80 on the host. If you want to have tests on a different port, you need to map to it. The way it works is like <port inside container>:<port on your host>

tfeige91

comment created time in 13 hours

push eventvsoch/opensource-heartbeat

github-actions[bot]

commit sha 841ab081cb84210c0a615972605dd157a2ad03e2

Automated deployment to update contributors 2020-10-27 (#71) Co-authored-by: github-actions <github-actions@users.noreply.github.com>

view details

push time in 21 hours

delete branch vsoch/opensource-heartbeat

delete branch : opensource-heartbeat/update-2020-10-27

delete time in 21 hours

PR merged vsoch/opensource-heartbeat

[opensource-heartbeat] opensource-heartbeat/update-2020-10-27

Opensource Heartbeat events update automated pull request.

+96 -0

0 comment

6 changed files

github-actions[bot]

pr closed time in 21 hours

push eventvsoch/django-oci

vsoch

commit sha 485ad24bf8e26de77680d6c690d8d158f11987a6

fix Signed-off-by: vsoch <vsochat@stanford.edu>

view details

push time in a day

push eventvsoch/django-oci

vsoch

commit sha 4be2fab85c291c10f58eaffabb590106312d1f49

forgot to install pyjwt Signed-off-by: vsoch <vsochat@stanford.edu>

view details

push time in a day

PR opened vsoch/django-oci

Add/authentication

This PR will add a "docker style OAuth2" authentication to django oci. The things I'd still like to do include:

  • update settings in the options.md with newly added
  • write up the auth.md page with an example of using reggie (and link from reggie page)
  • clean up docstrings / args for functions
+707 -131

0 comment

27 changed files

pr created time in a day

push eventvsoch/django-oci

vsoch

commit sha da6a33a144b04d372b66581ec602dc199bb6fae0

finishing up updating tests to include auth Signed-off-by: vsoch <vsochat@stanford.edu>

view details

push time in a day

create barnchvsoch/django-oci

branch : add/authentication

created branch time in a day

pull request commentsnakemake/snakemake

Test/gls directory output

I'm not really sure what to think, I've poured many hours into this and tried debugging this so many times and it seems to be inconsistent. Maybe someone else can take a look.

vsoch

comment created time in a day

push eventyeastphenome/yeastphenome.org

Vanessasaurus

commit sha c870dc4946d031eac74082a776758078139cd1e1

small tweaks to navigation (#41) Signed-off-by: vsoch <vsochat@stanford.edu>

view details

push time in a day

delete branch yeastphenome/yeastphenome.org

delete branch : updates/october-26

delete time in a day

create barnchyeastphenome/yeastphenome.org

branch : updates/october-26

created branch time in a day

pull request commentsnakemake/snakemake

Test/gls directory output

@johanneskoester that might be it! I just tested with the adopted snakefile:

rule all:
    input:
        "testdir"

rule directory:
    output:
        directory("testdir")
    log:
        "logs/directory.log"
    shell:
        "mkdir -p {output}; touch {output}/test.txt"

And using the custom built container

snakemake --default-remote-prefix snakemake-testing/dirtest --google-lifesciences --default-resources "machine_type=n1" --container-image vanessa/snakemake:dirtest

That didn't seem to work (this is in red). Both with and without the slash currently fail.

ImproperOutputException in line 5 of /home/vanessa/Desktop/Code/snakemake/snakemake/Snakefile:
Outputs of incorrect type (directories when expecting files or vice versa). Output directories must be flagged with directory(). for rule directory:
snakemake-testing/dirtest/testdir
  File "/home/vanessa/Desktop/Code/snakemake/snakemake/snakemake/executors/__init__.py", line 814, in handle_job_success
  File "/home/vanessa/Desktop/Code/snakemake/snakemake/snakemake/executors/__init__.py", line 247, in handle_job_success
Shutting down, this might take some time.
Exiting because a job execution failed. Look above for error message

So we definitely need more testers.

vsoch

comment created time in a day

PullRequestReviewEvent

issue commentopencontainers/distribution-spec

WWW-Authenticate & discovery authentication server

Thanks @ad-m! @jdolitsky what are your thoughts?

ad-m

comment created time in a day

issue commentopencontainers/distribution-spec

WWW-Authenticate & discovery authentication server

Okay, so given a JWT token in context of OAuth - to return to my question - you are saying that it doesn't really matter then how it's encoded and decoded? There is no best practice for the secret?

ad-m

comment created time in a day

issue commentopencontainers/distribution-spec

WWW-Authenticate & discovery authentication server

Heyo! I'm well into the auth implementation but I have one quick question. What are best practices for the secret used to decode? Should they be generated for one time use, on the level of the repository, or the server? If the purpose is only for the server to generate (encode) and then decode, it seems like it doesn't add much, security wise, and even could just be one value. I ask because I was looking over quay's implementation and they use some kind of public key? https://github.com/quay/quay/blob/38be6d05d08bc72cc13a89073bb5364b8adf6c04/util/security/registry_jwt.py#L100 And they pass it via some kind of kid header?

    kid = headers.get("kid", None)
    if kid is None:
        logger.error("Missing kid header on encoded JWT: %s", bearer_token)
        raise InvalidBearerTokenException("Missing kid header")

How does the header get passed around, and is the kid equivalent to the jti? Thanks!

ad-m

comment created time in 2 days

push eventvsoch/opensource-heartbeat

github-actions[bot]

commit sha bbdbaad10db60f6ed01447cd5001911290f5465e

Automated deployment to update contributors 2020-10-26 (#70) Co-authored-by: github-actions <github-actions@users.noreply.github.com>

view details

push time in 2 days

delete branch vsoch/opensource-heartbeat

delete branch : opensource-heartbeat/update-2020-10-26

delete time in 2 days

PR merged vsoch/opensource-heartbeat

[opensource-heartbeat] opensource-heartbeat/update-2020-10-26

Opensource Heartbeat events update automated pull request.

+107 -0

0 comment

7 changed files

github-actions[bot]

pr closed time in 2 days

issue commentpydicom/dicom-database

Github still underdevelopment?

Great job! :tada:

Gresliebear

comment created time in 2 days

push eventrseng/software

github-actions

commit sha c94721ff710d463421b341932131afec38205e36

Automated deployment to update software database 2020-10-25

view details

Vanessasaurus

commit sha d44c0a98d74319a9fd4a58841220db869fd6da9b

Merge pull request #145 from rseng/annotate/criteria-vsoch-2020-10-25/19-30-49 Update from annotate/criteria-vsoch-2020-10-25/19-30-49

view details

push time in 2 days

delete branch rseng/software

delete branch : annotate/criteria-vsoch-2020-10-25/19-30-49

delete time in 2 days

PR merged rseng/software

Update from annotate/criteria-vsoch-2020-10-25/19-30-49

Fixes https://github.com/rseng/software/issues/143

+3 -0

0 comment

3 changed files

github-actions[bot]

pr closed time in 2 days

issue closedrseng/software

[CRITERIA]

Repository

https://github.com/fair-software/howfairis

Criteria

  • [ ] criteria-RSE-domain-intention
  • [x] criteria-RSE-research-intention
  • [x] criteria-RSE-usage

closed time in 2 days

vsoch

push eventrseng/software

github-actions

commit sha 1326e360bc69ce0015a9e14ee2c3a49f173a42c7

Automated deployment to update software database 2020-10-25

view details

Vanessasaurus

commit sha a9532eef933bb71a7e584243a37aa2620b027c6e

Merge pull request #144 from rseng/annotate/taxonomy-vsoch-2020-10-25/19-30-47 Update from annotate/taxonomy-vsoch-2020-10-25/19-30-47

view details

push time in 2 days

delete branch rseng/software

delete branch : annotate/taxonomy-vsoch-2020-10-25/19-30-47

delete time in 2 days

PR merged rseng/software

Update from annotate/taxonomy-vsoch-2020-10-25/19-30-47

Fixes https://github.com/rseng/software/issues/142

+1 -0

0 comment

1 changed file

github-actions[bot]

pr closed time in 2 days

issue closedrseng/software

[TAXONOMY]

Repository

https://github.com/fair-software/howfairis

Taxonomy

  • [x] RSE-taxonomy-data-collection

closed time in 2 days

vsoch

push eventrseng/rseng

vsoch

commit sha 98aed8999efffa862bfe4084656ecf7a5d11f1f7

adding howfairis Signed-off-by: vsoch <vsochat@stanford.edu>

view details

vsoch

commit sha 83aba2f66a63b413865889a7f0b54b8c68548a7a

Merge branch 'gh-pages' of github.com:rseng/rseng into gh-pages

view details

push time in 2 days

issue openedrseng/software

[CRITERIA]

Repository

https://github.com/fair-software/howfairis

Criteria

  • [ ] criteria-RSE-domain-intention
  • [x] criteria-RSE-research-intention
  • [x] criteria-RSE-usage

created time in 2 days

issue openedrseng/software

[TAXONOMY]

Repository

https://github.com/fair-software/howfairis

Taxonomy

  • [x] RSE-taxonomy-data-collection

created time in 2 days

issue openedfair-software/howfairis

check_badge should not system exit

If a user wants to use this library programatically, e.g., run over many repositories, it would be ideal for the check_badge function to not sys.exit(0), but instead to return True or False. For the case of the client, the sys.exit would go after this function call. I can put in a pull request with this suggested change if you think it's a good idea!

created time in 2 days

push eventsingularityhub/sregistry

Vanessasaurus

commit sha 000961e6fb289324b461ea552c64b0cd7179b65a

Adding howfairis badge

view details

push time in 2 days

PullRequestReviewEvent

Pull request review commentUSRSE/usrse.github.io

adding US-RSE version of BSSw post on

+---+layout: post+title: The RSE-HPC-2020 Workshop - Creating Community, Building Careers, Addressing Challenges+tags: [conference]+posted_by: Charles Ferenbaugh, Sandra Gesing, Simon Hettrick, and Daniel S. Katz+---++*This article has been crossposted on [BSSw](https://bssw.io).*++We are excited to announce the [Research Software Engineers in HPC Workshop+(RSE-HPC-2020)](https://us-rse.org/rse-hpc-2020/) to be held as part of [SC20](https://sc20.supercomputing.org/) (held virtually) this fall! This will be a half-day+workshop 10:00am-2:00pm EST, Thursday, November 12, 2020. It will feature keynote addresses from+Simon Hettrick and Frank Löffler, leaders in the RSE movements in the UK and Germany,+followed by talks and panel discussions on the needs of RSEs and RSE groups.++High Performance Computing (HPC), Computational Science and Engineering (CSE), and data+science rely on high-quality software, and the developers of this software are critical to the+impact of HPC, CSE, data science, and the larger scientific community. It is increasingly+recognized that such developers need a unique combination of skills: expertise in software+development together with a deep understanding of the scientific field for which the software is+being written. Recently, the term “Research Software Engineer” (RSE) has been applied to+people in such roles; this term originated in the UK in 2012, and has become widely recognized+worldwide over the past several years.++Although many research projects rely heavily on RSE contributions, formal recognition of the+unique RSE role is often lacking. Sometimes, these positions are pigeonholed into the existing+hierarchy of research positions, such as postdoctoral associates and research scientists in+academia, or analogous positions at other kinds of institutions, including at national labs and in+industry. However, this classification does not adequately describe RSE responsibilities, and+can cause problems for RSEs who seek career progression. This lack of a defined position and+career outlook leads many promising practitioners to abandon research altogether. In+response, many research institutions are creating specific positions and groups for RSEs, and+several national organizations of RSEs have formed.++In the HPC community in particular, software projects have historically required significant work+to develop specialized, highly performant software. This need has increased greatly in the past+few years, as projects have grappled with adapting their codes to new architectures such as+GPUs or many-core CPUs. Many projects have also had to address questions of correctness+and reproducibility. With all of these changes, the need has increased for skilled software+developers (RSEs) to write HPC software that is understandable, well-tested, maintainable, and+extensible. Even so, many of these RSEs still struggle to find positions and career recognition+in the modern research culture.++Because of all this, the time is right to hold a workshop for RSEs in the HPC community at this+year’s SC20 conference. This workshop will build on RSE panels and BOF sessions at earlier+SC conferences and other events, and on RSE conferences held in the UK and elsewhere.+Last year at SC19, for example, we discussed RSE roles and career paths in a BoF; we learned+that there was a large group interested in the topic, and that the term “RSE” was much better known than it was a couple of years earlier. This workshop will bring together RSEs and allies+involved in HPC, from all over the world, to grow the RSE community further by establishing and+strengthening professional networks of current RSEs and RSE leaders.++The planned agenda includes the following talks and discussions:++* Keynotes+  * *The Birth of RSE* - Simon Hettrick, Software Sustainability Institute+  * *de-RSE: Forking an RSE Success Story* - Frank Löffler, Friedrich Schiller+University++* Lightning talks+  * *How Research Software Engineers Can Support Scientific Software* - Miranda+Mundt, Sandia National Laboratory+  * *SC3UIS Research Software Engineering Ecosystem for Scientific Computing* -+Emilio Carcamo, Universidad Industrial de Santander++* Panel discussion: Building RSE Teams and Groups+  * Reed Milewicz, Sandia National Laboratory

My one comment that isn't specific to the text but to the content (since we've shone a light on this recently) is that I hope the speakers and panels are a diverse set of individuals. I'm only seeing two women out of 12, and I can't easily see other kinds of diversity, but I hope that the rest aren't just white, European men.

danielskatz

comment created time in 2 days

PullRequestReviewEvent

push eventvsoch/opensource-heartbeat

github-actions[bot]

commit sha 056d28074fe0e6e7b6e4c96fc98525459fe471e5

Automated deployment to update contributors 2020-10-25 (#69) Co-authored-by: github-actions <github-actions@users.noreply.github.com>

view details

push time in 3 days

more