User Details
- User Since
- Jun 10 2021, 05:36 (55 w, 4 d)
- Roles
- Administrator
- Availability
- Available
Fri, Jul 1
@speck I think we're sort of good to go here? maybe update?
Tue, Jun 14
Fri, Jun 10
Wed, Jun 8
Mon, Jun 6
I'd point out that Gerrit was originally intended to work with a client-side tool called repo (Which also manages multi-repo code trees).
The git push ... <magic ref> is kind of a workaround for users that found having a client-side tool annoying to use :)
May 3 2022
Apr 18 2022
Apr 13 2022
err, I was trying to put it out as a Security PSA, so I clicked "Create security task" which I guess is the opposite of a PSA...
Apr 6 2022
Apr 5 2022
Mar 24 2022
The upstream discussion is at https://secure.phabricator.com/T8787
Mar 21 2022
Mar 19 2022
Mar 14 2022
4pm-8pm GMT (6-10pm GMT+2) sounds good to me - I can even go up to ~midnight and looks like I'm the east-most.
Modern(ish) linters support a separate "interpreter" config - if that's set, they run $interpreter $binary $args rather then just $binary $args. Can this be utilized?
Mar 11 2022
Feb 4 2022
This is my primary jab at Packages - think of it maybe as an RFC.
Jan 25 2022
oh, wow. 8.1 breakage are massive - and I'm guessing more such breaking changes would creep in in next versions?
Dec 18 2021
I've left a comment on the server-side diff.
Nov 18 2021
Oct 24 2021
Oct 22 2021
Oct 21 2021
Oct 17 2021
Sep 30 2021
Sep 24 2021
Sague font family is probably important on Windows.
Sep 22 2021
Also, https://secure.phabricator.com/T7413 for the phone-home feature.
The kind of teams that use Centos/Redhat are very conservative - they're exactly the teams that would not install PHP from an "alternative" source (or from source code). They also tend to keep to older OS versions, as long as they are supported, and would not be happy with a single machine being different from the rest.
All that to say, it would make these teams sad to require an upgrade.
+1 for CentOS 7.
Sep 20 2021
I may be late for the party, but can't the translated verbiage be provided to the dialog in the $form_attributes in AphrontDialogView.php:337, and read using form.getAttribute(key) in the js?
Sep 6 2021
Aug 26 2021
Turns out there is Javelin support for "copy text" already implemented - I think it's used when copying from 2-up display, or when white-space is visible.
Anyway, I have an example code at https://secure.phabricator.com/P2080 for a button that copies arbitrary text.
I think I just set that via "Global Default": https://we.phorge.it/settings/builtin/global/
Aug 24 2021
I like the idea of having an easily greppeable token...
Aug 20 2021
What are the implications of making changes to the javelinjs.com https://github.com/phacility/javelin/ library?
Aug 11 2021
Jul 28 2021
I just want everything "important" to be happening here, where the search and cross-references works and async communication is easy.
The translated text can be a property of the dialogue itself, if we're worried about having extra objects laying around - the confirmation feels like it's a feature of the dialogue anyway.
There's no way to invoke pht from JS (because it's really complicated in the general case). The general practice is to provide the translated value from PHP when building the relevant objects. There should be an example in the UIExamples app - there's a page with buttons built in JS.
There already are a bunch of worthwhile changes in Phabricator we should pick up; @Matthew - want to load them to check out the procedure? I can do that otherwise.
Jul 17 2021
Here's the terms I've been thinking of for accepting a project to Phactory:
- Directly related to Phorge in a significant way:
Good: Module for integration with some other system; New Phorge app that does something reasonable; scripts for administration work.
Bad: A space-zombie game that can report high-scores to IRC, Slack and Phorge.
Jul 13 2021
nit-pick: maybe name them phabricator/master and phabricator/stable.
(I should stop reading stuff before coffee. You'd think I'd know that by now...)
I'm thinking of hosting them here, giving each project to manage their own repositories, but having a more tight control over the creation of the repo (for technical reasons) and projects.
I'd like to only have projects that are clearly related to Phorge in the install, because we're not GitHub.
We are planning on hosting community-driven extensions/projects (temp codename "Phactory"), either here or in a different domain; the idea is to have each project maintain their own repositories.
Jul 10 2021
I would like to officially submit myself as a Core Team member.
Jul 7 2021
TBH, I'm a little confused about the way forward here, and I think this our biggest blocker?
I have some time I can put towards this, but I'm not sure what I should be doing.
Jul 3 2021
Caddy looks interesting - if you get it going, can you make a small instructions writeup?
Jul 1 2021
I like the current version :)
Jun 27 2021
Are we reasonably ok with what we have in the google doc?
Jun 26 2021
The plan upstream was to (eventually) have arc land trigger T182, and do the whole thing server-side.
If you can break it to one diff with the new method/css stuff and one or two string changes, and several with only string change, we can just review it and land them one at a time.
Jun 25 2021
ahh, there's a global setting for revisions - differential.generated-paths.
I was thinking of ArcanistGeneratedLinter.php, but it looks like the only way to mark a file is by adding @generated in it, and I think we can't do that?
I thought there was another way, because this also applies to revisions (it folds the file by default).
https://we.phorge.it/source/phorge/browse/master/src/infrastructure/internationalization/translation/PhabricatorUSEnglishTranslation.php has a few more instances of Phabricator (not in pht()).
(I'm 100% with @speck on requiring tasks)
@deadalnix's I like option 3 from a UX perspective - and it also lets us hold on this issue for a little while, without making things worse.
I had a thought, that adding a %xx argument to pht without matching argument is probably not a really good idea, so I went exploring.
Jun 24 2021
I didn't talk with him in a while. Maybe opening a ticket in secure.phabricator.com is the quickest way?
I like the {Phabricator} idea! For technical compatibility with the rest of pht, it should probably be something like %PH.
Jun 23 2021
Running ./bin/i18n extract . and then this scripts, shows 455 strings with the words Phabricator or Phacility (1 for Phacility), plus 19 in arcanist.
How can I help?
Are we down to just grepping, or is there still some design left to do?
It says "Lint/Unit were skipped" for this diff - did you actually "skip" them, or is this some setup/usage artifact?