Looks good, yeah.

@avivey does this look good to you?

In D25936#25132, @aklapper wrote:

@Cigaryno: Thanks! Could you elaborate why the change in .arcconfig is needed?

@Cigaryno: Thanks! Could you elaborate why the change in .arcconfig is needed?

So, this turns out to be a lot harder than I thought.

I don't know why, but O1 has to be manually added as a reviewer as it does not own R10.

It seems H29 works lol. I've improved it a bit to do not trigger if the celerity map was already touched.

To me, "obsolete" manes "no longer appliable" - basically, "the information in this page doesn't apply any more".
Some (made up) examples:

• "Can Phorge run on PHP 7.0?" (The answer is no, because of a specific bug in 7.0, which was EOL a long time ago)
• "I have this problem in the Chatbot app" (We've deleted the chatbot app)

In T15450#16936, @Iniquity wrote:

I agree that an additional status is needed for closing when creating a task. Current statuses are not obvious

Uh! That's magic. Thanks avivey. Created here: H29 Phorge: add comment to remember "celerity map" - T15209

@valerio.bozzolan try to create the global rule now.

Sounds good. It should have no CAPTCHA configured (maybe we.phorge.it needs CAPTCHA to reduce unused account creations) and just like on secure.phabricator.com (see this), there should be a notice for users willing to demo the software on the demo instance and not the upstream instance (in Phabricator you can create a Phacility test instance and even to this day, this is still possible).

try now

Tried. I Shall Not Pass :O

@valerio.bozzolan go ahead and give it a try? I think you have access to create rules.

@avivey what do you think about? Maybe we can test with some powerful clicks

This seems to impact mail deliverability to @icloud.com addresses too.

Please "remind" me about this ticket as often as possible, so I will fix it. I have everything I need to actually fix this, except the willpower.

We should maybe rewrite a bit the proposed solution, since ideally it's possible to use upstream.phorge.dev but it should be at least reachable to pass some anti-spam checkers I guess. At the moment it isn't:

And my spam filter says:

Maybe relevant, from my Postfix logs:

I agree that an additional status is needed for closing when creating a task. Current statuses are not obvious. "Closed, Graduated" is good to fast decision.

I've created R10 PhorgeIt Extension for this, with a little bit of content. I'll load it to the server shortly.