From: David B. <da...@ra...> - 2011-10-12 02:21:15
|
Hello Everyone - OpenBTS Community - About a year ago, the primary developers of this project formed a company, Range Networks, Inc., for the purpose of developing commercial systems based on the OpenBTS stack. Since that time, we (Range) have taken a very hands-off approach with respect to the public release of OpenBTS. We have not been happy with this approach and we know that many in the OpenBTS community have not been happy with it either. Going forward, we will be much more active to ensure that the OpenBTS codebase and community thrive. As a first step, we are releasing OpenBTS P2.8 ("Opelousas") and opening a new Trac system, available here: http://wush.net/trac/rangepublic This release includes many bug-fixes and feature upgrades taken from the current C2.8 commercial release and is architecturally much more similar to the commercial release than any of the forks in public circulation right now. It is our intention, moving forward, to make a corresponding public release for every commercial release, and to track both releases in the same repository to allow easy transfer of code between the two releases. We know there will be some initial questions that we will try to answer immediately. Q: The new Trac makes a lot more references to Range's commercial products and services. Why? A: The development of OpenBTS is and always has been a commercial activity. OpenBTS is our product, even in its free (libre) form, and we will present it and manage it as such. Q: The new repo is SVN instead of git. Why? A: We (Range) use SVN for our internal repo. Keeping the public and commercial releases in the same repo will make it much easier for Range's commercial development team to participate in the public release. Q: Does Range still withhold commercial features from the public release? A: Yes, although we have made policy changes that will keep the two releases more similar moving forward. Q: Does Range still require contributors to the official public release to sign a CLA? A: Generally, yes, but we have made exceptions in some cases. We are reviewing our policy with respect to the CLA and trying to find ways to accommodate a broader range of contributions. Q: The new real-time Asterisk stuff breaks my old dialplans and the ODBC components are hard to install. Why did you do that? A: The new approach is more flexible and scalable. Also, we use this approach in the commercial release and it's important that the public and commercial code-bases are similar so we can continue to make improvements to the public release in the future. We apologize for any inconvenience this upgrade may cause. Q: When will you provide a guest account with write-acces to the new wiki? A: Soon. Q: When will you provide a public ticket tracker in the new wiki? A: Soon. Of course, there will be many other questions not answered here. We will try to address them as directly and promptly as possible. Thanks and Best Regards, David, Harvind and the Range Networks Team David A. Burgess Founder, CEO Range Networks, Inc. 560 Brannan St. San Francisco, CA 94107 USA cell +1 707 208 2622 |
From: Kurtis H. <khe...@cs...> - 2011-10-12 03:08:00
|
Great news! Quick note: 1) Can you call it something other than "public" in the SVN tree? Maybe OpenBTS-public? 2) Those folks who are upset about the git->svn shift should look at git-svn (http://www.viget.com/extend/effectively-using-git-with-subversion/) which provides a git interface to svn. Everyone can be happy! 3) Configure is breaking on "config.status: error: cannot find input file: Transceiver52M/Makefile.in", which, if I remember correctly, is the USRP and should be there. Maybe a check-in oversight? On Tue, Oct 11, 2011 at 7:21 PM, David Burgess <da...@ra...> wrote: > Hello Everyone - > > OpenBTS Community - > > About a year ago, the primary developers of this project formed a company, Range Networks, Inc., for the purpose of developing commercial systems based on the OpenBTS stack. Since that time, we (Range) have taken a very hands-off approach with respect to the public release of OpenBTS. We have not been happy with this approach and we know that many in the OpenBTS community have not been happy with it either. Going forward, we will be much more active to ensure that the OpenBTS codebase and community thrive. > > As a first step, we are releasing OpenBTS P2.8 ("Opelousas") and opening a new Trac system, available here: > > http://wush.net/trac/rangepublic > > This release includes many bug-fixes and feature upgrades taken from the current C2.8 commercial release and is architecturally much more similar to the commercial release than any of the forks in public circulation right now. It is our intention, moving forward, to make a corresponding public release for every commercial release, and to track both releases in the same repository to allow easy transfer of code between the two releases. > > We know there will be some initial questions that we will try to answer immediately. > > Q: The new Trac makes a lot more references to Range's commercial products and services. Why? > A: The development of OpenBTS is and always has been a commercial activity. OpenBTS is our product, even in its free (libre) form, and we will present it and manage it as such. > > Q: The new repo is SVN instead of git. Why? > A: We (Range) use SVN for our internal repo. Keeping the public and commercial releases in the same repo will make it much easier for Range's commercial development team to participate in the public release. > > Q: Does Range still withhold commercial features from the public release? > A: Yes, although we have made policy changes that will keep the two releases more similar moving forward. > > Q: Does Range still require contributors to the official public release to sign a CLA? > A: Generally, yes, but we have made exceptions in some cases. We are reviewing our policy with respect to the CLA and trying to find ways to accommodate a broader range of contributions. > > Q: The new real-time Asterisk stuff breaks my old dialplans and the ODBC components are hard to install. Why did you do that? > A: The new approach is more flexible and scalable. Also, we use this approach in the commercial release and it's important that the public and commercial code-bases are similar so we can continue to make improvements to the public release in the future. We apologize for any inconvenience this upgrade may cause. > > Q: When will you provide a guest account with write-acces to the new wiki? > A: Soon. > > Q: When will you provide a public ticket tracker in the new wiki? > A: Soon. > > > Of course, there will be many other questions not answered here. We will try to address them as directly and promptly as possible. > > Thanks and Best Regards, > > David, Harvind and the Range Networks Team > > > David A. Burgess > Founder, CEO > Range Networks, Inc. > 560 Brannan St. > San Francisco, CA 94107 > USA > cell +1 707 208 2622 > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2d-oct > _______________________________________________ > Openbts-discuss mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openbts-discuss > |
From: Akib S. <aki...@gm...> - 2011-10-12 05:01:27
|
Whoaa its really great waiting to try this one !!!!! documentation is really great.it gives you well and neat information On Wed, Oct 12, 2011 at 8:37 AM, Kurtis Heimerl <khe...@cs...>wrote: > Great news! > > Quick note: > 1) Can you call it something other than "public" in the SVN tree? > Maybe OpenBTS-public? > 2) Those folks who are upset about the git->svn shift should look at > git-svn ( > http://www.viget.com/extend/effectively-using-git-with-subversion/) > which provides a git interface to svn. Everyone can be happy! > 3) Configure is breaking on "config.status: error: cannot find input > file: Transceiver52M/Makefile.in", which, if I remember correctly, is > the USRP and should be there. Maybe a check-in oversight? > > On Tue, Oct 11, 2011 at 7:21 PM, David Burgess <da...@ra...> > wrote: > > Hello Everyone - > > > > OpenBTS Community - > > > > About a year ago, the primary developers of this project formed a > company, Range Networks, Inc., for the purpose of developing commercial > systems based on the OpenBTS stack. Since that time, we (Range) have taken > a very hands-off approach with respect to the public release of OpenBTS. We > have not been happy with this approach and we know that many in the OpenBTS > community have not been happy with it either. Going forward, we will be > much more active to ensure that the OpenBTS codebase and community thrive. > > > > As a first step, we are releasing OpenBTS P2.8 ("Opelousas") and opening > a new Trac system, available here: > > > > http://wush.net/trac/rangepublic > > > > This release includes many bug-fixes and feature upgrades taken from the > current C2.8 commercial release and is architecturally much more similar to > the commercial release than any of the forks in public circulation right > now. It is our intention, moving forward, to make a corresponding public > release for every commercial release, and to track both releases in the same > repository to allow easy transfer of code between the two releases. > > > > We know there will be some initial questions that we will try to answer > immediately. > > > > Q: The new Trac makes a lot more references to Range's commercial > products and services. Why? > > A: The development of OpenBTS is and always has been a commercial > activity. OpenBTS is our product, even in its free (libre) form, and we > will present it and manage it as such. > > > > Q: The new repo is SVN instead of git. Why? > > A: We (Range) use SVN for our internal repo. Keeping the public and > commercial releases in the same repo will make it much easier for Range's > commercial development team to participate in the public release. > > > > Q: Does Range still withhold commercial features from the public release? > > A: Yes, although we have made policy changes that will keep the two > releases more similar moving forward. > > > > Q: Does Range still require contributors to the official public release > to sign a CLA? > > A: Generally, yes, but we have made exceptions in some cases. We are > reviewing our policy with respect to the CLA and trying to find ways to > accommodate a broader range of contributions. > > > > Q: The new real-time Asterisk stuff breaks my old dialplans and the ODBC > components are hard to install. Why did you do that? > > A: The new approach is more flexible and scalable. Also, we use this > approach in the commercial release and it's important that the public and > commercial code-bases are similar so we can continue to make improvements to > the public release in the future. We apologize for any inconvenience this > upgrade may cause. > > > > Q: When will you provide a guest account with write-acces to the new > wiki? > > A: Soon. > > > > Q: When will you provide a public ticket tracker in the new wiki? > > A: Soon. > > > > > > Of course, there will be many other questions not answered here. We will > try to address them as directly and promptly as possible. > > > > Thanks and Best Regards, > > > > David, Harvind and the Range Networks Team > > > > > > David A. Burgess > > Founder, CEO > > Range Networks, Inc. > > 560 Brannan St. > > San Francisco, CA 94107 > > USA > > cell +1 707 208 2622 > > > > > > > ------------------------------------------------------------------------------ > > All the data continuously generated in your IT infrastructure contains a > > definitive record of customers, application performance, security > > threats, fraudulent activity and more. Splunk takes this data and makes > > sense of it. Business sense. IT sense. Common sense. > > http://p.sf.net/sfu/splunk-d2d-oct > > _______________________________________________ > > Openbts-discuss mailing list > > Ope...@li... > > https://lists.sourceforge.net/lists/listinfo/openbts-discuss > > > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2d-oct > _______________________________________________ > Openbts-discuss mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openbts-discuss > -- Akib Sayyed Matrix-Shell aki...@gm... aki...@ma... Mob:- +91-966-514-2243 |
From: David B. <da...@ra...> - 2011-10-12 05:54:11
|
On Oct 11, 2011, at 8:07 PM, Kurtis Heimerl wrote: > Great news! I hope so. Now, if we can get Thomas' hardware support rolled in, we can get back to a unified release. > 3) Configure is breaking on "config.status: error: cannot find input > file: Transceiver52M/Makefile.in", which, if I remember correctly, is > the USRP and should be there. Maybe a check-in oversight? Yes. We removed all of the Makefile.in from most of the rest of the repository. I updated the files. Hopefully, this is fixed. -- David David A. Burgess Founder, CEO Range Networks, Inc. 560 Brannan St. San Francisco, CA 94107 USA cell +1 707 208 2622 |
From: Kurtis H. <khe...@cs...> - 2011-10-12 05:58:40
|
Still not building for me, same error. Can you reproduce it with a clean pull? Always a chance I'm being an idiot. What do you mean you "removed all of the Makefile.in from most of the repository"? There's plenty of those still around... On Tue, Oct 11, 2011 at 10:54 PM, David Burgess <da...@ra...> wrote: > > On Oct 11, 2011, at 8:07 PM, Kurtis Heimerl wrote: > >> Great news! > > I hope so. Now, if we can get Thomas' hardware support rolled in, we can get back to a unified release. > >> 3) Configure is breaking on "config.status: error: cannot find input > >> file: Transceiver52M/Makefile.in", which, if I remember correctly, is >> the USRP and should be there. Maybe a check-in oversight? > > Yes. We removed all of the Makefile.in from most of the rest of the repository. I updated the files. Hopefully, this is fixed. > > -- David > > David A. Burgess > Founder, CEO > Range Networks, Inc. > 560 Brannan St. > San Francisco, CA 94107 > USA > cell +1 707 208 2622 > > |
From: Sylvain M. <24...@gm...> - 2011-10-12 06:07:19
|
> 3) Configure is breaking on "config.status: error: cannot find input > file: Transceiver52M/Makefile.in", which, if I remember correctly, is > the USRP and should be there. Maybe a check-in oversight? Actually all Makefile.in the configure.in and a bunch of other files shouldn't even be there. Those should be a in a tarball release but not in a SVN tree. See http://openbts.git.sourceforge.net/git/gitweb.cgi?p=openbts/openbts;a=commitdiff;h=50006e364d12513be3a8419c42df552754f6b6a6 for files that shouldn't be there. autoreconf -i should renerate all of those. Cheers, Sylvain |
From: Kurtis H. <khe...@cs...> - 2011-10-12 06:10:27
|
This makes more sense. However, that's not working either, the entire Transceiver52M directory isn't present. No amount of reconfing is going to remedy that. On Tue, Oct 11, 2011 at 11:07 PM, Sylvain Munaut <24...@gm...> wrote: >> 3) Configure is breaking on "config.status: error: cannot find input >> file: Transceiver52M/Makefile.in", which, if I remember correctly, is >> the USRP and should be there. Maybe a check-in oversight? > > Actually all Makefile.in the configure.in and a bunch of other files > shouldn't even be there. > Those should be a in a tarball release but not in a SVN tree. > > See http://openbts.git.sourceforge.net/git/gitweb.cgi?p=openbts/openbts;a=commitdiff;h=50006e364d12513be3a8419c42df552754f6b6a6 > for files that shouldn't be there. > > autoreconf -i should renerate all of those. > > Cheers, > > Sylvain > |
From: Thomas T. <tt...@vt...> - 2011-10-12 06:54:28
|
On Wed, Oct 12, 2011 at 2:09 AM, Kurtis Heimerl <khe...@cs...> wrote: > This makes more sense. > > However, that's not working either, the entire Transceiver52M > directory isn't present. No amount of reconfing is going to remedy > that. For the time being, you can delete the Transceiver52M line in configure.ac and it builds fine. My commits are almost ready for merge; the biggest obstacle right now is that I'm travelling for the rest of the week. I don't expect the final testing and svn merge to take much time after I return this weekend. Thomas |
From: David A. B. <dbu...@jc...> - 2011-10-12 07:39:23
|
Yes, there's something screwed up here with that directory. I'll fix it ASAP. On Oct 11, 2011, at 11:09 PM, Kurtis Heimerl wrote: > This makes more sense. > > However, that's not working either, the entire Transceiver52M > directory isn't present. No amount of reconfing is going to remedy > that. |
From: Sylvain M. <24...@gm...> - 2011-10-12 06:20:36
|
Hi David, Great news about the release and good to know that Range Networks will try to be more interactive with the community from now on. Looking at the code tough I'm a bit disappointed that the external fixes that were submitted to the git repository by people with CLA haven't been merged and seems to have been lost with this new release. (e.g. just talking about my stuff, all the GSMTap updates are not present) :( Cheers, Sylvain |
From: Alexander C. <ale...@gm...> - 2011-10-15 10:19:06
|
Hi David, Great news! We'll give it a try soon here. Manual you wrote is exceptionally cool. Thank you for that. Though I found some bugs and typos in it. How should I submit them? Copyright on the manual states "do not reproduce or redistribute without permission". Do you really think it's a good way for a manual for an open-source product? On Wed, Oct 12, 2011 at 06:21, David Burgess <da...@ra...> wrote: > Hello Everyone - > > OpenBTS Community - > > About a year ago, the primary developers of this project formed a company, Range Networks, Inc., for the purpose of developing commercial systems based on the OpenBTS stack. Since that time, we (Range) have taken a very hands-off approach with respect to the public release of OpenBTS. We have not been happy with this approach and we know that many in the OpenBTS community have not been happy with it either. Going forward, we will be much more active to ensure that the OpenBTS codebase and community thrive. > > As a first step, we are releasing OpenBTS P2.8 ("Opelousas") and opening a new Trac system, available here: > > http://wush.net/trac/rangepublic > > This release includes many bug-fixes and feature upgrades taken from the current C2.8 commercial release and is architecturally much more similar to the commercial release than any of the forks in public circulation right now. It is our intention, moving forward, to make a corresponding public release for every commercial release, and to track both releases in the same repository to allow easy transfer of code between the two releases. > > We know there will be some initial questions that we will try to answer immediately. > > Q: The new Trac makes a lot more references to Range's commercial products and services. Why? > A: The development of OpenBTS is and always has been a commercial activity. OpenBTS is our product, even in its free (libre) form, and we will present it and manage it as such. > > Q: The new repo is SVN instead of git. Why? > A: We (Range) use SVN for our internal repo. Keeping the public and commercial releases in the same repo will make it much easier for Range's commercial development team to participate in the public release. > > Q: Does Range still withhold commercial features from the public release? > A: Yes, although we have made policy changes that will keep the two releases more similar moving forward. > > Q: Does Range still require contributors to the official public release to sign a CLA? > A: Generally, yes, but we have made exceptions in some cases. We are reviewing our policy with respect to the CLA and trying to find ways to accommodate a broader range of contributions. > > Q: The new real-time Asterisk stuff breaks my old dialplans and the ODBC components are hard to install. Why did you do that? > A: The new approach is more flexible and scalable. Also, we use this approach in the commercial release and it's important that the public and commercial code-bases are similar so we can continue to make improvements to the public release in the future. We apologize for any inconvenience this upgrade may cause. > > Q: When will you provide a guest account with write-acces to the new wiki? > A: Soon. > > Q: When will you provide a public ticket tracker in the new wiki? > A: Soon. > > > Of course, there will be many other questions not answered here. We will try to address them as directly and promptly as possible. > > Thanks and Best Regards, > > David, Harvind and the Range Networks Team > > > David A. Burgess > Founder, CEO > Range Networks, Inc. > 560 Brannan St. > San Francisco, CA 94107 > USA > cell +1 707 208 2622 > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2d-oct > _______________________________________________ > Openbts-discuss mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openbts-discuss > -- Regards, Alexander Chemeris. |
From: Akib S. <aki...@gm...> - 2011-10-15 12:05:56
|
i am completely agree with Alexander On Sat, Oct 15, 2011 at 3:48 PM, Alexander Chemeris < ale...@gm...> wrote: > Hi David, > > Great news! > We'll give it a try soon here. > > Manual you wrote is exceptionally cool. Thank you for that. > Though I found some bugs and typos in it. How should I submit them? > > Copyright on the manual states "do not reproduce or redistribute > without permission". Do you really think it's a good way for a manual > for an open-source product? > > On Wed, Oct 12, 2011 at 06:21, David Burgess <da...@ra...> > wrote: > > Hello Everyone - > > > > OpenBTS Community - > > > > About a year ago, the primary developers of this project formed a > company, Range Networks, Inc., for the purpose of developing commercial > systems based on the OpenBTS stack. Since that time, we (Range) have taken > a very hands-off approach with respect to the public release of OpenBTS. We > have not been happy with this approach and we know that many in the OpenBTS > community have not been happy with it either. Going forward, we will be > much more active to ensure that the OpenBTS codebase and community thrive. > > > > As a first step, we are releasing OpenBTS P2.8 ("Opelousas") and opening > a new Trac system, available here: > > > > http://wush.net/trac/rangepublic > > > > This release includes many bug-fixes and feature upgrades taken from the > current C2.8 commercial release and is architecturally much more similar to > the commercial release than any of the forks in public circulation right > now. It is our intention, moving forward, to make a corresponding public > release for every commercial release, and to track both releases in the same > repository to allow easy transfer of code between the two releases. > > > > We know there will be some initial questions that we will try to answer > immediately. > > > > Q: The new Trac makes a lot more references to Range's commercial > products and services. Why? > > A: The development of OpenBTS is and always has been a commercial > activity. OpenBTS is our product, even in its free (libre) form, and we > will present it and manage it as such. > > > > Q: The new repo is SVN instead of git. Why? > > A: We (Range) use SVN for our internal repo. Keeping the public and > commercial releases in the same repo will make it much easier for Range's > commercial development team to participate in the public release. > > > > Q: Does Range still withhold commercial features from the public release? > > A: Yes, although we have made policy changes that will keep the two > releases more similar moving forward. > > > > Q: Does Range still require contributors to the official public release > to sign a CLA? > > A: Generally, yes, but we have made exceptions in some cases. We are > reviewing our policy with respect to the CLA and trying to find ways to > accommodate a broader range of contributions. > > > > Q: The new real-time Asterisk stuff breaks my old dialplans and the ODBC > components are hard to install. Why did you do that? > > A: The new approach is more flexible and scalable. Also, we use this > approach in the commercial release and it's important that the public and > commercial code-bases are similar so we can continue to make improvements to > the public release in the future. We apologize for any inconvenience this > upgrade may cause. > > > > Q: When will you provide a guest account with write-acces to the new > wiki? > > A: Soon. > > > > Q: When will you provide a public ticket tracker in the new wiki? > > A: Soon. > > > > > > Of course, there will be many other questions not answered here. We will > try to address them as directly and promptly as possible. > > > > Thanks and Best Regards, > > > > David, Harvind and the Range Networks Team > > > > > > David A. Burgess > > Founder, CEO > > Range Networks, Inc. > > 560 Brannan St. > > San Francisco, CA 94107 > > USA > > cell +1 707 208 2622 > > > > > > > ------------------------------------------------------------------------------ > > All the data continuously generated in your IT infrastructure contains a > > definitive record of customers, application performance, security > > threats, fraudulent activity and more. Splunk takes this data and makes > > sense of it. Business sense. IT sense. Common sense. > > http://p.sf.net/sfu/splunk-d2d-oct > > _______________________________________________ > > Openbts-discuss mailing list > > Ope...@li... > > https://lists.sourceforge.net/lists/listinfo/openbts-discuss > > > > > > -- > Regards, > Alexander Chemeris. > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2d-oct > _______________________________________________ > Openbts-discuss mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openbts-discuss > -- Akib Sayyed Matrix-Shell aki...@gm... aki...@ma... Mob:- +91-966-514-2243 |
From: <da...@ra...> - 2011-10-15 17:17:14
|
Alexander - Send the "patches" to me and we will update the manual. Since the distribution restriction may be in conflict with GPL, we will probably remove the manual from the doc directory and just put it on the website. It is gratis-free but not libre-free. We don't want to make it libre-free because we don't want it forked. -- David -- David Sent from my Verizon Wireless BlackBerry -----Original Message----- From: Alexander Chemeris <ale...@gm...> Date: Sat, 15 Oct 2011 14:18:39 To: David Burgess<da...@ra...> Cc: ope...@li... List<ope...@li...> Subject: Re: [Openbts-discuss] new P2.8 release and Trac Hi David, Great news! We'll give it a try soon here. Manual you wrote is exceptionally cool. Thank you for that. Though I found some bugs and typos in it. How should I submit them? Copyright on the manual states "do not reproduce or redistribute without permission". Do you really think it's a good way for a manual for an open-source product? On Wed, Oct 12, 2011 at 06:21, David Burgess <da...@ra...> wrote: > Hello Everyone - > > OpenBTS Community - > > About a year ago, the primary developers of this project formed a company, Range Networks, Inc., for the purpose of developing commercial systems based on the OpenBTS stack. Since that time, we (Range) have taken a very hands-off approach with respect to the public release of OpenBTS. We have not been happy with this approach and we know that many in the OpenBTS community have not been happy with it either. Going forward, we will be much more active to ensure that the OpenBTS codebase and community thrive. > > As a first step, we are releasing OpenBTS P2.8 ("Opelousas") and opening a new Trac system, available here: > > http://wush.net/trac/rangepublic > > This release includes many bug-fixes and feature upgrades taken from the current C2.8 commercial release and is architecturally much more similar to the commercial release than any of the forks in public circulation right now. It is our intention, moving forward, to make a corresponding public release for every commercial release, and to track both releases in the same repository to allow easy transfer of code between the two releases. > > We know there will be some initial questions that we will try to answer immediately. > > Q: The new Trac makes a lot more references to Range's commercial products and services. Why? > A: The development of OpenBTS is and always has been a commercial activity. OpenBTS is our product, even in its free (libre) form, and we will present it and manage it as such. > > Q: The new repo is SVN instead of git. Why? > A: We (Range) use SVN for our internal repo. Keeping the public and commercial releases in the same repo will make it much easier for Range's commercial development team to participate in the public release. > > Q: Does Range still withhold commercial features from the public release? > A: Yes, although we have made policy changes that will keep the two releases more similar moving forward. > > Q: Does Range still require contributors to the official public release to sign a CLA? > A: Generally, yes, but we have made exceptions in some cases. We are reviewing our policy with respect to the CLA and trying to find ways to accommodate a broader range of contributions. > > Q: The new real-time Asterisk stuff breaks my old dialplans and the ODBC components are hard to install. Why did you do that? > A: The new approach is more flexible and scalable. Also, we use this approach in the commercial release and it's important that the public and commercial code-bases are similar so we can continue to make improvements to the public release in the future. We apologize for any inconvenience this upgrade may cause. > > Q: When will you provide a guest account with write-acces to the new wiki? > A: Soon. > > Q: When will you provide a public ticket tracker in the new wiki? > A: Soon. > > > Of course, there will be many other questions not answered here. We will try to address them as directly and promptly as possible. > > Thanks and Best Regards, > > David, Harvind and the Range Networks Team > > > David A. Burgess > Founder, CEO > Range Networks, Inc. > 560 Brannan St. > San Francisco, CA 94107 > USA > cell +1 707 208 2622 > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2d-oct > _______________________________________________ > Openbts-discuss mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openbts-discuss > -- Regards, Alexander Chemeris. |