Here we'll track the Rebranding effort.

The process we settled for is this:

1. Pick an app from the list below. Put your name next to it.
2. Make a revision to this instance (rP), updating the strings in this app (See below for Guidelines on that)
3. Once we're happy with it, we'll copy the diff over to secure.phabricator.com for inclusion in Phabricator. If you don't have an account there, someone with an account (e.g. @avivey, @speck) will copy it.
4. The diff will not be landed directly in Phorge - we'll pick it up from the upstream after its landed there.
   • https://secure.phabricator.com/T13658#256501

Rebranding Guidelines

1. For each application, review all user-facing text and rephrase it to be general purpose text.
   • Change references of "Phabricator" to "the installation" or "this installation"
   • See https://secure.phabricator.com/D21712#inline-60877 where Evan clarifies that the term "Phabricator instance" should be used in distinguishing cluster instances and not the installation instance.
   • See more examples in https://secure.phabricator.com/D21712.

2. For any user-facing documentation which requires referencing "Phabricator", there is a new remarkup interpreter which resolves the {{{ strings.platform.name }}} macro to the brand name (update: this exists in the Phabricator upstream which is not yet merged into Phorge).

3. Anything which refers to phabricator as a path on disk or a class name, which is not user-facing, can remain for now and be addressed in a different change. This helps to limit to scope of necessary changes for the branding effort. Note that many of the descriptive text in in the config application will refer to running scripts on the server phabricator/bin/ path, which will need updated to reference a variable for the repo name.

Coding Guidelines

Since all changes are going to be submitted to the upstream prior to landing here in Phorge it would be easiest if changes were made to a clone of Phabricator and not a clone of Phorge.

To help locate user-visible text grep for the following regular expressions

• '.*Phabricator
• ".*Phabricator

Formatting

• Phabricator maintains PHP formatting which keeps lines 80 characters or less, using indentation of 2 spaces per indent. For multiple lines attempt to maximize the number of words on each line (and necessary formatting, see next point) to be less than or equal to 80 characters.
• When splitting long text across multiple lines use the . concatenation, and split the lines such that spaces between words and the . concatenation are at the end of the line
• Prefer to align indentation of multi-lines such that the quotes are aligned. To maximize space if needed you may place the first argument to pht() on a new line
• Prefer to use single-quotes. Use of double-quotes is preferred when the text content contains newline escapes, which won't render properly in single quote text.
• Use formatted text e.g. pht('Welcome %s', $name); instead of variable concatenation pht('Welcome '.$name). This is strictly required except in rare circumstances, as translations into other languages cannot assume placement of words that concatenation enforces.

$object->setValue(pht(
  '... this installation requires '.
  'that all blah %s blah '.
  'and such',
  $this->getDisplayName()));

Applications

(phts denotes a simple count of how many times pht() shows up in the code - it should give a rough estimate of how much work each app needs.)

/src/applications/

/src/infrastructure/:

/src/docs/

T15012: Update Diviner documentation to reference Phorge