-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bip.io site returns HTTP 500 Internal Server Error #70
Comments
Hi @voxadam - I'm not involved with bipio these days, hopefully the new maintainers will resolve this issue. |
I just discovered bip. But this damanged website makes me feel that this project might be dead ? Is anyone working on this ? |
Sadly, |
While I know little of Bip's internals (lack of time on my part), I don't imagine that all is lost. If the system is sufficiently useful I expect that a new front end could be implemented. Though, without digging into the code I couldn't say how much work such an undertaking would be. Unfortunately I never managed to get around to trying Bip. I was hesitant to sink much time into a tool with such a large quantity of closed source code (my reasoning is likely quite obvious at the moment). |
Quick update that not all is lost. I'm working with the current maintainers to define the terms of making all of bipio open source. However, with so much that isn't public (including extra pods, apps and server modules) it can't be done by just one person. A public call for contributors will happen in the next few days, to make bipio the # 1 open source API integration tool for developers. In the meantime if anyone feels they can contribute code (front and back-end javascript), UI/UX (+CSS/HTML), devops or integrations to help maintain and evolve bipio with a community focus, please respond to this thread. I'll link to contributor registration and more architectural details as they become available. We can do this! |
Great news! Count me in, there is a pent up demand for bip.io and several organizations interested in supporting the project. |
Hi all, I worked on Bip.io for the better part of a year in 2014-15, and although I’m no longer working directly for the organization, I’m happy to contribute some free time to the project because I think it’s intrinsically valuable to have an open-source project like this. My experience working on Bip.io’s internals might be of some use here, and I know Michael and Tom personally. Let me know what I can do :) Le 6 avril 2016 à 13:02:02, Tom Gilley ([email protected]) a écrit: Great news! Count me in, there is a pent up demand for bip.io and several organizations interested in supporting the project. — |
I'm exceedingly pleased to see such a rallying around the project. Let's do this! |
Well, I just got a scheduled email and the site seems to be back up. Yey! |
Interesting... While I'm pleased to see the site back up, I have to say, the unexplained downtime hasn't exactly left me brimming with confidence. I'm finding it difficult to decide if bip, regardless of its potential, as a platform that I'm willing to invest my time and effort into |
The site seems to be down again today. I was going to try writing my own GUI as a coding exercise, but for now it looks like it may be the only way to reliably access a bip.io server. I'd love to contribute on this project as well as IFTTT isn't as flexible as I would like and Zapier can get prohibitively expensive very quickly. |
Hi there! |
@bmenant I've heard nothing back so have moved onto other projects. Sorry folks, good luck. |
is the website down now forever ? |
@mjpearson Hi! can I please join you to maintain this great project? Is there any slack channel or similar that I can jump in? |
@JasonShin The call for contributors never occurred. I forked the repo awhile back, but I've had too many personal upheavals to dedicate any real time to this project. I do have another project that needs to get some priority, but if there are devs willing to help I'm still willing to dedicate time to this one. If there is still any interest, I made a Slack channel at https://bipioteam.slack.com/ and I'm happy to add contributors to my fork (or someone else's if they have been working on it.) It seems that this repo is completely dead, |
@JasonShin @serri588 I can’t dedicate any time to this project right now, but definitely down for it in a (hopefully) not so far future. |
@serri588 Hey, thanks for the reply. I am more than happy to make the contributions to your fork. Can you please invite me to the Slack team? My email is [email protected] |
Hi people let me know if anyone wants to be part of https://bipioteam.slack.com/ |
@JasonShin @bmenant @serri588 and all - thank you for your interest in bip.io I work for the current owners of bip.io. Sorry we have been so quiet. Behind the scenes, we've been trying to work out exactly how we want to move forward with bip.io (both the project and the website) for quite a while now. If you wish, I would be happy to join your slack team and continue these conversations. |
@sburr I'd be happy to send you an invite. If you don't want to post your email publically, you can send it to [email protected]. |
Great. [email protected] will find me. |
is there any chance that site will again go live working in normal state |
That is the plan |
when this will be working any idea ? |
Hi, please add me to the slack team if that's still happening. [email protected] Thanks! |
Invite sent |
Hi, please add me to the slack team [email protected] Thank you. |
invite sent- sorry for the delay |
Hi guys, I am building an open source reboot of Bipio. Our slack team is based in https://bipioteam.slack.com. Please request invitation to myself or @serri588 . |
if you're taking bip.io and renaming it into bipHub, might consider there's a project that already has that name: https://github.com/adamfluke/biphub |
We're migrating to a new slack server (and getting rid of the bipio name). You can generate an invite link for yourself using https://biphubslackinvite.herokuapp.com |
That about sums it up... I just thought @mjpearson might want to know.
The text was updated successfully, but these errors were encountered: