@ibuchanan @Anthony , As part of RFC-29 I’ve asked what the process is for escalating an RFC: [image] RFC-29: App Access Rule - Revised followup to New Data Access APIs Request for Comments (RFC) @ibuchanan , can you please outline the process for escalating an RFC? As me…

@remie , Per RFC-1 which defines RFCs , there isn’t an RFC-specific escalation path. Indeed, your argument from suboptimization applies here: I don’t want to establish an escalation policy for 1 practice, when the problem described (suboptimization) applies equally to early access programs, change lo…

Hi @ibuchanan , Please not that the issue that I’m trying to escalate is the introduction of Cloudevents, not ARI. I’m not against ARI per se, the problem is that it is not documented anywhere and is not accepted by any other REST endpoint. But I’m sure @JustinThirkell will give us the required co…

@remie , Ah, thanks for clarifying that you’re more concerned about CloudEvents. I’ll focus on this in discussion with @JustinThirkell . That said, I know that Justin had considered that in the change from RFC-25 to RFC-29. He wrote: We’ve noted Partners’ concerns about the use of another standard …

@ibuchanan I think the RFC’s intention are good. However there have been cases where it feels like it’s a rubber stamping approach. This is obviously not your (and Atlassians) intention with it. Part of it is that communication is happening in stages. It’s all in the forum. It would be awesome if e…

RFC escalation policy

General

JustinThirkell October 19, 2023, 4:00am 6

Hi @ibuchanan, @remie,

I have added a reply to this thread - but I have done so in the RFC itself, rather than in this thread which is about how/where to escalate RFC concerns. To continue the conversation about Cloudevents specifically, let’s keep it over there.