Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 0.1.0, 0.2.0
    • Fix Version/s: backlog
    • Component/s: general
    • Labels:
      None

      Description

      Bigtop has a lot of redundancy in the way it names its directories:
      $ ls trunk/
      bigtop-deploy bigtop-packages bigtop-test-framework CHANGES.txt DEVNOTES docs Makefile package.mk README test
      bigtop.mk bigtop-repos bigtop-tests check-env.sh DISCLAIMER LICENSE NOTICE pom.xml src

      It would be nice to remove the prefix "bigtop-" in all these directories

        Activity

        Hide
        abayer Andrew Bayer added a comment -

        Some cleanup is necessary in terms of nuking redundant directories - most notably the top level test dir, and possibly the top level docs dir. But I think the "bigtop-" prefix is reasonable to keep. It's become reasonably standard in open source projects to use a project prefix on directories like this - see https://github.com/apache/hadoop-common, e.g. It helps make it easy to tell what project you're in, etc.

        Show
        abayer Andrew Bayer added a comment - Some cleanup is necessary in terms of nuking redundant directories - most notably the top level test dir, and possibly the top level docs dir. But I think the "bigtop-" prefix is reasonable to keep. It's become reasonably standard in open source projects to use a project prefix on directories like this - see https://github.com/apache/hadoop-common , e.g. It helps make it easy to tell what project you're in, etc.
        Hide
        bmahe Bruno Mahé added a comment -
        • What value does that bring? So far I see more value in removing this redanduncy than keeping them
        • I see more projects not using that standard rather than using it. I would rather say Hadoop is the exception
        Show
        bmahe Bruno Mahé added a comment - What value does that bring? So far I see more value in removing this redanduncy than keeping them I see more projects not using that standard rather than using it. I would rather say Hadoop is the exception
        Hide
        plinnell Peter Linnell added a comment -

        +1 for nuking bigtop from the toplevel naming. Its painful working on packaging. Tab completion is difficult. Thank god for mc to move around the tree quickly.

        Show
        plinnell Peter Linnell added a comment - +1 for nuking bigtop from the toplevel naming. Its painful working on packaging. Tab completion is difficult. Thank god for mc to move around the tree quickly.
        Hide
        cos Konstantin Boudnik added a comment -

        Still seems like a good idea? Anyone?

        Show
        cos Konstantin Boudnik added a comment - Still seems like a good idea? Anyone?
        Hide
        oflebbe Olaf Flebbe added a comment -

        +1 for cleaning up namespace on top level.

        However its seems a big task to do this change in only one commit, since I think almost nobody is fluent in all the different aspects of bigtop involved.

        I would prepose to postpone it to 1.1.0 and doing it gradually. (Adding subtasks)

        Show
        oflebbe Olaf Flebbe added a comment - +1 for cleaning up namespace on top level. However its seems a big task to do this change in only one commit, since I think almost nobody is fluent in all the different aspects of bigtop involved. I would prepose to postpone it to 1.1.0 and doing it gradually. (Adding subtasks)
        Hide
        cos Konstantin Boudnik added a comment -

        Absolutely. Moving to 1.1.0

        Show
        cos Konstantin Boudnik added a comment - Absolutely. Moving to 1.1.0

          People

          • Assignee:
            Unassigned
            Reporter:
            bmahe Bruno Mahé
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:

              Development