I also want to thank Erik for all the work. We are using a derivative of his build here at ExpanDrive and it's going quite well.
Thomas has graciously given the MaCFUSE repository back to ExpanDrive [we registered it for this exact purpose a couple months ago] and we're the owners of the organization right now. Speaking with him, we agree that getting a stable "official" release based on the Tuxera patches is a top priority, if for no other reason than to get people to stop distributing and using a non-threadsafe monkeypatch for K64. Also, for those unaware of Amit's role with this project - he is now developing and selling NuFS, essentially MacFUSE v3. It's closed source, has new features, and all of Amit's love and support. If you deeply rely on MacFUSE and need the very best engineer in the business on your project, you should check it out. It's used in Transmit 4 among others. http://www.iohead.com/NuFS/index.html -Jeff On May 5, 8:03 pm, Peter <[email protected]> wrote: > I think this thread is important enough that I feel obligated to share > thoughts as a MacFUSE user. > > First of all, I really appreciate Anatol's efforts into putting up a > new home. There is clearly a need for continuation of MacFUSE and > without Amit, we're essentially stalled on the official development. > Also, Google Groups seem to have been flooded by recruitment emails > lately, for whatever reason. It's natural that someone should take the > project to Github and hopefully the development can continue. Benjamin > has pointed out great questions that's also on my mind. Before going > forward with the creation of repository and websites, I feel it's > important to agree on the answers. > > I personally think Eric Larsson has demonstrated great understanding > of MacFUSE internals and good faith with his commits to allow 64 bit > locking possible on x86_64 kernels. I'd personally like to see him > being the gatekeeper for repository and owner of the private key. > Thanks a lot Eric for your great, and kudos to Tuxera for releasing > Eric's work. I think as long as Tuxera continues to uses MacFUSE for > their NTFS3G for Mac, the company will have business interests to make > MacFUSE as stable and robust as possible, but it also means as long as > MacFUSE works good enough, there's no point to spend additional > development effort. I think that's the current status of their > branch. > > I also think Benjamin has showed great passion in the project with his > 2.1.7 release for back porting Eric's release of tufs into MacFUSE > svn. He has also demonstrated good knowledge on MacFUSE when helping > other users and distinguishing the difference between various 64 bit > ports in his responses. His patch to buildtool also makes building > possible. > > From what I learned on threads in this group, I'd like to see the > following: > > 1. Private key owner: Eric, and he decides which is official build > 2. Commit privilege: Eric, Ben > 3. Edit wiki: Eric, Ben, Anatol > > I don't necessarily think we need to use macfuse.org, signed binary > can be added to github so there won't be any issue on ownership of the > domain in the future. I like MacFUSE as the project name but I also > have no knowledge on the legal side. > > Again, all of the above are my personal thoughts based on threads I've > read up to this day, and my apologies if you feel you are qualified > but I didn't mention. > > Peter > > On May 5, 3:06 pm, Benjamin Fleischer <[email protected]> wrote: > > > > > Am 05.05.2011 um 21:02 schrieb Anatol Pomozov: > > > >> What about the regular MacFUSE update > > >> mechanism (PrefPane)? The PrefPane in the official MacFUSE SVN is broken. > > >> Therefore I fixed it last October when I released a patched version of > > >> MacFUSE 2.1.7 using Erik's early stage locking code to get this thing > > >> working with 64 bit kernels. > > >> If anyone is interested in this you can find my work > > >> athttps://github.com/bfleischer/macfuseinbranch macfuse-2.1. My latest > > >> stable binary release (2.1.11) is based on the latest modifications from > > >> Tuxera (2.1.9) and can be found athttp://bfleischer.github.com/macfuse/. > > >> By > > >> the way, the patched up PrefPane checks this github-page for updates, > > >> too. > > > > Great to hear it! May I ask you to send the fix as a commit based on > > > the current HEAD?https://github.com/macfuse/macfuse/ PrefPane fix is > > > definitely worth submitting to the upstream. > > > There a several questions that need to be answered before this happens. > > Correct me if I am wrong but from what I can see you started posting to > > this mailing list about three weeks ago and now you want to be the new > > project head. Did you do any development on this project in the past? But > > most importantly you did not really tell the rest of us what you plan to do > > besides importing all the patches floating around and see where it leads. > > > - What about the name MacFUSE. I guess having two "official" MacFUSE > > projects will lead to problems or at least confusion. If you just use > > MacPorts everything might be fine but if you google it there will always be > > two "official" projects. What if Amit decides to pick up development again > > or pass it to someone else (I don't think so, but who knows)? Amit seems to > > have started a commercial counterpart to MacFUSE called NuFS (Have a look > > athttp://iohead.com). Using the name MacFUSE won't work unless the original > > google code project points to the new project page or "disappears". I don't > > see that happening at the moment (conflict of interests). What do you think? > > > In addition to that I'm not sure if adopting the name MacFUSE could lead to > > legal troubles. I have no legal degree or something like that so correct me > > if I'm wrong but MacFUSE belongs to Google. Amit has been an Google > > employee. > > Seehttp://code.google.com/p/macfuse/source/browse/trunk/COPYING.txt > > > - What Mac OS X versions should be supported? I would suggest dropping > > support for 10.4 and 10.5. The existing MacFUSE versions 2.0.3 and beta > > 2.1.5 run just fine on 10.4 and 10.5. That will make development a lot > > smoother in the end. Supporting 10.6 (Intel) and later 10.7 should be > > sufficient for new releases. BTW is there anybody who has access to 10.7 > > and is willing to contribute? > > > - Who decides which code makes it into the "official" tree? In other words > > who will have write access to the repository and who will be in charge? > > > In the end just collecting patches won't do the job. > > > I started where you are now (code-wise) and am happy that I got the whole > > thing (macfuse_buildtool.sh -t dist) working after investing many hours and > > now you ask me to fork your code base . Depending on the versions of Mac OS > > you plan to support this will be a lot of work (since I dropped everything > > but 10.6 and use the 10.6 SDK instead of 10.5 as Erik's/your code does). > > From where I stand, it would be far easier if you just forked my repository > > :-) I'm not willing to put that much effort into patching up everything > > again just to use your code base as a starting point if the future of your > > project fork is this vague. > > > Getting the update mechanism to work is not just about fixing the PrefPane > > (there are some bugs regarding signing and verifying a signature > > nonetheless). For the whole update process to work there need to be a RSA > > key pair to authenticate updates and some persistent webspace. > > > - The private key should not be publicly known for obvious reasons. So > > uploading it to the repository would be a bad idea :-) Who should possess > > the key? > > > - I figure you plan to use a github-page (as I did) since Tomas' domain > > macfuse.org points to github. Is this correct? > > > I would suspect there are more questions that need to be answered if > > working together as a community on a new project fork should have a change > > of success. And of course we would need at least some dedicated developer > > for this to work. > > > Regards, > > Benjamin -- You received this message because you are subscribed to the Google Groups "MacFUSE" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/macfuse?hl=en.
