Is the extension still maintained? While there is no extension store yet, it's possible to host repositories here. https://we.phorge.it/w/docs/extensions/phactory/

Done:

Did that Phactory: Hosting Projects Here

@avivey to do now:

The repo is set to "host" right now, but it can also be set to "observe from" or "mirror to" another repo.

Nice. Maybe a start-extension Arcanist workflow is a bit overkill, but a boilerplate extension would be lovely

Nuance has a "GitHub Repository: Import issues and pull requests from a GitHub repository" Source Type - it might already be doing something related?

Uh thanks!

Created repo rQR QR Stickers and project QR Codes Extension

Created repo rQR QR Stickers and project QR Codes Extension

In T15568#12244, @valerio.bozzolan wrote:

every extension should have its own

Ah, yeah, even better I think, if possible

every extension should have its own

In T15568#12239, @avivey wrote:

I was thinking of adding a script to ./bin to manage (mostly add/remove from load-libraries, maybe also clone) extensions.

Probably related, I think that any installed extension should not cause any touch to /src/__phutil_library_init__.php, as long as it's versioned in git in Phorge and so will cause of course merge conflicts after any update.

I was thinking of adding a script to ./bin to manage (mostly add/remove from load-libraries, maybe also clone) extensions.

I'd like to give this a shot, as part of streamlining extensions as discussed in T15568

Created R7 arc-vscode, but it's currently Observing the GH one.

Created Semi Structured (Extension) and R6 Semi Structured:

ihih I always thought the lack of tags was a feature. So I always manually Tagged also the Description. Thanks for the Task.

In T15525#11410, @valerio.bozzolan wrote:

I would like to mention #diagrams_extension in the Repository description, but I do not have enough permissions.

I would like to mention #diagrams_extension in the Repository description, but I do not have enough permissions.

This task is mostly done now that the repository is present and someone made an initial release of Diagram.

And you can manage Diagrams (Extension), which has access to manage the repo.

I think we are done with the logo as we have a graphical kit.

One other thing we’ll need to address is the current code sharing between arcanist and phorge. I’m not sure the full scope of what Phorge relies on from arcanist but I think there’sa fair amount. We can probably get an idea by looking at the libphutil repo which was the shared library between the two which was eventually merged into arcanist

I was similarly looking at lua for the same reason as it's used by neovim 😆 . There are a few libraries for lua in rust but the one that seems recently active is mlua, which doesn't implement lua execution in rust but binds to lua binary/library. If we go the route of binding to another library/binary then our build/package would have to include the lua library file too (though it may be possible to embed it?). Something like Rhai (or there's also Rune and a few others), are implemented fully in Rust so there's less to worry about during the build/package process. I wasn't sold one way or the other but wanted to check out Lua along with some of the others to see how well they turn out.

I see what you are saying. I quite like Lua and how neovim uses it to achieve this extensibility...

I’m fully aware of the friction that comes up trying to get developers using arcanist, the difficulties with PHP, the complexity in not understanding what’s going on, etc. and also familiar with the benefits of a compiled binary solution.

@speck the whole point of an alternative phab client implementation is remove friction that comes with arcanist. Namely:

Hah this has been something spinning in the back of my mind for a while. One thing that will be difficult to support in something like Rust (not sure about Go) is that the PHP arcanist allows for very easily extending by dropping in your own PHP files to the extensions folder.

Thanks @avivey !

Rust Conduit Client/R4 is the first project in Phactory!

I created Rust Conduit Client and (unnamed) R4.

Cool. Let's start with rRustConduit, because I think there's a bad joke in there about rusted pipes (12 seconds of google did not find a special name for it).

Phactory [will] also want an in-brand logo.