Dashboard adjusted, we only need to work on the links. Dashboard has been set to the home page.

Dashboard is a start on a dashboard

From my notes

Just my 2cts:

Just emailed/DM'd some people, I'll see who replies.

git grep phurl.io has a about 10 links to documentation (mostly in Setup checks).

I tried to get a start on this in P1, just running

grep -r -n -E '[Pp]habricator[ \.,;:\-\!\?)]' ./src

and found a few occurrences. Not sure how we want to handle the configuration values that are `phabricator.<XYZ>' since they're sort-of internal, sort-of exposed in the UI. I left them in the Paste just to have them documented

Welcome to Phorge. Phorge is an open source, community driven platform for collaborating, managing, organizing and reviewing software development projects. You can learn more about the features of Phorge [here] and how to install Phorge [here]. You can ask for help [here] and [here] and you can learn about contributing to Phorge (here)

On the topic of increasing community involvement we will also want to produce documentation for setting up development environments as well as the steps to submit changes upstream (like a quality checklist). To make development environments even easier we might want to consider supporting something like a vagrantfile so people can get started with very few steps.

I feel that the first center-panel should be a "Welcome" panel. This panel would in the shortest amount of text possible :

There is great benefit from having people submitting the code to push it themselves.

So some feedback from my experience doing this in the open.

As of right now, both Blessed Committers and Security Viewers have the admins as members. I have no problem with that changing.

In T15001#38, @chris wrote:

Could just do like Phorge Upstream → Governance, Phorge → Maniphest, etc. with subprojects to have a kind of clean-ish separation between "application" stuff and "administrative" stuff?

Could just do like Phorge Upstream → Governance, Phorge → Maniphest, etc. with subprojects to have a kind of clean-ish separation between "application" stuff and "administrative" stuff?

I was initially planning to use Phorge for upstream maintenance and project governance and using individual projects for apps (Maniphest, for example). If Phorge is about the software, where are you planning to put project governance?

One final change I will make, I've created a phorge.it install project, so that way the Phorge project can be about the software.

Thanks. We might want to add Trusted Contributors create/edit policies on projects too, but otherwise I think that should be everything to get us started.

Okay, this is done. My solution is four Maniphest forms:

• Create Task - This is the simple create form for tasks. it defaults to "needs triage," doesn't provide a chance to assign the task to someone, and hides the policies of a task.
• Create Task (Advanced) - This is the full create task form. It is restricted to Trusted Contributors
• Create Security Task - This is a create form visible to everyone. It automatically puts the task in S2, assigns the Security project, and creates a custom policy on the task.
• Edit Task - This is the same form as Create Task (Advanced), but it is set as the edit form due to the permission restrictions on that form.

In T15001#27, @taavi wrote:

In T15001#26, @Matthew wrote:

Okay, I have set up the projects, spaces, forms, and other policies with one exception:

At least in Maniphest all users seem to still be able to mess with custom policies.

I will made the adjustment to the forms, I'd think we want a simple create for anyone new anyway

In T15001#26, @Matthew wrote:

Okay, I have set up the projects, spaces, forms, and other policies with one exception:

Okay, I have set up the projects, spaces, forms, and other policies with one exception: I can't remember how to restrict arc land, so I'm going to take care of that in a bit.

In T15001#23, @taavi wrote:

I think that's good to get us going. Who would be able to manage membership of the blessed_commiters / security groups? Admins?

I think that's good to get us going. Who would be able to manage membership of the blessed_commiters / security groups? Admins?

I can take care of the initial setup for this issue.