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 >> at https://github.com/bfleischer/macfuse in branch 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 at http://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 at http://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. See http://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.
