@fago & @klausi:
It's been a pleasure working in the issue queue helping to make users' experiences here as productive and helpful as possible. It's been an especially wonderful experience contributing toward your and other developing contributors' work by organizing the information provided from Rules' awesome user base.

A number of times while performing maintenance tasks, I have butted up against the limitation of having to wait for you guys to make very small changes in the components list or I have wanted to make clarifications in the "report an issue" welcome message to fit with related support material reorganization. If you were to give me permission to officially maintain the issue queue, then it would be very helpful during my sprints for when one of these necessary changes comes up, then I would be able to make them and continue on with that change.

I would be happy to file issues (perhaps on a "Rules Issue Queue" component) whenever I make a change just to keep a record. My first task will be to add a component for "GDO Rules Group" in order to address the changes that Itangalo and I talked about today. We have a number of improvements in mind to make that space much more useful for developers and end-users. The second change will be to add more formal instructions to the "report an issue" message in order to refocus the content organization scheme and try to fix accessibility of all our existing information that we have already invested in.

Thanks again for everything, #1269876: Cred to the Rules maintainers!!

Comments

fago’s picture

fago
Primary language German
Location Vienna
commented

mitchell, I really appreciate your efforts but I prefer to keep control of the issue queue myself, as I'll be working with it regularly. Still, I'm open to improvements and I'm happy to discuss them.

Then, I think we should try to re-introduce the rules issue squad and give it more visibility.

I'd like to propose the following:
* Work out the guidelines based upon http://groups.drupal.org/node/135664 and put them in the handbooks.
* Also, let's add a docu page for the issue squad in the rules handbooks and list the members there.
* Grant "Maintain issue queue" permission to all the members, so they can actually assign issues that need input to myself and klausi.
* For better visibility, mention the issue squad at the project page and link to the handbooks. Invite others to join!
* I'd like to nominate someone as head of the issue squad, which tries to coordinate efforts with the squad members, maintains the list of squad members and also coordinates the guide-lines and generally efforts with klausi and me.

Thoughts on that? Maybe you'd like to be the issue squad head? :-)

+1 for improving "report an issue" message and updating the FAQs. If you come up with concrete suggestions I'd be happy to review them and give feedback and/or improve them. I've just granted you "maintain issue" permission, so you can assign those issues needing input to me and klausi.

mitchell’s picture

mitchell commented
Status: Needs review » Fixed

fago, here are the actionable things I'll mention foremost, then talk more about issue queue maintenance and a proper thank you.

Those two items above are what I had in mind that will be big wins for the issue queue. Getting people more involved is what I'm also focusing on now, but, imho, it would be more successful as a follow-up to clearly defined priorities that go into more depth than answering support requests. I think something along the lines of initiatives like improving the docs, getting text/data transforms reviewed and committed, and working on other major groups of issues like list and loops extensions. I'm blanking on other more developer assistance related meta issues at the moment, but currently it's difficult to get a birds eye sense of what's important, at the moment. So, I'm going to try to take care of a bit more groundwork in preparation for a public announcement inviting more involvement. I'm also working on that announcement and a docs update about that group.

Re maintain issue queue permissions:
First off, thank you. I appreciate the gesture of support. I hope to make good use of it, but I'm still trying to figure that out. I'm more familiar with the triage side of managing the issue queue and answering support requests, neither of which require those permissions. You're already picking up on issues, and assigning responsibilities feels weired; as klausi wrote:

the only thing that I feel a little uncomfortable about is the assigning of issues to either me or fago. I want to know about an issue before I get assigned to it, otherwise it feels like somebody just wants to load off some work on my shoulders. I want to pick my work voluntarily. We can use the issue priorities to make important issues more visible.

Also, we should use the full power of the issue queue states. Has a patch been inspected and tested successfully by someone? ==> Mark it RTBC. People tend to classify everything as a bug report ==> filter out the support requests and change the status accordingly.

I'd be happy to be coordinate the effort of on-boarding more contributors. I'll try to finish up the docs updates and prepare a release announcement today.

klausi’s picture

klausi
he/him||they/them
Primary language German
Location 🇦🇹 Vienna
commented

@fago: I just granted mitchell access to the issue queue settings and the project page. I saw your post about feeling uncomfortable a bit too late, but I still think it is justified to grant mitchell access. He is very active in the issue queue and he is ready to do more.

mitchell’s picture

mitchell commented
Component: Miscellaneous » Project Maintenence

klausi & fago: Thank you guys for everything. I'm sincerely humbled to have been given this role in such an important project. Rules has been a priority to me ever since I saw its value, as a non-programmer, at par with CCK and Views for all site building needs. I'll work hard to continue maintaining and advancing its value for all Drupal users and developers.

mitchell’s picture

mitchell commented
Component: Project Maintenence » Project Maintenance

Updated component.

fago’s picture

fago
Primary language German
Location Vienna
commented
Component: Project Maintenance » Forms Support

He is very active in the issue queue and he is ready to do more.

True - it looks like michell made really great progress (++). Thus, I agree that it makes sense to grant michell the editing permission.

@fago: I just granted mitchell access to the issue queue settings and the project page. I saw your post about feeling uncomfortable a bit too late, but I still think it is justified to grant mitchell access.

Still, as pointed out the issue component categorization has impacts on the whole queue - thus changing it is not a small-ish issue. The improvements from #1597940: Update components list are mostly great, but still I'd have expected that important things to be decided in consense. Thus, I'm not happy about how #1597940: Update components list went. For the future I expect any further major changes to the code, issue queue or project page to be discussed with me first.

Howsoever, I know I've been too busy and unavailable recently, sry for that - I'll try to keep up better in future. What do you think about doing bi-weekly IRC meetings for coordinating efforts and/or discussing important issues?

@assigning:
As said, I'm feeling fine with having issues assigned to me as it helps to put issues that need my input on my radar. So feel free to do so.

I'd be happy to be coordinate the effort of on-boarding more contributors. I'll try to finish up the docs updates and prepare a release announcement today.

That' awesome! I'm looking forward to that + thanks a lot for your engagement :-)

fago’s picture

fago
Primary language German
Location Vienna
commented
Component: Forms Support » Project Maintenance

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.