Hi,
Please check it again. It should be open now.
The main open question is "Can third-party Phabricator development be staged and tested on labs and then merged into a downstream production repo?"
Thank you for your help, Christopher
On 18 September 2014 13:02, Quim Gil qgil@wikimedia.org wrote:
I'm very excited to see that you have something working!
On Thursday, September 18, 2014, Christopher Johnson < christopher.johnson@wikimedia.de> wrote:
Hi,
We have independently tested the third party "library" for sprint
burndown
charts that is located here: https://github.com/bluehawk/phabricator-sprint.
You can see it here: http://phab.wmflabs.org/burndown/view/1/
No we cannot. Anonymous users can't see it (Public policy is missing, I guess), and registration is restricted to @wikimedia.de emails.
Despite being hacked in to the libphutil as a library, though it is
phabricator dependent, it works on a basic level. We would require
further
modification of the code for it to work for us, however. What would it take to get this into the test instance https://phab -01.wmflabs.org/ ? Is this labs test puppet cloning a development repo? Also, how will core and library code changes to phabricator be deployed
to
the production instance?
Where shall we put this phabricator-sprint code so that we can work on it with the intention of having it reviewed and deployed in production as
soon
as possible?
-- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l