Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I am evaluating biicode in my organization.
I started this activity last year in september but did not continue because of other pressing concerns. I have resumed the same now.
It seems biicode has shut down their operations. None of their help links seem to be working. The login page as well as signup page are dead.
Is there anyone using biicode nowadays or is it dead?
Yes, biicode is closed. While you are evaluating options you can take a look to conan project and conan.io. It's an full open source project with a lot of community contributions right now.
Conan uses a more direct (and easier) approach to library dependencies management than biicode, supporting both binary packages as building from source.
Biicode as a company has shutdown. The central biicode servers have been closed, and will no longer operate. The current pages, blogs, etc, that can be seen are in fact static pages captured and hosted in github, thats why it is impossible to login/register. There are no support people (in fact no employees at all) since July 2015. If you still have interest, it is an OSS project (MIT), included the server, if you want to run biicode, you have to run your own server.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
We're currently scouting for a good version control software with the following criterias:
File locking.
Supports binary files.
With web-based UI for check-in, check-out and other features.
With user security and management.
We'll be using this for a project that is already live. Basically we'll store all the source objects here and use these as source files when additional requirements are necessary.
Appreciate any suggestion.
Thanks.
Edit:
Forgot to mention that we are currently using Serena's PVCS VM. However we are trying to look for other good alternatives.
Also, I'd like to add that we also prefer check-out and revision numbering per file.
Thanks.
Try JIRA with FishEye. I've found it to be really useful for most aspects of on-going projects.
https://www.atlassian.com/software/jira
https://www.atlassian.com/software/fisheye/overview
Because locking is mandatory for your case, you haven't choice for backend-SCM - it can be only Subversion.
Suggestion of JIRA as issue-tracker and FishEye as web-frontend is still applicable
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
Am trying to implement a few deployment policies in my organization. Usually, we do all the development on localhost and then simply deploy the site to the production site (i.e. site.com). Am trying to place a rule to first deploy the site to say beta.site.com, test it completely and then deploy it to the final site. Now I know many companies use dev.site.com, then beta.site.com and then finally site.com.
Am wondering what exactly is the purpose of dev.site.com and then beta.site.com. Will be both be active at the same time or is it that during development we should use dev.site.com and then later beta.site.com? What exactly is the use of a staging server/site then?
Please feel free to ask if anything is unclear. Thankyou for your time and patience.
This is totally up to interpretation and there are no binding rules, but everywhere I've been it's been along these lines:
dev. for the development environment, a full mirror of the site/project/product, to which developers upload changes to find out whether things work at all, and where they can test new technologies / products / versions / settings. Often updated with data from the public version (if one exists)
beta. for staging versions that have been tested by the developers, but need "higher-level" user testing / review before going public, already available to a wider circle than just the developers (colleagues, the whole team, beta testers, the public, etc.)
I would expect that your dev site would primarily be for internal Q/A. For a site like this, I would restrict the incoming IP addresses to those of your own company so your development site isn't exposed to the general public accidentally.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
My next project will be a lightweight PHP alternative to Trac, since Trac is often confusing to install and is often a little too big or feature-rich for smaller project.
Features planned so far:
Wiki
Bug tracker
Forum(s)
Static pages (easily edited of course)
Markdown support
No code repo hosting (I consider this a feature since most people would prefer to use a 3rd party such as GitHub for the actual code hosting)
My question: if you were to use a self-hosted app for making a website about one of your open source projects, what would you want? Is there anything on that list that's missing? Would you absolutely require the ability to actually host the code repo on the site itself, or would you be ok hosting the code elsewhere (Google Code, GitHub, BitBucket), and using the site only to upload major versions?
Summary: if you were to use a self-hosted app to provide info and support for an open source project of yours, what would you want it to be like?
Redmine is my current favorite, I usually install it via BitNami
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
Should I just go to SourceForge and try to find something that looks interesting by doing a search? Or is there a Ruby-specific website that helps you to find open source projects to contribute to?
After you find it one, do you usually just send an email to the project owner to see if you can help or do you just start submitting code to their repository and they will take it or leave it after reviewing it for quality?
The standard hosting site for Ruby projects is RubyForge. Another site that is slightly older than RubyForge, is the Ruby Application Archive (RAA). In addition to RubyForge, there are also a lot of Ruby projects hosted on SourceForge. Projects that are specific or related to JRuby, are sometimes hosted on CodeHaus or Sun's new project hosting site Kenai. For IronRuby, some projects live on CodePlex. Projects that use the Git Version Control System, are often hosted on either Gitorious or GitHub, whereas projects that use the Darcs Version Control System tend to be self-hosted.
However, especially larger Ruby projects often have their own infrastructure, e.g. Merb, DataMapper and of course Ruby on Rails.
I'd recommend going onto github to look for projects. You can search around, check things out easily and its easier for the project owner to manager your changes.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
What is the best way to retire a currently active project? I've been working on this one for a while now and I think its time to let go. Without going into too much detail, there are other projects and technologies that are way ahead now and I don't see much value in investing in it any further.
What have you done to retire a project and what is the process like?
As operating systems, compilers, etc. change, it can be difficult to rebuild old projects.
Consider creating a virtual machine that is configured to build it again, in case you need to update it for some reason in the future. Archive that VM along with the source code, etc.
Personally, I've done this before, and put up on the homepage of the project
"I no longer wish to maintain this project - if you're interested in taking it over, then feel free to email me (email#address)"
And then let someone take it over.
Is this a personal, community, or commercial/professional project?
I have had a professional prject go sour due to lack of feedback form the client. Bascially they were going at a slower pace than they should have and it got to a point where the software would be more expensive to contine than to get a prebuilt alternative. In that case i just brought in the data to show the client where their saving are and recommend to abondon. Its hard to swallow, but after a while they realize it was for the best.