Page MenuHomePhorge

Create projects for this install
Closed, ResolvedPublic

Description

As recommended by @chris in T15001, we will want to create projects for each component. The current idea is as follows:

Phorge is the software project itself. All components of Phorge will be sub projects
Phorge Upstream is the project for this install. It would contain “governance” and “systems” as sub projects.

If there is no objection, I’ll implement this change.

Migration from Phab

I essentially copy and pasted the entire project list here, to give us a starting point of what to create / ditch

Phab ProjectPhorge ProjectNotes
Abuse
Accessibility
Almanac Almanac
Android
AphlictAphlict
Aphront
ApplicationEditor
Applications
ApplicationSearch
ArcanistArcanist
Asana
AuditAudit
AuthAuth
BadgesBadges
Blessed CommittersBlessed Committers
Blessed Reviewers
CalendarCalendar
Celerity
Chad's HouseN/A
ChatlogConfig
Clusters
Community
ConduitConduit
ConfigConfig
ConpherenceConpherence
Contributor Onboarding
CountdownCountdown
Cowboy Commits
Custom Fields
DaemonsDaemons
DashboardsDashboards
Data Exporters
Database
Design
DifferentialDifferential
DiffusionDiffusion
Disqus
DivinerDiviner
Documentation
Doorkeeper
DrydockDrydock
EditEngine
Elasticsearch
Facebook
FactsFacts
FeedFeed
FilesFiles
Firefox
FlagsFlags
FreeBSD
FundFund
Git
GitHub
Google Chrome
GuidesGuides
Harbormaster Harbormaster
Hard
Haskell.org
HeraldHerald
HipChat
Hovercards
Infrastructure
Inline Comments
Installing & Upgrading
Internet Explorer
Javelin
KDE
LDAP
Legal
libphutilKeep for Backwards Compat?
Lightbox
Lint
llvm
Localization
Macros Macro
Mail Mail
Mailing Lists
ManiphestManiphest
Marketing
Mercurial
Mobile
Modernization
Must Encrypt Mail
Notifications
NuanceNuance
NUX
OAuthServer
Oncall Tool
OpenStack
Ops
Overseer
OwnersOwners
Packages
PassphrasePassphrase
PastePaste
PeoplePeople
Performance
PhacilityN/A
Phacility Core AccessN/A
Phacility Documentation EditorsN/A
Phacility High CommandN/A
Phacility Keystore AccessN/A
Phacility Root AccessN/A
Phage
PhamePhame
Phlux
PholioPholio
Phortune
Phragment
PhrequentPhrequent
PhrictionPhriction
PHUI
PhurlPhurl
Plans
PonderPonder
Ponder Moderators
Process Improvement
Profile
ProjectsProjects
Public & Media Relations
Quick Look
Quicksand
Remarkup
Safari
Search
Security#security
Setup
SlowvoteSlowvote
Sounds
Space Test Users
SpacesSpaces
Subversion
Support
Support Request
Symbols
TokensTokens
Transactions
Typeahead
Unit
Unnamed Manual Test Case Application
User Delight
User Preferences
v0
Wikimedia
Windows
Workboards
XHPAST
XHProf

Related Objects

Event Timeline

Matthew triaged this task as Normal priority.Jun 10 2021, 19:08
Matthew created this task.
Matthew updated the task description. (Show Details)
Matthew edited projects, added Upstream General/Unknown; removed Phorge Upstream.

Projects created, sorry about the spam.

Matthew changed the visibility from "All Users" to "Public (No Login Required)".Jun 11 2021, 23:53

I’ll note here that I’m going to work on creating projects for some of the prototypes that do get used.

MacFan4000 updated the task description. (Show Details)
MacFan4000 removed Matthew as the assignee of this task.

Now that I look at this some more, this isn’t quite done - there are still some components of phorge that are missing projects.

I’ll note here that I’m going to work on creating projects for some of the prototypes that do get used.

I just wanted to note that Phrequent is an integral part in my company, even though it's a prototype. We heavily rely on time tracking.

I just wanted to note that Phrequent is an integral part in my company, even though it's a prototype. We heavily rely on time tracking.

I honestly think that there's a lot of very good alternatives for time tracking out there that provide a ton of features and creature comforts that Phrequent doesn't. I personally would think that time tracking is outside the scope of a project like Phorge. I'd argue that time tracking should be done by third party software or an extension (which Phrequent could become).

My argument for it being outside the scope: The time spent handling a task provides no measure of the quality of the resolution provided. There's no correlation between quality code and the time taken to write it. It's generally just used for accounting purposes and HR-planning.

MacFan4000 claimed this task.

For the rest, I think they can be created on an as-needed basis.