[jira] [Updated] (YETUS-6) reorganize repo layout for break from Hadoop code base

["Sean Busbey (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/YETUS-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Busbey updated YETUS-6:
----------------------------
    Attachment: YETUS-6.1.patch

-01

first pass post-yetus.

* create a top-level "docs" for project-wide (presumably will become source for website in YETUS-2)
* create top-level 'audience-annotations' for java api annotations + tooling
* create top-level 'release-doc-maker' for the so-named component
* create top-level 'shelldoc' for the so-named component
* create top-level 'test-patch' for the so-named component

not sure about:

* we refer to both "test-patch" and "Yetus Precommit" in our docs/files. pick one, possibly in follow-on
* put all the non-maven components in "%component%/src" directories. presumably they'd eventually get a "%component%/test" directory to match. Not sure if we should instead lay out like maven even if we don't use maven to build them. (e.g. release-doc-maker/src/main/python/releasedocmaker.py, test-patch/src/main/bash, ?test-patch/src/main/resources/personality?)


not addressed:

* audience annotations needs to be updated for move out of hadoop (packages, class names, pom, etc). YETUS-3
* no top level README (probably should be guide to project for contributors)
* top level LICENSE and NOTICE files need to be updated. YETUS-7

> reorganize repo layout for break from Hadoop code base
> ------------------------------------------------------
>
>                 Key: YETUS-6
>                 URL: https://issues.apache.org/jira/browse/YETUS-6
>             Project: Yetus
>          Issue Type: Task
>          Components: build
>    Affects Versions: 0.1.0
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>             Fix For: 0.1.0
>
>         Attachments: HADOOP-12361.HADOOP-12111.1.sh, YETUS-6.1.patch
>
>
> Reorganize current top level repo to include our starting modules (and only those modules), so that it's easier to start bringing in new contributors:
> * shelldoc
> * releasedocmaker
> * interface audience
> * test-patch



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)