I’ve noticed a number of times people have asked how to help out small. Rust has started this program [0] where issues that come up have small commitment times. And if you add yourself to a GitHub group you will be notified of all such issues.

Is something similar doable with the bugzilla setup? If an issue is opened and it’s

A) relatively easy
B) small buy can be mentored
C) ?

Then push out an email to everyone on some list?

[0] https://blog.rust-lang.org/inside-rust/2019/10/22/LLVM-ICE-breakers.html

On 23/10/2019 7:06 PM, Aliak wrote:
> I’ve noticed a number of times people have asked how to help out small. Rust has started this program [0] where issues that come up have small commitment times. And if you add yourself to a GitHub group you will be notified of all such issues.
> 
> Is something similar doable with the bugzilla setup? If an issue is opened and it’s
> 
> A) relatively easy
> B) small buy can be mentored
> C) ?
> 
> Then push out an email to everyone on some list?
> 
> [0] https://blog.rust-lang.org/inside-rust/2019/10/22/LLVM-ICE-breakers.html

https://issues.dlang.org/buglist.cgi?keywords=trivial
https://issues.dlang.org/buglist.cgi?keywords=bootcamp

On Wednesday, 23 October 2019 at 06:11:34 UTC, rikki cattermole wrote:
> On 23/10/2019 7:06 PM, Aliak wrote:
>> I’ve noticed a number of times people have asked how to help out small. Rust has started this program [0] where issues that come up have small commitment times. And if you add yourself to a GitHub group you will be notified of all such issues.
>> 
>> Is something similar doable with the bugzilla setup? If an issue is opened and it’s
>> 
>> A) relatively easy
>> B) small buy can be mentored
>> C) ?
>> 
>> Then push out an email to everyone on some list?
>> 
>> [0] https://blog.rust-lang.org/inside-rust/2019/10/22/LLVM-ICE-breakers.html
>
> https://issues.dlang.org/buglist.cgi?keywords=trivial
> https://issues.dlang.org/buglist.cgi?keywords=bootcamp

I figured someone would suggest: "just go search yourself" :) - I should've addressed it in the original post...

Yes, rust has labels as well. A) different participation model (pull vs push). B) you don't know when there's new stuff. C) A ping every now and then on a list you voluntarily want to be on is a good thing as it may ping you at the "right time". D) setup is minimal and produces another avenue for people to get involved and be reminded that they want to be involved.

And ok so the next response is probably going to be something along: "if you're too lazy to go check yourself then there's no point" ... or something. That's a response from someone who just doesn't understand that people work differently. What works for you does not work for another. And having different styles or avenues for getting involved increases reach - which is what you want in an open source project (I assume).

On 23/10/2019 8:10 PM, aliak wrote:
> On Wednesday, 23 October 2019 at 06:11:34 UTC, rikki cattermole wrote:
>> On 23/10/2019 7:06 PM, Aliak wrote:
>>> I’ve noticed a number of times people have asked how to help out small. Rust has started this program [0] where issues that come up have small commitment times. And if you add yourself to a GitHub group you will be notified of all such issues.
>>>
>>> Is something similar doable with the bugzilla setup? If an issue is opened and it’s
>>>
>>> A) relatively easy
>>> B) small buy can be mentored
>>> C) ?
>>>
>>> Then push out an email to everyone on some list?
>>>
>>> [0] https://blog.rust-lang.org/inside-rust/2019/10/22/LLVM-ICE-breakers.html
>>
>> https://issues.dlang.org/buglist.cgi?keywords=trivial
>> https://issues.dlang.org/buglist.cgi?keywords=bootcamp
> 
> I figured someone would suggest: "just go search yourself" :) - I should've addressed it in the original post...
> 
> Yes, rust has labels as well. A) different participation model (pull vs push). B) you don't know when there's new stuff. C) A ping every now and then on a list you voluntarily want to be on is a good thing as it may ping you at the "right time". D) setup is minimal and produces another avenue for people to get involved and be reminded that they want to be involved.
> 
> And ok so the next response is probably going to be something along: "if you're too lazy to go check yourself then there's no point" ... or something. That's a response from someone who just doesn't understand that people work differently. What works for you does not work for another. And having different styles or avenues for getting involved increases reach - which is what you want in an open source project (I assume).

You kinda missed my point.

The lists of bugzilla issues that newbies can do are already curated.
As per you question "Is something similar doable with the bugzilla setup?".

On Wednesday, 23 October 2019 at 07:18:39 UTC, rikki cattermole wrote:
> You kinda missed my point.
>
> The lists of bugzilla issues that newbies can do are already curated.

Let's dial it back a bit though.

It's widely regarded that one of the major successes of Github was to make source control a social platform.

The problem being raised in this thread isn't exactly whether the information exists, it's whether it is in a presentable state for humans.

(The engineers here will have their eyes twitch and raise their fingers... It's cool. I get it. But Bugzilla is hardly a social platform, and isn't the best tool for engaging with people outside of this small community.)

On Wednesday, 23 October 2019 at 08:54:59 UTC, Ethan wrote:

> (The engineers here will have their eyes twitch and raise their fingers... It's cool. I get it. But Bugzilla is hardly a social platform, and isn't the best tool for engaging with people outside of this small community.)

+1

On Wednesday, 23 October 2019 at 07:18:39 UTC, rikki cattermole wrote:
> On 23/10/2019 8:10 PM, aliak wrote:
>> On Wednesday, 23 October 2019 at 06:11:34 UTC, rikki cattermole wrote:
>>> [...]
>> 
>> I figured someone would suggest: "just go search yourself" :) - I should've addressed it in the original post...
>> 
>> Yes, rust has labels as well. A) different participation model (pull vs push). B) you don't know when there's new stuff. C) A ping every now and then on a list you voluntarily want to be on is a good thing as it may ping you at the "right time". D) setup is minimal and produces another avenue for people to get involved and be reminded that they want to be involved.
>> 
>> And ok so the next response is probably going to be something along: "if you're too lazy to go check yourself then there's no point" ... or something. That's a response from someone who just doesn't understand that people work differently. What works for you does not work for another. And having different styles or avenues for getting involved increases reach - which is what you want in an open source project (I assume).
>
> You kinda missed my point.
>
> The lists of bugzilla issues that newbies can do are already curated.
> As per you question "Is something similar doable with the bugzilla setup?".

Maybe I should’ve explained it better. But anyway, similar as in: join a list, get pinged when there’s a new issue that is beginner level.

So that’d mean, when a new issue is labeled as boot camp, is there a list that people can join to be notified.

On 24/10/2019 4:45 AM, Aliak wrote:
> On Wednesday, 23 October 2019 at 07:18:39 UTC, rikki cattermole wrote:
>> On 23/10/2019 8:10 PM, aliak wrote:
>>> On Wednesday, 23 October 2019 at 06:11:34 UTC, rikki cattermole wrote:
>>>> [...]
>>>
>>> I figured someone would suggest: "just go search yourself" :) - I should've addressed it in the original post...
>>>
>>> Yes, rust has labels as well. A) different participation model (pull vs push). B) you don't know when there's new stuff. C) A ping every now and then on a list you voluntarily want to be on is a good thing as it may ping you at the "right time". D) setup is minimal and produces another avenue for people to get involved and be reminded that they want to be involved.
>>>
>>> And ok so the next response is probably going to be something along: "if you're too lazy to go check yourself then there's no point" ... or something. That's a response from someone who just doesn't understand that people work differently. What works for you does not work for another. And having different styles or avenues for getting involved increases reach - which is what you want in an open source project (I assume).
>>
>> You kinda missed my point.
>>
>> The lists of bugzilla issues that newbies can do are already curated.
>> As per you question "Is something similar doable with the bugzilla setup?".
> 
> Maybe I should’ve explained it better. But anyway, similar as in: join a list, get pinged when there’s a new issue that is beginner level.
> 
> So that’d mean, when a new issue is labeled as boot camp, is there a list that people can join to be notified.

https://issues.dlang.org/query.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=VERIFIED&keywords=bootcamp%2C trivial%2C &keywords_type=anywords&order=bug_status%2Cpriority%2Cassigned_to%2Cbug_id&product=D&query_format=advanced&query_type=advanced&resolution=---&known_name=trivial%2Fbootcamp issues

This it the query you want.

In theory bugzilla can send out as an email via its whining feature. However I have no idea if its configured and setup, or its just that I don't know bugzilla very well ;)

It won't be a good experience, but in theory it should be possible with everything in place right now.

On Wednesday, 23 October 2019 at 08:54:59 UTC, Ethan wrote:
> On Wednesday, 23 October 2019 at 07:18:39 UTC, rikki cattermole wrote:
>> You kinda missed my point.
>>
>> The lists of bugzilla issues that newbies can do are already curated.
>
> Let's dial it back a bit though.
>
> It's widely regarded that one of the major successes of Github was to make source control a social platform.
>
> The problem being raised in this thread isn't exactly whether the information exists, it's whether it is in a presentable state for humans.
>
> (The engineers here will have their eyes twitch and raise their fingers... It's cool. I get it. But Bugzilla is hardly a social platform, and isn't the best tool for engaging with people outside of this small community.)

You can track (+vote) the progress of the migration to GitHub here:

https://github.com/dlang/projects/issues/43