Workplan

From Freephile Wiki
Revision as of 03:17, 31 May 2018 by Freephile (talk | contribs) (draft)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Priorities[edit | edit source]

  1. Migrate the DCS Wiki to QualityBox’s MWaaS, fully integrated with the Rails App, upgraded to Ubuntu 18.04 LTS (or other 2018 Linux LTS) and MW 1.31 LTS.
  2. Understand the DCS Wiki so as to be able to make any bug fixes and minor improvements requested by Matt.
  3. Increase the maintainability of the DCS Wiki by rewriting and replacing extensions. Not a major priority now, but will be once the migration has been successful.

Progress Report / Work Summary[edit | edit source]

  • Failed attempt to transfer DCS Wiki, as is, to QualityBox. Reason: complexity and non-extension nature of the current SSO and authentication code
  • 100% complete extension inventory

Evaluation of progress in achieving priority objectives[edit | edit source]


June Work Plan (with estimated range of hours)[edit | edit source]

Est. Hours Work
3-6 Discuss with Jared, Aran and Mark the feasibility of using the MW SSO extension
8-16 If this SSO extension appears feasible, set up the DCS Wiki without its SSO and authentication, in a QualityBox MWaaS instance on your PC. Linux and MW versions are selected to ease migration problems so do not have to be, and probably shouldn’t, be the latest versions.
??[1] If successful, the intention is to migrate to a DO server to implement the SSO extension with Jared.
?? If the MW SSO extension is not feasible, develop a plan B [2] to achieve Objective #1.
8-10 In either event, completing and consolidating the list of active DCS’ extensions, including category (Regular, Custom DCS, Organic Design, etc), lines of code, type of code, and other useful columns, including questions and recommendations to be discussed with Aran. This can be in wiki format, but not in Github.

References[edit source]

  1. depends on #1 to find out what work is entailed on the Rails side.
  2. narrow the footprint of the code during configuration, initialization and dependencies for easy by-pass in testing