|
Post by Carl on May 28, 2024 8:18:52 GMT
|
|
|
Post by Roger Fishwick on May 28, 2024 11:23:57 GMT
I know this is a terrible time, but I really need to get our code from the system, it came up briefly on Friday but has been timing-out ever since do you have any idea when we might be able to pull all our repos?
|
|
mlr
New Member
Posts: 3
|
Post by mlr on May 28, 2024 11:54:08 GMT
Hi Carl, thanks for the report.
We had Jira integration with xp-dev and had it talking to our TeamCity build server. A2 did not overwhelm with their helpfulness on those fronts. I am looking at Perforce, Codebase, and Beanstalk, but Beanstalk looks unfortunately very small... If anyone else has suggestions for git and svn hosting I would be very grateful.
|
|
|
Post by Keef44 on May 28, 2024 17:33:33 GMT
I am unable to login at all. We only use XP-Dev for Trac - and really want to take a copy of all our tickets. But as i cannot login at all - does this mean our account has been deleted?
|
|
|
Post by Wael on May 29, 2024 7:06:34 GMT
For all users looking for alternative solution, I would recommend migrating to DevZing They host Trac/Bugzilla/Testopia/Subversion devzing.com/If you managed to export your Trac DB and dump your SVN repo, they you can migrate them to devzing with full history
|
|
|
Post by Tushar Shet on May 29, 2024 10:00:17 GMT
we can able to access the my xp dev repository now. keep trying in a day for sometime server gets active we have exported the repository and moved to beanstalkapp.com/
|
|
|
Post by lucario on Jun 1, 2024 7:07:34 GMT
So, any update?
|
|
|
Post by Unhappy Customer on Jun 7, 2024 18:10:10 GMT
We'd really like some updated information.
We're paying customers being treated like dirt.
|
|
|
Post by Roopinder's Family on Jun 9, 2024 12:44:24 GMT
Roopinder's company had one director who was also the only employee. Which means that when he died very suddenly and unexpectedly, all working knowledge died with him. So, in nutshell, the company is essentially without an operator. This is not a family business nor enterprise. We do not have a clue in the first instance, how to take over, and neither are we interested in taking over his platforms. We are trying to help customers (where possible) and this means that his family has to take on a problem that is not theirs to begin with. We have been advised by our counsel to not get involved as we are not liable. Nevertheless, we would like to help.
Regarding payments - all Paypal accounts have been frozen, and those using Stripe are having money refunded as they come into his company account. Once the accountants have a look, money owed to annual subscribers will be refunded once we have legal authority to do so. Also to add at this point, no one in his family has access to his business accounts (other than Stripe) and therefore it is not a question of anyone here holding on to funds that could be returned.
Legal advice is to close the company down, which we will do. In saying that, before we do so, we would like to TRY to restore access for customers. We are incurring personal cost in the process by doing so, and we are not asking for financial assistance (the reason we mention cost, is to say that we do actually care and are going above and beyond what should be expected of his IT-illiterate family).
This is a massive undertaking which is not allowing us to move forward and grieve at our pace. We are effectively bystanders who see that there are people on the other side of the screen requiring help. Software engineers have explained that they may not be able to restore the access we'd like his clients to have, but they will try. We cannot put a timeline to this, as the legal process to facilitate the engagement of IT professionals is outside of our control. To clarify one final time, we do not have passwords, and do not know how Roopinder managed his platforms, we do not have the ability to block or to restore access to his platforms.
Despite having our own jobs and families who require our attention for various reasons, we are working on this daily. We have not ignored any correspondence, and certainly are not ignoring his customers to have raised tickets via his email account - this, by the way, was the only page open on his computer when he died and how we have access (all other apps had timed lock-outs and shut down when he took unwell). We are also paying to keep his servers going out-of-pocket in the hopes that it buys some of his clients time to migrate their data elsewhere. It is very difficult for us to comprehend, how we could be accused of treating anyone like dirt. In spite of the intonation and accusatory tones directed at us in some interactions, we are reminded of the overwhelming majority of clients who have been very kind and understanding in respect of our predicament. We try to not take comments personally, and remind ourselves that there are real employers and employees behind usernames who are also in a difficult position, but it is not of our making.
When we have something concrete to update, we will definitely do so, in the spirit of transparency.
|
|
|
Post by alasdaircs on Jun 10, 2024 10:49:57 GMT
I just want to thank you for doing your best in difficult circumstances. Were I to have the time and the required knowledge (I have neither) I would volunteer to help you document and support the platform. Perhaps someone here with the required knowledge of linux, python, subversion, git, trac etc. could put their hands up to help? Other ideas include selling the company to a supportive, community-minded enterprise, or perhaps an academic institution could take on the assets as a community project? I suggest anyone reading this consider who they might know who could be trusted to help and put forward some ideas.
|
|
|
Post by guest2 on Jun 10, 2024 10:58:20 GMT
I also want to thank you. We are extremely grateful that you are still paying the bills and if we can somehow help defray the costs, we would like to do so. I can imagine that this is a terrible situation for you, and am saddened that anyone would make it worse with accusations and threats. We also find ourselves in bad position here -- we had history going back to 2012 and for some reason, our AWS S3 backups were not complete, so we cannot restore our SVN repo -- but that is our own fault, we should have been testing that as a part of our disaster management. Luckily we do have recent snapshots so we are moving forward as if we are starting afresh. Wishing the family all the best and hoping for a stroke of luck all around.
|
|
kate
New Member
Posts: 1
|
Post by kate on Jun 10, 2024 14:53:52 GMT
Hi all! Please accept our sincere condolences and endless support! We understand that many of you are uncertain about the future of XP-Dev and are looking for an alternative that supports SVN. RhodeCode is might be one of them. It is designed for behind-the-firewall Mercurial, Git, and SVN. It is open source, secure, provides centralized control over distributed code repositories, and has a free-forever Community Edition. Our team is ready to assist you each step of the way, ensuring a smooth transition. You can visit our website for more information - rhodecode.com/
|
|
|
Post by vu on Jun 10, 2024 19:10:03 GMT
Ours is still down
|
|
|
Post by Roopinder's Family on Jun 10, 2024 20:09:51 GMT
Thank you for your words - please everyone bear in mind - we ARE waiting for software engineers to have a look at his platforms. But, they will only examine them after we prove that we have legal authority.
This is a very complex process which is more than a simple declaration of, 'I volunteer to take over and give further instructions'.
We have lined up IT professionals (they are waiting), and we are working tireless with the other professionals that have to be allowed carry out their work too - we are all working together, to get legal control. I'd like to reiterate, this is the rate-limiting step over which we have no control.
As soon as we get the green light, we will move forward. A reminder though, we had to engage with several IT companies when searching for the right people to help out - not one of them could tell us with certainty that they will succeed in gaining access. We will, however, keep trying until all options are exhausted. That is a promise.
|
|
|
Post by pjh on Jun 11, 2024 11:47:39 GMT
I just wanted to add my thanks to the family for not simply pulling the plug on xp-dev at a very difficult time when they have far more important things to deal with and think about. I haven't stopped payments from my end but I notice I'm getting payment failure emails. I left payments active in the hope that xpdev would rise from the ashes, and as long as there's the remotest chance of this happening please feel free to continue taking payments to help defray the costs. I'm sure many customers feel the same.
I notice that some users have lost data. This event highlights the importance of having a robust disaster recovery plan. If xp-dev was a single point of failure in anyone's plan then who is to blame? Roopinder's (uninvolved in the business) family? My own attitude is that data doesn't really exist if it isn't stored in at least three locations spread over two continents. If that ever turns out to be inadequate the fault will be mine.
As a footnote, I've been looking for Mercurial hosting of comparable quality and maturity to xp-dev without success. It would be a tragedy if xp-dev disappeared without trace, so I hope the family decide and are able to restore it.
|
|