This is a straw poll to explore support for various options for IndieUI after the end of its current charter period (which is April 30). While the previous survey explored support for various individual options, it has been difficult to find overall support for a given combination.

Each option in this survey proposes actions for the Events and User Context deliverables, and the working Group as a whole. Each option is listed in a numbered list and bold-face type. A list of consequence for each option is provided underneath each one. While this is a complex presentation, it is an attempt to be precise on available paths.

Please consider your level of support for the set of actions together in each question. The goal is to find an overall plan that is supported, even when components of the plan are not everybody's preferred option.

Note: A proposal called Web Accessibility Properties and Actions (WAPA) is being brought to the WebApps Working Group. This has overlapping features with IndieUI Events. The WebApps Working Group would have to sort a single path forward, which could result in IndieUI Events not being continued in that group. In theory the functionality would be continued, but this is a known risk to moving Events to WebApps.

Details for the various options:

1. Shift deliverables to WebApps and CSS and close group:
   • Move Events to the WebApps WG. Any currently projected events they choose not to develop would not advance further.
   • Move User Context to the CSS WG. Any properties and features they choose not to develop would not advance further.
   • Close the IndieUI Working Group.
   • The APA WG may form joint task forces with the other groups to help advance the work, though the deliverables would remain with WebApps / CSS.
2. Shift Events to WebApps and recharter to continue User Context:
   • Move Events to the WebApps WG. Any currently projected events they choose not to develop would not advance further.
   • Recharter IndieUI to work solely on User Context.
   • The APA or IndieUI WG may form a joint task force with WebApps to help advance the work, though the deliverables would remain with WebApps.
   • The IndieUI WG may form a joint task force to work with CSS on areas of mutual interest, such as the privacy model for properties.
   • Note that rechartering to pursue User Context alone may be difficult to gain approval from W3C management and the Advisory Committee. The group would need to feel strongly in favor of this option to pursue it.
3. Shift Events to WebApps, User Context to APA, and close group:
   • Move Events to the WebApps WG. Any currently projected events they choose not to develop would not advance further.
   • Move User Context to the APA WG. User Context might become a component of ARIA in this scenario. It is not known at this time if APA would accept the deliverable.
   • Close the IndieUI Working Group.
   • The APA WG may form a joint task force with WebApps to help advance the work, though the deliverable would remain with WebApps.
   • Note if APA does not accept the deliverable, the fallback is to attempt to recharter IndieUI to work on User Context alone (option 2 above). But that path may not be supported in this survey or may fail later approval stages. Please consider those risks in evaluating this question.
4. Shift deliverables to APA and close group:
   • Move both deliverables to the APA WG. It is not known if APA would accept these deliverables.
   • Close the IndieUI Working Group.
   • The APA WG may form joint task forces with WebApps and CSS to work on issues of common interest, and may publish jointly with those groups.
   • Note we have been informed this approach might draw objections at the Advisory Committee review stage.
5. Shift Events to WebApps, User Context to a Community Group, and close group:
   • Move Events to the WebApps WG. Any currently projected events they choose not to develop would not advance further.
   • Create a Community Group to take over work on User Context with a goal of advancing it back to a W3C Working Group in the future.
   • Close the IndieUI Working Group.
   • The APA WG may form a joint task force with WebApps to help advance the work, though the deliverable would remain with WebApps.
6. Shift deliverables where possible but continue work:
   • Encourage the WebApps WG to take up Events. Any events not taken up would continue development in the IndieUI WG, and either advanced to Recommendation by IndieUI or moved to other groups when more mature.
   • Encourage the CSS WG to take up User Context. Any properties not taken up would continue development in the IndieUI WG, and either advanced to Recommendation by IndieUI or moved to other groups when more mature.
   • Recharter IndieUI to continue work on these deliverables.
   • The IndieUI WG would form joint task forces with the other groups to help advance the work.
   • Note we have been informed this approach might draw objections at the Advisory Committee review stage.
7. Short extension of the current charter to give more time to resolve:
   • This option requires permission from W3C management
   • This allows us to refine the options better, including conducting more specific discussions with the WebApps, CSS, and APA Working Groups.
   • In the meantime, the group could in principle continue work on deliverables as it has been doing.

Please indicate your preference for each option below. To help find an acceptable path, please be generous in marking options as "Yes, but prefer not" instead of "No" whenever you can avoid an absolute objection to the option.

Summary

Ranking of choices in order of least unacceptable/most prefered:

Details