fineract-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Stein <>
Subject Re: Concerned about quiet dev@
Date Fri, 01 Apr 2016 09:49:10 GMT
On Fri, Apr 1, 2016 at 4:32 AM, Keith Woodlock <>
> Being bombarded with their notifications through the dev lists de-values
> the dev list for me.

There is an argument for delivering those to dev@, as the set of people
interested in [development, issues, GitHub PRs] is near perfect equality.

But when you add "casual" or "potential" contributors into the mix, they
need to find "touch points" into the community. Apache typically looks to
dev@ for that. But with (as you say) a "bombarded" mailing list will make
that difficult. As a mentor, I did not realize how much traffic the
already-existing community would generate. The ASF typically uses a
notifications@ mailing list to receive such messages. The *default* is to
stick to dev@ for social/transparency reasons.

It may be appropriate to shift those notifications. ... tho I'd also
suggest a deeper change is needed to bring community discussion onto the
dev@ list.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message