Discussions about how Community Projects ("Phactory") management.
Relevant topics:
- Request/discuss projects for admittance into Phorge
- Discuss and document Phorge policies
- Support stuff for services provided to the hosted projects
Discussions about how Community Projects ("Phactory") management.
Relevant topics:
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.