> Erik Larsson <mailto:[email protected]> > June 13, 2011 4:29 AM > > > Hi, > > > > 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. > I care about FUSE on BSD, but I would imagine that most of the people on the BSD team would not be interested in wading through OS X specific bits, of which there is probably a lot of in MacFUSE?
> Regards, > > - Erik > > ------------------------------------------------------------------------ > > Graham Perrin <mailto:[email protected]> > June 12, 2011 9:27 PM > > > > 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'. > > ------------------------------------------------------------------------ > > Anatol Pomozov <mailto:[email protected]> > June 9, 2011 12:31 PM > > > > > Many of us tried to contact Amit and Google people, but they ignored > all requests. And yes indeed - I was able to negotiate the project > ownership transfer with GoogleCode, but then Amit & Chris got it back. > You can find mail from them that describes the reason why they got it > back, just search the maillist ~4 weeks ago. > > ------------------------------------------------------------------------ > > Graham Perrin <mailto:[email protected]> > June 9, 2011 12:26 PM > > > > Hello folks > > Code > ==== > > http://macfuse.975588.n3.nabble.com/-tp2901294p2924820.html suggests > to me that transfer of ownership of the project is already negotiated. > All due respect to Amit and other past committers/contributors; big > thanks to Anatol for negotiation; and so on. > > Now: if http://code.google.com/p/macfuse/people/list does not reflect > recent changes, I *guess* that's because this group will discuss (for > as long as is necessary): > > * how the established Google Code resources should complement use of > github > > -- is that a reasonable interpretation, or am I missing a key point? > > I see Erik's post at > http://macfuse.975588.n3.nabble.com/-tp2901294p2926499.html , > Benjamin's reply, and various other posts in that topic. I haven't > read the whole thing yet. > > Name > ==== > > If the transfer of the Google Code project for MacFUSE **does includes > the code** (I assume so), then should we simply continue to use that > name, MacFUSE? > > If the big picture is neatly presented, then there should be no > confusion within and beyond this group about concurrent use of > multiple resources (github + Google Code + discussion area + whatever) > for the single ongoing end result. > > (Sorry if I caused any confusion earlier by continuing the discussion > re: possible alternative names; I had not, still have not, read some > of the longer topics in full!) > > ---- > Off-topic, but important: > http://groups.google.com/group/macfuse/browse_frm/thread/9259db3620954f4f > I'm trying to contact the owner or moderators of the Google *Group* > for MacFUSE. Unless I'm missing something, nothing relevant in my > Inbox since I posted that plea. Can anyone advise? (Reply under that > other topic -- thanks.) > > Best regards > Graham > > ------------------------------------------------------------------------ > > Erik Larsson <mailto:[email protected]> > June 7, 2011 2:47 AM > > > While I agree that it would be preferable to keep using the name > MacFUSE, whether is is legal or not it's simply not practical if the > original project is not handed over to the community that wants to > pick up development. > Two projects named MacFUSE will only cause confusion. > > Regards, > > - Erik > > > > ------------------------------------------------------------------------ -- Joe Auty, NetMusician NetMusician helps musicians, bands and artists create beautiful, professional, custom designed, career-essential websites that are easy to maintain and to integrate with popular social networks. www.netmusician.org <http://www.netmusician.org> [email protected] <mailto:[email protected]> -- 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.
<<inline: compose-unknown-contact.jpg>>
<<inline: nmtwitter.png>>
