This page describes who is doing what on the FOSSology team, and his/her status. Note that “rfo” refers to the repository to be operated by fossology.org If you want to work on any of these (or other) areas of interest to fossology users, please write to the list (fossology at fossology dot org).
| Responsibility | Status | Name |
| Automated Test subsystem | | Mark |
| UI test development | | Mark |
| Duty: programming in any area of FO | | Mark |
| Generate Debian packages for testing purposes | | Mark, Mary |
| Release Services - creating a release; generate tarball, update release notes, update version number, etc | | Mark, Mary |
| — |
| FOSSology Support | | Mary (Team) |
| Maintain FOSSology installation on fo.fc | | Mary (Mark) |
| Maintain FOSSology installation on rfo | | Mary (Mark) |
| Support the FOSSology production servers (RFO, FO), and HP (FFHC); performance tuning for externally visible apps. PostgreSQL, Apache | | Mary |
| Duty: Testing | | Mary |
| (HP only) OSRB distro meeting liaison (this is a rotating responsibility from release to release) This means participating in the OSRB distro meeting to insure FO can replace (then supersede) nomos. This person must report back any FO shortcomings and potential enhancements that the OSRB needs. | | Mary (Bob) |
| — |
| Sysadmin for all production systems - kernel patches, maintenance, monitoring | | Dan |
| 1.2 Task Define, test & implement full backup & recovery process for rfo production servers | | Vincent |
| Duty: Release Program Management - keeping track issues and making sure the things that need to happen to release happen. | | Dan |
| Communications with other program teams | | Dan |
| Equipment ordering | | Dan (Ryan) |
| — |
| Duties: usability, docs | | TBD |
| UI Usability | | TBD |
| UI Documentation wiki updates | | TBD |
| — |
| Technology lead - Design, features, requirements gathering, integration, community involvement, research | | Bob |
| Duty: Community behavior (i.e. making sure that we are running FO as an open source project and doesn't become HP centric) This includes using the public IRC, standard installs and packages, filing and tracking bugs in upstream fossology dependencies, being more inclusive outside of HP, … | | Bob |
| Contact/mentor for others working on fo technology: 1. Adam (machine learning), 2. University of Victoria grant (dependency analysis, vulnerability tracking), 3. TBD grant | | Bob |
| Proficiency on Adam's code | | Bob |
| — |
| 1.2 Task Nomos license analysis module | | Chan (Bob) |
| — |
| Maintain Debian packaging code and generate official packages | | taggart |
| Provide FOSSology results for Debian: - Automate the periodic processing of Debian, Work with distro package maintainers and build systems to make the results usable for them. | | taggart |
| — |
| FOSSology Installation development - make sure that an fo install works, regardless of what changes are needed, list of supported distros | | TBD |