Re: GoodFirstBug lists

[Mason Freed]

Quick apology, the "hotlist" version links in this email should have pointed to https://issues.chromium.org/hotlists/5483263.

Thanks,

Mason

On Wed, Jan 8, 2025 at 3:19 PM Mason Freed <mas...@chromium.org> wrote:

TL;DR: I'm planning to delete the "custom field" version of the GoodFirstBugs list, and leave only the "hotlist" version of that list. Please speak up soon if that will break your process. 

------

This is a quick PSA about the "GoodFirstBug" lists. I use the plural "lists" because we currently have two of these. The first list is the "custom field" version, which was created during the migration away from Monorail, and initially contained everything with the Monorail "Hotlist-GoodFirstBug" label, around 5000 total issues. This first list was the "main" list from Monorail, and the migration stored it as a Buganizer custom field called "Chromium Labels" with a value of "GoodFirstBug". The second list is the "hotlist" version, which was also created during the migration from Monorail, but it came from a much-less-used hotlist called "GoodFirstBug" that initially (during the migration) contained about 56 issues. That list, post-migration, expanded to about 150 issues, as people added to it.

As you can guess, the above situation caused some confusion, for a few reasons:

 - Since there are two ways to label a good first bug, some folks chose one and some chose another.

 - The "main list" used a more obscure custom field, rather than a more mainstream hotlist, which caused (more) people to start using the hotlist rather than the custom field.

To avoid these problems, I'm working to eliminate one of the two lists, so we have only a single place to store good first bugs. Generally, since hotlists are the preferred way to handle lists like this in Buganizer, I'd like to eliminate the custom field list entirely. I've already synchronized the lists, so both contain the same list of bugs, as of now. But I wanted to give people time to chime in if there's a good reason *not* to eliminate the custom field version of the good first bugs list from Buganizer. Otherwise, I plan to do that in one week, on January 15, 2025.

Thanks,

Mason

[Mason Freed]

[Nate Fischer]

LGTM to use the hotlist. This is what I've been using since the buganizer migration, so that should work nicely for my team.

Thanks for chasing this down!

[John Davis]

Hello,

What is the purpose of a "GoodFirstBug" list?  I'm thinking it might be bugs which are good for new developers to attempt.  Is that what you mean?

John

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAM%3DNeDjyXrBmmScxb24gHsZbeTo6YTRVpHywo-hy2tGhL0m3%3DA%40mail.gmail.com.

This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.

[Xianzhu Wang]

Perhaps we should just remove (or leave them as is?) the GoodFirstBug label/hotlist for closed bugs, especially old ones. I was surprised when I first read the email notifications for old closed bugs that were added to the GoodFirstBug hotlist.

--

--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.

To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAM%3DNeDh7BYffpXoRJE6g2m-UFBHhGCiA%3DE1ONU6X53-rc0LxHw%40mail.gmail.com.

[Mason Freed]

On Wed, Jan 8, 2025 at 5:51 PM Nate Fischer <ntf...@google.com> wrote:

LGTM to use the hotlist. This is what I've been using since the buganizer migration, so that should work nicely for my team.

Great, thanks for the feedback.

 

On Thu, Jan 9, 2025 at 10:08 AM Xianzhu Wang <wangx...@chromium.org> wrote:

Perhaps we should just remove (or leave them as is?) the GoodFirstBug label/hotlist for closed bugs, especially old ones. I was surprised when I first read the email notifications for old closed bugs that were added to the GoodFirstBug hotlist.

Yeah, that's a good suggestion. My main concern is avoiding confusion in the future about "how" to add a GoodFirstBug label.

[Kranthi Swaroop]

I hope this message finds you well. My name is Kranthi Swaroop, and I have a strong foundation in Java, C++, and Web development.
I am deeply enthusiastic about leveraging my skills to contribute to Chromium and its impactful open-source initiatives. I believe this would be an excellent opportunity for me to collaborate with the community, make a meaningful difference, and gain valuable experience in the process.
I would greatly appreciate it if you could guide me on where to start, how I can align my skill set with Chromium’ goals, and contribute effectively to the organization. Any pointers on existing projects, areas needing contributions.
Thank you for your time and consideration. I look forward to hearing from you and to becoming a productive contributor to the Chromium community.