training-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sönke Liebau (JIRA) <j...@apache.org>
Subject [jira] [Created] (TRAINING-6) Get the top-level repo structure agreed and committed
Date Wed, 17 Apr 2019 13:45:00 GMT
Sönke Liebau created TRAINING-6:
-----------------------------------

             Summary: 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


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