The best idea would be to run both projects off the same phab but with different repos that we can keep rebasing to keep feature parity
The best idea would be to run both projects off the same phab but with different repos that we can keep rebasing to keep feature parity
If you are still interested I'd be game, I just wanted to have my own phab so no matter what I have a good copy.
How'd you get around the requiring an email address to setup phab users thing?
If you are still interested I'd be game, I just wanted to have my own phab so no matter what I have a good copy.
How'd you get around the requiring an email address to setup phab users thing?
And if you're down to it we have no problem in sharing phab instances. It'll make it way easier to fix bugs if the reports are in the same place, It'll be easier for me to send code your way if you ever need help tweaking something
And if you're down to it we have no problem in sharing phab instances. It'll make it way easier to fix bugs if the reports are in the same place, It'll be easier for me to send code your way if you ever need help tweaking something
See there was this idea I had when I first started poal where I would federate with their phabricator instance or something similar, and I really meant too I did. like phab.poal.co is up and running, however it has like 12 issues to solve and you can't setup users without email addresses so I setup a mail server for poal and then I got side tracked. I'm still hoping to share code between poal and phuks someday both sites have some damn good ideas. I think the admins here are a great bunch of guys and I know at least at one point they wanted to look at what we where doing. Its still on my to do list.
@polsaker once told me when updating the source I should run the command and then pray to whatever god I believe in that things went well, and then accept there is no god and accept that I would have to fix everything, this gave me the idea to setup my own phabricator. He is probably still right.