BOXBILLING is ALIVE #507
Comments
|
Any forks active? |
|
Edited!:NOP! It is not completelly DEAD! Many people around here have bean used BoxBilling for many Things... But This perpective will change in some weeks... Stay Tuned for more News... |
|
There were comments last year about a complete rewrite, and several fixes offered in PRs that didn't seem to be of interest. With 203 forks of this code, I can't image a complete loss of interest. I am interested in keeping this going. Anyone interested in building a team to take it on? |
|
@62BRAINS I am interested to continue the boxbilling work. I already did some bug fixes, PHP 7 support and so on some months ago. Let's create a team and start working on a new version! Maybe we can use slack for some discussions? |
|
Shall I do a startup? I am highly interested. We should set up a community to rebuild and expand BoxBilling. |
|
@StefvanEgmond I already wrote with @62BRAINS and we've created a slack workspace to discuss about the topic boxbillig. You can email me to kontakt@jonah-bohlmann.de that I can send you an invation for slack. I would be happy to hear from you! |
|
Hi All, This is an awesome news!! yes bring box to life! Regards, |
|
Sent an email! Would be happy to get a reply soon! |
|
@Eiskaltereistee @StefvanEgmond @62BRAINS this is good news. I will be able to help with some resources that I can make available! |
|
@Eiskaltereistee @StefvanEgmond @62BRAINS I would feel very useful to be able to help, I already sent an email to get in touch ... It would be very useful to be able to get an answer! |
|
You have a Slack account for BoxBilling @Eiskaltereistee? Just to clarify guys, if you have new feature's you want to get released on this GitHub, I'll be more than happy to get them on here & provide credit to those that developed it - the community for BoxBilling is vital for BoxBilling. As you know BoxBilling went open-source two-three years ago now, this was so developers can better develop further BoxBilling without relying on the developers of BoxBilling. Features include PHP 7.x support, bug fixes, patches & module updates (E.g. cPanel, Plesk, PayPal, Stripe etc.). |
|
If you guys want help I have been learning the ins and outs of Boxbilling to develop a CentOS WebPanel extension. I only have a rudimentary version working at the moment, but I would love to help push development along. =) |
|
Hi |
|
If you have something you want to contribute to BoxBilling, send your info to: https://portal.mymbs.eu/boxbilling.php - we can get this onto this GitHub after we review the changes/modules you have done. Again, I do not mind giving credit where it is due, if anyone wants to give some of our feature requests a go, do let us know using the above link. |
|
And you are ? |
|
@TuxMay if you are representing the official BB team, then might I suggest you guys compile fixes in to a new release. Also fix the boxbilling support forum it is unusable from bots. And fix the extensions.boxbilling.com site so it is available again. These are things that make the project look dead. |
|
@namenodeis I have been apart of BoxBilling for many years, it is not a recent start. If you have not noticed, the extensions sub-domain is not coming back as all stuff on it was put onto our GitHub as soon as the open source version was released. I have already noticed the increase of spam bots trolling the forum, as such the forum was locked a few days ago while we start removing the 30,000+ (25,000 already removed) articles posted, as SPAM is not tolerated on our system, the forum will remain locked until further notice while an investigation is undertook and ISP notified of the SPAM. I presume that version of BoxBilling is authorised for distribution, remember that BoxBilling still holds full authority over BoxBilling & all modules & components within it? |
|
So you have a ETA for a new release? You plan to begin supporting the product officially again? |
|
You can follow us: [LINK REMOVED] We're are a group of bb-lovers and want to continue bb under a different name. BB next generation. ;-) We're happy for every follower! |
|
@TuxMay what are you trying to say? Sounds like these guys want to expand on the open version and have every right to do so. Just start a new forum??? The current version is outdated and in dire need of an overhaul. I would rewrite the entire extension integration anyhow. |
|
That isn't the point, we don't mind you expanding on it & sharing it, but when you try to rebrand it to ciclebilling - without our knowledge, that is called theft & as I don't see any ticket requesting if you could do this & us authorising it, this is called theft. Even Open-Source Projects have licenses that prohibit you rebranding the software for distribution. |
|
Pretty much why boxbilling is dead. It has not been updated in years but the moment someone interest is sparked @TuxMay comes in with the theft BS. I stopped using it long ago because i could never get it to pass a security scan. I hope you guys that want to make an actual supported and updated open billing platform do so. My advice is to just avoid this toxic crap all together. |
|
@TuxMay. When i know it correct, it's Apached 2.0 and you DO NOT NEED knowledge about , when someone fork, rename and release it. SO learn something about Licences before insulting people which doing your Job. ;) But this was the Problem all the Time with Boxbilling Team. Want to earn Money, but never get Money ;) We had the same Discussion with removing LIcence Check, you remember? I removed it and i tell everyone how to remove and i post also a Blog Article about it ;) Again for your less knowledged about Licences with pictures ;) Maybe you understand this. If not, pls stop talking about licences and code stealing ;) https://tldrlegal.com/license/apache-license-2.0-(apache-2.0) |
|
@TuxMay maybe you should read and understand the apache licence agreement. You can find a short version on wikipedia: https://en.wikipedia.org/wiki/Apache_License https://tldrlegal.com/license/apache-license-2.0-(apache-2.0) As you can see in our license file, boxbilling is still in there: "Copyright 2014 Boxbilling, Inc" But there is a missing "NOTICE" file, so I will add them soon. @gOOvER thank you! We just having the same idea. |
|
@Eiskaltereistee You are not wrong. ;) Had the same discussion with this Guy with removing Licence Check ;) He have abolutly no knowledge of Licences and he still don't know what he talking about ;) |
|
Thats the Boxbilling Team in real and live.... ;) |
|
FFFFF go make something great guys. |
|
Why are all issues closed? |
|
All Issues were closed due to outdated issues so we are starting fresh, any new issues will be looked at, but may not be responded too, as this software is open source, we are hoping fans/developers of the BoxBilling software will help resolve new issues. |
|
I don't think BB has any fans left since it didn't updated for 2 years |
|
That is your opinion, yet from the activity on this GitHub & the support ticket requests we still receive state otherwise. |
|
I think, this will be the same like 2 years before. Now you see, that a fork started and noch you will be active. I bet, it will be quite again in 1 till 2 months. Sry, i have BB now since 5 years and i hear a lot, what are you talking and doing and nothing comes real... Like v5 ;) |
You mean the active "shitstorm" and angry users.. I think it's not the activity you need.. ;) |
|
If you do not wish to help with the next version of BoxBilling, I really do not see why you have the need to view this GitHub in my opinion. The point of this GitHub is so users can help each other diagnose & fix issues such as those that were in the Issues, but allas I must be wrong & is just a place that users come to scream their anger to new users. |
|
I think I am not going to wait for
Will continue with https://github.com/CircleBilling/CircleBilling |
|
Well I have one question for you, why are you still visiting this GitHub? |
|
Dr Frankenstein was also thinking "He's alivee!" but... |
|
Well for me I used to use boxbilling paid for it in fact. I keep running into security vulnerabilities so I fixed some and decided to see if I can track down any signs of life. So for 2 years I went back and gathered my own fixes and made it compliant for what i was doing. After seeing your responses to people @TuxMay I can see why this project tanked. |
|
@TuxMay Why you don't help at the Fork? Your Project is definitiv Dead and it's to shame oneself, that you delete all the Links. Why you don't be active in last years? Now you start to try to beeing active ;) Where was you since the last years ;) Al lot of Users paid you and what are you doing? You left them alone. Shame on you ;) Now it's time for new People and new Wind; and thats definitive not you., You had your chance ;) |
|
@gOOvER I have removed links to this circlebilling GitHub project as it isn't being advertised on the BoxBilling GitHub. You state that we haven't been active on GitHub, I presume you mean responding to users & merging stuff, then you are correct, but we have been monitoring since the last version. Again, why are you all on this GitHub if you are not going to help develop it, if you have no development for BoxBilling, then why are you here? Instead of getting aggressive towards me for being a member of the BoxBilling team, I'm not the developer of the software, I have not been here since v1.0 - I came into BoxBilling since v3.0 to help with the support ticket demand (200+ tickets per hour), yet because I started to respond & try to give updates to you, you backlash it in my face (or screen in this case). MyMBS Networks started work on the v5.0 development but abandoned it due to no demand for it as everyone started to think it was dead. Development takes time & money. I admit the original BoxBilling developers may have dropped BoxBilling after v4.20, yet I will not give up on BoxBillling, yet in order to do that, I need time, developers & money towards the development - aka the reason why I stated if you do have any module updates, development updates, vulnerability patches etc, I would like to see them, review them & get them onto BoxBilling master to help get this v5 done! |
|
I came back to this Github because I do care about BoxBilling. The world needs a better FOSS Webhosting front-end. And I trudged through BB for a while in my first business attempt. Support for virtualizor and other emerging platforms, as well as payment gateway bugs and other issues drove me to tolerating WHMCS for a time. I would have gladly paid that money to BB had my experience seeking support there not been so unhelpful. I learned quickly the forum was a waste of time because no one was posting actual solutions or explanations. It was like, oh it's open-source go figure it out. And I am not a developer as my main gig. (Development is hard on us sysadmins we like that stuff figured out for us.) So fixing problems in other coder's applications is not just something I can always just go do. So while I wanted BB to be this greater thing than it was, it became a big disappointment for me. And when I got a notification in Softaculous Admin area to turn it off because it was outdated/not maintained. I was reminded of this great script and all of its potential. As I searched around, I found a lot of other people like me, that really wanted to make it work for them, too. But the biggest issues usually had no real applicable solutions for an inexperienced developer or a non-developer. But I give a s***, oddly enough. I wanted to go back with my knowledge since that time and bend BB to my will to make it work the way I want it, also. And so I have been getting down to the nuts and bolts of PHP and not just reading over it. I have written an extension for CWP Server Manager already, the functions work, but it keeps giving me "backend fetch failed" 500 errors at the end of each task - i.e. suspend, unsuspend, create account, even though the actions succeed on the host. So I will not publish it until I can better understanding of using github AND fixing it so that this backend fetch error on the BB api stops happening. When I see again other people similar to me, having the idea to move on and make the Phoenix rise again: I feel good in that this software is not really abandoned. It can grow and fulfill it's role, all with the help of volunteers. Changing a name is a technicality. Adding value to the world with the short time you are given in your life is priceless. Irregardless of getting 'credit' for something, it is more about your own internal reward, in the end. I know this may sound crazy, but I have the love for you. Thank you for coming back and giving us some kind of acknowledgement that people were not unheard in some way. And thank you for a giving a s*** about BoxBilling, too! I can tell that you do, or you would not have taken it on here. With that, I apologize if I came across as aggressive or insulting in any comments here. That is not my intention. I hope you understand I do care and that was the only reason I bothered to make a github account to comment here. So now I would like to ask you to help make value for the world in a way that will enable you to reach your v5, as well. Because I understand it is hard to focus development where you want when you have to pay the bills. As you acknowledged this has already crippled the project's ability to gain traction. And, if this really is a step-child for you/your team, then this could be leveraged in to a win-win. Let me explain, if I may. But right now, I thank you for all your time you have already given me here. Continuing on, I know that your level of experience in the existing project would be invaluable to the CB fork. And BB would not have to end, either. But, by partnering with CB, you would have direct access and assistance in developing. You can already get work CB does back upstream to BB if you desire it. You get a free dev team for a new version out of this, either way. But if you were willing to help, then we could build a much more cohesive and productive environment, built on the work of the community that is already going to work on it anyway. The only question is, would you be willing? To bring your support and advice to CB would bring value to your time. You could help people who care and want success for you and your project, too. I don't think anyone at CB wants to "steal" your work. Only to help the project fulfill it's destiny and reach the level of greatness that it deserves. And I honor you, that someone would fork your work. I hope if i can ever manage to get code on here that someone might want to fork it, too. And I hope I would want to support them and bring value to their life, too. So, again, I apologize. I am a little tearful, and fearful, that the possibility of someone with so much experience in the nuts and bolts of BB will never want to help CB because of stuff said out of frustration in this issue page. Sincerely, |
|
Hello Malcolm (@namenodeis), I will continue to support BoxBilling, yet I will not support CircleBilling as CB as you are calling it is a completely separate development & is not apart of BoxBilling. |
|
Alright then, @TuxMay, fair enough. Thank you for taking the time to read and reply. Best wishes to you and the BB team! |
Is there any active development going on for this project?
The text was updated successfully, but these errors were encountered: