Re: Dev vs User Mailing Lists

Hi Joan, On Wed, Oct 17, 2018 at 9:18 PM Joan Touzet wrote: > ...I'm firmly of the opinion that you can't completely ignore real-time > communications and expect 100% of everything to occur asynchronously > on mailing lists I totally agree with that, as you say synchronous discussions will

Re: Dev vs User Mailing Lists

: "Bertrand Delacretaz" > To: "dev" > Cc: d...@fineract.apache.org, "Myrle Krantz" , > mifos-develo...@lists.sourceforge.net, mifos-us...@lists.sourceforge.net, > u...@fineract.apache.org > Sent: Wednesday, October 17, 2018 12:04:27 PM > Subject: Re:

Re: Dev vs User Mailing Lists

ceforge.net, mifos-us...@lists.sourceforge.net, u...@fineract.apache.org Sent: Wednesday, October 17, 2018 12:04:27 PM Subject: Re: Dev vs User Mailing Lists On Tue, Oct 16, 2018 at 7:46 PM wrote: > > ...[ASIDE] Realtime communications are not inclusive... FWIW there was a good discussion about

Re: Dev vs User Mailing Lists

Thanks for sharing that Bertrand - it was a good read - and easy for you to share because it was discussed publicly on a mailing list :) On that thread as well there was also a lot of support for a discourse-based forum too which can be a nice happy medium offering the advantages of a mailing

Re: Dev vs User Mailing Lists

On Tue, Oct 16, 2018 at 7:46 PM wrote: > > ...[ASIDE] Realtime communications are not inclusive... FWIW there was a good discussion about this recently in Apache Arrow: https://lists.apache.org/thread.html/8433cda04dc9e1d6bb235e4f29bde30d07c3e5d81177af785af177f2@%3Cdev.arrow.apache.org%3E

Re: Dev vs User Mailing Lists

ifos-users'; u...@fineract.apache.org Subject: RE: Dev vs User Mailing Lists A single list with good subjects is far better, from a community building perspective, than multiple lists with reduced visibility across those lists. Think about going to some social event where you don't know anyone. Is it e

RE: Dev vs User Mailing Lists

ay, October 15, 2018 10:33 AM To: Dev ; Myrle Krantz Cc: Mifos software development ; mifos-users ; u...@fineract.apache.org; dev@community.apache.org Subject: Re: Dev vs User Mailing Lists Circling back to the original topic of discussion on this thread, given the volume on the user ma

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

Re: Dev vs User Mailing Lists

Javier, Thanks for the suggestion about a WhatsApp group - I agree that a user-friendly more real-time chat tool is a nice complement to mailing lists but by no means a replacement. I agree with all the feedback shared by Mark and Myrle and don't really think WhatsApp might be the most ideal tool

Re: Dev vs User Mailing Lists

Thanks all for your comments, there are strong arguments against Whatsapp, and it seems that the biggest one is that cannot be stored on ASF servers (for now?). Hipchat is good, but Whatsapp is ubiquitous and for many of us, number 1 messaging and communication tool. We just need to lower the

Re: Dev vs User Mailing Lists

On Sat, Oct 13, 2018 at 10:09 PM Javier Borkenztain wrote: > > ...I really enjoyed the presentation > James > Dailey shared a couple of months ago... Great reference, thank you! (BTW https://jira.mongodb.org/browse/PYTHON-532

Re: Dev vs User Mailing Lists

On Sun, Oct 14, 2018 at 3:47 PM Shawn Heisey wrote: > ...I suspect that it's a little > bit odd within Apache for a dev list to be larger than a user list... It depends on the "shape" of your community. The rationale for recommending that (most) Apache podlings initially get a dev list only is

Re: Dev vs User Mailing Lists

On 10/10/2018 9:59 AM, Ed Cable wrote: 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

Re: Dev vs User Mailing Lists

Hey all, We already have a hipchat channel: https://apache.hipchat.com/chat/room/4661218 I will not go to a WhatsApp group for Fineract for the following reasons: * Splitting my communications across 9+ communication applications has made it near impossible for me to track all of the questions

Re: Dev vs User Mailing Lists

Repeating (with minor edits for this context) what I have said on similar topics on other threads: I don't think a WhatsApp group is a good idea. The criteria that the ASF looks for in communication channels used by projects are (in no particular order): - open to all - asynchronous - available

Re: Dev vs User Mailing Lists

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

Re: Dev vs User Mailing Lists

www.google.com Xavier.Galindo1972 On Oct 11, 2018 04:53, "Bertrand Delacretaz" wrote: Hi, On Wed, Oct 10, 2018 at 6:00 PM Ed Cable wrote: > ...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 >

Re: Dev vs User Mailing Lists

Hi, On Wed, Oct 10, 2018 at 6:00 PM Ed Cable wrote: > ...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... Until that happens it's

Re: Dev vs User Mailing Lists

Hi all, In my opinion, it's better to have a single consolidated list but each thread would have a tag in the subject. E.g. [Tech] Regarding tech stuff 1... [Announcement] Some Announcement... That would ensure all the info reaching to everyone and also, will give a clear idea whether