training-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Francke (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (TRAINING-6) Get the top-level repo structure agreed and committed
Date Thu, 16 May 2019 19:16:00 GMT

     [ https://issues.apache.org/jira/browse/TRAINING-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Lars Francke updated TRAINING-6:
--------------------------------
    Status: Patch Available  (was: Open)

(not really submitting a patch but our current Jira workflow requires going through the step
before being able to close)

> Get the top-level repo structure agreed and committed
> -----------------------------------------------------
>
>                 Key: TRAINING-6
>                 URL: https://issues.apache.org/jira/browse/TRAINING-6
>             Project: Apache Training
>          Issue Type: Task
>            Reporter: Sönke Liebau
>            Assignee: Sönke Liebau
>            Priority: Blocker
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Assuming that we want to go with a mono-repo strategy we need to agree on how to keep
the following things separated in our repository:
>  * webpage
>  * content
>  ** staging
>  ** converted, tagged and searchable
>  * compositions (courses built from content)
>  * tooling
>  * anything else that people can come up with
> There is a [playground repository|[https://github.com/opencore/training-playground]]
available which contains a proposal of how this might look.
>  
> This ticket is explicitly only for the top-level structure, any more detailled discussions
should then be had by the relevant subset of people I believe. But we need this to be able
to kick of some real work.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message