training-issues mailing list archives

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

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

Justin Mclean commented on TRAINING-6:
--------------------------------------

Suggest you just use _A, _B, _C or _1, _2, _3 etc etc rather than who donated it. That information
is going to end up in the LICENSE or NOTICE file for the material anyway. You could also add
a CONTRIBUTORS file if people thought it was needed - personally that are a hassle to keep
updated and version control gives you the history anyway.

Re "com.cloudera" and the like I really prefer would avoid doing that as it could be taken
as some people as endowment or advertising of a commercial entity. Most often (unless there
are technical reasons not to) package names are changed to apache.org after donation in most
code.

But as far as the top level structure it looks good to me.

> 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