branch | status |
---|---|
master | |
dev |
Augur is focused on prototyping open source software metrics.
Functionally, Augur is a prototyped implementation of the Linux Foundation's CHAOSS Project on open source software metrics. Technically, Augur is a Flask web application, Python library and REST server that presents metrics on open source software development project health and sustainability.
The quickest way to get started working on Augur is by using Vagrant to spin up a virtual machine (VM) that comes with Augur already installed. We'll do all the work of setting up and installing dependencies, leaving you free to jump right into making something awesome.
Caveat: if you’re a super nerd who likes to have total control over your development environment, there’s a local installation link at the bottom of this page. For the rest of you, Vagrant is the way to go, especially if you've had trouble getting all the dependcies installed locally, are not comfortable installing them yourself, or are using an OS for which we don't currently support local installation. We currently only support local installation for macOS and most flavors of Linux.
Windows installation instructions using Vagrant can be found here.
- Git client
- Vagrant
- Virtualbox
- GitHub Access Token (no write access required)
- Clone the repository and boot up the VM.
# on your local machine
git clone https://github.com/chaoss/augur.git
cd augur
make vagrant
Note: you'll probably see a fair bit of errors during this provisioning process as Augur is getting installed. Don't worry about them, most of them are harmless. Probably.
- Log in as
root
and navigate to/vagrant/augur
. This folder is synced with your local clone ofaugur
, meaning you'll be able to use your preferred local editor and just use the VM to run augur.
# inside the vagrant VM
sudo su -
cd /vagrant/augur
# due to vagrant weirdness, we have to manually install the python packagew (this might take a while)
$AUGUR_PIP install --upgrade .
-
Add your GitHub API key to the
augur.config.json
file under the sectionGitHub
. -
Start both the backend and frontend servers with
make dev
.
make dev
- When you're done working in the VM, type
exit
twice: once to log out ofroot
, and another to log out of the VM. Don't forget to shut down the VM withvagrant halt
.
If you're interested in adding a new plugin, data source, or metric, check out the backend development guide. If new visualizations are more your speed, you'll want the [frontend development guide](http://augur.augurlabs.io/static/docs/dev-guide/4-frontend.html\).
# on your local machine
# using your Git client:
git clone https://github.com/chaoss/augur.git
# using Command Prompt
cd augur
vagrant up
vagrant ssh
# inside the vagrant VM
sudo su -
cd /vagrant/augur
# due to vagrant weirdness, we have to manually install the python packages
$AUGUR_PIP install --upgrade .
# add your GitHub personal access token to augur.config.json
# start the frontend and backend servers
make dev
# full steam ahead!
To contribute to our code base routinely, we recommended that developers configure Augur on their local workstations. Start here to get a primer on the project, or jump straight into our local installation instructions for developers.
To contribute to Augur, please check out our development guide and notes on making contributions. Also, please note our code of conduct. We want Augur to be a welcoming development community that is open to everyone.
Our technical, outreach, and academic goals roadmap.
Copyright © 2018 University of Nebraska at Omaha, University of Missouri and CHAOSS Project at the Linux Foundation
Augur is free software: you can redistribute it and/or modify it under the terms of the MIT License as published by the Open Source Initiative. See the file LICENSE for more details.
(This work has been funded through the Alfred P. Sloan Foundation)
Augur has proven to be an unruly beast and our expectation at the beginning now seem much tougher. None of of Use cases haven't reached their full fruition but it isn't for a lack of trying.
Use case 1: Have a navbar that has given time parameters(1 week, 6 weeks, 6 months, 1 year), these are displayed as buttons. With these buttons, you will be able to dynamically change the graph to fit the time parameter chosen. The event handlers have the current date minus the time parameters, this gives the start date. This start date is sent to the augur.js file to change the graph.
Use case 2: When the submit button is clicked for the repo search bar we want a second plot of lines to populate the graph. We are having trouble working on the backend on this however.
Use case 3: On this use case we rotated between struggling to grab the correct information and presenting the grabbed information in a way that did not ruin the page. At times it seemed like we found how to at least hold on to the info that we wanted it was clear we were not retrieving it in a way that was healthy for the UI so we found ourselves repeatedly brought back to square one.