To be clear Justin’s red flags are here: 
https://github.com/apache/comdev-working-groups/blob/main/wg-sharpeners/red-flags.md

> On Feb 14, 2024, at 11:46 AM, Phil Steitz <phil.ste...@gmail.com> wrote:
> 
> I guess I am too late here, but fwiw, I agree strongly with Rich's
> comment.  I would much rather see the checklisty stuff incorporated into
> either the use cases or the main doc somewhere and not presented as "things
> 'we' are looking for".  I do not like at all the statement in the intro to
> the new doc,

I agree with Phil and would also add that this list of red flags is repetitive 
and is not a definitive list. It completely lacks nuance and you could 
reasonably bike shed what color of flag each of Justin’s signals deserves.

> "However, having an idea of what red flags we're looking for
> in a project can be a helpful way to start looking for places to mentor,
> and sharpen, our projects."
> 
> That is absolutely the wrong message to give.  Who is "we"?   This kind of
> thing sets the tone of the working group as some kind of external policing
> / inspecting function.  That will not help.

I’ve seen the impact of this list being to provide many disjoint concerns 
instead of carefully providing a list of concerns and assuming good intention 
from the PMC about one or more Members concerns. A scattershot approach is not 
respectful of the PMC.

> What *will help* is people showing up, listening and coming up with useful
> suggestions for how to solve problems that communities are facing.  In some
> cases, that may actually mean helping them explain why their way of doing
> things is perfectly fine.  I was shocked, for example, by "too many release
> candidates"  on the list of "red flags."   That is ridiculous, IMO, and
> nobody's business but the community.

My reaction as well. There can be many more RCs for x.y.0 than for x.y.4.

Regards,
Dave

> A sharpener certainly might help
> share experience about how other projects have handled packaging, testing
> and deployment issues, but just jumping in because a few releases have
> burned through a few RC numbers makes zero sense.
> 
> Phil
> 
> 
> 
> On Wed, Feb 14, 2024 at 7:39 AM Rich Bowen (Jira) <j...@apache.org> wrote:
> 
>> 
>>    [
>> https://issues.apache.org/jira/browse/COMDEV-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817400#comment-17817400
>> ]
>> 
>> Rich Bowen commented on COMDEV-543:
>> -----------------------------------
>> 
>> Added to doc in https://github.com/apache/comdev-working-groups/pull/2
>> 
>>> Sharpeners use cases
>>> --------------------
>>> 
>>>                Key: COMDEV-543
>>>                URL: https://issues.apache.org/jira/browse/COMDEV-543
>>>            Project: Community Development
>>>         Issue Type: Improvement
>>>         Components: Comdev
>>>           Reporter: Phil Steitz
>>>           Priority: Minor
>>>        Attachments: use-cases.md
>>> 
>>> 
>>> Brain dump of ideas for sharpeners use cases
>> 
>> 
>> 
>> --
>> This message was sent by Atlassian Jira
>> (v8.20.10#820010)
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> For additional commands, e-mail: dev-h...@community.apache.org
>> 
>> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Reply via email to