> I don't list any of the others because I personally only track one > list, OSXFUSE, whilst I know there are quite a few alternatives out > there that are better documented elsewhere on this increasingly spam > filled list. I'd rather people make their own mind up on which fork to > follow as each has their own ethos and objectives.
Ok. So it's okay for people to fork, good! > And a project in a stalled state for three years actively blocking > those who wish to make it work on an operating system that is now a > couple of months old and for the 64-bit native versions of the prior > release of said operating system (2009, around the same era as the > last release really) is rather much a PITA. One year? Sure, ok, busy. After a year, someone should have forked it, obviously. What's the problem with this? This isn't about good vs evil. > Two years? Perhaps time to look at things. Three years? Accept you're > not going to get back to it and move on or support those who wish to > help you out. I don't think forking after trying to recover a project > and having a company that prides itself on doing no evil and open > source step in the way instead of helping to facilitate the > improvement of that open source venture. Again, open source doesn't mean 'we do whatever Sam Moffat wants' or even 'we maintain a piece of software for x years' it doesn't even mean that we commit to naming successor projects. It does mean that people can fork the software if they don't like how it runs or how the project is being run. There isn't anything wrong with that and that's why we release under real open source licenses. Similarly, It isn't an open source 'venture'. It's a project. We've released something like 3k of them, not all of them are successful, fewer are under continuous development and fewer still are popular enough to warrant restaffing after a developer has moved on. Open sourcing something doesn't mean that the original developer has to continue to work on it until their last dying breath. It's okay for developers to move on, and it is similarly okay to ask that the project that is left behind isn't handed over to another and that they can fork if they don't like it. > Realistically the point of this place at the moment is to keep people > up and running with the lights on answering the posts directing > traffic and to continue to defend that Google didn't maliciously put > this software on their computer secret but most likely some other > application did it but just never told you or to explain why > com.google.macfuse is crashing on their system after upgrading to > Lion. Oh and to get spam because that never gets old I'm not going to begin to parse this, or reply further to this thread. Please fork this project and tell people where to find it. > > Cheers, > > Sam Moffatt > http://pasamio.id.au > > > > On Thu, Nov 17, 2011 at 12:15 AM, Chris DiBona <[email protected]> wrote: >> It's not evil for a developer to wish to maintain a project even in a >> stalled state. Nor is it evil to fork a project you see as being dead. >> So, please fork the code, and do wonderful work with it. Why don't you >> list some of the lists so that those who are interested can go check >> out those lists? >> >> Chris >> >> On Wed, Nov 16, 2011 at 11:04 AM, Sam Moffatt <[email protected]> wrote: >>> MacFUSE has been abandoned by it's owner for quite a long time. An >>> attempt to recover the project was made but Google in their infinite >>> wisdom reverted this because it was originally developed by a Googler >>> and returned the project back to said Googler ensuring that MacFUSE as >>> a name will die due to lack of interest from the owner. Do no evil >>> right? >>> >>> If you don't want spam, I'd suggest signing up to the lists of one of >>> the forked projects instead which are actively maintained and not >>> being ignored. >>> >>> Cheers, >>> >>> Sam Moffatt >>> http://pasamio.id.au >>> >>> >>> >>> On Wed, Nov 16, 2011 at 6:30 AM, Paul Eipper <[email protected]> wrote: >>>> Is there a mod of this list that can clean the spam out by >>>> kicking/banning the spammer accounts? >>>> >>>> -- >>>> Paul Eipper >>>> >>>> -- >>>> 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. >>>> >>>> >>> >> >> >> >> -- >> Director of Open Source, Google Inc. >> Our open source and developer programs can be found at http://code.google.com >> Site, Bio, Pics: http://dibona.com Google Plus: http://goo.gl/MRK6a >> Twitter: @cdibona >> > -- Director of Open Source, Google Inc. Our open source and developer programs can be found at http://code.google.com Site, Bio, Pics: http://dibona.com Google Plus: http://goo.gl/MRK6a Twitter: @cdibona -- 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.
