Hi On Wed, May 4, 2011 at 3:41 PM, Tomas Carnecky <[email protected]> wrote: > We have a new home at https://github.com/macfuse. > > The sources from svn have been imported into a git repo > (https://github.com/macfuse/macfuse). At least one of the original > authors didn't wish his email to be publicly available, so I assigned > all the original developers a @macfuse.org email address. A few > details on that are available at > https://github.com/macfuse/macfuse/wiki/Migration. > > The wiki pages are also on github. A conversion from google code wiki > syntax to markdown was required. The conversion isn't perfect, but > it's a start. We can clean it up later. See > https://github.com/macfuse/macfuse/wiki/_pages. > > We can use github issues to track bugs and feature requests. > > Google groups seems a good solution for end-user support, unless > someone has a better alternative. > > We also have the #macfuse channel on freenode, in case people prefer IRC. > > > There's still lots of stuff that needs to be done: > > - A proper homepage for end-users (web developers/designers needed) Ok, now we have a webpage for the macfuse http://macfuse.github.com/. http://macfuse.org/ should be updated shortly as well.
if you want to add anything to the site - send patches for https://github.com/macfuse/macfuse.github.com > - Clean up the wiki (remove references to the old google code page etc). > - Merge patches which have accumulated over time (macports, external > companies which ported macfuse to the 64bit kernel etc) It looks like we decided to go with tuxera changes, it is great! > Did I miss something? A new official release? As the current HEAD is the same as tuxera repo the new release will be the same as 2.1.9.dmg The reason I want it is to force macports to move to it. So macports either abandon their changes or move it upstream. This way we remove yet another source of confusion. A few mid-term tasks: * update fuse to 2.8.5. Currently macfuse depends on horribly outdated 3 yo libfuse release. * create a fork of libfuse and sshfs repositories. Currently diffs between upstream and macfuse changes is stored as a patch. https://github.com/macfuse/macfuse/tree/master/core/10.5/libfuse It is ugly. Especially if you want to look diff over diff. Instead we should have separate repos with 2 branches - upstream and macfuse. When you make a change to libfuse repo - you update the diff as well. Or even better - to remove *.patch files at all and just use git submodules. -- 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.
