training-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Francke (JIRA)" <>
Subject [jira] [Commented] (TRAINING-6) Get the top-level repo structure agreed and committed
Date Wed, 24 Apr 2019 10:43:00 GMT


Lars Francke commented on TRAINING-6:

I disagree. Because it's easy for other files to get out of sync I'd rather keep the information
where it can't be lost/will be removed automatically. I also don't think it's bad to have
vendor names in there. We have connectors to Amazon and Microsoft etc. in various projects
where we also have the company names and I don't see that as an endorsement either.

I don't have a super strong opinion though.

And: It's not something we need to decide on now.

> Get the top-level repo structure agreed and committed
> -----------------------------------------------------
>                 Key: TRAINING-6
>                 URL:
>             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|[]]
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

View raw message