<HTML>
<style> BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px; }</style>My first post in the mailing list, though I've been reading it for some time. Hopefully I don't blow it re. how you are supposed to post here. :)<br>
<br>
I have something to say on this point:<br>
<br>
<span style="color: rgb(102, 102, 102); font-weight: bold;">2. Cancel your wiki and encourage those fresh faces to further improve the Arch one and discourage learned helplessness.</span><br>
<br>
It is my understanding that one of the prime considerations concerning the content of the Manjaro wiki, is that it be written in a fashion that new GNU/Linux users can understand. The ArchWiki is not written in that fashion, it expects the user to have some experience with GNU/Linux & also to know how to search for anything that they don't know about a topic, be the search within their wiki (where it is policy not to duplicate information) or elsewhere.<br>
<br>
If I went over to the ArchWiki, using my wiki editing privileges there & started rewriting their pages to suit those who are new to GNU/Linux, I would have my work removed & I would be chastised.<br>
<br>
There exists no common ground in this regard. <br>
<br>
<span style="color: rgb(102, 102, 102); font-weight: bold;">"and discourage learned helplessness</span>" is the kind of statement that I would expect from someone who has no compassion for those less knowledgeable, skilled & experienced than themselves. It is "that" all too common heartless attitude that turned me off Arch in the first place. That attitude in the Arch community is the biggest failing in the Arch community. <br>
<br>
<br>
<br>
<span style="font-weight: bold;">On Thu 12/12/13 08:18 , manjaro-dev-request@manjaro.org sent:<br>
</span><blockquote style="BORDER-LEFT: #F5F5F5 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">Send manjaro-dev mailing list submissions to<br>
<a href="mailto:manjaro-dev@manjaro.org">manjaro-dev@manjaro.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a target="_blank" href="http://lists.manjaro.org/cgi-bin/mailman/listinfo/manjaro-dev"><span style="color: red;">http://lists.manjaro.org/cgi-bin/mailman/listinfo/manjaro-dev</span></a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:manjaro-dev-request@manjaro.org">manjaro-dev-request@manjaro.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:manjaro-dev-owner@manjaro.org">manjaro-dev-owner@manjaro.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of manjaro-dev digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Fwd: Manjaro vs Arch (Rob McCathie)<br>
2. someone issues ff26 (Ringo de Kroon)<br>
3. Re: Fwd: Manjaro vs Arch (Philip M?ller)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Thu, 12 Dec 2013 00:39:59 +1100<br>
From: Rob McCathie <<a href="mailto:korrode@gmail.com">korrode@gmail.com</a>><br>
To: <a href="mailto:manjaro-dev@manjaro.org">manjaro-dev@manjaro.org</a><br>
Subject: Re: [manjaro-dev] Fwd: Manjaro vs Arch<br>
Message-ID:<br>
<caounmdekd=<a href="mailto:_OCEw6TFNz4EcSGvJ8jssAQRyVaOzKZiMWEUk2Jw@mail.gmail.com">_OCEw6TFNz4EcSGvJ8jssAQRyVaOzKZiMWEUk2Jw@mail.gmail.com><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
I haven't read his article yet, but in response to just the bullet points<br>
made in his email:<br>
<br>
<span style="color: rgb(102, 102, 102);">>1. Enable Manjaro setup to run out of the Arch repositories so people aren't locked in to your walled garden.</span><br>
<span style="color: rgb(102, 102, 102);">>2. Cancel your wiki and encourage those fresh faces to further improve the Arch one and discourage learned helplessness.</span><br>
<span style="color: rgb(102, 102, 102);">>3. Call yourself Arch so that you get better combined numbers on distrowatch, and more news articles. Any name is fine.</span><br>
<br>
<br>
<br>
1. The clear disadvantage to operating as just a repo listed above the<br>
official Arch ones in pacman.conf (like how Archbang and a few others do)<br>
is that the concept of preventing or at least reducing the amount of manual<br>
intervention required by users during updates goes out the window. Manjaro<br>
either wants to offer this or it doesn't, if it doesn't, then he's right,<br>
but my understanding is it does.<br>
Also I don't think it's at all accurate to refer to Manjaro as a "walled<br>
garden", it utterly isn't.<br>
<br>
2. This should be considered carefully. I basically agree with him that any<br>
information that can be universally applied to both Arch and Manjaro (which<br>
is like 98% of everything) should probably be going on the Arch wiki. It's<br>
illogical and inefficient to split the information across 2 wikis when the<br>
entire purpose of a wiki is to be a publicly created information source.<br>
<br>
3. I simply disagree here. Too much brand recognition and goodwill has<br>
already come "Manjaro's" way. Even if Manjaro were just a repo to be run in<br>
conjunction with the official Arch repos, I'd still see it as advantageous<br>
to keep the Manjaro name. Plus so long as Manjaro does a good job of<br>
catering to it's target user, i don't see that it does Arch any damage 9if<br>
anything, only benefit). Even if it didn't do a good job, Arch(ers) can<br>
just laugh and be like "yeah well, run Arch, not some fork/repo/whatever".<br>
<br>
<br>
<span style="color: rgb(102, 102, 102);">>One of the benefits of the above is that you will run your efforts more efficiently, so you will have more time to work on the important problems rather than all the grunt work of creating a full distro and a new brand, dealing with security bugs, keeping up with the flood of packages, needing to manage mirrors wikis, forums, etc. Do you want to make a new brand, or do you want to help Arch kick ass? Also, how much are you giving back to Arch right now?</span><br>
<br>
I think he doesn't understand the where the boundaries of Manjaro's target<br>
audience frontier are, or what's required to satisfy them. Though,<br>
sometimes I think I don't exactly understand those boundaries either.<br>
<br>
<br>
PS. Please excuse my email formatting if it's shotty. When I initially<br>
installed Manjaro I decided I wanted to re-evaluate my email client choices<br>
and just have never got around to it, been using webmail interfaces,<br>
they're generally not awesome.<br>
<br>
Regards,<br>
Rob.<br>
<br>
<br>
<br>
On Sun, Dec 8, 2013 at 8:47 PM, Philip M?ller <<a href="mailto:philm@manjaro.org">philm@manjaro.org</a>> wrote:<br>
<br>
<span style="color: rgb(102, 102, 102);">> Hmm, I got an interesting e-mail today in my inbox.</span><br>
<span style="color: rgb(102, 102, 102);">> What do you think?</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> greez</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> Phil</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> -------- Original Message -------- Subject: Manjaro vs Arch Date: Sat,</span><br>
<span style="color: rgb(102, 102, 102);">> 7 Dec 2013 22:38:59 -0500 From: Keith Curtis <<a href="mailto:keithcu@gmail.com">keithcu@gmail.com</a>><<a href="mailto:keithcu@gmail.com">keithcu@gmail.com</a>> To:</span><br>
<span style="color: rgb(102, 102, 102);">> <a href="mailto:philm@manjaro.org">philm@manjaro.org</a></span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> Hi;</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> Manjaro is an interesting project. Adding a simpler first step into</span><br>
<span style="color: rgb(102, 102, 102);">> the Arch world is an extremely valuable idea.</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> However, I have some suggestions:</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> 1. Enable Manjaro setup to run out of the Arch repositories so people</span><br>
<span style="color: rgb(102, 102, 102);">> aren't locked in to your walled garden.</span><br>
<span style="color: rgb(102, 102, 102);">> 2. Cancel your wiki and encourage those fresh faces to further improve</span><br>
<span style="color: rgb(102, 102, 102);">> the Arch one and discourage learned helplessness.</span><br>
<span style="color: rgb(102, 102, 102);">> 3. Call yourself Arch so that you get better combined numbers on</span><br>
<span style="color: rgb(102, 102, 102);">> distrowatch, and more news articles. Any name is fine.</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> I can understand that you might not want to consider anything so</span><br>
<span style="color: rgb(102, 102, 102);">> radical. You've probably come to love the name Manjaro, and are</span><br>
<span style="color: rgb(102, 102, 102);">> excited by the recent success and new users, etc.</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> However, in general, it is best if people specialize. I'd love a</span><br>
<span style="color: rgb(102, 102, 102);">> pretty (HiDPI) installer that did all the right things for me</span><br>
<span style="color: rgb(102, 102, 102);">> including following the best practices from the wiki, setting up</span><br>
<span style="color: rgb(102, 102, 102);">> Plymouth, etc. That problem is plenty big for a team of your size. I</span><br>
<span style="color: rgb(102, 102, 102);">> can think of many ways Arch could have a better out of box experience</span><br>
<span style="color: rgb(102, 102, 102);">> but it can entirely be done from a custom ISO from the standard</span><br>
<span style="color: rgb(102, 102, 102);">> repositories and one extra. That gives you plenty of flexibility for</span><br>
<span style="color: rgb(102, 102, 102);">> innovation, yet runs things more stream-lined for you.</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> One of the benefits of the above is that you will run your efforts</span><br>
<span style="color: rgb(102, 102, 102);">> more efficiently, so you will have more time to work on the important</span><br>
<span style="color: rgb(102, 102, 102);">> problems rather than all the grunt work of creating a full distro and</span><br>
<span style="color: rgb(102, 102, 102);">> a new brand, dealing with security bugs, keeping up with the flood of</span><br>
<span style="color: rgb(102, 102, 102);">> packages, needing to manage mirrors wikis, forums, etc. Do you want to</span><br>
<span style="color: rgb(102, 102, 102);">> make a new brand, or do you want to help Arch kick ass? Also, how much</span><br>
<span style="color: rgb(102, 102, 102);">> are you giving back to Arch right now?</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> Here is an article I wrote that discusses these ideas in more detail:<a target="_blank" href="http://keithcu.com/wordpress/?p=3389"><span style="color: red;">http://keithcu.com/wordpress/?p=3389</span></a></span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> Great job! Please focus.</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> What do you think?</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> -Keith</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> _______________________________________________</span><br>
<span style="color: rgb(102, 102, 102);">> manjaro-dev mailing list</span><br>
<span style="color: rgb(102, 102, 102);">> <a href="mailto:manjaro-dev@manjaro.org">manjaro-dev@manjaro.org</a></span><br>
<span style="color: rgb(102, 102, 102);">> <a target="_blank" href="http://lists.manjaro.org/cgi-bin/mailman/listinfo/manjaro-dev"><span style="color: red;">http://lists.manjaro.org/cgi-bin/mailman/listinfo/manjaro-dev</span></a></span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a target="_blank" href="http://lists.manjaro.org/pipermail/manjaro-dev/attachments/20131212/bf49646f/attachment-0001.html>"><span style="color: red;">http://lists.manjaro.org/pipermail/manjaro-dev/attachments/20131212/bf49646f/attachment-0001.html></span></a>;<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Wed, 11 Dec 2013 21:52:04 +0100<br>
From: Ringo de Kroon <<a href="mailto:ringodekroon@gmail.com">ringodekroon@gmail.com</a>><br>
To: <a href="mailto:manjaro-dev@manjaro.org">manjaro-dev@manjaro.org</a><br>
Subject: [manjaro-dev] someone issues ff26<br>
Message-ID: <<a href="mailto:52A8D074.6050003@gmail.com">52A8D074.6050003@gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
hi someone uses firefox26 ? it looks kind of unstable... at start it can <br>
drop out but at second or 3th time it stay cool...<br>
had rebooted into 3.10 kernel but yeah same got this:<br>
<br>
java version "1.7.0_45"<br>
OpenJDK Runtime Environment (IcedTea 2.4.3) (ArchLinux build <br>
7.u45_2.4.3-1-x86_64)<br>
OpenJDK 64-Bit Server VM (build 24.45-b08, mixed mode)<br>
/build/icedtea-web-java7/src/icedtea-web-1.4.1/plugin/icedteanp/IcedTeaNPPlugin.cc:652: <br>
thread 0x7f48bab66cc0: Error: Unknown plugin value requested.<br>
[<a href="mailto:ringo@manjaro">ringo@manjaro</a> ~]$ firefox<br>
<br>
<br>
<br>
trying recreate it but failed on that :'(<br>
<br>
-- <br>
ringo de kroon <<a href="mailto:ringodekroon@gmail.com">ringodekroon@gmail.com</a>><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Wed, 11 Dec 2013 22:16:14 +0100<br>
From: Philip M?ller <<a href="mailto:philm@manjaro.org">philm@manjaro.org</a>><br>
To: <a href="mailto:manjaro-dev@manjaro.org">manjaro-dev@manjaro.org</a><br>
Subject: Re: [manjaro-dev] Fwd: Manjaro vs Arch<br>
Message-ID: <<a href="mailto:52A8D61E.7040906@manjaro.org">52A8D61E.7040906@manjaro.org</a>><br>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"<br>
<br>
On 12/11/2013 02:39 PM, Rob McCathie wrote:<br>
<span style="color: rgb(102, 102, 102);">> I haven't read his article yet, but in response to just the bullet </span><br>
<span style="color: rgb(102, 102, 102);">> points made in his email:</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> >1. Enable Manjaro setup to run out of the Arch repositories so people aren't locked in to your walled garden.</span><br>
<span style="color: rgb(102, 102, 102);">> >2. Cancel your wiki and encourage those fresh faces to further improve the Arch one and discourage learned helplessness.</span><br>
<span style="color: rgb(102, 102, 102);">> >3. Call yourself Arch so that you get better combined numbers on distrowatch, and more news articles. Any name is fine.</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> 1. The clear disadvantage to operating as just a repo listed above the </span><br>
<span style="color: rgb(102, 102, 102);">> official Arch ones in pacman.conf (like how Archbang and a few others </span><br>
<span style="color: rgb(102, 102, 102);">> do) is that the concept of preventing or at least reducing the amount </span><br>
<span style="color: rgb(102, 102, 102);">> of manual intervention required by users during updates goes out the </span><br>
<span style="color: rgb(102, 102, 102);">> window. Manjaro either wants to offer this or it doesn't, if it </span><br>
<span style="color: rgb(102, 102, 102);">> doesn't, then he's right, but my understanding is it does.</span><br>
<span style="color: rgb(102, 102, 102);">> Also I don't think it's at all accurate to refer to Manjaro as a </span><br>
<span style="color: rgb(102, 102, 102);">> "walled garden", it utterly isn't.</span><br>
<br>
There is one simple reason we clone Arch-Repositories on our own server <br>
framework we have built up on many locations thru the world:<br>
<br>
- this is the only way that we are in control when and what we want to <br>
update.<br>
<br>
Arch is sometimes fast in updates and it doesn't care much about <br>
3rd-party development groups. I had this situation with KDEmod I did <br>
under the Chakra Project. Our packages simply broke time to time and it <br>
was really frustrating to rebuild all those packages all the time. <br>
Manjaro isn't locked at all. We simply slow down the updates. You can do <br>
almost all what you do with a normal Archlinux installation.<br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> 2. This should be considered carefully. I basically agree with him </span><br>
<span style="color: rgb(102, 102, 102);">> that any information that can be universally applied to both Arch and </span><br>
<span style="color: rgb(102, 102, 102);">> Manjaro (which is like 98% of everything) should probably be going on </span><br>
<span style="color: rgb(102, 102, 102);">> the Arch wiki. It's illogical and inefficient to split the information </span><br>
<span style="color: rgb(102, 102, 102);">> across 2 wikis when the entire purpose of a wiki is to be a publicly </span><br>
<span style="color: rgb(102, 102, 102);">> created information source.</span><br>
<br>
The Arch-Wiki is filled with almost everything. The Manjaro-Wiki on the <br>
other hand is specific on things you need most in Manjaro and it is <br>
written for our distribution in mind being user friendly and easy to <br>
understand. We write articles for beginners, Arch wiki is understandable <br>
but written for more advanced users. Each wiki has its purpose.<br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> 3. I simply disagree here. Too much brand recognition and goodwill has </span><br>
<span style="color: rgb(102, 102, 102);">> already come "Manjaro's" way. Even if Manjaro were just a repo to be </span><br>
<span style="color: rgb(102, 102, 102);">> run in conjunction with the official Arch repos, I'd still see it as </span><br>
<span style="color: rgb(102, 102, 102);">> advantageous to keep the Manjaro name. Plus so long as Manjaro does a </span><br>
<span style="color: rgb(102, 102, 102);">> good job of catering to it's target user, i don't see that it does </span><br>
<span style="color: rgb(102, 102, 102);">> Arch any damage 9if anything, only benefit). Even if it didn't do a </span><br>
<span style="color: rgb(102, 102, 102);">> good job, Arch(ers) can just laugh and be like "yeah well, run Arch, </span><br>
<span style="color: rgb(102, 102, 102);">> not some fork/repo/whatever".</span><br>
<br>
This will never happen. Manjaro is a great brand and well known. If you <br>
want pure Arch you can go for Antergos, an Arch-Distrolet we work hard <br>
together.<br>
For example, thus is based on cnchi and we help each other to solve <br>
bugs. Also we try to use the same code as much as possible.<br>
<span style="color: rgb(102, 102, 102);">> >One of the benefits of the above is that you will run your efforts more efficiently, so you will have more time to work on the important problems rather than all the grunt work of creating a full distro and a new brand, dealing with security bugs, keeping up with the flood of packages, needing to manage mirrors wikis, forums, etc. Do you want to make a new brand, or do you want to help Arch kick ass? Also, how much are you giving back to Arch right now?</span><br>
<span style="color: rgb(102, 102, 102);">> I think he doesn't understand the where the boundaries of Manjaro's </span><br>
<span style="color: rgb(102, 102, 102);">> target audience frontier are, or what's required to satisfy them. </span><br>
<span style="color: rgb(102, 102, 102);">> Though, sometimes I think I don't exactly understand those boundaries </span><br>
<span style="color: rgb(102, 102, 102);">> either.</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> PS. Please excuse my email formatting if it's shotty. When I initially </span><br>
<span style="color: rgb(102, 102, 102);">> installed Manjaro I decided I wanted to re-evaluate my email client </span><br>
<span style="color: rgb(102, 102, 102);">> choices and just have never got around to it, been using webmail </span><br>
<span style="color: rgb(102, 102, 102);">> interfaces, they're generally not awesome.</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> Regards,</span><br>
<span style="color: rgb(102, 102, 102);">> Rob.</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> On Sun, Dec 8, 2013 at 8:47 PM, Philip M?ller <<a href="mailto:philm@manjaro.org">philm@manjaro.org</a> </span><br>
<span style="color: rgb(102, 102, 102);">> <<a href="mailto:philm@manjaro.org">philm@manjaro.org</a>>> wrote:</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> Hmm, I got an interesting e-mail today in my inbox.</span><br>
<span style="color: rgb(102, 102, 102);">> What do you think?</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> greez</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> Phil</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> -------- Original Message --------</span><br>
<span style="color: rgb(102, 102, 102);">> Subject: Manjaro vs Arch</span><br>
<span style="color: rgb(102, 102, 102);">> Date: Sat, 7 Dec 2013 22:38:59 -0500</span><br>
<span style="color: rgb(102, 102, 102);">> From: Keith Curtis <keithcu@gmail.com> <<a href="mailto:keithcu@gmail.com">keithcu@gmail.com</a>></keithcu@gmail.com></span><br>
<span style="color: rgb(102, 102, 102);">> To: philm@manjaro.org <<a href="mailto:philm@manjaro.org">philm@manjaro.org</a>></span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> Hi;</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> Manjaro is an interesting project. Adding a simpler first step into</span><br>
<span style="color: rgb(102, 102, 102);">> the Arch world is an extremely valuable idea.</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> However, I have some suggestions:</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> 1. Enable Manjaro setup to run out of the Arch repositories so people</span><br>
<span style="color: rgb(102, 102, 102);">> aren't locked in to your walled garden.</span><br>
<span style="color: rgb(102, 102, 102);">> 2. Cancel your wiki and encourage those fresh faces to further improve</span><br>
<span style="color: rgb(102, 102, 102);">> the Arch one and discourage learned helplessness.</span><br>
<span style="color: rgb(102, 102, 102);">> 3. Call yourself Arch so that you get better combined numbers on</span><br>
<span style="color: rgb(102, 102, 102);">> distrowatch, and more news articles. Any name is fine.</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> I can understand that you might not want to consider anything so</span><br>
<span style="color: rgb(102, 102, 102);">> radical. You've probably come to love the name Manjaro, and are</span><br>
<span style="color: rgb(102, 102, 102);">> excited by the recent success and new users, etc.</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> However, in general, it is best if people specialize. I'd love a</span><br>
<span style="color: rgb(102, 102, 102);">> pretty (HiDPI) installer that did all the right things for me</span><br>
<span style="color: rgb(102, 102, 102);">> including following the best practices from the wiki, setting up</span><br>
<span style="color: rgb(102, 102, 102);">> Plymouth, etc. That problem is plenty big for a team of your size. I</span><br>
<span style="color: rgb(102, 102, 102);">> can think of many ways Arch could have a better out of box experience</span><br>
<span style="color: rgb(102, 102, 102);">> but it can entirely be done from a custom ISO from the standard</span><br>
<span style="color: rgb(102, 102, 102);">> repositories and one extra. That gives you plenty of flexibility for</span><br>
<span style="color: rgb(102, 102, 102);">> innovation, yet runs things more stream-lined for you.</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> One of the benefits of the above is that you will run your efforts</span><br>
<span style="color: rgb(102, 102, 102);">> more efficiently, so you will have more time to work on the important</span><br>
<span style="color: rgb(102, 102, 102);">> problems rather than all the grunt work of creating a full distro and</span><br>
<span style="color: rgb(102, 102, 102);">> a new brand, dealing with security bugs, keeping up with the flood of</span><br>
<span style="color: rgb(102, 102, 102);">> packages, needing to manage mirrors wikis, forums, etc. Do you want to</span><br>
<span style="color: rgb(102, 102, 102);">> make a new brand, or do you want to help Arch kick ass? Also, how much</span><br>
<span style="color: rgb(102, 102, 102);">> are you giving back to Arch right now?</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> Here is an article I wrote that discusses these ideas in more detail:</span><br>
<span style="color: rgb(102, 102, 102);">> <a target="_blank" href="http://keithcu.com/wordpress/?p=3389"><span style="color: red;">http://keithcu.com/wordpress/?p=3389</span></a></span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> Great job! Please focus.</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> What do you think?</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> -Keith</span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> _______________________________________________</span><br>
<span style="color: rgb(102, 102, 102);">> manjaro-dev mailing list</span><br>
<span style="color: rgb(102, 102, 102);">> manjaro-dev@manjaro.org <<a href="mailto:manjaro-dev@manjaro.org">manjaro-dev@manjaro.org</a>></span><br>
<span style="color: rgb(102, 102, 102);">> <a target="_blank" href="http://lists.manjaro.org/cgi-bin/mailman/listinfo/manjaro-dev"><span style="color: red;">http://lists.manjaro.org/cgi-bin/mailman/listinfo/manjaro-dev</span></a></span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">></span><br>
<span style="color: rgb(102, 102, 102);">> _______________________________________________</span><br>
<span style="color: rgb(102, 102, 102);">> manjaro-dev mailing list</span><br>
<span style="color: rgb(102, 102, 102);">> <a href="mailto:manjaro-dev@manjaro.org">manjaro-dev@manjaro.org</a></span><br>
<span style="color: rgb(102, 102, 102);">> <a target="_blank" href="http://lists.manjaro.org/cgi-bin/mailman/listinfo/manjaro-dev"><span style="color: red;">http://lists.manjaro.org/cgi-bin/mailman/listinfo/manjaro-dev</span></a></span><br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a target="_blank" href="http://lists.manjaro.org/pipermail/manjaro-dev/attachments/20131211/c7dbfb29/attachment.html>"><span style="color: red;">http://lists.manjaro.org/pipermail/manjaro-dev/attachments/20131211/c7dbfb29/attachment.html></span></a>;<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
manjaro-dev mailing list<br>
<a href="mailto:manjaro-dev@manjaro.org">manjaro-dev@manjaro.org</a><br>
<a target="_blank" href="http://lists.manjaro.org/cgi-bin/mailman/listinfo/manjaro-dev"><span style="color: red;">http://lists.manjaro.org/cgi-bin/mailman/listinfo/manjaro-dev</span></a><br>
<br>
<br>
------------------------------<br>
<br>
End of manjaro-dev Digest, Vol 5, Issue 11<br>
******************************************<br>
<br>
</caounmdekd=<a></blockquote></HTML>