The problem with this project is that it hasn't ever been a truly open development process. The source code that is released and available to everyone under GPL (currently version 3.6) is not the same as the one Novell uses. Novell has a private development branch that they haven't opened up. So users will report bugs, for example, and Novell DOES fix them, but then they don't release the source for the latest version they have in private development.
This is why the coummunity hasn't taken the code and made it an open project, because no one wants to take on a project where bugs are getting fixed and features are getting added and then possibly being released or not. (Their releases of code have been sporadic). So the project has sat stagnant. Several developers have asked for Novell to clarify their position on the project. We wanted to know if Novell plans to keep developing it, if they plan to leave it closed source, or release it open source. If they plan on keeping their branch closed for good, then developers, could, for example take the code that has been GPL'd and run with it in a community project as a fork. If Novell plans on opening up to the community their inside process, that would be welcomed too. When the community wanted clarification on the future status of the ifolder project, Novell responded on the developer mailing list with this: "Sorry for no activity on the bug. With the feedback we have received from many of you in the community, we have been working on stabilizing the various modules in iFolder product which has been a long drawn activity. Thanks for your patience. Novell has been looking at various options to take this product forward. While we go through this process, appreciate your support and patience." And then a few months later (Jan 09) one of the Novell people said this: https://bugzilla.novell.com/show_bug.cgi?id=362541#c25 "Based on your commitment to have XXXX spearhead the connections with the community, and his efforts to help drive a vibrant community for both Kablink and iFolder, we are aligned to take the newer iFolder code (3.7) and open source it. So, officially we support open sourcing iFolder. We are aligned, and as such XXXX and I will inform the PMs and Development of that plan. I would ask that XXXX lead the effort to bring the teams together and perhaps kick off the new direction - perhaps build some team unity around the effort. We'll need, at least initially, the engagement of PM, Development, Legal, Product Mktg,and potentially operations, etc." So it looks like there may be hope. Rumor has it that Novell plans to make this an open project. As of today, a change was made on www.ifolder.com that states: "Stay Tuned for some Good News from Novell :-) Look for it during Web 2.0 Expo in San Francisco coming up March 31, 2009". So something* is going on. I look forward to seeing where Novell goes with it and what kind of announcement they make. There are those willing to step up and help in the development effort if Novell makes this a truly open community project. By the way, in your search for alternatives, you could consider these in addition to Unison: www.teamdrive.net www.getdropbox.com Jungle Disk (personal or workgroup edition; allows storing files on Amazon's S3 Cluster or Mosso Cloud Hosting) Unison works well and has mechanisms for resolving conflicts--read the manual. It's no iFolder, but it has it's place. -- [needs-packaging] iFolder https://bugs.launchpad.net/bugs/87122 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
