48
edits
QA/Data harvesting: Difference between revisions
→Risk Assessment
| Line 70: | Line 70: | ||
== Risk Assessment == | == Risk Assessment == | ||
LilyCMS is a very new software project (released July 2010), that is however backed by a company that has been developing content repository software for quiet some time. | |||
These are the major implementation steps here, that have to be completed to get the first actual dashboard feature in: | |||
* Set up Lily so that it understands Bugzilla bugs | |||
** should not be a problem | |||
* Modify the current Bugzilla ETL (''extract, transform, load'') to ouput results into Lily | |||
** simple in theory, but it could become very complicated as the technology is very young, relatively high risk here. | |||
* Extend the ETL to include keywords and flags | |||
** very difficult with current DW, but should be straightforward with LilyCMS. | |||
* Set up Solr to index keywords and flags. | |||
** also rather straightforward | |||
* Make the Bugzilla dashboard talk to hbase and solr, to get the data that is actually needed | |||
**the dashboard can use hbase data anyway, not so sure about accessing solr: moderate risk | |||
This means that we have quiet a lot to do to get the first dashboard feature implemented, while all the following features would just use the same groundwork. | |||
== Meeting Notes == | == Meeting Notes == | ||