The Open App Standard and Kit are the best we have in terms of interoperability standards for Drupal. But both have languished in relative stasis.

There are now many players potentially interested in and dependent on interoperability. Some are present for example in the Apps issue queue, but the broader discussions are lacking. And some key players are notably absent.

One potential model would be to convene a group that takes responsibility for the OAS and Kit standards.

Comments

febbraro’s picture

febbraro commented
Component: Code » Open App Standard

Before we work out some big plan to have a governing body for these documents, lets just focus on getting them some updates. I can take the lead on the OAS with input from nedjo, populist, and any others that want to be involved. As far as Kit is concerned, that is in the hands of Grayside currently. He has been very receptive to updates/changes, but I don't think many have taken him up on it.

In the meantime, I have created a component in this issue queue for Open App Standard that we can begin filing tickets against. Ideally, we could manage that in a place that is much better for editing/formatting/displaying than g.d.o. Those tools are just awful for a doc like that. Any suggestions other than the obvious one of GitHub?

nedjo’s picture

nedjo
he/him/his
Primary language English
commented

It's true that the drupal.org tools aren't ideal, but I think we're best off trying to use them rather than pushing out to a less visible location. If we work wording through in an issue, the actual patch will be trivial.

There are probably many reasons that Kit has languished, but pushing text edits to Github hasn't in itself helped.

I've started digging into the work of updating and expanding the Kit features spec. Posted a bunch of issues on Kit, http://drupal.org/project/issues/kit.

For starters, we should get Kit updated for 7.x. Issue: #1455796: [meta] Create a D7 "version" of Kit.