« Previous -
Version 14/95
(diff) -
Next » -
Current version
Dong Ma, 05/21/2012 09:17 am
This is the FOSSology backlog, or list of all desired but unimplemented features that need to be prioritized and developed over time. It is dynamic and will be updated frequently.
| Current Iteration (May 14-28, 2012) | ||||
|---|---|---|---|---|
| Task | Priority | Owner | Estimate | Notes |
| Keep build running successfully | High | Everyone | Ongoing | |
| Support the community | High | Everyone | Ongoing | |
| Ubuntu Developer Summit: - Manage the HP table, make introductions, make connections with Ubuntu community & Canonical |
High | Mary | 5 | Done - good conference |
| Add more disk space -- it is a pressing concern. - There is enough disk left to last about 2-3 weeks, so it needs to be addressed ASAP. - Done means each of the agents has a 1TB (or larger) disk, preserving all of its existing data. - This is a straightforward task of creating new virtual disks on the EVA and transferring the old contents to the new disks. Dan should be able to do this with all systems remaining on-line. |
High-High | Dan | 1 | - Dan has added 2 TB disks to all agents and re-synched - Will finish once fo.usa is updated so the system is only down once |
| Transition Mark's tasks to Dan to ensure Dan understands process - This is difficult to measure; the outcome is "fuzzy". For the first iteration, Dan would like to get a solid understanding of the existing test harnesses, test cases, test coverage, build systems, continuous integration systems, configuration management, package configuration, packaging automation, and existing documentation for each of these. - Dan would also like to make sure that he has all the necessary login permissions and memberships needed to participate in the project. - Done means have a drawing (literally) of the existing pieces of the continuous integration systems and how they fit together and can explain each piece (this can then be used in the next iteration to identify gaps and misunderstandings); be added or re-added to all mailing lists and other project resources needed (svn, wiki, mailing lists, system logins, etc). |
High | Dan | 5 | - Dan having daily discussions with Mark; understanding better the Jenkins/build/test infrastructure - Dan and Paul synched re: long-term vision and are fully aligned: automation is key to team |
| Fix 2.0 defects - #1887 - #1893 - #1899 - #1857 - #1875 - #1965 - #1905 - #1911 - #1917 |
High | Alex, Vincent | Alex: 3, Vincent: 2, Larry: 1 | - All defects are resolved; owners to close them and Bob/Larry to verify them |
| Validate defect fixes | High | Bob, Larry | 2 | Done -- all iteration defects verified and closed |
| Create packages and tag RC - Done means: Have an updated set of packages and set of notes (possibly not yet complete) on how to create packages. |
High | Vincent with Dan | 2 | Done RC2 packages created. Vincent will create the packages but Dan will help so he understands how packages are built using ProjectBuilder. |
| Test validation - Develop final test plan, execute test plan - Done means: all tests run and pass on RC2 |
High | Mary: 2, Vincent, Larry, Alex: 3 | 5 | See http://www.fossology.org/projects/fossology/wiki/20-specific_Test_Suite#Testing-for-RC2 |
| Perform Release Checklist - Done means: all tasks on this page are UPDATED & completed |
High | Mary | 1 | Will be updated as we go |
| Update instructions for installation (single systems, clusters, fossology.usa.hp.com) - Done means: Instructions are accurate, complete and results in a properly tuned/configured working system |
High | Mary | 2 | Input from Bob & others will be important as they were instrumental in getting fo.usa properly tuned and running. |
| Update fossology.usa with new server - Done means: fossology.usa is upgraded and running with RC2. |
High | Mary | 1 | |
| Move 2.0 branch to trunk - There is no per file merging. The 2.0 branch completely supersedes the trunk |
High | Dan | 1 | Need to analyze any changes to trunk that should also be in 2.0 branch before copying over |
| Analysis of available tools for FOSS Discovery (OLEX, Sonatype, Antelink, Daniel German’s tool) - Deliverable will be better understanding and hard data on analysis to make decision - Will have a hard copy of Daniel German’s report |
High | Bob | 9 | - Daniel German using tool on HP data; fixing math errors as they are found - Looking beyond Java to other languages - bat tool from Armijn also looks good - Antelink public API tbd - Still following up with OpenLogic and Sonatype |
| Increase the number of automated unit and functional tests - Scheduler (Alex) - Package Agent (Vincent) - Upload from server, url |
High | Team | Alex: 5, Vincent: 3, Larry: 3 | larry: done, found a bug #2025, after #2025 is fixed, revise the tests are needed. Vincent: Done, added more unit test case for pkgagent. |
| Move Alex to FO pod and boot PaulW out | High | PaulH | 2 | |
| Prioritized Possible Future Work | ||||
|---|---|---|---|---|
| Task | Priority | Owner | Estimate | Notes |
| Fix 2.0.1 Defects | High | Alex, Vincent, Larry | ||
| Initial Design for FOSS Discovery | High | Bob | ||
| Truly make it a push-button end-to-end, continuous integration environment (at least nightly check out, build, unit test, functional test, package, install, functional test) | High | Dan | ||
| Report on current state of testing (pass/fail, # successful, # run, etc) – make emails more informative, refine reports to make it easier to digest | High | Dan | ||
| Clean up test plans and be clear what needs testing | High | Mary | ||
| Training on existing functionality (tagging, etc) | High | Bob | ||
| Clean up test assignments and test cases | High | Mary | ||
| Make sure coverage for supported distros | High | Mary | ||
| Increase the number of automated unit and functional tests | High | Team | ||
| Add test cases as necessary | High | Team | ||
| Modify code to support the db server on a separate system. This has always been a design goal but has not been tested. | High | Easy – test | ||
| Remove pfile.pfile_liccount from schema and code (common/common-license.php, plugins/agent-license.php, plugins/agent-license-reanalyze.php, plugins/ui-license.php. This was an experimental feature that mistakenly had code checked in around it. | High | Easy | ||
| FOSS Discovery/Output | High | TBD | ||
| UI reconciliation/editing | High | TBD | ||
| Need method to correct license scan (#1869) | High | |||
| Set up integration staging machine | High | |||
| Metric development (creation, capturing, reporting) | High | |||
| Password reset capability (from ScottL) | High | |||
| Aligning license names with SPDX license names | High | |||
| (Mark) improve reporting of UI test results. | High | |||
| (Mark) Create a license test data set from analysis we've done already | High | |||
| Add load testing to automated test suite | High | |||
| Implement automated nightly builds - should also include performance regression tests. | High | |||
| Upload from version control system (CVS, SVN, PVCS) - From George Pace, Jeroen, SpottedOtter | High | |||
| When viewing a file add ability to pop-up the full text of a license. | High | |||
| Update license reference list so nomos refers to the license ref with the license text. | High | |||
| Add to nomos licenses used by ninka and spdx. This includes exceptions. | High | |||
| Add capability for reanalysis without breaking data persistence ie. do new analysis without removing previous analysis results. This can be used, to compare new and old analysis results, and to insure that report url's are persistent. 1.2 implemented data collection for this for nomos and buckets. The UI needs to catch up and allow one to select the data set they want to see. The code is already in ui-buckets.php and ui-nomos-license.php (search for FUTURE). But we need to decide if this is the interface we want. | High | |||
| Public FOSSology instance at UNO | High | |||
| Move fo.usa siteminder service from ITG to PRO | High | |||
| Move from the LIT lab | High | |||
| Setup backups | High | |||
| Features to be developed by the community? | Medium | |||
| Transition Alex's work | Medium | Alex expects to remain through summer | ||
| How can one tell who, when and from where an upload came? Add to ui-browse | Medium | Easy; add to info | ||
| Document FOSSology recommended hardware configs | Medium | |||
| Consider changing repo layout to work with "large" perhaps 16MB files kind of like hadoop. Using small files like now (avg size ~32k) makes repo deletes take forever and makes copying the repo take forever. For our repo, we could pack as many files as will fit wholly fit into ~16MB. Larger files would be saved as individual files. The whole point is to consolidate the tiny files to use fewer inodes and thus speed up delagent and repo copies. | Medium | |||
| FO permission scheme needs full implementation | Medium | |||
| We need a client only package so that people can submit jobs (fossjobs) from a machine not running fossology. | Medium | |||
| Need agent to remove orphan files from the repository. This can happen on a delagent failure. | Medium | |||
| Add license from kernel object modules (license from modsym) to license_file | Medium | |||
| Create a user interface to create bucket pools, bucket definitions, scripts and anything else needed, along with a prompt & screen to rerun analysis with your newly defined bucket pool. Current method is too ugly. | Medium | |||
| Remove bucket code that determines what bucket a container is in. After implementation we decided that this feature was way too confusing for the user because of the hierarchical nature of bucket evaluation. This will speed up bucket scans. Remove bucket_container table. | Medium | |||
| FOSSology.org cleanup (how team uses website, rules/process, etc) – using RedMine most effectively | Medium | |||
| Archive and remove old wiki content | Medium | |||
| Finish documentation organization | Medium | |||
| Identify documentation gaps, inconsistencies | Medium | |||
| Commenting uses/contributions/process descriptions | Medium | |||
| Update screenshots | Medium | |||
| Update instructions | Medium | |||
| Update monitoring scripts/administration | Medium | |||
| Add Servers | Medium | |||
| Fix 2.1.0 defects | Medium-Low | |||
| Detect code snippets | Low | |||
| Binary analysis | Low | |||
| Binary analysis for open source discovery | Low | |||
| Code clone detection | Low | |||
| Archived reports - simple text file dump, PDF reports, eventually full web archive of all analysis reports. Or else just don't throw away any data. Nomos and buckets already can do this but there is still no guarantee that someone doesn't subvert this process (see ars tables). | Low | |||
| Write tar agent - re-tar arbitrary parts of repo - don't have an owner/customer to support | Low | |||
| Easy way to install buttons/links on micro menu to run system utilities/scripts on a file. For example, .ko files could have an nm link, and a modinfo link. The script may need a way to determine if it should be added to menu or not. For example, nm applies to object files, but modinfo only applies to .ko. The purpose is to process fossology files in real time with system scripts/apps. | Low | |||
| Allow license admin to work in read only mode at low (read) permission level. | Low | |||
| Performance improvements (repository, delagent, …) | Ongoing | |||
| Ongoing community support (emails, help installations, etc) | Overhead | |||
| Support others on Community presentations (Bruno, Martin, etc) | Overhead | |||
| Fossology.org support (process and ownership for interfacing with OSU/OSL) | Overhead | |||
| Community development (incorporating contributors, bringing people in, etc.) – ongoing list on website, opportunities for people outside HP, etc | Overhead | |||