[
https://issues.apache.org/jira/browse/TRAINING-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16824223#comment-16824223
]
Sönke Liebau commented on TRAINING-6:
-------------------------------------
Hi Justin,
regarding where things go, my understanding is that _staging_ is purely for
donated content and content will live there until it has been converted, tagged
with metadata, inventoried, .... at which point it will move over to the _core_
directory.
Regarding the names I agree with you, we should probably not have those -
though we might need to consider if and how we want to honor contributions in
some way.
That being said, with this pull request I just want to get the top level
structure committed, anything below that we can discuss in individual issues to
avoid slowing down separate workstreams.
> 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: 10m
> 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)
