The end of Shift Linux


Recommended Posts

I think many have seen this day coming for a while.

We've made the decision to end Shift Linux, for a number of reasons. The biggest one is that we simply don't have the time. CrimsonRedMk and I have both school and other projects to work on (mine with Neowin mostly, and his on numerous other things, Firefly included).

We also can't really generate the interest on Neowin. We have tried, and there are spurs of activity, but for the most part it has been quiet in these forums. A lot of this also relates back to the lack of time: any time we have for Shift goes into Shift itself, and not promoting it.

Finally, we could never define the right purpose, and when we did we always veered off the path we wanted.

I am very unhappy to have to do this, but the time has come to let Shift go. Anyone interested in developing a Linux distro should consider helping out Firefly Linux. It's a great project that spawned from Shift.

Thanks to all of you for the support you have given. In particular, thanks to Barney for starting this adventure. We have done amazing things, and the potential was great, but the time and dedication needed was just not worth it. Also, thanks to CrimsonRedMk who did a kick ass job developing a majority of the developing and did an amazing job spearheading our Arch Linux conversion. Thanks also to DaveLegg for hosting our website and putting a lot of time into developing it, and to Ste for hosting our repository. Everyone else, too: advisors, developers, users: you all helped so much with this project. There are far too many to name.

A huge thanks to the Neowin administration. The support we have received from the site has been phenomenal, through promotional space on the front page and other venues of support.

- Simon

Edited by Mr. Andrews
Link to comment
https://www.neowin.net/forum/topic/752672-the-end-of-shift-linux/
Share on other sites

I'm sad to hear this, I was going to give the late (>.9) releases a try since I don't have a test box. As a future user, I never understood what direction this project was supposed to take that would set it apart from dozens of distros already out there, I didn't know that it wasn't clear the developers either. Sad to hear this die. :(

I'm sad to hear this, I was going to give the late (>.9) releases a try since I don't have a test box. As a future user, I never understood what direction this project was supposed to take that would set it apart from dozens of distros already out there, I didn't know that it wasn't clear the developers either. Sad to hear this die. :(

We tried... but we didn't want something too specific. We wanted a netbook distro, but knew that wouldn't go really far under the Shift name, or on a community as diverse as neowin. So CrimsonRedMk made Firefly.

We gave it all we had, and achieved the goal: I think we taught more than one person how to make a Morphix ISO, an Ubuntu ISO, and finally, an Arch Linux ISO. Boy, we've been far.

This is the important thing. Our real purpose was to learn. Lately we got caught up in making something new, because we were ready to. But the goal was to learn, and we had a lot of fun doing it.

The problem is, that Linux only attracts a minority and already has its big players and fans...

You can't simply throw out Linux distro nr 1'000'000 and hope that a big community will help to make it popular and to justify its existence...

Why should a Linux guy that already is fighting agains xxxx throw away his distro and switch over?

Also if say... ubuntu with a different icon for an app and a new about graphics comes out... i don't switch to it and do that big work again when im happy with my current solution...

And just imagine having a problem and theres only a twomen show working on that distro...

You need manpower, ideas and time... not only a good intention.

But thumbs up for every intention to help the community! :)

I'd just like to extend a personal welcome to Firefly Linux. Based on Shift, but with a Netbook and Virtual-Machine goal, with openness for community editions. Here's the forum, the wiki, and the Twitter. Get involved and we can go far. I also have preliminary plans for a How-To wiki covering everything the Shift team learned by making Shift - mainly how to make Live CDs the "real" way (manually, through the command-line). If anyone wants to help with the wikis, stop by. I need to learn MediaWiki formatting :unsure:

We gave it all we had, and achieved the goal: I think we taught more than one person how to make a Morphix ISO, an Ubuntu ISO, and finally, an Arch Linux ISO. Boy, we've been far.

This is definitely true. I don't know how to quantify how much I owe the Shift Team since I switched to Linux almost two years ago. A sad day indeed! :(

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • This got me thinking, would you rather a self driving car prioritise protecting its passengers or everyone else? I'd choose the one that keeps me and my kids safest. At some point, these cars have to make those choices already, don't they? Wonder if we have a way to find out what way they lean.
    • The proportion (or number of iterations) has nothing to with this aspect of Copyright I am describing. In short, it doesn't matter how many times the manager tells you to change something or how. Your work product is always YOURS until and unless you then assign that to the person representing the client/company, usually for financial compensation -- either in salary or as a subcontract work for hire payment. if iterations determined copyright, then businesses would have learned to just keep making changes until they could claim they owned the copyright, without having to compensate the artist for their work. And that would be BAD. The only place where the amount of changes does have a role is in how much does a human modify a previous public domain work (from any source) before it is considered fair use or their own work, etc. For example, if a human makes substantial changes to a public domain (re: AI, by definition) work, then they can then claim that derivative work as their own...but NEVER the original version, of course. That's why anyone can make a movie about Dracula, for example, as long as it is based on the public domain novel, but not if they take new ideas from copyrighted movies made afterwards. As one of the people who personally advised the US Copyright Office on their recent ruling on these very issues, be assured that I specifically used the terminology precisely -- though I made it simple enough for laymen to understand it. If I made this confusing by doing so, I apologize. But, to be clear regarding your assumption that I would agree to your second statement that I quoted above -- the answer is NO. If AI does the work, no matter how much "direction" you give it, it cannot be copyrighted. All AI generated content is in the Public Domain and therefore the copyright cannot be assigned to ANYONE, even you -- until and unless substantial modifications are made to it BY A HUMAN BEING (yourself or a contracted artist/writer/etc.) and then that copyright on the derivative work is legally (in writing) transferred to you. This is a critical distinction. And it is important that people, especially AI sloppers, understand this. For example, YouTube is not paying AI slop generators for the copyright, etc. of their AI slop. What YouTube is doing is sharing AD REVENUE for permission to publish your AI slop. Copyright/ownership/rights never come into it. Importantly, that means that anyone can copy any AI slopware on YouTube, etc. and rehost it anywhere they want, even back on YouTube, and there is nothing legal that YouTube can do about it with regards to copyright protections, ownership, DMCA, etc. Anyone is legally free to use any AI slopware in any way they want. When this ruling was pending, I warned Disney legal of all of this before they did their OpenAI deal -- that it would literally dilute their entire IP portfolio forever. They ignored that warning for the PR and stock bump. But that is why, when the ruling came down last year, Disney quickly extricated themselves from that OpenAI deal, even eating the initial upfront fees -- followed closely by OpenAI ending their entire AI video generating business model. They adjusted their PR release dates to make this less obvious to shareholders, of course. Phew. I hope that this clears up the key distinctions for you and anyone reading. If you have any additional questions or even hypotheticals about AI and Copyright, please feel free to ask.
    • Each of the devices displayed on this page now has a little volume meter next to it to show if there is audio actively playing. About time.
    • Owing to the nature of Windows feature enablement updates, it was distributed over Windows Update services as a complete system upgrade rather than as an ordinary cumulative update
  • Recent Achievements

    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      565
    2. 2
      +Edouard
      188
    3. 3
      Michael Scrip
      79
    4. 4
      PsYcHoKiLLa
      74
    5. 5
      neufuse
      71
  • Tell a friend

    Love Neowin? Tell a friend!