1. Hi,
2.  
3. Not sure if it is related, but when I tried to look at the commits correcting a bug I was interested on (https://freeswitch.org/jira/browse/FS-10904), I got the message "You don't have access to view all related commits. Please contact your administrator." Looks like the reporter got the same message too.
4.  
5. screenshot: https://imgur.com/y29ysyT
6.  
7.  
8. Best Regards,
9. --
10. Vallimamod Abdullah
11. vma@sip.solutions
12. linkedin.com/in/vallimamod
13. .
14.  
15. > On 26 Jun 2018, at 11:19, David Villasmil <david.villasmil.work@gmail.com> wrote:
16. >
17. > Hello all,
18. > Is this true??? Bug fixes aren't available for the general open source community for EIGHTEEN MONTHS???
19. > This seems REALLY wrong to me... I'm pretty sure there are better ways of making money from freeSWITCH...
20. >
21. > Now I'm very concerned, and probably a lot of people will, if/when they find out about this...
22. >
23. > David
24. >
25. >
26. > On Tue, Jun 26, 2018, 02:57 Matteo via FreeSWITCH-users <freeswitch-users@lists.freeswitch.org> wrote:
27. >
28. >
29. >
30. > ---------- Forwarded message ----------
31. > From: Matteo <mbrancaleoni@voismart.it>
32. > To: freeswitch-users <freeswitch-users@lists.freeswitch.org>
33. > Cc:
34. > Bcc:
35. > Date: Wed, 20 Jun 2018 11:50:26 +0200 (CEST)
36. > Subject: Re: [Freeswitch-users] Enterprise/Production Quality?
37. > Well I agree too.
38. >
39. > Since the introduction of the FSA (term not cited anywhere on website), we started evaluating a subscription.
40. >
41. > But a lot of things are really, really vague and keeping us away:
42. >
43. > * What is in the FSA? What we get for the money?
44. > * What about prices?
45. > * What is the release cycle? When things gets pushed into the OSS version?
46. > * What is the FSA? please add a blog post to clarify this shift in policy and how things "works" from now on.
47. >
48. > Basically there's no communication about that and everything appears really vague.
49. >
50. > Other OSS projects with similar policy have a very clear release path, what is in, what is not,
51. > when new things will appear in OSS and so on.
52. >
53. > And then a suggestion:
54. > Why not offer a "basic" FSA with just access to latest git?
55. > And not provide dedicated support, but use traditional channels?
56. >
57. > This should be cheaper and interesting for companies that are autonomous into investigating and fixing issues by themselves.
58. >
59. > And about bugfixes... well I agree with others... they should be released because affects something that's already out.
60. >
61. > Not doing that may backfire because the OSS product may be perceive buggy (especially if using latest features which may not be debugged properly yet)
62. >
63. > Keep in mind that from a company perspective, if the things are free you can be loose on how the project is handled, because is free after all.
64. > But if you want to get payed (which is completely natural and needed to keep things go on), you must be very clear and communicative on what you give for the price.
65. >
66. > Just my 2 cents.
67. >
68. > Matteo
69. >
70. > ----- Il 30-mag-18, alle 21:00, Michael Avers michael@mailworks.org ha scritto:
71. >
72. > > I agree. I think they are doing it wrong. I obviously believe they need to make
73. > > money and get paid for their work, I have no problem with that at all, and my
74. > > company has bought quite a few licenses of their commercial modules and we
75. > > attend Cluecon every other year. So we have no problem paying but we need to
76. > > know what we are paying FOR.
77. > >
78. > > This kind of vague state of things where you just don't know if bugs are now
79. > > going to be fixed for everyone or just for the privileged ones is not a good
80. > > path to go down.
81. > >
82. > > Bug fixes really should be made available to everyone (assuming they are in
83. > > previously public modules, of course).
84. > >
85. > > The Freeswitch team should focus their efforts on creating commercial modules,
86. > > ready-made apps and setups, pro versions of older modules, say enhanced
87. > > mod_callcenter or whatever. Things like that. But to tell someone to get a
88. > > premium subscription just to get a bug fixed... that's simply wrong.
89. > >
90. > > Just my 2 cents
91. > >
92. > > Mike
93. > >
94. > >
95. > >
96. > >
97. > > On Wed, May 30, 2018, at 11:37 AM, William Simon wrote:
98. > >
99. > >
100. > >