Posted by mitchell on March 25, 2012 at 4:53am
3 followers
Jump to:
| Project: | Rules |
| Version: | 7.x-2.x-dev |
| Component: | Project Maintenance |
| Category: | support request |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed (won't fix) |
Issue Summary
What would you like to see in Rules' next release?
This is the inversion of a support request.
Comments
#1
My opinion:
UX is a huge challenge for Rules, and we need to thoroughly examine issues that affect UX.
We should work toward a release that sanctifies UX and pushes Rules to more general adoption.
Our collective process can be to come up with a set of improvements that will satisfy ours and our users' needs, and reach consensus around timelines that fit our budgets as well.
// Aside
(Speaking of our timelines and budgets, I'm very motivated to do this at the moment and have a relatively high allocation of bandwidth toward this release, so if anyone wants to help keep this flow, now is a good time to contribute, either by participating in the issues or contacting me directly with other ideas and resources. I will try to dedicate some time to prospecting and coordinating with the Snowball Project/ the 501(c)3 People Who Give a Damn, for collection, management, and dispersal of collected funds to givey/needy participants to the initiative. So, if anyone knows anyone or is themselves interested in this, please don't feel shy about helping. Contact me.)
//Continued aside
{As it stands now, this initiative is still gathering steam, requirements, contributors, and resources. It would be nice to move into the next level of activity and progress on more than one front.}
// !back
I think that the next release of Rules should include {x} and be done by {y} because of {z}.
[I'll mad libs that later].
Open questions: What is "UX"? What issues affect UX? What is "more general adoption"? How important is UX compared to other things that we could focus on? What are our users' needs? When do we need these improvements? Who is interested in working on this?
Copied and edited from #1498580: Move rules admin ui to /admin/structure.
#2
+1 for planing, still this is a wishlist which is not going to block continuous improvements and fixes - so I remove the release blocker.
#3
Updated component.
#4
Updated component.
#5
We don't need an issue for this. If we had #135800: Milestone management, explored as well in #1300972: Replace /community-inititaives (and meta issues) with a more structured means of creating initiatives + tracking progress and mentioned in #605512: Convert "API version" to generic milestones and #166631: Support for lifecycle information, in addition to one more where dww mentions that he hacked project_release to support "future releases" on another site... we could have a version node that a subset of the issues currently pointing to -dev would be targeted for.
In the meantime, the only ways I can think of doing this are with a "next release" tag or a "favorite of fago" tag, or a page here or on gdo for tracking the accepted change requests so that contributors can quickly see what are the priorities and then get to work on them. fago, do you have a preference between the two of those or another idea?