Hello Greg, Le 1 juil. 09 à 20:36, Greg Grossmeier a écrit :
> > <quoting name="Charles-H. Schulz" date="2009-07-01" time="16:25:03 > +0200"> > >> Hello all, > > Hello, > >> I'm still looking for the source code, and I can't use the binary as >> I'm not on Suse. > > https://forgesvn1.novell.com/viewsvn/ifolder/ > and > https://forgesvn1.novell.com/viewsvn/simias/ > > Here is instructions on how to package it for Debian/Ubuntu (written > from an Ubuntu perspective): https://wiki.ubuntu.com/iFolderPackaging > > And request to package for Ubuntu: > https://launchpad.net/bug/87122 thanks! > >> It's supposed to be under GPL v2, but what about AGPL? GPL v2 does >> not >> address the issues discussed by the Franklin Street Statement, and it >> is precisely why a group such as this one exists. > > I would disagree with that statement. The GPLv2 does provide the > necessary aspect of the code being FLOSS. It does not, as you rightly > address, ensure that all modifications made to the source are > available when it is implemented as a service. But that does not stop > it from being Franklin Street Statement compliant. Yes; but it does not provide anywhere a simple or complex explanation on how it deals or it may deal with users' date in the future. Of course, the issue here is that iFolder only does one thing: it saves and syncs users' date between two hard disks. iFolder is used (I used to work for Novell when they bought Suse and Ximian) mostly in a classical corporate environment: you have a business documents folder on your corporate desktop. You may have a laptop with the same folder, and of course the company wants you to sync it with its corporate server behind a corporate firewall. It may sound like an old-fashioned way to use iFolder, but it's how it's primarily used, and it's a good tool for that. I guess what I'm trying to say is that perhaps iFolder may not fall in the scope of the services we tend to study or promote here, because depending on the environment you are in, the data will have a specific IP (in theory). In my example, it was belonging to Novell, my employer at that time. But unless we see an "ifolderforall.com" offering to anyone backup services, this software won't be very relevant to us I think. > > I'm assuming that since this is an old project, the license choice was > made before the AGPL was released. Yes. > And while the AGPL satisfies one > aspect of the Franklin Street Statement, it is not the only option > provided. The service provider (lets say, iFolder4You) that has a > hosted iFolder solution can simply provide any modifications they make > to the source code back to the upstream devs, or even as a diff on > their site, and fullfil that aspect of the FSS. This is similar to > what Autonomous has done: http://autonomo.us/our_source/ You're right, but it is only relevant in the context of a provider offering the service on the web to everyone, not for corporate intranets or extranets. > > The developers of iFolder have satisfied 2 out of the 3 encouragements > from the FSS: > 1) "Develop freely-licensed alternatives to existing > popular but non-Free network services." since it is a replacement for > Dropbox/UbuntuONE > > 2) "Develop software that can replace centralized services and data > storage with distributed software and data deployment, giving control > back to users." since there is nothing stopping someone from > mirroring their shared folder among multiple iFolder installations. > >> iFolder, as far as I understand, still works as a file syncing/saving >> software and service. Unlike UbuntuOne, it cannot be described as a >> "cloud service". It was around 6 years ago. > > Define "cloud service." I define a "cloud service" as any service > where the infrastucture is "in the cloud," ie: not local but instead > on someone else's servers in another location. There is nothing > stopping anyone from using iFolder as the base of a Dropbox/UbuntuONE > alternative, which would make it a "cloud service," no? Indeed, you can use it as the base of a cloud service. But my initial point was that I was looking with a narrow sight at their website and commenting about what you had written about it; and I was thinking that if it were just because of the software usecase iFolder is being used in, your points were not overly relevant. Of course, in a different context, for instance one where a commercial provider of backup services offers iFolder-based technologies to the market, that's different . > >> Hence I'd like to get some clarifications about this project. > > Everything I have said above I leared from reading the iFolder wiki > [1] and talking with Brent McConnell (the iFolder community manager) > who is available on #ifolder on Freenode (as "emcconne"). They also > have a Sourceforge-host forum [2] (which I follow via email). Also, > they have a "iFolder Community" site [3] (how that is different from > the wiki and forum, I don't know). > > Basically, what I mean to say from the above paragraph: this is the > extent of my knowledge of this project but there are many avenues to > find out more. Okay. Thank you for having shared all this with us. I'm happy to see this project take back off anyway. Cheers, Charles. > > > Best, > > Greg > > > [1] > http://sourceforge.net/apps/mediawiki/ifolder3/index.php?title=Main_Page > > [2] http://sourceforge.net/forum/forum.php?forum_id=933711 > > [3] > http://community.ifolder.com/ssf/a/do?p_name=ss_forum&p_action=1&binderId=1486&action=view_ws_listing&newTab=ssNewTabPlaceHolder > > Charles-H. Schulz Associé / Founding Partner, Ars Aperta _______________________________________________ Discuss mailing list [email protected] http://lists.autonomo.us/mailman/listinfo/discuss
