Are we reasonably ok with what we have in the google doc?

Should we plan a timeline to finalize it?

Are we reasonably ok with what we have in the google doc?

I believe we should do a cleanup pass? It's not obvious what is intended for the final document vs scaffoldings that are left over. The content seems fine to me but still needs some "weaving in".

We could try to build a first "clean" draft and see how it looks like?

I've made some updates to the vision statement document to try and bring it closer to completion. I've incorporated the rest of the outstanding notes and addressed the current comments.

The document is divided into three sections,

• Project: What is it
• Community: Who we are, how we op erate
• Design Tenets: What are the driving guidelines as we design and develop changes

Please take some time to review, comment, or make updates.

The vision statement really is fantastic.

I made a couple of suggestions in it, but all in all, it's a great doc. Congrats @speck .

Thanks for the suggestions - I've updated the document to address them.

Nothing to comment on: It’s great!

I like the current version :)

Ship it!

But seriously, I love the vision statement and think it's great for what we're doing!

I like it

I've copied the contents into L1 Phorge Vision Statement which allows us to track signatures

Did another pass on it: only thing I found is a typo (which I'm not allowed to fix): extra space after "Opinionated" and before to column in the list under "What is Phorge".

@jupe thanks for pointing out the typo, I've updated to fix that.

After agreeing and signing the document I submit myself here as a core team member, officially.

My experience with Phabricator started in 2014 in evaluating it as a tool primarily for code review as my company already has code hosting and task management tools in place. I implemented it at my company in 2015 and it grew organically to where our quality policy now requires its use for most products. I've worked with IT to keep Phabricator updated, investigate issues, submit issues upstream (including in a limited Phacility support pact), and provide some minor customizations.

My interests in Phorge are to see a successful continued maintenance support of a Phabricator fork, primarily for my company to continue it's use internally. My company had already been looking at GitLab primarily for its CI capabilities but the announcement that Phabricator would no longer be maintained has effectively pushed us towards adopting a sun-down plan involving migrating to GitLab (I really really really prefer mercurial).

I see my involvement in the core team being primarily geared towards:

• Organize the initial effort to create a fork
• Have a voice with regards to feature development guidance
• Support community members with some limited knowledge of the current architecture and ensuring quality of changes
• Some implementation efforts, namely around support for Mercurial
• And more!

My activity in the Phabricator community:

• In the upstream I am cspeckmim
• Upstream revisions I've worked on
• Upstream tasks I've submitted
• Upstream Ponder questions I've provided answers for
• My profile on the phabricator discourse

My activity in the Phorge community:

• On we.phorge.it I'm @speck~
• Setup the Zulip chat (I'm "Christopher Speck" on there)
• Worked on the vision statement
• Working on the foundation/organization
• Working on the rebranding

Are we supposed to make a similar lengthy statement?

I think it's good, I'm in :)

I would like to officially submit myself as a Core Team member.

I've started using Phabricator in 2011 at Facebook; I've been contributing code and supporting installs since 2012. I've managed installs in two companies.
I don't currently use Phabricator in work.
I believe I can commit about 4 hours/week to the Phorge project.

I intend to focus on making Phorge great for self-hosting and extended in organizations, and in making it better for organizations (and individuals) to cooperate as a comunity.

My Phabricator links:

• avivey at secure-dot
• My revisions
• Discourse Profile

Are we supposed to make a similar lengthy statement?

Heh, I wasn't really sure what people were expecting so just wrote up some stuff to explain who I am and what my role will probably end up being.

I believe I can commit about 4 hours/week to the Phorge project.

I think I'll roughly have the same amount of time commitment.

I would like to be a part of the core team, and I've signed the document.

Glad to see Phabricator continuing as Phorge. Not going to lie, I had a panic attack this morning when I found out that Phacility was winding down.

I don't know that I have the time to commit code at the apparent core member rate yet *per-se*, but I want to get very much involved. (I also have project management, devops, and community management experience.)

For many years, I've single-handedly administrate dthe Phabricator instance for MousePaw Media (a company I also run). It makes up almost our entire distributed workflow. Without it, we'd be up a creek.

As a result, when things go ka-blooie, I usually find out. I would not be opposed to putting development time into fixing things and adding small features as they come up.

I agree with the doc, and would like to sign too.

In T15010#1060, @codemouse92 wrote:

I agree with the doc, and would like to sign too.

Any user should be able to sign the doc at L1 Phorge Vision Statement - did you try it and got an error?

In T15010#1062, @avivey wrote:

Any user should be able to sign the doc at L1 Phorge Vision Statement - did you try it and got an error?

Oh, excellent, that's live. Somehow I overlooked that.

Not sure if this is where to mention, I would definitely like to help develop/maintain/review Phorge (I have signed the doc), I currently maintain a 600+ user Phabricator instance housing 50+ git repos,

I've made a number of changes locally which I would love to have the concept of potentially up streaming in the future. I have extensive knowledge of conduit for both creation of reviews but also for CI integration.

I'm also an administrator on the LLVM Phabricator instance.

I added @dcog @codemouse92 and @mydeveloperday to the trusted contributors group. Glad to have everyone involved!

I would also love to contribute to Phorge. I have signed the legalpad doc.

I'd be happy to contribute. I currently maintain an installation with over 4,000 git repos and over 2,000 users since 2016. Our company apparently had the highest karma count by a wide margin with our Phacility Support Pact, for whatever that's worth :)

I added you both as well! Welcome to the team. If anyone has pre-existing functionality that they feel would be good to include in the upstream feel free to submit the changes. There's ongoing work (unfortunately slowly) to rebrand the project, but that's not holding up other changes at this time.

Really glad to see Phabricator will live on - I've previously managed some bugfixes in an external repo and would love to try to get them into upstream. I've run Phabricator instances for 7 of the last 9 years (and was unable to convince my previous employer to switch) so I've got a bit of experience on the managing side as well.

In T15010#1272, @MikeCripps wrote:

Really glad to see Phabricator will live on - I've previously managed some bugfixes in an external repo and would love to try to get them into upstream. I've run Phabricator instances for 7 of the last 9 years (and was unable to convince my previous employer to switch) so I've got a bit of experience on the managing side as well.

The evolution of Phorge is super exciting :)

Any chance that anyone has insight on D25015? Specifically, a way to get l18n (internationalization/translation) information from PHP into JavaScript from a minimalist approach

@MikeCripps welcome aboard! I added you to trusted contributors group.

I think we're done here too? E13.