To add you to the JOSS editorial team we need:
- Your GitHub username
- Your editorial topic areas/specialisms
- A picture for the JOSS site
- A short biography, including your professional affiliation
- An email address for the JOSS Google group.
- Your ORCID
# Complete worked example here: https://joss.readthedocs.io/en/latest/submitting.html#example-paper-and-bibliography | |
--- | |
title: 'Gala: A Python package for galactic dynamics' | |
tags: | |
- Python | |
- astronomy | |
- dynamics | |
- galactic dynamics | |
- milky way |
require 'octokit' | |
require 'csv' | |
require 'hashie' | |
require 'active_support/all' | |
class PR < Hashie::Dash | |
property :pr | |
property :created_at | |
property :comment_count | |
property :commit_count |
Over the last four decades, AURA has driven a science model where astronomers and astrophysicists from any University or Institution, through rigorous peer-review, can access forefront facilities without having to be “black-belt” experts in the complex machinery of modern ground or space based telescopes. AURA’s most successful model of this broad engagement has been the Hubble Space Telescope, which, when measured by the metric of number of refereed papers/year integrated over the lifetime of the Observatory, has become the most productive science facility in history. Today, AURA confronts a new challenge: they are building a number of new facilities, which are specifically designed to generate huge data sets, most notably the Large Synoptic Survey Telescope (LSST). LSST will continuously survey the entire Southern sky every three nights, generating over 15 trillion bytes of raw data per night. The over-arching science goals driving this facility are well known: The Nature of Dark
require 'octokit' | |
GH_TOKEN = "XXXXXXXXXXXXXXXXXXXXXXXXXX" | |
GITHUB = Octokit::Client.new(:auto_paginate => true, :access_token => GH_TOKEN) | |
repositories = GITHUB.repositories('arfon') | |
puts "Working with #{repositories.size} repositories" | |
repositories.each do |r| |
The MIT License (MIT) | |
Copyright (c) 2018 Arfon Smith | |
Permission is hereby granted, free of charge, to any person obtaining a copy | |
of this software and associated documentation files (the "Software"), to deal | |
in the Software without restriction, including without limitation the rights | |
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | |
copies of the Software, and to permit persons to whom the Software is |
Over the past couple of weeks we've seen a couple of great examples of service integrations from figshare and Zenodo that use the GitHub outbound API to automatically archive GitHub repositories. While the implementation of each solution is likely to be somewhat different I thought it might be useful to write up in general terms how to go about building such a service.
In a nutshell we need a tool that does the following:
octokit/octokit.net activity on GitHub similar to https://github.com/blog/2195-the-shape-of-open-source
github/VisualStudio activity on GitHub similar to https://github.com/blog/2195-the-shape-of-open-source
Jekyll activity on GitHub similar to https://github.com/blog/2195-the-shape-of-open-source