Skip to content

Commit de2703e

Browse files
committed
[Branding] Remove Web from name at top-level
Per nasa#816, change Open MCT Web to Open MCT in all top-level files.
1 parent 01f290d commit de2703e

File tree

4 files changed

+25
-25
lines changed

4 files changed

+25
-25
lines changed

CONTRIBUTING.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
1-
# Contributing to Open MCT Web
1+
# Contributing to Open MCT
22

3-
This document describes the process of contributing to Open MCT Web as well
3+
This document describes the process of contributing to Open MCT as well
44
as the standards that will be applied when evaluating contributions.
55

66
Please be aware that additional agreements will be necessary before we can
@@ -21,9 +21,9 @@ The short version:
2121

2222
## Contribution Process
2323

24-
Open MCT Web uses git for software version control, and for branching and
24+
Open MCT uses git for software version control, and for branching and
2525
merging. The central repository is at
26-
https://github.com/nasa/openmctweb.git.
26+
https://github.com/nasa/openmct.git.
2727

2828
### Roles
2929

@@ -116,18 +116,18 @@ the merge back to the master branch.
116116

117117
## Standards
118118

119-
Contributions to Open MCT Web are expected to meet the following standards.
119+
Contributions to Open MCT are expected to meet the following standards.
120120
In addition, reviewers should use general discretion before accepting
121121
changes.
122122

123123
### Code Standards
124124

125-
JavaScript sources in Open MCT Web must satisfy JSLint under its default
125+
JavaScript sources in Open MCT must satisfy JSLint under its default
126126
settings. This is verified by the command line build.
127127

128128
#### Code Guidelines
129129

130-
JavaScript sources in Open MCT Web should:
130+
JavaScript sources in Open MCT should:
131131

132132
* Use four spaces for indentation. Tabs should not be used.
133133
* Include JSDoc for any exposed API (e.g. public methods, constructors.)
@@ -159,7 +159,7 @@ JavaScript sources in Open MCT Web should:
159159
* Third, imperative statements.
160160
* Finally, the returned value.
161161

162-
Deviations from Open MCT Web code style guidelines require two-party agreement,
162+
Deviations from Open MCT code style guidelines require two-party agreement,
163163
typically from the author of the change and its reviewer.
164164

165165
#### Code Example
@@ -260,7 +260,7 @@ these standards.
260260

261261
## Issue Reporting
262262

263-
Issues are tracked at https://github.com/nasa/openmctweb/issues
263+
Issues are tracked at https://github.com/nasa/openmct/issues
264264

265265
Issues should include:
266266

README.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,22 +1,22 @@
1-
# Open MCT Web
1+
# Open MCT
22

3-
Open MCT Web is a web-based platform for mission operations user interface
3+
Open MCT is a web-based platform for mission operations user interface
44
software.
55

66
## Bundles
77

88
A bundle is a group of software components (including source code, declared
99
as AMD modules, as well as resources such as images and HTML templates)
1010
that are intended to be added or removed as a single unit. A plug-in for
11-
Open MCT Web will be expressed as a bundle; platform components are also
11+
Open MCT will be expressed as a bundle; platform components are also
1212
expressed as bundles.
1313

1414
A bundle is also just a directory which contains a file `bundle.json`,
1515
which declares its contents.
1616

1717
The file `bundles.json` (note the plural), at the top level of the
1818
repository, is a JSON file containing an array of all bundles (expressed as
19-
directory names) to include in a running instance of Open MCT Web. Adding or
19+
directory names) to include in a running instance of Open MCT. Adding or
2020
removing paths from this list will add or remove bundles from the running
2121
application.
2222

@@ -56,26 +56,26 @@ To run:
5656

5757
## Build
5858

59-
Open MCT Web is built using [`npm`](http://npmjs.com/)
59+
Open MCT is built using [`npm`](http://npmjs.com/)
6060
and [`gulp`](http://gulpjs.com/).
6161

6262
To build:
6363

6464
`npm run prepublish`
6565

6666
This will compile and minify JavaScript sources, as well as copy over assets.
67-
The contents of the `dist` folder will contain a runnable Open MCT Web
67+
The contents of the `dist` folder will contain a runnable Open MCT
6868
instance (e.g. by starting an HTTP server in that directory), including:
6969

70-
* A `main.js` file containing Open MCT Web source code.
70+
* A `main.js` file containing Open MCT source code.
7171
* Various assets in the `example` and `platform` directories.
72-
* An `index.html` that runs Open MCT Web in its default configuration.
72+
* An `index.html` that runs Open MCT in its default configuration.
7373

7474
Additional `gulp` tasks are defined in [the gulpfile](gulpfile.js).
7575

7676
### Building Documentation
7777

78-
Open MCT Web's documentation is generated by an
78+
Open MCT's documentation is generated by an
7979
[npm](https://www.npmjs.com/)-based build. It has additional dependencies that
8080
may not be available on every platform and thus is not covered in the standard
8181
npm install. Ensure your system has [libcairo](http://cairographics.org/)
@@ -89,7 +89,7 @@ Documentation will be generated in `target/docs`.
8989

9090
# Glossary
9191

92-
Certain terms are used throughout Open MCT Web with consistent meanings
92+
Certain terms are used throughout Open MCT with consistent meanings
9393
or conventions. Any deviations from the below are issues and should be
9494
addressed (either by updating this glossary or changing code to reflect
9595
correct usage.) Other developer documentation, particularly in-line
@@ -112,7 +112,7 @@ documentation, may presume an understanding of these terms.
112112
(Most often used in the context of extensions, domain
113113
object models, or other similar application-specific objects.)
114114
* _domain object_: A meaningful object to the user; a distinct thing in
115-
the work support by Open MCT Web. Anything that appears in the left-hand
115+
the work support by Open MCT. Anything that appears in the left-hand
116116
tree is a domain object.
117117
* _extension_: An extension is a unit of functionality exposed to the
118118
platform in a declarative fashion by a bundle. For more

bower.json

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
{
2-
"name": "openmctweb",
3-
"description": "The OpenMCTWeb core platform",
2+
"name": "openmct",
3+
"description": "The Open MCT core platform",
44
"main": "",
55
"license": "Apache-2.0",
66
"moduleType": [],
7-
"homepage": "http://nasa.github.io/openmctweb/",
7+
"homepage": "http://nasa.github.io/openmct/",
88
"private": true,
99
"dependencies": {
1010
"angular": "1.4.4",

package.json

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
{
2-
"name": "openmctweb",
2+
"name": "openmct",
33
"version": "0.10.1-SNAPSHOT",
44
"description": "The Open MCT core platform",
55
"dependencies": {
@@ -53,7 +53,7 @@
5353
},
5454
"repository": {
5555
"type": "git",
56-
"url": "https://github.com/nasa/openmctweb.git"
56+
"url": "https://github.com/nasa/openmct.git"
5757
},
5858
"author": "",
5959
"license": "Apache-2.0",

0 commit comments

Comments
 (0)