training-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Mclean (JIRA)" <>
Subject [jira] [Commented] (TRAINING-6) Get the top-level repo structure agreed and committed
Date Wed, 17 Apr 2019 22:04:01 GMT


Justin Mclean commented on TRAINING-6:

So looking at the structure:
- it's unclear why (or who chooses even) things go in core or staging
- Having companies or people names in directories should IMO be frowned upon. We don't put
@author tags in code for good reasons that also apply here. i.e any implication of ownership
decreases the chance that others contibute.


> 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