Open Opportunities open source platform
JavaScript CSS HTML PLpgSQL
Latest commit 94e1d06 Oct 27, 2016 @EricSchles EricSchles committed on GitHub Merge pull request #1494 from ulfmagnetics/agency-filter
Filter tasks by agency via query param
Permalink
Failed to load latest commit information.
api Make json2csv synchronous again Sep 30, 2016
assets Fix the currentUser check in BrowseMainView#initialize Oct 23, 2016
config Set CORS configuration from VCAP_APPLICATION Oct 24, 2016
docs need `npm run watch` to run the server Jun 6, 2016
migrations migration for task, add ‘restrict’ column May 31, 2016
tasks Update dashboard view to show opportunities; Sep 9, 2016
test removing broken test LocationController, because map functionality re… Sep 2, 2016
tools Add abbr, slug, domain, et al to seed data for tags Oct 23, 2016
views updating config.md Oct 17, 2016
.about.yml fix some typos Mar 22, 2016
.buildpacks Adjust application config to read from CF environment and services Oct 6, 2015
.cfignore Adjust application config to read from CF environment and services Oct 6, 2015
.dockerignore Docker Aug 26, 2015
.editorconfig Update editorconfig to match codebase Dec 30, 2015
.eslintrc Update linting to be less strict Sep 9, 2016
.gitattributes Initial checkin of demo structure Oct 8, 2013
.gitignore Update travis to use a tmp directory Aug 17, 2016
.jshintrc casperjs & phantomjs for browser tests May 3, 2016
.nodemonignore Get `npm run watch` working again 🎉 Sep 9, 2016
.sailsrc use .sailsrc to turn off sockets (#1331) May 16, 2016
.travis.yml Move the skip_cleanup because TravisCI docs are... Aug 17, 2016
Aptfile deploy to Cloud Foundry Apr 25, 2016
CONFIG.md updating config.md Oct 17, 2016
CONTRIBUTING.md Minor copy edits to CONTRIBUTING.md Sep 7, 2016
CORETEAM.md adding Roger's full name May 20, 2016
DEPENDENCIES.md Update the dependency documentation Sep 30, 2016
Dockerfile Re-adding a Dockerfile to the repo. Jun 7, 2016
GOVERNANCE.md Adding a file to describe the governance model. (#1316) May 19, 2016
Gruntfile.js sails new Apr 1, 2016
INSTALL.md Update docs to include new required variable Oct 24, 2016
LICENSE.md include INSTALL, LICENSE & tools Apr 12, 2016
README.md Update version number Oct 17, 2016
app.js cloud foundry env settings + newrelic May 9, 2016
circle.yml Add VCAP_APPLICATION env to CircleCI Oct 24, 2016
exclude.txt changes required to make the theme work (#1322) May 15, 2016
logfile fixing dependency issue Sep 2, 2016
manifest-dev.yml Update the manifests to reflect the lower quota; Aug 17, 2016
manifest-new.yml deploy to Cloud Foundry Apr 25, 2016
manifest-prod.yml Revert production resources to 1G Sep 6, 2016
manifest-staging.yml Some last fixes on 0.14.0 Sep 19, 2016
manifest.yml deploy to Cloud Foundry Apr 25, 2016
newrelic.js deploy to Cloud Foundry Apr 25, 2016
package.json Update version number Oct 17, 2016
system-security-plan.yml Final version changes Sep 30, 2016

README.md

OpenOpps Platform

Badge Status
Circle CI Build Build Status
Travis CI Deployment Deployment Status
Version Eye Version Eye Dependency Status
Code Climate Code Climate
Current Version Current Version

Open Opportunities is creating a network of federal employees that will lead to a more effective, efficient, responsive government by sharing skills and collaborating on projects that support the mission of an agency or the government as a whole.

OpenOpps is the open source platform that supports the Open Opportunities program. As open source software, it can be deployed by state or local governments or in the private sector. It is free to use by anyone who can has technical operations staff and passion to start a new program, and we welcome everyone who would like to contribute to improving the platform.

Here’s how Open Opportunities works: You come up with a great idea that would help your workplace, but you and your coworkers don’t have the skills to execute it. Rather than bringing in a contractor, you can post your project idea to Open Opportunities, where other people within your organization can see it and then work on it, if they’d like.

Open Opportunities Testimonial from DigitalGov Search Manager

Open Opportunities can benefit all organizations, but it’s especially useful for those with distributed teams and whose employees have diverse skill sets. Using Open Opportunities, you and your colleagues can work on projects together, get to know each other better, and develop skills you don’t use as often as you’d like.

Screenshots

open opps 1 open opps 2 open opps 3

How you can help

  • Use our community test server and write up issues
  • Join our Google Group and introduce yourself, please ask any general questions here -- how the product is supposed to work, usability issues, technical questions, whatever you want to know, we want to hear about. If you are interested in using Open Opportunities for your organization, let us know.
  • Read our Contribution Guide -- everything you do with us is a contribution to the public domain, there are also some tips for getting started
  • If you are a developer, install the software for development
  • Dive into our help wanted issues -- there are both dev and design opportunities there

More Project Details

Problem Statement: Our workforce often lacks talent and skills where and when they are needed.

  • working across organizational boundaries is difficult
  • professional development opportunities are scarce
  • only 35% of federal employees believe creativity and innovation are rewarded (2014 Federal Employee Viewpoint Survey)

Solution: provide a software platform that enables a program with very small central staff and program leaders across government that provide professional development opportunities

Our Goal: to foster innovation across team boundaries by connecting individuals who identify challenges and then work collaboratively to implement solutions.

A cross-agency working group meets regularly to discuss program needs. We use an Agile Roadmap where the product team selects features that we believe will meet goals. We strive to make data-driven decisions based on metrics and qualitative user research and to validate the outcomes based on observed community behavior. This is an iterative process.

We also welcome direct participation from government and private sector and are always in need of people who can write documentation or marketing material, visual and UX designers, as well as software coders.

Dependencies

Please read the DEPENDENCIES.md file containing dependency version information for all the dependencies that the Open Opportunities Platform is built with. This file contains version badges and explanations of out-of-date or forked dependencies and contains the most up-to-date information about versioned dependencies.

History

Open Opportunities was initially validated as part of a Digital Government initiative using WordPress and a Lean Startup "concierge" approach. In its initial pilot phase, people from over 50 government agencies, completing over 100 projects, ranging from 1 hour tasks to working part-time for 3-6 months. Open Opportunities moved to this software platform in October 2014, and is now available for all federal employees. The platform was originally developed for foreign service officers the Department of State in 2013 as a Presidential Innovation Fellows project under the code name Midas.

License

This project is in the public domain within the United States, and copyright and related rights in the work worldwide are waived through the CC0 1.0 Universal public domain dedication.

For more information, see license.