From d21a84e2fa80885d4636518976c96916594d04a5 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Mon, 6 Jan 2025 00:08:17 +0000 Subject: [PATCH] Updates --- community/core/community/README.md/index.html | 2 +- community/core/community/SUPPORT_POLICY.md/index.html | 2 +- community/core/community/governance.md/index.html | 2 +- community/core/community/help-wanted.md/index.html | 4 ++-- community/core/community/liaisons.md/index.html | 4 ++-- community/core/community/sig-devsecops/README.md/index.html | 4 ++-- community/core/community/sig-devsecops/charter.md/index.html | 4 ++-- .../core/community/sig-observability/README.md/index.html | 2 +- .../core/community/sig-observability/charter.md/index.html | 2 +- .../core/community/sig-stack-guidance/README.md/index.html | 2 +- .../core/community/sig-stack-guidance/charter.md/index.html | 2 +- .../core/community/sig-user-experience/README.md/index.html | 2 +- .../core/community/sig-user-experience/charter.md/index.html | 2 +- community/core/community/wg-cnbi/README.md/index.html | 4 ++-- community/core/community/wg-cnbi/charter.md/index.html | 2 +- community/core/docs/ROADMAP.md/index.html | 2 +- .../index.html | 2 +- .../core/docs/adr/0001-use-gpl3-as-license.md/index.html | 2 +- community/core/docs/adr/0002-release-policy.md/index.html | 2 +- .../core/docs/adr/0003-decommision-qeb-hwt.md/index.html | 2 +- .../core/docs/adr/0004-naming-convention-images.md/index.html | 2 +- .../index.html | 2 +- .../core/docs/adr/0005-obtimizing-keb-runs.md/index.html | 2 +- .../core/docs/adr/0006-thoth-github-action.md/index.html | 2 +- community/core/docs/adr/0007-scorecard-metrics.md/index.html | 2 +- community/core/docs/adr/template.md/index.html | 2 +- .../index.html | 2 +- .../index.html | 2 +- .../detecting-lincenses-of-python-modules.md/index.html | 4 ++-- .../generate-prescription-from-text.md/index.html | 4 ++-- .../intern-projects/prescriptions-bootstrap.md/index.html | 4 ++-- community/core/docs/sprint-demos/35.md/index.html | 2 +- community/core/docs/sprint-demos/37.md/index.html | 2 +- community/core/docs/sprint-demos/38.md/index.html | 2 +- community/core/docs/sprint-demos/39.md/index.html | 2 +- community/core/docs/sprint-demos/README.md/index.html | 2 +- community/index.html | 2 +- index.html | 4 ++-- metrics/index.html | 2 +- metrics/issue_metrics.md/index.html | 2 +- metrics/site_metrics.md/index.html | 2 +- page-data/sq/d/1276261476.json | 2 +- support/faq/overview.mdx/index.html | 2 +- support/faq/thoth_yaml.mdx/index.html | 2 +- support/index.html | 2 +- support/issue_tracker.mdx/index.html | 2 +- 46 files changed, 55 insertions(+), 55 deletions(-) diff --git a/community/core/community/README.md/index.html b/community/core/community/README.md/index.html index 2f7196f53d..a3117b8278 100644 --- a/community/core/community/README.md/index.html +++ b/community/core/community/README.md/index.html @@ -14,7 +14,7 @@ - }

Repository configuration

The github-config.yaml file contains the details of the + }

Repository configuration

The github-config.yaml file contains the details of the GitHub configuration for our organization.

This file is used by Peribolos to apply the configuration to the various repositories. Check the Peribolos diff --git a/community/core/community/SUPPORT_POLICY.md/index.html b/community/core/community/SUPPORT_POLICY.md/index.html index e88e103f6e..0a59a01896 100644 --- a/community/core/community/SUPPORT_POLICY.md/index.html +++ b/community/core/community/SUPPORT_POLICY.md/index.html @@ -14,7 +14,7 @@ - }

Support Policy

This document outlines the support policy for Project Thoth. For general information how and where to contact us, + }

Support Policy

This document outlines the support policy for Project Thoth. For general information how and where to contact us, please see our help page.

Supported Runtime Environments

When adding new content to Thoth’s Knoweldge Graph, we follow (roughly) the following policy:

  1. what runtime is used by RHODS/Open Data Hub? Right now most data science work is based on ubi8-py38
  2. what runtime is the latest release and maintained by Red Hat? ubi9-py39
  3. based on our research (py311 due to perf incr.), see also https://www.phoronix.com/review/python-311-performance

End of Life

We will disable solvers and the corresponding Python versions when they reach end of life. The data aggregated by Project Thoth will be kept in the Knowledge Graph for as long as possible. We will not delete data from the Ceph storage, but might disable its use for advises.

\ No newline at end of file diff --git a/community/core/community/governance.md/index.html b/community/core/community/governance.md/index.html index 6d6349a032..130aa636ca 100644 --- a/community/core/community/governance.md/index.html +++ b/community/core/community/governance.md/index.html @@ -14,7 +14,7 @@ - }

Principles

The Thoth Station community adheres to the following principles:

  • Open: Project Thoth is open source. See repository guidelines, below.
  • Welcoming and respectful: See Code of Conduct, below.
  • Transparent and accessible: Work and collaboration should be done in public. See SIG governance, below.
  • Merit: Ideas and contributions are accepted according to their technical merit and alignment with project objectives, [scope], and [design principles].

Code of Conduct

The Thoth Station community abides by [out code of conduct]:

As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.

As a member of the project, you represent the project and your fellow contributors. + }

Principles

The Thoth Station community adheres to the following principles:

  • Open: Project Thoth is open source. See repository guidelines, below.
  • Welcoming and respectful: See Code of Conduct, below.
  • Transparent and accessible: Work and collaboration should be done in public. See SIG governance, below.
  • Merit: Ideas and contributions are accepted according to their technical merit and alignment with project objectives, [scope], and [design principles].

Code of Conduct

The Thoth Station community abides by [out code of conduct]:

As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.

As a member of the project, you represent the project and your fellow contributors. We value our community tremendously and we’d like to keep cultivating a friendly and collaborative environment for our contributors and users. We want everyone in the community to have [positive experiences].

Community groups

The project is comprised of the following types of subgroups:

  • Special Interest Groups, SIGs
    • Subprojects

SIGs

The project is organized primarily into Special Interest diff --git a/community/core/community/help-wanted.md/index.html b/community/core/community/help-wanted.md/index.html index 07463a9c6b..dc6fc0541b 100644 --- a/community/core/community/help-wanted.md/index.html +++ b/community/core/community/help-wanted.md/index.html @@ -20,7 +20,7 @@ - }Help Wanted and Good First Issue Labels | Thoth Station Help

Help Wanted and Good First Issue Labels

Overview

We use two labels to identify issues that have been specifically created or selected for new contributors: help wanted and good first + }Help Wanted and Good First Issue Labels | Thoth Station Help

Help Wanted and Good First Issue Labels

Overview

We use two labels to identify issues that have been specifically created or selected for new contributors: help wanted and good first issue. The good first issue label is a subset of the help wanted label, indicating that members have committed to providing extra assistance for new contributors. All good first issue items also have the help wanted @@ -75,4 +75,4 @@ They want to know the acceptable way to ask for people to review a PR, and how to nudge things along when a PR is stalled. Show them how we operate by helping move their first PR along.

  • If you have time, let the contributor know that they can DM you with questions -that they aren’t yet comfortable asking the wider group.
  • \ No newline at end of file +that they aren’t yet comfortable asking the wider group.
    \ No newline at end of file diff --git a/community/core/community/liaisons.md/index.html b/community/core/community/liaisons.md/index.html index 97e6fcd4f6..1eb9e90332 100644 --- a/community/core/community/liaisons.md/index.html +++ b/community/core/community/liaisons.md/index.html @@ -14,10 +14,10 @@ - }

    Liaisons

    Each community group or SIG of Project Thoth assigned a Steering Committee + }

    Liaisons

    Each community group or SIG of Project Thoth assigned a Steering Committee liaison. Liaisons act as a point of contact from steering, engage with their respective community groups to ensure they are healthy and facilitate communication.

    Liaisons do not make decisions for the community group or on behalf of the Steering Committee.

    Liaisons are assigned community groups at random (adjustments can be made, if needed) with each member having an (almost) equal distribution -of SIGs, WGs and UGs.

    Community GroupSteering Committee Liaison
    SIG DevSecOpsChristoph Görn (@goern)
    SIG ObservabilityChristoph Görn (@goern)
    SIG Stack GuidanceChristoph Görn (@goern)
    SIG User ExperienceChristoph Görn (@goern)
    \ No newline at end of file +of SIGs, WGs and UGs.

    Community GroupSteering Committee Liaison
    SIG DevSecOpsChristoph Görn (@goern)
    SIG ObservabilityChristoph Görn (@goern)
    SIG Stack GuidanceChristoph Görn (@goern)
    SIG User ExperienceChristoph Görn (@goern)
    \ No newline at end of file diff --git a/community/core/community/sig-devsecops/README.md/index.html b/community/core/community/sig-devsecops/README.md/index.html index c3fbe5637e..37bb692591 100644 --- a/community/core/community/sig-devsecops/README.md/index.html +++ b/community/core/community/sig-devsecops/README.md/index.html @@ -14,7 +14,7 @@ - }

    DevSecOps Special Interest Group

    HIBERNATION NOTICE: This SIG is currently hibernating. If you are interested in reviving this SIG, please reach out to the Thoth team via an issue in the the core or support repository. + }

    DevSecOps Special Interest Group

    HIBERNATION NOTICE: This SIG is currently hibernating. If you are interested in reviving this SIG, please reach out to the Thoth team via an issue in the the core or support repository. This SIG covers all the tools and supporting container images that deliver Thoth-Station applications, as well as the build pipelines and Continuous Integration systems that enable the automated builds. This includes the discussion related to the release process of the Thoth-Station applications, the build pipelines themselves, supporting container images, tooling, and architectural decisions.

    The charter defines the scope and governance of the DevSecOps Special Interest Group.

    Leadership

    Chairs

    The Chairs of the SIG run operations and processes governing the SIG.

    Technical Leads

    The Technical Leads of the SIG establish new subprojects, decommission existing -subprojects, and resolve cross-subproject technical issues and decisions.

    Contact

    Subprojects

    The following subprojects are owned by sig-devsecops:

    Notebooks

    A set of base images that are useful for Data Science work

    Pipelines

    A set of base images and pipelines to build application container images

    Services

    Tooling and configuration to manage the releases of various Thoth services and components

    \ No newline at end of file +subprojects, and resolve cross-subproject technical issues and decisions.

    Contact

    Subprojects

    The following subprojects are owned by sig-devsecops:

    Notebooks

    A set of base images that are useful for Data Science work

    Pipelines

    A set of base images and pipelines to build application container images

    Services

    Tooling and configuration to manage the releases of various Thoth services and components

    \ No newline at end of file diff --git a/community/core/community/sig-devsecops/charter.md/index.html b/community/core/community/sig-devsecops/charter.md/index.html index 405f122935..be79199b19 100644 --- a/community/core/community/sig-devsecops/charter.md/index.html +++ b/community/core/community/sig-devsecops/charter.md/index.html @@ -14,8 +14,8 @@ - }

    SIG DevSecOps Charter

    This charter adheres to the conventions described in the Kubernetes Charter README and uses the Roles and Organization Management outlined in sig-governance. For all things taken from the Kubernetes community, we use scaled down variants, Kubernetes documents are references.

    Scope

    This SIG covers all the tools and supporting container images that deliver Thoth-Station + }

    SIG DevSecOps Charter

    This charter adheres to the conventions described in the Kubernetes Charter README and uses the Roles and Organization Management outlined in sig-governance. For all things taken from the Kubernetes community, we use scaled down variants, Kubernetes documents are references.

    Scope

    This SIG covers all the tools and supporting container images that deliver Thoth-Station applications, as well as the build pipelines and Continuous Integration systems that enable the automated builds.

    This includes the discussion related to the release process of the Thoth-Station applications, the build pipelines themselves, supporting container images, tooling, -and architectural decisions.

    In scope

    • Pipelines to build and publish application container images
    • Supporting container images
    • End-user oriented content about Thoth pipelines and supporting images
    • GitOps configurations to deploy the services
    • Release management for Thoth-Station

    Out of scope

    • Operation of the clusters that host the services

    Roles and Organization Management

    This sig follows adheres to the Roles and Organization Management outlined in sig-governance.

    Subproject Creation

    SIG Chairs can create subprojects without requiring member votes.

    \ No newline at end of file +and architectural decisions.

    In scope

    • Pipelines to build and publish application container images
    • Supporting container images
    • End-user oriented content about Thoth pipelines and supporting images
    • GitOps configurations to deploy the services
    • Release management for Thoth-Station

    Out of scope

    • Operation of the clusters that host the services

    Roles and Organization Management

    This sig follows adheres to the Roles and Organization Management outlined in sig-governance.

    Subproject Creation

    SIG Chairs can create subprojects without requiring member votes.

    \ No newline at end of file diff --git a/community/core/community/sig-observability/README.md/index.html b/community/core/community/sig-observability/README.md/index.html index 652666401a..fb0bb8cd2f 100644 --- a/community/core/community/sig-observability/README.md/index.html +++ b/community/core/community/sig-observability/README.md/index.html @@ -14,6 +14,6 @@ - }

    Observability Special Interest Group

    HIBERNATION NOTICE: This SIG is currently hibernating. If you are interested in reviving this SIG, please reach out to the Thoth team via an issue in the the core or support repository. + }

    Observability Special Interest Group

    HIBERNATION NOTICE: This SIG is currently hibernating. If you are interested in reviving this SIG, please reach out to the Thoth team via an issue in the the core or support repository. Work on all things that concern Observability! This includes the definition of metrics, monitoring, reporting and alerting.

    The charter defines the scope and governance of the Observability Special Interest Group.

    Leadership

    Chairs

    The Chairs of the SIG run operations and processes governing the SIG.

    Technical Leads

    The Technical Leads of the SIG establish new subprojects, decommission existing subprojects, and resolve cross-subproject technical issues and decisions.

    Contact

    Subprojects

    The following subprojects are owned by sig-observability:

    Monitoring

    \ No newline at end of file diff --git a/community/core/community/sig-observability/charter.md/index.html b/community/core/community/sig-observability/charter.md/index.html index 248be4493b..413253004d 100644 --- a/community/core/community/sig-observability/charter.md/index.html +++ b/community/core/community/sig-observability/charter.md/index.html @@ -14,6 +14,6 @@ - }

    SIG Observability Charter

    This charter adheres to the conventions described in the Kubernetes Charter README and uses + }

    SIG Observability Charter

    This charter adheres to the conventions described in the Kubernetes Charter README and uses the Roles and Organization Management outlined in sig-governance. For all things taken from the Kubernetes community, we use scaled down variants, Kubernetes documents are references.

    Scope

    Work on all things that concerns Observability! This includes the definition of metrics, monitoring, reporting and alerting.

    Roles and Organization Management

    This sig follows adheres to the Roles and Organization Management outlined in sig-governance.

    Subproject Creation

    SIG Chairs can create subprojects without requiring member votes.

    \ No newline at end of file diff --git a/community/core/community/sig-stack-guidance/README.md/index.html b/community/core/community/sig-stack-guidance/README.md/index.html index faf2bb6689..b90dfeff84 100644 --- a/community/core/community/sig-stack-guidance/README.md/index.html +++ b/community/core/community/sig-stack-guidance/README.md/index.html @@ -14,5 +14,5 @@ - }

    Stack Guidance Special Interest Group

    HIBERNATION NOTICE: This SIG is currently hibernating. If you are interested in reviving this SIG, please reach out to the Thoth team via an issue in the the core or support repository. + }

    Stack Guidance Special Interest Group

    HIBERNATION NOTICE: This SIG is currently hibernating. If you are interested in reviving this SIG, please reach out to the Thoth team via an issue in the the core or support repository. Work on recommending the most effective, performant and secure software stack for user applications and on actively creating prescriptions and security related information

    The charter defines the scope and governance of the Stack Guidance Special Interest Group.

    Leadership

    Contact

    Subprojects

    The following subprojects are owned by sig-stack-guidance:

    adviser

    prescriptions

    solver

    storages

    \ No newline at end of file diff --git a/community/core/community/sig-stack-guidance/charter.md/index.html b/community/core/community/sig-stack-guidance/charter.md/index.html index 3d6a3fe5b0..37ba39990e 100644 --- a/community/core/community/sig-stack-guidance/charter.md/index.html +++ b/community/core/community/sig-stack-guidance/charter.md/index.html @@ -14,4 +14,4 @@ - }

    SIG Stack Guidance Charter

    This charter adheres to the conventions described in the Kubernetes Charter README and uses the Roles and Organization Management outlined in sig-governance. For all things taken from the Kubernetes community, we use scaled down variants, Kubernetes documents are references.

    Scope

    This includes the discussion related to recommending the most effective, performant and secure software stack for user applications and on actively creating prescriptions and security related information.

    Roles and Organization Management

    This sig follows adheres to the Roles and Organization Management outlined in sig-governance.

    Subproject Creation

    SIG Chairs can create subprojects without requiring member votes.

    \ No newline at end of file + }

    SIG Stack Guidance Charter

    This charter adheres to the conventions described in the Kubernetes Charter README and uses the Roles and Organization Management outlined in sig-governance. For all things taken from the Kubernetes community, we use scaled down variants, Kubernetes documents are references.

    Scope

    This includes the discussion related to recommending the most effective, performant and secure software stack for user applications and on actively creating prescriptions and security related information.

    Roles and Organization Management

    This sig follows adheres to the Roles and Organization Management outlined in sig-governance.

    Subproject Creation

    SIG Chairs can create subprojects without requiring member votes.

    \ No newline at end of file diff --git a/community/core/community/sig-user-experience/README.md/index.html b/community/core/community/sig-user-experience/README.md/index.html index 19f8f4adc4..a0a6388143 100644 --- a/community/core/community/sig-user-experience/README.md/index.html +++ b/community/core/community/sig-user-experience/README.md/index.html @@ -14,6 +14,6 @@ - }

    User Experience Special Interest Group

    HIBERNATION NOTICE: This SIG is currently hibernating. If you are interested in reviving this SIG, please reach out to the Thoth team via an issue in the the core or support repository. + }

    User Experience Special Interest Group

    HIBERNATION NOTICE: This SIG is currently hibernating. If you are interested in reviving this SIG, please reach out to the Thoth team via an issue in the the core or support repository. The User Experience SIG focuses on the interaction points between end users and Thoth components.

    The charter defines the scope and governance of the User Experience Special Interest Group.

    Leadership

    Chairs

    The Chairs of the SIG run operations and processes governing the SIG.

    Technical Leads

    The Technical Leads of the SIG establish new subprojects, decommission existing subprojects, and resolve cross-subproject technical issues and decisions.

    Contact

    Subprojects

    The following subprojects are owned by sig-user-experience:

    jupyterlab-requirements

    kebechet

    s2i-thoth

    thamos

    user-api

    \ No newline at end of file diff --git a/community/core/community/sig-user-experience/charter.md/index.html b/community/core/community/sig-user-experience/charter.md/index.html index f12057a5be..1bc472c6dc 100644 --- a/community/core/community/sig-user-experience/charter.md/index.html +++ b/community/core/community/sig-user-experience/charter.md/index.html @@ -14,7 +14,7 @@ - }

    SIG User Experience Charter

    This charter adheres to the conventions described in the Kubernetes Charter README and uses + }

    SIG User Experience Charter

    This charter adheres to the conventions described in the Kubernetes Charter README and uses the Roles and Organization Management outlined in Kuberentes’ sig-governance. For all things taken from the Kubernetes community, we use scaled down variants, Kubernetes documents are references.

    Scope

    The goal of this SIG is to ensure that the entry points to Thoth provide a great user experience.

    This includes the interaction with human users (be it though direct component diff --git a/community/core/community/wg-cnbi/README.md/index.html b/community/core/community/wg-cnbi/README.md/index.html index 88d09e9e02..eeb07c773f 100644 --- a/community/core/community/wg-cnbi/README.md/index.html +++ b/community/core/community/wg-cnbi/README.md/index.html @@ -14,5 +14,5 @@ - }

    CNBi Working Group

    HIBERNATION NOTICE: This WG is currently hibernating. If you are interested in reviving this WG, please reach out to the Thoth team via an issue in the the core or support repository. -The goal of this working group is to create a service that implements the backend side of the Custom Notebook Image (CNBi) MVP in the context of Open Data Hub (ODH).

    The charter defines the scope and governance of the CNBi Working Group.

    Stakeholder SIGs

    • SIG DevSecOps
    • SIG Stack Guidance
    • SIG User Experience

    Organizers

    • Christoph Görn (@goern), Red Hat

    Contact

    \ No newline at end of file + }

    CNBi Working Group

    HIBERNATION NOTICE: This WG is currently hibernating. If you are interested in reviving this WG, please reach out to the Thoth team via an issue in the the core or support repository. +The goal of this working group is to create a service that implements the backend side of the Custom Notebook Image (CNBi) MVP in the context of Open Data Hub (ODH).

    The charter defines the scope and governance of the CNBi Working Group.

    Stakeholder SIGs

    • SIG DevSecOps
    • SIG Stack Guidance
    • SIG User Experience

    Organizers

    • Christoph Görn (@goern), Red Hat

    Contact

    \ No newline at end of file diff --git a/community/core/community/wg-cnbi/charter.md/index.html b/community/core/community/wg-cnbi/charter.md/index.html index 40dc01d703..b2b3335725 100644 --- a/community/core/community/wg-cnbi/charter.md/index.html +++ b/community/core/community/wg-cnbi/charter.md/index.html @@ -14,4 +14,4 @@ - }

    WG Custom Notebook Image (CNBi) Charter

    The goal of this working group (WG) is to design and implement an MVP for the backend side of the Custom Notebook Image (CNBi) functionality of Open Data Hub (ODH).

    The WG is a continuation of the work of the BYON WG. The work produced by the working group aims at meeting the requirements specified in the RHODS epics about the functionality, including:

    For reference, deliverables for phase 1 (BYON) were tracked in the byon repository and its corresponding project planning board.

    Scope

    The focus of this WG is on the backend components that handle the creation, validation, and importing of container images for use into ODH, as well as the software stack guidance service provided to the users of these images.

    In scope

    • The CNBi operator
    • Tekton Pipeline definitions that implement the CNBi / BYON functionality
    • Thoth APIs that contribute to the requirements of the CNBi functionality on ODH
    • Coordination with ODH in integrating the funtcionality
    • Deployment of the PoC and coordination with Operate First and OS-Climate on its usage

    Out of scope

    • ODH User Interface design and implementation

    Stakeholders

    • Thoth SIGs:
      • DevSecOps
      • Stack Guidance
      • User Experience
    • ODH SIGs:
      • ML-DevExp
      • Platform

    Deliverables

    • Documentation of the design of the backend, the components involved, the interactions between them, and the interface between ODH and the backend.
    • An evolution of the meteor operator that acts as the main controller for the CNBi functionality.
    • A set of Tekton / OpenShift pipelines definitions that implement the functionality.
    • A working PoC of the operator and pipelines, with ODH integration when available, ready to use by a target group: the OS-Climate project.

    Disband criteria

    If stakeholder SIGs and the WG decide all features described in the In Scope section are complete and no more discussions and investigations are needed in this WG, they may decide to disband this WG.

    \ No newline at end of file + }

    WG Custom Notebook Image (CNBi) Charter

    The goal of this working group (WG) is to design and implement an MVP for the backend side of the Custom Notebook Image (CNBi) functionality of Open Data Hub (ODH).

    The WG is a continuation of the work of the BYON WG. The work produced by the working group aims at meeting the requirements specified in the RHODS epics about the functionality, including:

    For reference, deliverables for phase 1 (BYON) were tracked in the byon repository and its corresponding project planning board.

    Scope

    The focus of this WG is on the backend components that handle the creation, validation, and importing of container images for use into ODH, as well as the software stack guidance service provided to the users of these images.

    In scope

    • The CNBi operator
    • Tekton Pipeline definitions that implement the CNBi / BYON functionality
    • Thoth APIs that contribute to the requirements of the CNBi functionality on ODH
    • Coordination with ODH in integrating the funtcionality
    • Deployment of the PoC and coordination with Operate First and OS-Climate on its usage

    Out of scope

    • ODH User Interface design and implementation

    Stakeholders

    • Thoth SIGs:
      • DevSecOps
      • Stack Guidance
      • User Experience
    • ODH SIGs:
      • ML-DevExp
      • Platform

    Deliverables

    • Documentation of the design of the backend, the components involved, the interactions between them, and the interface between ODH and the backend.
    • An evolution of the meteor operator that acts as the main controller for the CNBi functionality.
    • A set of Tekton / OpenShift pipelines definitions that implement the functionality.
    • A working PoC of the operator and pipelines, with ODH integration when available, ready to use by a target group: the OS-Climate project.

    Disband criteria

    If stakeholder SIGs and the WG decide all features described in the In Scope section are complete and no more discussions and investigations are needed in this WG, they may decide to disband this WG.

    \ No newline at end of file diff --git a/community/core/docs/ROADMAP.md/index.html b/community/core/docs/ROADMAP.md/index.html index c1dc3c9740..49601d8b6e 100644 --- a/community/core/docs/ROADMAP.md/index.html +++ b/community/core/docs/ROADMAP.md/index.html @@ -14,7 +14,7 @@ - }

    Thoth Roadmap

    After the current and coordinated release of Thoth’s components, we started this document to outline our + }

    Thoth Roadmap

    After the current and coordinated release of Thoth’s components, we started this document to outline our current focus areas and the major items we are working on.

    For a more detailed overview of our current activities, have a look at our GitHub projects. We use them to plan our sprints.

    Informative Advice

    Based on a command line tool and our GitHub App we will extend the advice we give to human developers. This diff --git a/community/core/docs/adr/0000-use-markdown-architectural-decision-records.md/index.html b/community/core/docs/adr/0000-use-markdown-architectural-decision-records.md/index.html index b0095dee22..ae1ce942f4 100644 --- a/community/core/docs/adr/0000-use-markdown-architectural-decision-records.md/index.html +++ b/community/core/docs/adr/0000-use-markdown-architectural-decision-records.md/index.html @@ -14,4 +14,4 @@ - }

    Use Markdown Architectural Decision Records

    Context and Problem Statement

    We want to record architectural decisions made in Project Thoth. Which format and structure should these records follow?

    Considered Options

    Decision Outcome

    Chosen option: “MADR 2.1.2”, because

    • Implicit assumptions should be made explicit.

      Design documentation is important to enable people understanding the decisions later on.

      See also A rational design process: How and why to fake it.

    • The MADR format is lean and fits our development style.

    • The MADR structure is comprehensible and facilitates usage & maintenance.

    • The MADR project is vivid.

    • Version 2.1.2 is the latest one available when starting to document ADRs.

    \ No newline at end of file + }

    Use Markdown Architectural Decision Records

    Context and Problem Statement

    We want to record architectural decisions made in Project Thoth. Which format and structure should these records follow?

    Considered Options

    Decision Outcome

    Chosen option: “MADR 2.1.2”, because

    • Implicit assumptions should be made explicit.

      Design documentation is important to enable people understanding the decisions later on.

      See also A rational design process: How and why to fake it.

    • The MADR format is lean and fits our development style.

    • The MADR structure is comprehensible and facilitates usage & maintenance.

    • The MADR project is vivid.

    • Version 2.1.2 is the latest one available when starting to document ADRs.

    \ No newline at end of file diff --git a/community/core/docs/adr/0001-use-gpl3-as-license.md/index.html b/community/core/docs/adr/0001-use-gpl3-as-license.md/index.html index 8ada28f1bf..58f7543458 100644 --- a/community/core/docs/adr/0001-use-gpl3-as-license.md/index.html +++ b/community/core/docs/adr/0001-use-gpl3-as-license.md/index.html @@ -14,7 +14,7 @@ - }

    Use GNU GPL as license

    Everything needs to be licensed, otherwise the default copyright laws apply. + }

    Use GNU GPL as license

    Everything needs to be licensed, otherwise the default copyright laws apply. For instance, in Germany that means users may not alter anything without explicitly asking for permission. For more information see https://help.github.com/articles/licensing-a-repository/.

    We want to have all source code related to Project Thoth to be used without any hassle and as free as possible, so that users can just execute and enjoy the four freedoms.

    Considered Options

    Decision Outcome

    Chosen option: “GNU GPL”, because this license supports a strong copyleft model.

    \ No newline at end of file diff --git a/community/core/docs/adr/0002-release-policy.md/index.html b/community/core/docs/adr/0002-release-policy.md/index.html index dd9c58b777..641506c87b 100644 --- a/community/core/docs/adr/0002-release-policy.md/index.html +++ b/community/core/docs/adr/0002-release-policy.md/index.html @@ -14,7 +14,7 @@ - }

    Project Thoth Release Policy

    • Status: proposed
    • Date: 2020-Nov-04

    Technical Story: As an Open Source project, we want to document the policies and guideline on how we create a new + }

    Project Thoth Release Policy

    • Status: proposed
    • Date: 2020-Nov-04

    Technical Story: As an Open Source project, we want to document the policies and guideline on how we create a new release.

    Context and Problem Statement

    Project Thoth itself consists of many components all having their own release cycles and delivery artifacts such as container image or Python libraries.

    Considered Options

    • a monolithic, coordinated release of all components by creating a tag within the thoth-application repository
    • have a rolling release, and no tags on any repository

    Decision Outcome

    Chosen option: we do a monolithic, coordinated release, because it will enable us to have a release at the project/product level while maintianing freedom of others to update.

    Positive Consequences

    \ No newline at end of file diff --git a/community/core/docs/intern-projects/generate-prescription-from-text.md/index.html b/community/core/docs/intern-projects/generate-prescription-from-text.md/index.html index 600c9458f6..5793c64f2d 100644 --- a/community/core/docs/intern-projects/generate-prescription-from-text.md/index.html +++ b/community/core/docs/intern-projects/generate-prescription-from-text.md/index.html @@ -14,5 +14,5 @@ - }

    Generate prescriptions from text (text2prescription)

    Assigned intern: ?? -Assigned mentor: ??

    Project Goal

    The goal of this research project is to create text2prescription model that can be used in a bot for generating prescriptions to heal Python Projects from text inputs.

    Deliverables

    A Jupyter Notebook, later an CLI application, that can automatically generate prescriptions from text input.

    Prerequisites for Team Members

    Please check you have all the following:

    • Access to Operate First
    • Access to GMail and Google Chat
      • Be part of Thoth-Station Google Chat Room
    • Be part of Thoth scrum meetings
      • You should receive an invite to a Google calendar Event
    • Access to GitHub using your GitHub your account
      • Thoth Station
    • Get access to JupyterHub

    Project outline

    1. Welcome to the Thoth Station! [1]
      1. get familiar with team members
    2. Get familiar with adviser [2], study how it works [3].
    3. Get familiar with prescriptions [4][5], study how they are created [6].
    4. Research methods for mapping text to templates (e.g. prescription).
    5. Create NLP pipeline to analyze Text inputs (using Elyra [7] and Kubeflow Pipelines[8] available on Operate First).
    6. Create NLP model for entity recognition from text specific to prescriptions. (e.g. Python package, runtime environment, hardware).
    7. Create a Jupyter Notebook that accepts text and produce prescription (.yaml format).
      1. Discuss NLP pipeline steps.
      2. Discuss NLP model for entity recognition specific to prescriptions.
    8. Discuss applicability and use of this new approach (e.g. bot supporting users that want to create a prescription for Python application)

    Stretch goals:

    • Create a bot that can receive text from an issue as input and create a pull request with prescriptions

    References

    1. https://thoth-station.ninja/
    2. https://github.com/thoth-station/adviser
    3. https://developers.redhat.com/articles/2021/09/22/thoth-prescriptions-resolving-python-dependencies#
    4. https://github.com/thoth-station/prescriptions
    5. https://thoth-station.ninja/docs/developers/adviser/index.html#pipeline-units
    6. https://www.youtube.com/watch?v=OCX8JQDXP9s
    7. https://github.com/elyra-ai/elyra
    8. https://www.kubeflow.org/docs/components/pipelines/overview/pipelines-overview/
    \ No newline at end of file + }

    Generate prescriptions from text (text2prescription)

    Assigned intern: ?? +Assigned mentor: ??

    Project Goal

    The goal of this research project is to create text2prescription model that can be used in a bot for generating prescriptions to heal Python Projects from text inputs.

    Deliverables

    A Jupyter Notebook, later an CLI application, that can automatically generate prescriptions from text input.

    Prerequisites for Team Members

    Please check you have all the following:

    • Access to Operate First
    • Access to GMail and Google Chat
      • Be part of Thoth-Station Google Chat Room
    • Be part of Thoth scrum meetings
      • You should receive an invite to a Google calendar Event
    • Access to GitHub using your GitHub your account
      • Thoth Station
    • Get access to JupyterHub

    Project outline

    1. Welcome to the Thoth Station! [1]
      1. get familiar with team members
    2. Get familiar with adviser [2], study how it works [3].
    3. Get familiar with prescriptions [4][5], study how they are created [6].
    4. Research methods for mapping text to templates (e.g. prescription).
    5. Create NLP pipeline to analyze Text inputs (using Elyra [7] and Kubeflow Pipelines[8] available on Operate First).
    6. Create NLP model for entity recognition from text specific to prescriptions. (e.g. Python package, runtime environment, hardware).
    7. Create a Jupyter Notebook that accepts text and produce prescription (.yaml format).
      1. Discuss NLP pipeline steps.
      2. Discuss NLP model for entity recognition specific to prescriptions.
    8. Discuss applicability and use of this new approach (e.g. bot supporting users that want to create a prescription for Python application)

    Stretch goals:

    • Create a bot that can receive text from an issue as input and create a pull request with prescriptions

    References

    1. https://thoth-station.ninja/
    2. https://github.com/thoth-station/adviser
    3. https://developers.redhat.com/articles/2021/09/22/thoth-prescriptions-resolving-python-dependencies#
    4. https://github.com/thoth-station/prescriptions
    5. https://thoth-station.ninja/docs/developers/adviser/index.html#pipeline-units
    6. https://www.youtube.com/watch?v=OCX8JQDXP9s
    7. https://github.com/elyra-ai/elyra
    8. https://www.kubeflow.org/docs/components/pipelines/overview/pipelines-overview/
    \ No newline at end of file diff --git a/community/core/docs/intern-projects/prescriptions-bootstrap.md/index.html b/community/core/docs/intern-projects/prescriptions-bootstrap.md/index.html index 0cd95f4f82..6d7c7e3f55 100644 --- a/community/core/docs/intern-projects/prescriptions-bootstrap.md/index.html +++ b/community/core/docs/intern-projects/prescriptions-bootstrap.md/index.html @@ -14,9 +14,9 @@ - }

    Bootstrap database of Thoth prescriptions

    Assigned intern: + }

    Bootstrap database of Thoth prescriptions

    Assigned intern: Assigned mentor:

    Project Goal

    The goal of this project is to extend the current database of prescriptions with known or not yet known issues in the Python ecosystem.

    Deliverables

    Set of YAML files committed to thoth-station/prescriptions repository that help the recommender system to advise better software stacks to -users.

    Prerequisites for Team Members

    Please check you have all the following:

    • Be part of Thoth-Station Google Chat Room
    • Be part of Thoth scrum meetings
      • You should receive an invite to a Google calendar Event
    • Access to GitHub using your GitHub your account
      • Thoth Station

    Project outline

    1. Welcome to the Thoth Station!
      1. get familiar with team members
    2. Get familiar with thoth-station/prescriptions repository
    3. Get familiar with prescriptions concept, follow the online documentation for more info
    4. Identify popular Python packages that can be valuable to data scientists and Python developers
      1. Take a look at already existing hundredsDatasciencePackages list
      2. Take a look at Python packages based on their popularity (number of downloads from PyPI)
    5. For the identified set of Python packages create prescriptions that add knowledge to the recommender system so that users do not encounter known issues
      1. Follow project issues and/or project release notes
      2. Collaborate with communities to understand issues and required fixes, present prescriptions concept to communities
    6. Get familiar with Amun service and Dependency Monkey
    7. Identify possible cases that are suitable for running Dependency Monkey to spot issues in packages or runtime environments
    8. Run Dependency Monkey jobs and/or Amun inspections to conduct experiments that can result in new prescriptions
      1. Discuss possible issues with upstream communities
    9. Discuss extensibility and possible improvements that would help you to get results more effectively

    References

    1. https://github.com/thoth-station/prescriptions
    2. https://thoth-station.ninja/docs/developers/adviser/prescription.html
    3. https://thoth-station.ninja/docs/developers/adviser/dependency_monkey.html
    4. https://github.com/thoth-station/amun-api
    \ No newline at end of file +users.

    Prerequisites for Team Members

    Please check you have all the following:

    • Be part of Thoth-Station Google Chat Room
    • Be part of Thoth scrum meetings
      • You should receive an invite to a Google calendar Event
    • Access to GitHub using your GitHub your account
      • Thoth Station

    Project outline

    1. Welcome to the Thoth Station!
      1. get familiar with team members
    2. Get familiar with thoth-station/prescriptions repository
    3. Get familiar with prescriptions concept, follow the online documentation for more info
    4. Identify popular Python packages that can be valuable to data scientists and Python developers
      1. Take a look at already existing hundredsDatasciencePackages list
      2. Take a look at Python packages based on their popularity (number of downloads from PyPI)
    5. For the identified set of Python packages create prescriptions that add knowledge to the recommender system so that users do not encounter known issues
      1. Follow project issues and/or project release notes
      2. Collaborate with communities to understand issues and required fixes, present prescriptions concept to communities
    6. Get familiar with Amun service and Dependency Monkey
    7. Identify possible cases that are suitable for running Dependency Monkey to spot issues in packages or runtime environments
    8. Run Dependency Monkey jobs and/or Amun inspections to conduct experiments that can result in new prescriptions
      1. Discuss possible issues with upstream communities
    9. Discuss extensibility and possible improvements that would help you to get results more effectively

    References

    1. https://github.com/thoth-station/prescriptions
    2. https://thoth-station.ninja/docs/developers/adviser/prescription.html
    3. https://thoth-station.ninja/docs/developers/adviser/dependency_monkey.html
    4. https://github.com/thoth-station/amun-api
    \ No newline at end of file diff --git a/community/core/docs/sprint-demos/35.md/index.html b/community/core/docs/sprint-demos/35.md/index.html index e2c2dffc80..1d4e9029ed 100644 --- a/community/core/docs/sprint-demos/35.md/index.html +++ b/community/core/docs/sprint-demos/35.md/index.html @@ -14,4 +14,4 @@ - }

    Sprint 35 - 2020-Apr-14

    Topic: ArgoCD (goern)

    Cards:

    Started working on ArgoCD and created a few Applications to play around with: https://github.com/thoth-station/thoth-application is the core application, branches in this repo reflect deployment environments (right now all are on Quicklab). Separate Applications for example for solver, as they need to go to more than one namespace. ArgoCD uses kustomize to create manifests from the git repositories and keeps an OpenShift project in sync.

    Topic: Tekton based Thoth-CI (hnalla)

    Cards:

    The work on the Thoth-CI is present in: https://github.com/thoth-station/thoth-ci.git

    Thoth-CI focuses on test checks and image creation on PR to test them. Pull Request is the main focus right now, on each PR as the pipeline is triggered to serve it. The instance of the Thoth-CI is running on Quicklab cluster. Use Thoth-CI: Attach the Webhook to Github repo: http://thoth-ci.aicoe.ultrahook.com/

    Topic: Handling unsolved python packages (fmurdaca)

    Cards:

    Acting on unresolved package_version by analysing advisor results using a new component https://github.com/thoth-station/advise-reporter. And modifying the architecture of the Qeb-Hwt App (https://github.com/thoth-station/Qeb-Hwt).

    Topic: Optimizing Thoth’s adviser (fpokorny)

    Cards:

    Optimizations of the adviser’s internal structure to derive recommendations faster or bring better recommendations. We switched from the standard heap queue implementation that is provided by the standard Python library to a custom library called “fext” that is implementat as an C/C++ extension to CPython. This library is optimized for Thoth’s adviser use case when handling internal resolver states.

    Topic: Repository Health Report (Proof of concept) (dominik)

    Visualized Repository Health Report in form of a dashboard (using Dash). Any user that wants to see the current status of (his/her) repository, could run SrcOpsMetrics analysis locally and launch a dashboard for a quick status preview of the project.

    Cards:

    \ No newline at end of file + }

    Sprint 35 - 2020-Apr-14

    Topic: ArgoCD (goern)

    Cards:

    Started working on ArgoCD and created a few Applications to play around with: https://github.com/thoth-station/thoth-application is the core application, branches in this repo reflect deployment environments (right now all are on Quicklab). Separate Applications for example for solver, as they need to go to more than one namespace. ArgoCD uses kustomize to create manifests from the git repositories and keeps an OpenShift project in sync.

    Topic: Tekton based Thoth-CI (hnalla)

    Cards:

    The work on the Thoth-CI is present in: https://github.com/thoth-station/thoth-ci.git

    Thoth-CI focuses on test checks and image creation on PR to test them. Pull Request is the main focus right now, on each PR as the pipeline is triggered to serve it. The instance of the Thoth-CI is running on Quicklab cluster. Use Thoth-CI: Attach the Webhook to Github repo: http://thoth-ci.aicoe.ultrahook.com/

    Topic: Handling unsolved python packages (fmurdaca)

    Cards:

    Acting on unresolved package_version by analysing advisor results using a new component https://github.com/thoth-station/advise-reporter. And modifying the architecture of the Qeb-Hwt App (https://github.com/thoth-station/Qeb-Hwt).

    Topic: Optimizing Thoth’s adviser (fpokorny)

    Cards:

    Optimizations of the adviser’s internal structure to derive recommendations faster or bring better recommendations. We switched from the standard heap queue implementation that is provided by the standard Python library to a custom library called “fext” that is implementat as an C/C++ extension to CPython. This library is optimized for Thoth’s adviser use case when handling internal resolver states.

    Topic: Repository Health Report (Proof of concept) (dominik)

    Visualized Repository Health Report in form of a dashboard (using Dash). Any user that wants to see the current status of (his/her) repository, could run SrcOpsMetrics analysis locally and launch a dashboard for a quick status preview of the project.

    Cards:

    \ No newline at end of file diff --git a/community/core/docs/sprint-demos/37.md/index.html b/community/core/docs/sprint-demos/37.md/index.html index 79e31ee08d..3ae742fe6b 100644 --- a/community/core/docs/sprint-demos/37.md/index.html +++ b/community/core/docs/sprint-demos/37.md/index.html @@ -14,5 +14,5 @@ - }

    Sprint 37 - 2020-May-08

    Topic: ArgoCD: Thoth-application (goern)

    See https://argocd-server-aicoe-argocd.apps.ocp.prod.psi.redhat.com/applications for all the thoth application components deployed to thoth01 (quicklab==test) cluster. Using sops/ksops to encrypt and decrypt secrets.

    Topic: Publish s2i migration tool (frido)

    Cards:

    Topic: Updates on Thoth-CI (hnalla)

    New Feature

    Tag based release of image of the application slash-command to interact with the thoth-ci. + }

    Sprint 37 - 2020-May-08

    Topic: ArgoCD: Thoth-application (goern)

    See https://argocd-server-aicoe-argocd.apps.ocp.prod.psi.redhat.com/applications for all the thoth application components deployed to thoth01 (quicklab==test) cluster. Using sops/ksops to encrypt and decrypt secrets.

    Topic: Publish s2i migration tool (frido)

    Cards:

    Topic: Updates on Thoth-CI (hnalla)

    New Feature

    Tag based release of image of the application slash-command to interact with the thoth-ci. /approve : To merge a pr on merge.

    CI focuses on test checks and image creation on PR to test them. Pull Request is the main focus right now, on each PR as the pipeline is triggered to serve it. The instance of the Thoth-CI is running on Quicklab cluster. Developers can interact with the CI for ease of operations.

    Use Thoth-CI: Attach the Webhook to Github repo: http://thoth-ci.aicoe.ultrahook.com

    Topic: Bandit Security Benchmark (kpostlet)

    \ No newline at end of file diff --git a/community/core/docs/sprint-demos/38.md/index.html b/community/core/docs/sprint-demos/38.md/index.html index 4242b5daa5..56cc7e960d 100644 --- a/community/core/docs/sprint-demos/38.md/index.html +++ b/community/core/docs/sprint-demos/38.md/index.html @@ -14,4 +14,4 @@ - }

    Sprint 38 - 2020-May-22

    Topic: Bandit Security Benchmark (kpostlet)

    Find us on YouTube: https://bit.ly/thoth-sprint-38

    Topic: SLO reporter (fmurdaca)

    Service Level Objective (SLO) reporter and the mails it’s sending out. Data is read form thanos (hosted by internal Data Hub), mail is send out each Friday night.

    Cards:

    Topic: End-to-end demo of Thoth’s Jupyter Notebook build pipeline for custom and internal repositories (hnalla)

    OpenShift-pipelines/TektonCD-pipeline based a build pipeline which on tag release of a github/gitlab repository containing the jupyter notebook, builds an image based on requirements of the jupyter notebook, for them to be comfortable import into jupyterhub. S2i build process is used for build procedure.

    Cards:

    \ No newline at end of file + }

    Sprint 38 - 2020-May-22

    Topic: Bandit Security Benchmark (kpostlet)

    Find us on YouTube: https://bit.ly/thoth-sprint-38

    Topic: SLO reporter (fmurdaca)

    Service Level Objective (SLO) reporter and the mails it’s sending out. Data is read form thanos (hosted by internal Data Hub), mail is send out each Friday night.

    Cards:

    Topic: End-to-end demo of Thoth’s Jupyter Notebook build pipeline for custom and internal repositories (hnalla)

    OpenShift-pipelines/TektonCD-pipeline based a build pipeline which on tag release of a github/gitlab repository containing the jupyter notebook, builds an image based on requirements of the jupyter notebook, for them to be comfortable import into jupyterhub. S2i build process is used for build procedure.

    Cards:

    \ No newline at end of file diff --git a/community/core/docs/sprint-demos/39.md/index.html b/community/core/docs/sprint-demos/39.md/index.html index bd740bd2ab..43073ab44c 100644 --- a/community/core/docs/sprint-demos/39.md/index.html +++ b/community/core/docs/sprint-demos/39.md/index.html @@ -14,4 +14,4 @@ - }

    Sprint 39 - 2020-Jun-05

    Find us on YouTube: http://bit.ly/thoth-on-youtube

    Topic: How does the SrcOpsMetrics gather data? (dtuchyna)

    The SrcOpsMetrics is currently able to gather the fundamental information about GitHub repository in order to calculate or visualize its Health Report. But how do we approach the data aggregation for multiple repositories present in organization that is inspected?

    Cards or Issues:

    Topic: Thoth Datasets (fmurdaca)

    Thoth datasets are related to observations regarding software stacks (e.g. dependency tree, installability, performance, security, health) as part of Project Thoth. All these datasets can be found also here where they are described and explored to facilitate their use. All these observations are created with different components which are part of Project Thoth and stored in Thoth Knowledge Graph. All this knowledge is used by Thoth Adviser to provide advices on software stacks depending on User requirements.

    Cards or Issues:

    References:

    \ No newline at end of file + }

    Sprint 39 - 2020-Jun-05

    Find us on YouTube: http://bit.ly/thoth-on-youtube

    Topic: How does the SrcOpsMetrics gather data? (dtuchyna)

    The SrcOpsMetrics is currently able to gather the fundamental information about GitHub repository in order to calculate or visualize its Health Report. But how do we approach the data aggregation for multiple repositories present in organization that is inspected?

    Cards or Issues:

    Topic: Thoth Datasets (fmurdaca)

    Thoth datasets are related to observations regarding software stacks (e.g. dependency tree, installability, performance, security, health) as part of Project Thoth. All these datasets can be found also here where they are described and explored to facilitate their use. All these observations are created with different components which are part of Project Thoth and stored in Thoth Knowledge Graph. All this knowledge is used by Thoth Adviser to provide advices on software stacks depending on User requirements.

    Cards or Issues:

    References:

    \ No newline at end of file diff --git a/community/core/docs/sprint-demos/README.md/index.html b/community/core/docs/sprint-demos/README.md/index.html index 57436b99c5..25e38d0308 100644 --- a/community/core/docs/sprint-demos/README.md/index.html +++ b/community/core/docs/sprint-demos/README.md/index.html @@ -14,7 +14,7 @@ - }

    Thoth-Station Sprint Demos

    This directory contains show notes for the Thoth-Station sprint demo session. Right now, our sprints are two weeks + }

    \ No newline at end of file diff --git a/community/index.html b/community/index.html index 3cec6a4e8e..82f0a6e9c6 100644 --- a/community/index.html +++ b/community/index.html @@ -14,7 +14,7 @@ - }

    Terms and Conditions for the Thoth Station Scrum

    Thoth Station Inhabitants, v0.4.0, 2022-05-04

    A scrum sprint (or iteration) is 3 weeks of calendar time, and a task should/can not span more than one sprint. + }

    Terms and Conditions for the Thoth Station Scrum

    Thoth Station Inhabitants, v0.4.0, 2022-05-04

    A scrum sprint (or iteration) is 3 weeks of calendar time, and a task should/can not span more than one sprint. If a task can not be accomplished in one sprint it must be broken up.

    Tasks are tracked as GitHub issues. Issues are created by anyone in the community, including the team and the users of the Thoth service.

    Issues are assigned to persons (they become an assignee of the issue) when a person picks up the card and starts working on it (pulls it into the ‘in diff --git a/index.html b/index.html index d95af05658..72710f8a15 100644 --- a/index.html +++ b/index.html @@ -14,7 +14,7 @@ - }

    + }

    @@ -25,4 +25,4 @@ YouTube channel | Twitter | Talks and articles | -Datasets

    Contact Us

    If you do not find required information or get in touch, feel free to contact us in Google Chat room. If you are an external contributor, feel free to request access in thoth-station/support repository by opening an issue.

    Community Meetings & Event Calendar

    Follow instructions in the thoth-station/core repository to find interesting sessions we do.

    Special Interest Groups

    The whole team is formed into “Special Interest Groups” (SIG). More info can be found in the thoth-station/core repository.

    \ No newline at end of file +Datasets

    Contact Us

    If you do not find required information or get in touch, feel free to contact us in Google Chat room. If you are an external contributor, feel free to request access in thoth-station/support repository by opening an issue.

    Community Meetings & Event Calendar

    Follow instructions in the thoth-station/core repository to find interesting sessions we do.

    Special Interest Groups

    The whole team is formed into “Special Interest Groups” (SIG). More info can be found in the thoth-station/core repository.

    \ No newline at end of file diff --git a/metrics/index.html b/metrics/index.html index 3d7e631033..e72e3874e2 100644 --- a/metrics/index.html +++ b/metrics/index.html @@ -14,4 +14,4 @@ - } \ No newline at end of file + } \ No newline at end of file diff --git a/metrics/issue_metrics.md/index.html b/metrics/issue_metrics.md/index.html index 4060632da1..f2381fb0db 100644 --- a/metrics/issue_metrics.md/index.html +++ b/metrics/issue_metrics.md/index.html @@ -14,4 +14,4 @@ - } \ No newline at end of file + } \ No newline at end of file diff --git a/metrics/site_metrics.md/index.html b/metrics/site_metrics.md/index.html index bace9913c9..4a6bff840b 100644 --- a/metrics/site_metrics.md/index.html +++ b/metrics/site_metrics.md/index.html @@ -14,4 +14,4 @@ - } \ No newline at end of file + } \ No newline at end of file diff --git a/page-data/sq/d/1276261476.json b/page-data/sq/d/1276261476.json index 84ddc754fc..8b7151798f 100644 --- a/page-data/sq/d/1276261476.json +++ b/page-data/sq/d/1276261476.json @@ -1 +1 @@ -{"data":{"navData":{"navItems":[{"id":"3Ea0uNisKY4wQJ5MG9dVk","label":"Terms and Conditions","href":"/community/core/docs/TermsAndConditionsForTheScrum.md","index":"/community","links":null},{"id":"WjnaFU7cA8-2pJLdyfRh6","label":"Blueprints","href":null,"index":null,"links":[{"id":"0fzy-ZGIfXdp43lK3sJXC","label":"Thoth Roadmap","remote":null,"href":"/community/core/docs/ROADMAP.md"},{"id":"3PHysh4NdQc7DLFbFFpmP","label":"Help Wanted Labels","remote":null,"href":"/community/core/community/help-wanted.md"}]},{"id":"ROxR7ju0aZp5SHPn5Ovm8","label":"Special Interest Groups","href":null,"index":null,"links":[{"id":"ljwPRqOgK6UZFSiTS6b9S","label":"Governance","remote":null,"href":"/community/core/community/governance.md"},{"id":"V_C-PKM0KYAOC-npgtlY7","label":"SIG DevSecOps","remote":null,"href":"/community/core/community/sig-devsecops/README.md"},{"id":"u-XqbVy4FPb_Vl48upE-R","label":"SIG Observability","remote":null,"href":"/community/core/community/sig-observability/README.md"},{"id":"yVVLgvVPsV1ZZN8sbd5Id","label":"SIG Stack Guidance","remote":null,"href":"/community/core/community/sig-stack-guidance/README.md"},{"id":"j4w692i3LPvG8H6KZsXqM","label":"SIG User Experience","remote":null,"href":"/community/core/community/sig-user-experience/README.md"}]},{"id":"Dp8rdc9JY-WOFOThCnMzB","label":"Architecture Decision Records","href":null,"index":null,"links":[{"id":"aeCl1GThxnrHG09tjD_HY","label":"0000 Architectural Decision","remote":null,"href":"/community/core/docs/adr/0000-use-markdown-architectural-decision-records.md"},{"id":"YjlAO_l-4YnRzNub2XraS","label":"0001 License","remote":null,"href":"/community/core/docs/adr/0001-use-gpl3-as-license.md"},{"id":"v6C8dvIxB_-6FSsd9D0En","label":"0002 Release Policy","remote":null,"href":"/community/core/docs/adr/0002-release-policy.md"},{"id":"_YGHmrTjKSULlseqaCKPm","label":"0003 Decommission qeb-hwt","remote":null,"href":"/community/core/docs/adr/0003-decommision-qeb-hwt.md"},{"id":"xzIR4R3uyStvh1TkIOMPK","label":"0004 Image Naming Convention","remote":null,"href":"/community/core/docs/adr/0004-naming-convention-images.md"},{"id":"bQcAyNRXdus7Y6JMPcTrR","label":"0005 Bump Versions","remote":null,"href":"/community/core/docs/adr/0005-automatically-bump-container-image-versions.md"}]},{"id":"Y1GtRQr7msXe_00aLwMqr","label":"Getting Support","href":"/support","index":null,"links":null},{"id":"QtZL5ndJELpbk54SpwtEY","label":"FAQ","href":null,"index":null,"links":[{"id":"roCRWU_VWbr5GjHVzdKKe","label":"Overview","remote":null,"href":"/support/faq/overview.mdx"},{"id":"ewU30eqrUU6oyotcALW5r","label":"Default .thoth.yaml","remote":null,"href":"/support/faq/thoth_yaml.mdx"}]},{"id":"rCKZFJey0d9adBx4XjoM8","label":"Track your issue","href":"/support/issue_tracker.mdx","index":null,"links":null},{"id":"oCRCOk9UUFA3HvCnNb84D","label":"Thoth Service Status","href":"/metrics","index":null,"links":null},{"id":"2O_qm8PJ922EAMlUvNj7s","label":"GitHub Support","href":"/metrics/issue_metrics.md","index":null,"links":null},{"id":"0su8Dn34Z3Ab94sfg5mhW","label":"Website Usage","href":"/metrics/site_metrics.md","index":null,"links":null}]}}} \ No newline at end of file +{"data":{"navData":{"navItems":[{"id":"GijvOD8zSDXy1D-JEYNB7","label":"Terms and Conditions","href":"/community/core/docs/TermsAndConditionsForTheScrum.md","index":"/community","links":null},{"id":"b3KX2-a-NBwLkh1FsATdx","label":"Blueprints","href":null,"index":null,"links":[{"id":"0-kwv5RLffs4AniT-0xCN","label":"Thoth Roadmap","remote":null,"href":"/community/core/docs/ROADMAP.md"},{"id":"4OUO4N1YNvtlOxvK-vLrz","label":"Help Wanted Labels","remote":null,"href":"/community/core/community/help-wanted.md"}]},{"id":"CFxQyRfr1t3o0CA0OZsQM","label":"Special Interest Groups","href":null,"index":null,"links":[{"id":"3p_AxC2j0yvnsynOxroH-","label":"Governance","remote":null,"href":"/community/core/community/governance.md"},{"id":"Y4F7txHixsWLVQv_Ru1lx","label":"SIG DevSecOps","remote":null,"href":"/community/core/community/sig-devsecops/README.md"},{"id":"4AjjbF7MUh2e2aCAKEe9W","label":"SIG Observability","remote":null,"href":"/community/core/community/sig-observability/README.md"},{"id":"FSdDHeIxN2mMjf6NRRQa0","label":"SIG Stack Guidance","remote":null,"href":"/community/core/community/sig-stack-guidance/README.md"},{"id":"mKkbXfrdVR0xkgbrU79-p","label":"SIG User Experience","remote":null,"href":"/community/core/community/sig-user-experience/README.md"}]},{"id":"gQOXTW8HVNUavM-zLI172","label":"Architecture Decision Records","href":null,"index":null,"links":[{"id":"L_t9xv0ZvV2TSMgu-YqLv","label":"0000 Architectural Decision","remote":null,"href":"/community/core/docs/adr/0000-use-markdown-architectural-decision-records.md"},{"id":"mF-9NZV8b6M45irpF_I-V","label":"0001 License","remote":null,"href":"/community/core/docs/adr/0001-use-gpl3-as-license.md"},{"id":"ThIiCWww7gKWyAHNjhc2a","label":"0002 Release Policy","remote":null,"href":"/community/core/docs/adr/0002-release-policy.md"},{"id":"u2tydanJTSbf0mZbhNNVe","label":"0003 Decommission qeb-hwt","remote":null,"href":"/community/core/docs/adr/0003-decommision-qeb-hwt.md"},{"id":"UD-E3L31ErF-XkpVTxEH9","label":"0004 Image Naming Convention","remote":null,"href":"/community/core/docs/adr/0004-naming-convention-images.md"},{"id":"w5pTD_K-r6Jdkrz2XDaD5","label":"0005 Bump Versions","remote":null,"href":"/community/core/docs/adr/0005-automatically-bump-container-image-versions.md"}]},{"id":"NAxea25j3Dcm3tgrSIVZc","label":"Getting Support","href":"/support","index":null,"links":null},{"id":"ae8YwS_mVWEQ2MjMbUtxy","label":"FAQ","href":null,"index":null,"links":[{"id":"qkEkpOSJwTbOgxK0QgQzk","label":"Overview","remote":null,"href":"/support/faq/overview.mdx"},{"id":"MpCtFXUAHfzSsSKfQKNsp","label":"Default .thoth.yaml","remote":null,"href":"/support/faq/thoth_yaml.mdx"}]},{"id":"y9jovbuOn7krpt8fb2Q4U","label":"Track your issue","href":"/support/issue_tracker.mdx","index":null,"links":null},{"id":"sAi2ZqnUeYSGhVopme-pe","label":"Thoth Service Status","href":"/metrics","index":null,"links":null},{"id":"cvrluA07MYIzyboYmMMov","label":"GitHub Support","href":"/metrics/issue_metrics.md","index":null,"links":null},{"id":"DqOoynFgqJN_104MOtlxm","label":"Website Usage","href":"/metrics/site_metrics.md","index":null,"links":null}]}}} \ No newline at end of file diff --git a/support/faq/overview.mdx/index.html b/support/faq/overview.mdx/index.html index f32f7b1659..ec14912c16 100644 --- a/support/faq/overview.mdx/index.html +++ b/support/faq/overview.mdx/index.html @@ -14,7 +14,7 @@ - }

    How do I use Thoth?

    Depending on your use case, you can interact with Thoth through a variety of integration points.

    Thamos CLI

    Thamos is a command line tool and library for communicating with the Thoth backend. More information on how to + }

    How do I use Thoth?

    Depending on your use case, you can interact with Thoth through a variety of integration points.

    Thamos CLI

    Thamos is a command line tool and library for communicating with the Thoth backend. More information on how to install and get started with it can be found in our tutorial space.

    Kebechet

    Kebechet is an extensible system of repository managers for GitHub, GitLab, and Pagure. You can use this bot integrate the functionality of Thoth into your repositories. More information on Kebechet can be found here.

    Jupyterlab Extension

    If you use Jupyterlab for development, this extension allows you to integrate Thoth’s adviser into your notebook’s environment.

    Thoth User API

    You can directly interact with the Thoth User API too.


    What are Kebechet managers and how do I configure them?

    Managers can be seen as separate bots all part of Kebechet. You can enable and configure each available bot by adding it diff --git a/support/faq/thoth_yaml.mdx/index.html b/support/faq/thoth_yaml.mdx/index.html index 1c462d6c57..e9689a61ff 100644 --- a/support/faq/thoth_yaml.mdx/index.html +++ b/support/faq/thoth_yaml.mdx/index.html @@ -14,7 +14,7 @@ - }

    # This is Thoth's configuration file placed in a root of a repo
    # (named as .thoth.yaml) used by Thamos CLI as well as by Thoth bots. Please
    # adjust values listed below as desired.
    + }

    # This is Thoth's configuration file placed in a root of a repo
    # (named as .thoth.yaml) used by Thamos CLI as well as by Thoth bots. Please
    # adjust values listed below as desired.
    # A remote Thoth service to talk to:
    host: khemenu.thoth-station.ninja
    # Configure TLS verification for communication with remote Thoth instance:
    tls_verify: true
    # Format of requirements file, supported are "pip" and "pipenv":
    requirements_format: {requirements_format}
    # A path to overlays directory relative to this configuration file. If null provided, no overlays are used.
    # Read more about overlays in the README: https://github.com/thoth-station/thamos#overlays-directory
    overlays_dir: null
    # Allow or disable managing virtual environment for each overlay.
    virtualenv: false
    diff --git a/support/index.html b/support/index.html index c3a07eed92..c3f4cdff3e 100644 --- a/support/index.html +++ b/support/index.html @@ -14,7 +14,7 @@ - }

    Getting Support

    Channels of support

    GitHub Issues

    The primary channel for getting support is by creating a GitHub issue through our support repository. + }

    Getting Support

    Channels of support

    GitHub Issues

    The primary channel for getting support is by creating a GitHub issue through our support repository. Choose between any of the issue templates or create a blank issue if no template fits your situation. Once created, your issue will be delegated out to one of Thoth’s Special Interest Groups (SIG) or a specific person on the Thoth team. They will help you get the issue ready to be worked on by refining the issue to diff --git a/support/issue_tracker.mdx/index.html b/support/issue_tracker.mdx/index.html index 1e81ecf343..233fa2029a 100644 --- a/support/issue_tracker.mdx/index.html +++ b/support/issue_tracker.mdx/index.html @@ -14,4 +14,4 @@ - }

    \ No newline at end of file + } \ No newline at end of file