- User Since
- Apr 15 2014, 1:04 PM (253 w, 3 d)
Jun 19 2018
Jan 31 2017
@epriestley Not that it will likely make you feel any better about it, but some of us just really want our Guns-Made-From-Rope™ to be powered by Phabricator instead of other much less awesome things. 😄
Feb 27 2016
Jan 26 2016
Another 2c for the piggy bank. As someone that quite likes the majority of the 'non-serious mode' text, "clowncopterize" feels just a step too far. I can explain weird names to new people, I can link them to a guide, but "clowncopterize" still gives most people, including myself despite using and even advocating the use of Phabricator to others for some time, too much pause for thought. Its not the content as much as it is the jarring level of 'non-sequitur' it may as well say "By this time, my lungs were aching for air" for all it relates to the action that it performs. If it has to come back, at least give me some way to turn it off without throwing away all the other stuff by turning on serious business mode.
Jan 24 2016
May 25 2015
If the estimate is 20 hours, then perhaps those of us still looking for this more earnestly can pass around the collection plate and collectively pay for it. 18 people are subscribed to this issue, if even 3 of us are willing to pony up the dough, then this goes from ~$3000 to ~$1000, and suddenly I can say "look finance guy, we spend $100 a month on private github repos, this $1000 eliminates that year over year cost".
Apr 4 2015
I frequently see this issue, and not only do i see it on secure.phabricator.com but on my own phabricator install. Cloudflare seems likely since I too use Cloudflare for my SSL.
Feb 28 2015
Nov 26 2014
Nov 10 2014
@qgil it sounds like what you want with each roadmap item being maintained and documented by the item owner, is an application of the existing permission system not necessarily somewhere the Roadmap idea I'm suggesting would be going the wrong way for Wikimedia.
@qgil I did examine the phabricator roadmap page before I began trying to work out how hard it would be, what I feel is that while T4863 goes a long way to making the work board a very close equivalent. All of these are more a case of 'good enough'.
Nov 8 2014
Just throwing my +1, agreeing with the stuff in T4694 and wanting a way to remove the need for call signs.
Nov 6 2014
The python "linting ecosystem' is one of those places where the only way to do a good job is "support all the things"
Sep 11 2014
@epriestley are you able to provide a little explanation of how D9599 fits into the plan to enable this feature. I think I understand that code, but some elaboration with regards to how it helps would be good and will probably help anyone else following along.
May 30 2014
@mattflaschen thank you for very nicely laying out the GitHub workflow with regard to amend based updates which are the mainstay of the projects I'm involved with that don't use Gerrit or any other tool that enforces it.
further to what @20after4 was saying, there do appear to be php memory profiling tools available should this become an issue again.