Open source projects and areas that need some help

opensourcehelp

Foreman (find help on IRC: #theforeman-dev on Freenode, http://github.com/theforeman/foreman)
- Standardize api/v2/hosts/power response across all compute resources. This requires learning what are the response codes for Openstack, EC2, VMware, etc.. and homogenize it to a standard response. More info in the PR discussion.
- Force Chef runs through Foreman UI. Possibly expand the Smart-proxy for this.
- Add location to discovery plugin. Discover hosts by MAC and use some software to get the location before retrieving facts
- Refactor app/observers and app/validators. They should either go away or move more logic into them. In particular my opinion is app/validators could get more custom validators and app/observers should go away.
- DigitalOcean Compute Resource plugin - discussion here
- Improve interactions like Kyle suggested. Basically move away from the "+ interface" -> child menu pattern (everywhere), and load by AJAX a whole new menu that creates a new object and saves it without leaving the current edit context. See PDF for examples.
- Rework keypair flow for VMs created in certain compute resources. Auto created pairs can only be retrieved from the db, which is very incovenient for non admin users.
- Move from Bootstrap to Patternfly
- Compute resources should be general, and users should have their own tab in their profile with credentials for them. Then when operations on the compute resource are performed, we
should pass user credentials through. Doing otherwise is a insecure by default and impossible to audit from the resource view, as all operations on the compute resource are performed by the same user.
- Tests for secure websockets connection to console are lacking
- Reduce friction to make hosts console usable to a minimum
- Refactor compute_resource_vms and hosts controller (console and power methods are the same)
- Start a javascript test suite.
- Refactor functional tests api/v2/parameters_controller
- Refactor find_compute_resource in compute_resource_vms to a before_filter
- Refactor unit tests for Host, particularly the ones about taxonomies
- Add Brakeman to Jenkins
- Stress test Foreman through foreman-bats
- Extend compute profiles so that they can be used the discovery plugin can use it for Bare metal hosts.

  docs and web
   - Improve README to show what the project is about
   - Add project to codeclimate and add it to the README
   - CONTRIBUTING docs, use Katello.org contributing section as a base (and eLobato's docs)
   - Add hammer docs to theforeman.org
   - IPMI and BMC setup documentation in theforeman.org

LDAP Fluff (find help on IRC: #theforeman-dev on Freenode, http://github.com/theforeman/ldap_fluff)
- Make passwords with spaces work (e.g: user: admin, pass: 'the admin')
- Refactor tests to use describe, contexts, etc...

Katello (find help on IRC: #theforeman-dev on Freenode, http://github.com/katello/katello)
- Make content views not based on versions but on "latest".

PrProcessor (find help on IRC: #theforeman-dev on Freenode, http://github.com/theforeman/prprocessor)
- Change the convention to #bug, #feature, #refactor instead of #fixes #refs. It would make the git history more meaningful.
- Ping pull request people involved in discussions with no updates after N days.
- Ask user to rebase PR when PR is not mergeable

SELinux coloring book (https://github.com/mairin/selinux-coloring-book/)
- Make SELinux coloring book easier to convert to PDF from SVG, through a script
- SVG to PDF all layers in the Spanish translation (might require tweaking text)

Validateur (http://clojurevalidations.info/)
- Add missing ActiveRecord validations

New projects
- Start a gem validates_uniqueness_in_memory gem - more here: https://github.com/theforeman/foreman/pull/1607, https://github.com/theforeman/foreman/pull/1607#issuecomment-51179194