From issues-return-45-archive-asf-public=cust-asf.ponee.io@training.apache.org Tue Apr 23 15:13:02 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 33FB3180621 for ; Tue, 23 Apr 2019 17:13:02 +0200 (CEST) Received: (qmail 28310 invoked by uid 500); 23 Apr 2019 15:13:01 -0000 Mailing-List: contact issues-help@training.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@training.apache.org Delivered-To: mailing list issues@training.apache.org Received: (qmail 28289 invoked by uid 99); 23 Apr 2019 15:13:01 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Apr 2019 15:13:01 +0000 Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 1E716E28B7 for ; Tue, 23 Apr 2019 15:13:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 80B4325813 for ; Tue, 23 Apr 2019 15:13:00 +0000 (UTC) Date: Tue, 23 Apr 2019 15:13:00 +0000 (UTC) From: =?utf-8?Q?S=C3=B6nke_Liebau_=28JIRA=29?= To: issues@training.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (TRAINING-6) Get the top-level repo structure agreed and committed MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/TRAINING-6?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1682= 4223#comment-16824223 ]=20 S=C3=B6nke 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, t= agged 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 - t= hough we might need to consider if and how we want to honor contributions i= n some way. That being said, with this pull request I just want to get the top level st= ructure 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=C3=B6nke Liebau > Assignee: S=C3=B6nke 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-p= layground]] available which contains a proposal of how this might look. > =C2=A0 > This ticket is explicitly only for the top-level structure, any more deta= illed discussions should then be had by the relevant subset of people I bel= ieve. But we need this to be able to kick of some real work. > =C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)