8000 GitHub · Where software is built
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Milestones

List view

  • The milestone to track the work on [Proxy frontend API requests through Nuxt](https://github.com/WordPress/openverse/issues/3473) project

    No due date
  • This milestone captures improvements that can be made to the batched update DAG: https://docs.openverse.org/catalog/reference/DAGs.html#batched-update

    No due date
    1/5 issues closed
  • https://github.com/WordPress/openverse/issues/431

    No due date
    7/11 issues closed
  • No due date
    3/6 issues closed
  • No due date
    1/3 issues closed
  • A milestone for tracking the removal of the data refresh server. Project thread: https://github.com/WordPress/openverse/issues/3925

    No due date
    13/18 issues closed
  • No due date
    13/24 issues closed
  • ## Problem <!-- Describe a problem solved by this feature; or delete the section entirely. --> All our services log unstructured logs (in other words, they log sentences or blobs of text). This makes it difficult or unreliable to parse and query logs using, for example, Logs Insights, or any other tool that relies on structured logs (Loki, LogStash, etc). ## Description <!-- Describe the feature and how it solves the problem. --> To make log querying easier, we can switch to things like [`django-structlog`](https://github.com/jrobichaud/django-structlog) (for the API), [`JSON-log-formatter`](https://pypi.org/project/JSON-log-formatter/) for the ingestion server (I couldn't find anything unique to Falcon) [and Airflow](https://stackoverflow.com/a/55502536), and a mature logging solution that supports [structured logging in Node](https://github.com/pinojs/pino/). This milestone collects the issues to implement the above suggestions. In all cases, for ease of reading in local development, we should add a switch to default to flat line style logs when `ENVIRONMENT == "local"`.

    No due date
    1/4 issues closed
  • Issues created as a result of this discussion: https://github.com/WordPress/openverse/discussions/2155 This milestone should only contain issues from that discussion and closed once the topics in that discussion are resolved and implemented. In other words, new feedback related to the contributor experience should not be added to this particular milestone unless it is a bug/issue with the original topic of discussion.

    No due date
    2/3 issues closed
  • The Openverse maintainers collectively spent some time looking through our documentation and identified a number of issues to resolve and improvements to make. This milestone collects those issues.

    No due date
    7/20 issues closed
0