Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
Contributor links box has links that are of questionable utility to contributors
Proposed resolution
- Novice issues link should filter to only "active" "needs work" and "needs review"
- Link to the new contributor tasks documentation page https://drupal.org/new-contributors
- link to /getting-involved
- remove bug bingo
- remove patch bingo
- remove drupal talk
Remaining tasks
- (done) request d.o environment - https://drupal.org/node/1018084
- (done) Find block and alter
- (done) export feature
- (done) submit patch
- review
User interface changes
Yes, cleaning up relevant links in contributor tasks block, but not introducing any new uswer interface pattern
Before |
After |
API changes
No
Comments
Comment #1
realityloopuploaded before image
Comment #2
realityloopPatch attached
Comment #3
realityloopComment #4
XanoCan we change this to "Issue queues" for more clarity?
Any link points to the web, but these are special! Let's make this heading more descriptive. What about "Interact with the community" or something similar that usesthe word "community"?
Comment #5
realityloopUpdated patch attached
Comment #6
realityloopheres the interdiff
Comment #7
XanoLooks good! I'd like to confirm that this has been discussed by @YesCT and @realityloop at the Drupalcon Austin sprint, so multiple people have gone over this change.
Comment #8
tvn CreditAttribution: tvn commentedComment #9
dwwMostly +1 to all this, thanks!
However, if memory serves me, this is the *only* place we link to the patch bingo stuff. If we're really killing those links, we should probably kill the corresponding code that provides the pages that they link to. Or are those links present in other landing pages and such on d.o outside of this block?
Also, I'm not sure that 3 people discussing this (at a sprint or via this issue) constitutes enough of a mandate for this change. But I'm out of the loop on d.o governance and teams and such. Apologies if I'm not understanding the context. :) But, personally, I'd like to see a bit more discussion/agreement before we commit/deploy.
If I'm wrong about both (quite possible) feel free to do it anyway. ;)
Thanks again,
-Derek
Comment #10
YesCT CreditAttribution: YesCT commentedYeah, I looked at these changes also. And I think they are good.
Options for how to proceed...
we could git blame the addition of the things we are taking out, and find out what issue added them, and post a comment on them...
but I think it's ok to get a few thumbs up here.
I'm not sure about the reordering of the links.
Planet seems to be best thing to list first...
where those just changed to alphabetical?
And... I think there was a small change since the after picture in the summary, so we need a new after picture.
Comment #11
realityloopUpdated
Comment #12
realityloopComment #13
realityloopComment #14
YesCT CreditAttribution: YesCT commentedwhy does the screenshot still say Queues instead of Issue queues?
Comment #15
Bojhan CreditAttribution: Bojhan commentedI am not going to do this without data. We really need to know how often each of these links are used. This is all based too much on a hunch on what is used and we simply do not know at this time.
Apart from that the queues section is incredibly large which makes it harder to scan. I'd prefer if we break it up in more parts.
Comment #16
drummThis is in the http logs. For a recent day of logs, 11 ~people (measured by IP address) played bingo 41 times. 25 of those was one person.
(Personally, I'd like to see bingo re-done with an actual 5×5 square and a free space. But I'm not about to write all the code for that in reality.)
Comment #17
drummExcept for removing bingo, this looks good to go.
I'd be on okay with removing bingo myself. Fixing a random thing in a random contrib project isn't something I'd want to ask someone to do in today's contrib. And core likes to really focus on fixing specific sets of issues, like beta blockers.
Comment #18
xjmCan someone check GA to address Bojhan's question in #15? Or can we move the removal of the bingo thing to a separate issue and commit the rest?
(I'm also in favor of removing the bingo but want to try to make incremental change if we can.) :)
Comment #19
Bojhan CreditAttribution: Bojhan commentedI am fine with not addressing my concern, I have asked for a GA thing before - and it just takes super long for it to be picked up. Lets proceed here without any data.
Its not something you can quickly pull out, you will need to add tracking.
Comment #20
drumm#16 was meant to show the usage. It isn't used much.
Comment #21
xjmCool, so sounds like the patch is good then. What's the link to the dev site? Can we rebuild it and get current screenshots, so we can RTBC this?
Comment #23
drummComment #24
drummThis is now deployed on Drupal.org.