Re: Dev vs User Mailing Lists
Circling back to the original topic of discussion on this thread, given the
volume on the user mailing list is so low and given the feedback on this
thread thus far, I would propose we consolidate into one list and adopt a
policy of appropriately tagging messages in the subject line. This hack on
a mailing list seems an effective way to achieve our desired aim. If and
when, volume grows too much or the dev list becomes unfocused or too
chatty, we can set up the separate user list again.
I will let discussion play out a bit more here and then start a separate
thread with the proposal and just follow lazy consensus if nobody objects.
If we do proceed ahead with that, we should clearly communicate the change
and make known that we have one mailing list for all communications and to
have clearly documented the common tags that we want to establish as the
Would the old list just be made an archive?
@Myrle Krantz <myrle@xxxxxxxxxx> Did you have feedback on the topic of
unifying into one mailing list instead of dev & user?
On Sat, Oct 13, 2018 at 9:23 AM Javier Borkenztain <javier@xxxxxxx> wrote:
> Hi all, +1 on one single list with tags (there are at least 6 lists 😶)
> For the non-technical contributors like me, that most of my contribution to
> the community happens "out of the list", It will be useful to have only one
> place of reference.
> Also, I think we need a Whatsapp group, I am a member of several Whatsapp
> groups on Bitcoin and Blockchain, and they are much more efficient and fast
> to communicate non-technical issues, I've created the group, you can join
> it here: https://chat.whatsapp.com/BVsYOq5eOxqLrvbWnQ3Dck
> I really enjoyed the presentation
> Dailey shared a couple of months ago, the message that we are on the "Open
> Source Age" is as powerful and meaningful as ever.
> More and more Fintechs, Financial Institutions and Banks are joining our
> community and they are our partners and community members, as we grow, we
> need to welcome them, I here propose we can announce each new partner that
> joins our global community, I think Whatsapp group is great for that and
> the community to grow.
> We are changing an entire industry as a community because the community
> outperforms the individuals.
> Let's keep rocking!!
> El mié., 10 oct. 2018 a las 13:00, Ed Cable (<edcable@xxxxxxxxx>)
> > Reading over the escalation guide and the advice it gave on directing
> > appropriate issues/matters to the respective mailing lists, it got me
> > thinking about our Fineract Dev and Fineract User lists.
> > We are always trying to be inclusive especially around awarding merit or
> > committership in valuing non-technical contributions to the project. In
> > that same spirit, I worry we sometimes might be leaving out non-technical
> > members of the community who might only be subscribed to the user list
> > we treat dev as the primary list for all communications
> > etc whether they're technical or not).
> > I know we don't want to clutter the mailing lists and we don't want to
> > cross-post everything across both lists but what do ewe think are some
> > to address this?
> > One possible option is just to consolidate the lists into dev but I don't
> > think that is good long-term because as community grows we will have
> > distinct technical vs. functional/design conversations happening.
> > I know that user list is small but that might be a product of the fact
> > we direct everyone to sign up for dev because most conversations happen
> > dev
> > Should everyone just operate under the norm that dev is the primary list
> > and any public community-related matter or announcement will come through
> > there and that everyone should be subscribed to that list to not miss any
> > key information?
> > Or should we just operate in the fashion of cross-posting to both lists
> > it's relevant to both audiences - that requires extra effort and ensures
> > everybody receives the message but then it does dilute the discussion as
> > input given on @user wouldn't be seen by @Dev <dev@xxxxxxxxxxxxxxxxxxx>
> > CC'ing ComDev too because they probably have some good suggestions based
> > on other projects. However our community might be distinct in that we
> > a larger user-facing community than most more
> > technical/infrastructure-oriented Apache projects.
> > Thanks,
> > Ed
> > ---------- Forwarded message ---------
> > From: Myrle Krantz <myrle@xxxxxxxxxx>
> > Date: Tue, Oct 9, 2018 at 11:41 PM
> > Subject: Escalation guide for project issues
> > To: dev <dev@xxxxxxxxxxxxxxxxxxx>
> > Hey all,
> > An escalation guide for Apache issues was just posted on
> > dev@xxxxxxxxxxxxxxxxxxxx. I wanted to make sure our community was
> > aware of this as well:
> > https://www.apache.org/board/escalation
> > In general, I invite you to discuss problems you see with the Fineract
> > project. Discussion should be done openly, on the
> > dev@xxxxxxxxxxxxxxxxxxx list, or, in some cases,
> > private@xxxxxxxxxxxxxxxxxxx. Addressing problems early and openly
> > will keep most problems from becoming too large to handle.
> > Best Regards,
> > Myrle
> > Committer, Apache Fineract
> > --
> > *Ed Cable*
> > President/CEO, Mifos Initiative
> > edcable@xxxxxxxxx | Skype: edcable | Mobile: +1.484.477.8649
> > *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
> > <http://facebook.com/mifos> <http://www.twitter.com/mifos>
President/CEO, Mifos Initiative
edcable@xxxxxxxxx | Skype: edcable | Mobile: +1.484.477.8649
*Collectively Creating a World of 3 Billion Maries | *http://mifos.org