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] [Commented] (TRAINING-6) Get the top-level repo structure agreed and committed
Date Tue, 23 Apr 2019 16:06:00 GMT

    [ https://issues.apache.org/jira/browse/TRAINING-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16824286#comment-16824286
] 

Lars Francke commented on TRAINING-6:
-------------------------------------

I agree with the @author tags but for the _staging_ stuff my intention was to somehow distinguish
similar contributions while they are being staged.

This actually has a precedent in my opinion where code is donated that lives in company specific
packages (e.g. com.cloudera). I added this because we have multiple "Apache Way" presentations
announced and it'd be better (imho) to have them tagged somehow (apacheway-foo, apacheway-bar).
Once we've migrated/cleared/merged them, this can go away.

On top of that: The whole structure is just an idea. If we adopt it we should definitely document
it.

> 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)

Mime
View raw message