Work related to Phorge.
Tue, Oct 19
Sun, Oct 17
Sat, Oct 16
Also this Vagrant pattern should work first-run: https://we.phorge.it/T15027#852
Yes - I could have some availability - Normally evenings (US Central Time) -
Fri, Oct 15
I can provide more information later this weekend but I think it would help if we set up a virtual meeting with anyone interested in helping to get this done.
@speck What can I help with here? - Are we waiting on upstream for anything currently?
The effort to rebrand Phabricator is going to result in changes to a lot of text which would likely invalidate a large number of translation entries.
At my company we have a similar situation however our management system is something we also actively develop. We solved this problem by configuring a web hook to hit an endpoint for the activities we are interested in having people track. The endpoint receives the transactions, pulls some additional info, and creates time-tracked activities for them in an aggregated list. Employees review the list and update time for each activity. It works pretty well and is not limited to activities from Phab allowing other systems to post activity to report, and for employees it’s nice because we can present the activity they’ve done and only require they estimate time spent as all other context is linked up.
Wed, Sep 22
and yes, I'm also running phabricator on top of CentOS 7 (using PHP 7.x via SCL).
Is it possible to pick a branching off point?
Yep I think this makes sense and is why I think our first release should still support PHP 5.4 but we can move off it after that.
Is it possible to pick a branching off point?
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.
I'm mostly a Debian person (so I'm not aware of CentOS specifics) but my understanding is that CentOS 7 shipped with PHP 5.4 and has newer versions available via alternative repositories (not sure if official or not), while CentOS 8 (and Rocky Linux 8, if that matters) had PHP 7.2 by default and shipped a few years back. Is there a reason we're not basing our PHP support on latest distro releases (plus something like a year or two for a transition buffer), especially if newer PHP versions are available for older distro versions available as backports? I don't think requiring PHP / distro upgrades every few years is unreasonable.
Isn't Centos End of Life soon?
+1 for CentOS 7.
Agreed. We should aim to follow some specific conservative release. CentOS 7 seems reasonable.
We should include the Diviner and tech docs generation as part of the upgrade process of this server, that should ensure it's always up to date.
@MikeCripps welcome aboard! I added you to trusted contributors group.
I think our general strategy here should be focused around the versions of PHP available from the default/common package repositories for major server-based Linux distributions. There might be some situations where those package repositories only support very old versions (e.g. CentOS 7) which we should only plan to provide documentation for how to get the required version of PHP installed.
Sep 18 2021
I will note that also the tech docs aren’t fully generated since there should be docs for most of the phorge/phabricator classes. Also the arcanist docs aren’t generated at all.
The Server also needs to periodically rebuild the Diviner Books to keep them in sync with Source Code. Eg. just set up a crontab entry. Or later, if more traffic is on the page: rebuild it once a commit affecting the Docs is committed.
Sep 17 2021
Sep 16 2021
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.
Sep 4 2021
Automated Landing should be what adds the "Land Revision" button to revisions -- so not fully automated but allows someone to land without needing a local clone to manage.
Also when I look at a diff on upstream phabricator i see a land revision button - but I don’t see that for diffs on this instance.
I'd suggest starting of the starmap by shedding some/most of the applications that were not part of the core of Phabricator or have been in the Prototype phase for a long time, allowing the project to regain focus and improve on the things that make Phorge unique. This would provide a number of advantages:
Aug 24 2021
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.