Hello,

If we split the list for DEV and USERS there is a possibility of losing
some queries/replies because I think that nowadays the know-how to use
fineract is more on the DEVELOPER side, currently there
are few FUNCTIONAL/BUSINESS USERS (my opinion) that actively reply to
questions raised by USERS.

For the people the instructions must be clear how to subscribe/unsubscribe
and how to send queries and which topics are covered in the mailing list.

And for the functional users on this mailing list the invitation is open to
help/reply to functional Apache Fineract questions.

Regards









El vie, 24 may 2024 a las 11:20, James Dailey (<jdai...@apache.org>)
escribió:

> Devs -
>
> Q1: Should we redefine this listserv as “primary aimed at the developer
> community of Fineract”.
>
> This listserv doesn’t get a lot of traffic but it is the main public
> discussion for the project.
>
> Originally we had a “us...@fineract.apache.org” but decided to close that
> down. Q2:  Should be bring it back?
>
> Sometimes users come here w configuration questions or set up questions
> that are, to me, a distraction and make this listserv sometimes noisy.
>
> If the users are also devs w an intention to contribute to the project,
> then that’s great but I think that’s a relatively small group.  They can
> self select.
>
> But, then, where should “users” go for help?  Should we send them to
> outside groups like Mifos which has a user listserv for the front end UI
> (that maybe some users don’t know is actually Fineract under the hood) or
> to a slack channel run by a third party?
>
> And who is a User?  This might be a can of worms but I consider the users
> of the project to be the  “IT teams” at an institution or a third party
> vendor doing implementations.
>
> End users (e.g. loan officers or product managers) should not be here
> unless it’s for giving really specific ideas for requirements in which case
> they’re more of the “banking expert” user that helps us serve end users and
> beneficiaries better.
>
> James
>

Reply via email to