I strongly suggest that after an updated "official" beta has been posted to the Google Code page that we all strongly discuss moving the project formally to GitHub. I'm happy to add any committed contributor to the GitHub organization.
I think moving to git-scm and specifically the GitHub model would be a real boon for the project. Along with all the obvious benefits of git [the idea of keeping the fuse patchset in a branch is a great idea], I think the ability to simply fork and merge repositories would make it infinitely easier for folk to contribute to the project in both serious and casual manners. Every serious developer already has a GitHub account and some amount of experience with git. Whereas I think a lot of people would now need to start digging back into man pages to get back up to speed with SVN. Regarding ExpanDrive's registering the "macfuse" GitHub account and subsequently getting it back: The main reason we registered it [and desire to maintain it] is to make sure an invested party is the owner of the repository. A common pattern in the open source community is for a developer to get excited by contributing to a project, take some amount of command over a few months and then get bored or busy and vaporize. We've been in business doing this exact project for about 7 years now [and we write our own version of WinFUSE], and aren't going anywhere. More than anyone, I want to make sure the project doesn't get locked up again. Additionally, I feel it's important to make sure that somebody with some amount of meaningful kernel development experience has control. The proliferation of the non-threadsafe K64 MacFUSE "beta" has been rather scary from both a recklessness and fragmentation perspective. Again: More than anything, I want to make sure the repository doesn't get left in dead hands like it has been. Anatol, I'm happy to see that you've stepped up to try and do some work here. But as far as I can tell, you have no activity in this group previous to last month and I'm unaware of a MacFUSE based project you or Thomas are associated with. That's not a problem, but I wanted to explain my hesitancy that you might get bored of this and move on. Myself and Erik, both, are involved in projects which are highly dependent on MacFUSE and have considerable experience shipping filesystem code and I think would be happy to run the repository. Thoughts? -Jeff -- 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.
