If I could build a distro within 1 year which boots into a terminal, it would already be good enough for me.
Ahh, I think you'll be much better off with: http://www.jamesmolloy.co.uk/tutorial_html/
]]>I 'll stop now. i don't like to drift this thread away in a different direction.
]]>No one can stick with Linux for a long time without understanding a bit.
Yearly repeat offenders (troll the dustbin for examples) says you're wrong
@OP - work on an installation framework (like the AIF) as a separate project. Document it well, be very clear on what decisions it makes automatically for the users, have a thread discussing it (maybe another one for user-support).
If its good enough, it will possibly be included with the Arch ISO (that's how AIF started out as well). If its not, its not.
]]>How about creating a custom ISO with the features you would have liked to be in the CD/DVD like archboot(I understand Archboot is still hosted in arch mirrors) and post the links in forums. There is a script that would let you create a archboot CD with latest packages too. You could start like that.
]]>Or keep within Arch, contribute the programs you want to write via the excellent community contribution section and the aur as alternatives to what is in the mainstream of Arch. And have fun too. :-)
]]>Imagine that you discover a vast wilderness untouched by the problems of modern society. The people who live there live simply and make their way as one with their ecosystem. They enjoy this way of life and they thrive there. Those who have joined that community have joined because they share common interests and values. They understand what it takes to make it there and they willingly embrace the philosophy and contribute to that way of life.
Upon seeing this, you realize how great it is and you want to open it up to more people, but you know that most people would not be willing to go without the comforts of modern indoor plumbing and massive supermarkets with frozen meals, so you propose to tear down a large chunk of the surrounding wilderness to build a strip mall and some highways to help others integrate into the existing ecosystem, because you love this way of life so much.
]]>What "we" think about it:
http://allanmcrae.com/2012/12/battle-of … spin-offs/
http://allanmcrae.com/2013/01/manjaro-l … stability/
http://allanmcrae.com/2013/01/manjaro-l … follow-up/
https://bbs.archlinux.org/viewtopic.php?id=157706
https://bbs.archlinux.org/viewtopic.php?id=157361
https://bbs.archlinux.org/viewtopic.php?id=158051
https://bbs.archlinux.org/viewtopic.php?id=156645
http://jasonwryan.com/blog/2013/03/02/forking/
Also if the Arch devs decide to make some changes to the way packages are built or delivered, there is a potential to break your entire distro. Case in point, when Arch decided to move to systemd, there was an effort by distros based on Arch to keep providing sysvinit based systems. How successful those attempts were, I am not sure. But be assured, it will require a lot of work on your part as a distro developer.
]]>I would love it if Arch became a more popular choice for end-users. But at the moment, the way it is installed and the efforts that have to be taken to get into a DE are, in my humble opinion, the reasons that Arch is still something for geeks and power-users. And if the Arch philosophy doesn't consider to get a bigger share in the distro choice and become more mainstream, I can totally understand that (heck, I wouldn't want Arch to change at all; for power-users it's the perfect distro IMO).
So simply put, I am not necessarily trying to roll out a new distro which reinvents the wheel entirely: I want to make a contribution of which I think that it would be helpful for Arch to become more popular. And if someone like you, jasonwryan, who made great contributions to Arch Linux, thinks it is unnecessary to open up this road, I can understand that and I will try to make contributions to this project on different ways, such as application development. I just thought this could be something which could improve the status of Arch Linux at end-users and non-Linux-users, but if people think it would be better to spend time on improving the possibilities for the power-users, that is what I will attempt to do
Oh, and don't get me wrong: I am not saying I am a skilled coder who can take on an enormous project and should be working for a big company a year ago, I am just a humble hobbyist who wants to add something to a community, so I can say within 5 years: "yes, I think I did my best to make a contribution to an open-source effort".
Like I said, your goals are admirable. But Arch isn't intended for "mainstream"
users (ie., people who view computers as appliances that they turn on and just
work™), so IMO you efforts would be better directed to assisting the existing
contributors make Arch itself better; bug fixing, submitting patches, editing
the wiki, helping out here and on IRC etc. There is plenty to do, rest assured
you won't get bored…
Wanna make something new? Start from scratch. Even if the output isn't perfect, it's going to be more credible in its novelty.
(Sorry: that's only 2 cents from a tired distro-watcher...)
]]>