+1 option 1 On Fri, Oct 28, 2022 at 9:17 PM VICTOR MANUEL ROMERO RODRIGUEZ < [email protected]> wrote:
> -1 Don't like it. The developers of the new features, fixes are aware of > the changes that affect the functional issues reported by users. Devs and > users should be connected in the same channel. > > El vie, 28 oct 2022 a las 13:57, Ed Cable (<[email protected]>) escribió: > >> +1 to option #1 but let's determine if we call it user or users - our >> previous incarnation of a Fineract User Mailing lists was just singular in >> [email protected] - if we kept it the same, could have same >> historical archive (albeit with a 4 year gap since 2018. >> >> Also, Mifos continues to maintain a #help channel in its slack workspace >> to try to help with support and general user inquiries as well. The >> mifos-users and mifos-developer lists still exist too given they cover >> questions/topics related to usage/UI/etc which technically aren't part of >> the Fineract 1.x solution stack. >> >> E >> >> On Fri, Oct 28, 2022 at 11:30 AM James Dailey <[email protected]> >> wrote: >> >>> Hi Devs - >>> >>> A few years ago we decided to collapse the [email protected] and >>> [email protected] listservs to have one place for discussions. >>> >>> This had the advantage of reducing the number of lists one needed to >>> subscribe to. >>> >>> The disadvantage is that we may - from time to time - get users who >>> simply want to know how to "run the software" and "how to use the software" >>> rather than "how to set up the dev environment", "how to describe an issue >>> in a ticket", "how to make a code contribution", or "go deep into technical >>> discussion abc". >>> >>> I'd like to offer two proposals for discussion: >>> >>> 1) Set up [email protected] and encourage users to move over >>> there with questions - keep this separate; obviously can be viewed or >>> subscribed to by anyone. >>> Hold a regular "user meeting" to establish some good Q&A for users. We >>> would want to have a few Contributors on the list to answer questions and >>> generally move that conversation along. >>> Alongside [email protected] would be some wiki pages to orient >>> the users. >>> With this, [email protected] becomes more focused on development >>> practices, tickets, commits, engineering design discussions. >>> >>> alternatively: >>> 2) Direct newcomers and users to a page on the wiki where we link to >>> various resources, including outside resources. When a person signs up >>> for the listserv, or shows up, we ask them to first go through those >>> resources, and if they still have questions for Dev, then we encourage >>> that. >>> >>> I believe that coming to the project cold can be quite baffling. >>> >>> This is a DISCUSS thread, meaning please comment. Quick reactions >>> could be: >>> +1 Like it >>> 0 No opinion or neutral >>> -1 Don't like it. >>> >>> >>> Thanks, >>> @jdailey >>> >> >> >> -- >> *Ed Cable* >> President/CEO, Mifos Initiative >> [email protected] | 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> >> >>
