Hi,
Graham Perrin wrote 2011-06-13 03.27:
Amit& Chris got it back … ~4 weeks ago.
Anatol and Benjamin, thanks -- got it now --
http://macfuse.975588.n3.nabble.com/-tp2939234p2939243.html
http://macfuse.975588.n3.nabble.com/-tp2939234p2939300.html
http://groups.google.com/group/macfuse/browse_thread/thread/8281bd7a9e59218a
Apologies for the confusion.
Timelines
=========
All: whilst continuing to discuss a name, and working on code, I would
strongly suggest **waiting until after Lion is released** before
making your final decisions regarding:
1. a name for the fork; and
2. how the fork might be positioned alongside (a) MacFUSE, (b) NuFS,
(c) any other new thing that is either complementary or comparable to
MacFUSE.
Two weeks after Apple's release of Lion might be a respectable period.
Time enough for individuals and organisations to first reveal what's
strictly under wraps with regard to Lion (and products for Lion),
secondly respond to the most urgent things that arise following the
release. In this context MacFUSE may be not the most urgent thing.
Just a suggestion :-)
Name for a fork
===============
I still like 'fuse4mac' but re
http://groups.google.com/group/macfuse/msg/ee3d70cfc33258a7
http://forum.hardmac.com/index.php?showtopic=10464 etc. I should
probably shift my first and second votes to:
#1 fuse4osx
#2 osxfuse
Prefer the first, as it begins with the word 'fuse'.
I think that the 'marketing name' of it all should be simply 'FUSE for
Mac OS X' (or 'OS X' if you would rather take the 'Mac' out of it
following Apple's latest marketing change). Whether we use osxfuse,
fuseosx, fuse4mac, fuse4osx, ... as the internal project name I think we
should consider this to be a port of FUSE to Darwin/Mac OS X (with some
Mac-specific extensions), hence 'FUSE for ...'.
(Is FUSE a trademark by the way? Can it be used freely?)
I would love to see this project reconnect with original FUSE, and long
term attempt to bring the features on par with FUSE development on Linux
(although code sharing won't work as we can't use GPL code).
However, we need more contributors to the kernel side of the code if
that is going to happen.
I would also love to see some reconnection with the BSD fuse project. If
we can share code and co-develop the BSD and XNU implementations of
FUSE, that would be a big win (although I'm not sure if anybody cares
much about FUSE on the BSD platform nowadays). This might be too much
effort though.
Regards,
- Erik
--
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.
