diff --git a/.gitignore b/.gitignore deleted file mode 100644 index 075acec..0000000 --- a/.gitignore +++ /dev/null @@ -1,15 +0,0 @@ -AUTHORS -ChangeLog -build -.tox -.venv -*.egg* -*.swp -*.swo -*.pyc -.testrepository -.idea/* -*/.DS_Store -.DS_Store -.DS_Store? -*~ diff --git a/.mailmap b/.mailmap deleted file mode 100644 index 516ae6f..0000000 --- a/.mailmap +++ /dev/null @@ -1,3 +0,0 @@ -# Format is: -# -# diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst deleted file mode 100644 index 499bce8..0000000 --- a/CONTRIBUTING.rst +++ /dev/null @@ -1,25 +0,0 @@ -If you would like to contribute to the development of OpenStack, you must -follow the steps in this page: - - http://docs.openstack.org/infra/manual/developers.html - -If you already have a good understanding of how the system works and your -OpenStack accounts are set up, you can skip to the development workflow -section of this documentation to learn how changes to OpenStack should be -submitted for review via the Gerrit tool: - - http://docs.openstack.org/infra/manual/developers.html#development-workflow - -Pull requests submitted through GitHub will be ignored. - -Bugs should be filed on Launchpad, not GitHub: - - https://bugs.launchpad.net/openstack-ux - -Blueprints should also be filed on Launchpad: - - https://blueprints.launchpad.net/openstack-ux - -Design Mockups are added and reviewed through InVision: - - https://openstack.invisionapp.com diff --git a/HACKING.rst b/HACKING.rst deleted file mode 100644 index 4817339..0000000 --- a/HACKING.rst +++ /dev/null @@ -1,4 +0,0 @@ -openstack-ux Style Commandments -=============================================== - -Read the OpenStack Style Commandments http://docs.openstack.org/developer/hacking/ diff --git a/LICENSE b/LICENSE deleted file mode 100644 index 68c771a..0000000 --- a/LICENSE +++ /dev/null @@ -1,176 +0,0 @@ - - Apache License - Version 2.0, January 2004 - http://www.apache.org/licenses/ - - TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION - - 1. Definitions. - - "License" shall mean the terms and conditions for use, reproduction, - and distribution as defined by Sections 1 through 9 of this document. - - "Licensor" shall mean the copyright owner or entity authorized by - the copyright owner that is granting the License. - - "Legal Entity" shall mean the union of the acting entity and all - other entities that control, are controlled by, or are under common - control with that entity. For the purposes of this definition, - "control" means (i) the power, direct or indirect, to cause the - direction or management of such entity, whether by contract or - otherwise, or (ii) ownership of fifty percent (50%) or more of the - outstanding shares, or (iii) beneficial ownership of such entity. - - "You" (or "Your") shall mean an individual or Legal Entity - exercising permissions granted by this License. - - "Source" form shall mean the preferred form for making modifications, - including but not limited to software source code, documentation - source, and configuration files. - - "Object" form shall mean any form resulting from mechanical - transformation or translation of a Source form, including but - not limited to compiled object code, generated documentation, - and conversions to other media types. - - "Work" shall mean the work of authorship, whether in Source or - Object form, made available under the License, as indicated by a - copyright notice that is included in or attached to the work - (an example is provided in the Appendix below). - - "Derivative Works" shall mean any work, whether in Source or Object - form, that is based on (or derived from) the Work and for which the - editorial revisions, annotations, elaborations, or other modifications - represent, as a whole, an original work of authorship. For the purposes - of this License, Derivative Works shall not include works that remain - separable from, or merely link (or bind by name) to the interfaces of, - the Work and Derivative Works thereof. - - "Contribution" shall mean any work of authorship, including - the original version of the Work and any modifications or additions - to that Work or Derivative Works thereof, that is intentionally - submitted to Licensor for inclusion in the Work by the copyright owner - or by an individual or Legal Entity authorized to submit on behalf of - the copyright owner. For the purposes of this definition, "submitted" - means any form of electronic, verbal, or written communication sent - to the Licensor or its representatives, including but not limited to - communication on electronic mailing lists, source code control systems, - and issue tracking systems that are managed by, or on behalf of, the - Licensor for the purpose of discussing and improving the Work, but - excluding communication that is conspicuously marked or otherwise - designated in writing by the copyright owner as "Not a Contribution." - - "Contributor" shall mean Licensor and any individual or Legal Entity - on behalf of whom a Contribution has been received by Licensor and - subsequently incorporated within the Work. - - 2. Grant of Copyright License. Subject to the terms and conditions of - this License, each Contributor hereby grants to You a perpetual, - worldwide, non-exclusive, no-charge, royalty-free, irrevocable - copyright license to reproduce, prepare Derivative Works of, - publicly display, publicly perform, sublicense, and distribute the - Work and such Derivative Works in Source or Object form. - - 3. Grant of Patent License. Subject to the terms and conditions of - this License, each Contributor hereby grants to You a perpetual, - worldwide, non-exclusive, no-charge, royalty-free, irrevocable - (except as stated in this section) patent license to make, have made, - use, offer to sell, sell, import, and otherwise transfer the Work, - where such license applies only to those patent claims licensable - by such Contributor that are necessarily infringed by their - Contribution(s) alone or by combination of their Contribution(s) - with the Work to which such Contribution(s) was submitted. If You - institute patent litigation against any entity (including a - cross-claim or counterclaim in a lawsuit) alleging that the Work - or a Contribution incorporated within the Work constitutes direct - or contributory patent infringement, then any patent licenses - granted to You under this License for that Work shall terminate - as of the date such litigation is filed. - - 4. Redistribution. You may reproduce and distribute copies of the - Work or Derivative Works thereof in any medium, with or without - modifications, and in Source or Object form, provided that You - meet the following conditions: - - (a) You must give any other recipients of the Work or - Derivative Works a copy of this License; and - - (b) You must cause any modified files to carry prominent notices - stating that You changed the files; and - - (c) You must retain, in the Source form of any Derivative Works - that You distribute, all copyright, patent, trademark, and - attribution notices from the Source form of the Work, - excluding those notices that do not pertain to any part of - the Derivative Works; and - - (d) If the Work includes a "NOTICE" text file as part of its - distribution, then any Derivative Works that You distribute must - include a readable copy of the attribution notices contained - within such NOTICE file, excluding those notices that do not - pertain to any part of the Derivative Works, in at least one - of the following places: within a NOTICE text file distributed - as part of the Derivative Works; within the Source form or - documentation, if provided along with the Derivative Works; or, - within a display generated by the Derivative Works, if and - wherever such third-party notices normally appear. The contents - of the NOTICE file are for informational purposes only and - do not modify the License. You may add Your own attribution - notices within Derivative Works that You distribute, alongside - or as an addendum to the NOTICE text from the Work, provided - that such additional attribution notices cannot be construed - as modifying the License. - - You may add Your own copyright statement to Your modifications and - may provide additional or different license terms and conditions - for use, reproduction, or distribution of Your modifications, or - for any such Derivative Works as a whole, provided Your use, - reproduction, and distribution of the Work otherwise complies with - the conditions stated in this License. - - 5. Submission of Contributions. Unless You explicitly state otherwise, - any Contribution intentionally submitted for inclusion in the Work - by You to the Licensor shall be under the terms and conditions of - this License, without any additional terms or conditions. - Notwithstanding the above, nothing herein shall supersede or modify - the terms of any separate license agreement you may have executed - with Licensor regarding such Contributions. - - 6. Trademarks. This License does not grant permission to use the trade - names, trademarks, service marks, or product names of the Licensor, - except as required for reasonable and customary use in describing the - origin of the Work and reproducing the content of the NOTICE file. - - 7. Disclaimer of Warranty. Unless required by applicable law or - agreed to in writing, Licensor provides the Work (and each - Contributor provides its Contributions) on an "AS IS" BASIS, - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or - implied, including, without limitation, any warranties or conditions - of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A - PARTICULAR PURPOSE. You are solely responsible for determining the - appropriateness of using or redistributing the Work and assume any - risks associated with Your exercise of permissions under this License. - - 8. Limitation of Liability. In no event and under no legal theory, - whether in tort (including negligence), contract, or otherwise, - unless required by applicable law (such as deliberate and grossly - negligent acts) or agreed to in writing, shall any Contributor be - liable to You for damages, including any direct, indirect, special, - incidental, or consequential damages of any character arising as a - result of this License or out of the use or inability to use the - Work (including but not limited to damages for loss of goodwill, - work stoppage, computer failure or malfunction, or any and all - other commercial damages or losses), even if such Contributor - has been advised of the possibility of such damages. - - 9. Accepting Warranty or Additional Liability. While redistributing - the Work or Derivative Works thereof, You may choose to offer, - and charge a fee for, acceptance of support, warranty, indemnity, - or other liability obligations and/or rights consistent with this - License. However, in accepting such obligations, You may act only - on Your own behalf and on Your sole responsibility, not on behalf - of any other Contributor, and only if You agree to indemnify, - defend, and hold each Contributor harmless for any liability - incurred by, or claims asserted against, such Contributor by reason - of your accepting any such warranty or additional liability. - diff --git a/MANIFEST.in b/MANIFEST.in deleted file mode 100644 index c978a52..0000000 --- a/MANIFEST.in +++ /dev/null @@ -1,6 +0,0 @@ -include AUTHORS -include ChangeLog -exclude .gitignore -exclude .gitreview - -global-exclude *.pyc diff --git a/README.rst b/README.rst index bed59ee..86e34d6 100644 --- a/README.rst +++ b/README.rst @@ -1,26 +1,10 @@ -=============================== -openstack-ux -=============================== +This project is no longer maintained. -OpenStack UX ------------- -* Wiki: https://wiki.openstack.org/wiki/UX -* Documentation: http://docs.openstack.org/developer/openstack-ux -* Source: http://git.openstack.org/cgit/openstack-us/openstack-ux -* Design Mockups: https://openstack.invisionapp.com/ -* Bugs: http://bugs.launchpad.net/openstack-ux +The contents of this repository are still available in the Git +source code management system. To see the contents of this +repository before it reached its end of life, please check out the +previous commit with "git checkout HEAD^1". -Mission -------- - -The mission of the UX Program is to support and facilitate cross-project -efforts to improve the overall user experience of OpenStack. We provide user -research to help teams identify any issues preventing adoption of their -services as well as help the projects validate design and development efforts -to address those issues. In addition, we help the project teams create -solutions to address customer needs and pain points. Finally, we will provide -the OpenStack community with visibility into any user experience issues -related to inconsistency across projects. - -The UX team is not prescriptive; our goal is to collaborate with OpenStack’s -projects to create better experiences. +For any further questions, please email +openstack-discuss@lists.openstack.org or join #openstack-dev on +Freenode. diff --git a/babel.cfg b/babel.cfg deleted file mode 100644 index 15cd6cb..0000000 --- a/babel.cfg +++ /dev/null @@ -1,2 +0,0 @@ -[python: **.py] - diff --git a/doc/source/conf.py b/doc/source/conf.py deleted file mode 100755 index 5eb3f14..0000000 --- a/doc/source/conf.py +++ /dev/null @@ -1,75 +0,0 @@ -# -*- coding: utf-8 -*- -# Licensed under the Apache License, Version 2.0 (the "License"); -# you may not use this file except in compliance with the License. -# You may obtain a copy of the License at -# -# http://www.apache.org/licenses/LICENSE-2.0 -# -# Unless required by applicable law or agreed to in writing, software -# distributed under the License is distributed on an "AS IS" BASIS, -# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or -# implied. -# See the License for the specific language governing permissions and -# limitations under the License. - -import os -import sys - -sys.path.insert(0, os.path.abspath('../..')) -# -- General configuration ---------------------------------------------------- - -# Add any Sphinx extension module names here, as strings. They can be -# extensions coming with Sphinx (named 'sphinx.ext.*') or your custom ones. -extensions = [ - 'sphinx.ext.autodoc', - #'sphinx.ext.intersphinx', - 'oslosphinx' -] - -# autodoc generation is a bit aggressive and a nuisance when doing heavy -# text edit cycles. -# execute "export SPHINX_DEBUG=1" in your terminal to disable - -# The suffix of source filenames. -source_suffix = '.rst' - -# The master toctree document. -master_doc = 'index' - -# General information about the project. -project = u'openstack-ux' -copyright = u'2013, OpenStack Foundation' - -# If true, '()' will be appended to :func: etc. cross-reference text. -add_function_parentheses = True - -# If true, the current module name will be prepended to all description -# unit titles (such as .. function::). -add_module_names = True - -# The name of the Pygments (syntax highlighting) style to use. -pygments_style = 'sphinx' - -# -- Options for HTML output -------------------------------------------------- - -# The theme to use for HTML and HTML Help pages. Major themes that come with -# Sphinx are currently 'default' and 'sphinxdoc'. -# html_theme_path = ["."] -# html_theme = '_theme' -# html_static_path = ['static'] - -# Output file base name for HTML help builder. -htmlhelp_basename = '%sdoc' % project - -# Grouping the document tree into LaTeX files. List of tuples -# (source start file, target name, title, author, documentclass -# [howto/manual]). -latex_documents = [ - ('index', - '%s.tex' % project, - u'%s Documentation' % project, - u'OpenStack Foundation', 'manual'), -] - -# Example configuration for intersphinx: refer to the Python standard library. -#intersphinx_mapping = {'http://docs.python.org/': None} diff --git a/doc/source/contributing.rst b/doc/source/contributing.rst deleted file mode 100644 index 1728a61..0000000 --- a/doc/source/contributing.rst +++ /dev/null @@ -1,4 +0,0 @@ -============ -Contributing -============ -.. include:: ../../CONTRIBUTING.rst diff --git a/doc/source/index.rst b/doc/source/index.rst deleted file mode 100644 index 392eff5..0000000 --- a/doc/source/index.rst +++ /dev/null @@ -1,16 +0,0 @@ -Welcome to openstack-ux's documentation! -======================================== - -Contents: - -.. toctree:: - :maxdepth: 2 - - readme - contributing - -Indices and tables -================== - -* :ref:`search` - diff --git a/doc/source/readme.rst b/doc/source/readme.rst deleted file mode 100644 index a6210d3..0000000 --- a/doc/source/readme.rst +++ /dev/null @@ -1 +0,0 @@ -.. include:: ../../README.rst diff --git a/mocks/Ironic Standalone - 07 March 2016.pdf b/mocks/Ironic Standalone - 07 March 2016.pdf deleted file mode 100644 index 11d1c33..0000000 Binary files a/mocks/Ironic Standalone - 07 March 2016.pdf and /dev/null differ diff --git a/mocks/Swift - proposal - explanation.svg b/mocks/Swift - proposal - explanation.svg deleted file mode 100644 index 9fcc5dc..0000000 --- a/mocks/Swift - proposal - explanation.svg +++ /dev/null @@ -1,52801 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - Link to InVision: https://openstack.invisionapp.com/d/main#/projects/6426550 - - Horizon Swift PanelProposal for different navigation/layoutBased on the feedback we got on the 4 proposals we uploaded previously (please refer to InVision) here is an updated proposal. We implemented the suggestions and the feedback we got from the community, with a different layout and a functionality closer to what users experience with Google Drive (mainly) and DropBox.Please note that we used the default Bootstrap UI design, and that this is not a visual proposal. The intent here is to focus on the UX/UI, and then eventually apply the visual later on.We added some comments in order to highlight important points in the functionality, please read them in order to have a complete view about the proposals. - - - - - - - - - - - - - - - - Link to InVision: https://openstack.invisionapp.com/d/main#/projects/6426550 - - Horizon Swift Panel ProposalIncluded the mockups in a current-Horizon style context.Collapsed containersNumber of items inside of containersIcons to distinguish folder, image, text or general file type (that could cover several sub-categories)CTAs referring to the current position - - - 1 - - - - 2 - - - - 3 - - - - 4 - - - - 5 - - - - 1 - - - - 2 - - - - 3 - - - - 4 - - - - 5 - - - - - - - - - - - - - - - - - Link to InVision: https://openstack.invisionapp.com/d/main#/projects/6426550 - - Horizon Swift Panel ProposalSearch is not actually in these mockups, but the global magic search could include Swift and the containers, it depends on the search functionalityClick on the arrow to open the container/folder. Click on the element title to select and open it(i) opens the information about the container(highlighting the current opened container as well)During the London UX mid-cycle we discussed to keep this kinds of actions with a "+" and then the name of the element to be added, for consistency - - - 1 - - - - 2 - - - - 3 - - - - 4 - - - - 1 - - - - 2 - - - - 3 - - - - 4 - - - - - - - - - - - - - - - - - Link to InVision: https://openstack.invisionapp.com/d/main#/projects/6426550 - - Horizon Swift Panel ProposalSorting by clicking the column titlesSwitch between public and privateUsing a table view more in line with default Bootstrap we used elsewhere, as part of the definition of the library components. - - - 1 - - - - 3 - - - - 2 - - - - 1 - - - - 2 - - - - 3 - - - - - - - - - - - - - - - - - Link to InVision: https://openstack.invisionapp.com/d/main#/projects/6426550 - - Horizon Swift Panel ProposalOne click on the row selects the item and shows a different CTAs on top, according to the selection (Google Drive, DropBox)Right click with additional CTAs for the selectionMulti-selection, drag and drop of the items, Google Drive and Dropbox like functionality.Drag and drop onto a folder to move the files for instance.Generally to upload files drag and drop is enabled (once again just like Google Drive and Dropbox). But we also included a button CTA for that on top. - - - 1 - - - - 3 - - - - 2 - - - - 1 - - - - 2 - - - - 3 - - - - - - - - - - - - - - - - - Link to InVision: https://openstack.invisionapp.com/d/main#/projects/6426550 - - Horizon Swift Panel ProposalWith a longer mouseover on the row, the whole long name is shown (same for containers)Current position highlighted (same for containers) - - - 1 - - - - 2 - - - - 1 - - - - 2 - - - - - - - - - - - - - - - - - Link to InVision: https://openstack.invisionapp.com/d/main#/projects/6426550 - - Horizon Swift Panel ProposalAfter you click on the (i) for the container. The CTAs for this container is also in the modal window. - - - 1 - - - - 1 - - - - - - - - - - - - - - - - - Link to InVision: https://openstack.invisionapp.com/d/main#/projects/6426550 - - Horizon Swift Panel ProposalThe columns can be resized in order to show more content or longer strings. Sample with deeper file tree. Anyway the file tree can also be ignored and the files browsed from the right window (Google Drive like functionality). - - - 1 - - - - 1 - - - - - - - - - - - - - - - - - Link to InVision: https://openstack.invisionapp.com/d/main#/projects/6426550 - - Horizon Swift Panel ProposalSample with "cut" content viewAlso these columns can be resized - - - 1 - - - - 2 - - - - 1 - - - - 2 - - - - diff --git a/requirements.txt b/requirements.txt deleted file mode 100644 index 30806d5..0000000 --- a/requirements.txt +++ /dev/null @@ -1,5 +0,0 @@ -# The order of packages is significant, because pip processes them in the order -# of appearance. Changing the order has an impact on the overall integration -# process, which may cause wedges in the gate later. - -pbr>=1.6 diff --git a/setup.cfg b/setup.cfg deleted file mode 100644 index 7f4c60b..0000000 --- a/setup.cfg +++ /dev/null @@ -1,46 +0,0 @@ -[metadata] -name = openstack-ux -summary = OpenStack Boilerplate contains all the boilerplate you need to create an OpenStack package. -description-file = - README.rst -author = OpenStack -author-email = openstack-dev@lists.openstack.org -home-page = http://www.openstack.org/ -classifier = - Environment :: OpenStack - Intended Audience :: Information Technology - Intended Audience :: System Administrators - License :: OSI Approved :: Apache Software License - Operating System :: POSIX :: Linux - Programming Language :: Python - Programming Language :: Python :: 2 - Programming Language :: Python :: 2.7 - Programming Language :: Python :: 3 - Programming Language :: Python :: 3.3 - Programming Language :: Python :: 3.4 - -[files] -packages = - foo - -[build_sphinx] -source-dir = doc/source -build-dir = doc/build -all_files = 1 - -[upload_sphinx] -upload-dir = doc/build/html - -[compile_catalog] -directory = openstack-ux/locale -domain = openstack-ux - -[update_catalog] -domain = openstack-ux -output_dir = openstack-ux/locale -input_file = openstack-ux/locale/openstack-ux.pot - -[extract_messages] -keywords = _ gettext ngettext l_ lazy_gettext -mapping_file = babel.cfg -output_file = openstack-ux/locale/openstack-ux.pot diff --git a/setup.py b/setup.py deleted file mode 100644 index 056c16c..0000000 --- a/setup.py +++ /dev/null @@ -1,29 +0,0 @@ -# Copyright (c) 2013 Hewlett-Packard Development Company, L.P. -# -# Licensed under the Apache License, Version 2.0 (the "License"); -# you may not use this file except in compliance with the License. -# You may obtain a copy of the License at -# -# http://www.apache.org/licenses/LICENSE-2.0 -# -# Unless required by applicable law or agreed to in writing, software -# distributed under the License is distributed on an "AS IS" BASIS, -# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or -# implied. -# See the License for the specific language governing permissions and -# limitations under the License. - -# THIS FILE IS MANAGED BY THE GLOBAL REQUIREMENTS REPO - DO NOT EDIT -import setuptools - -# In python < 2.7.4, a lazy loading of package `pbr` will break -# setuptools if some other modules registered functions in `atexit`. -# solution from: http://bugs.python.org/issue15881#msg170215 -try: - import multiprocessing # noqa -except ImportError: - pass - -setuptools.setup( - setup_requires=['pbr'], - pbr=True) diff --git a/test-requirements.txt b/test-requirements.txt deleted file mode 100644 index 5a48bff..0000000 --- a/test-requirements.txt +++ /dev/null @@ -1,6 +0,0 @@ -# The order of packages is significant, because pip processes them in the order -# of appearance. Changing the order has an impact on the overall integration -# process, which may cause wedges in the gate later. - -sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2 -oslosphinx>=2.5.0 # Apache-2.0 diff --git a/tox.ini b/tox.ini deleted file mode 100644 index d43fd8e..0000000 --- a/tox.ini +++ /dev/null @@ -1,19 +0,0 @@ -[tox] -minversion = 1.8 -envlist = py34,py27 -skipsdist = True - -[testenv] -usedevelop = True -install_command = pip install -U {opts} {packages} -setenv = - VIRTUAL_ENV={envdir} -deps = -r{toxinidir}/test-requirements.txt -commands = true - -[testenv:venv] -install_command = pip install -U {opts} {packages} -commands = {posargs} - -[testenv:docs] -commands = python setup.py build_sphinx