<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I think the next step would be to try to reconcile any differences
with the existing "Simplified Linux Server" proposal. The ideas are
somewhat similar, but may have philosophical differences. It would
work better if more people could agree on working on it together.<br>
<br>
Thanks,<br>
<br>
Omar<br>
<br>
<br>
<div class="moz-cite-prefix">On 5/2/2014 12:01 PM, Tim Krupinski
wrote:<br>
</div>
<blockquote
cite="mid:CA+F83q3UwOQutXOBosodfeXaOCAQxw6SxyAdODcF-33vJEZr4A@mail.gmail.com"
type="cite">
<p dir="ltr">Consider me interested. I unsuccessfully tried to get
involved in other ways with the centos project but the response
was pretty lukewarm. </p>
<p dir="ltr">I'm still very green with getting involved in
projects, but a lot if these goals line up with ideas I've had
for a while. </p>
<p dir="ltr">What's the next step? </p>
<p dir="ltr">Tim</p>
<div class="gmail_quote">On May 2, 2014 1:28 PM, "Omar Eljumaily"
<<a moz-do-not-send="true" href="mailto:omar1@omnicode.com">omar1@omnicode.com</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks Filippo. Here are some general comments on the home vs
business<br>
issue. I'm not trying to start an argument or anything like
that, just<br>
carry on a discussion about it.<br>
<br>
First of all when I think of what I would do strictly with a
home<br>
server, I'm thinking:<br>
<br>
1. Home security<br>
2. Home automation<br>
3. Entertainment<br>
4. Backup<br>
5. Cloudsync<br>
<br>
This is of course just me, my family, and my experience.
Also, I'm<br>
thinking of server vs client systems. So I think what would I<br>
personally do with a home server, these are things that I've
already<br>
done or intend to do. So I can put all my old VCR tapes and
DVDs onto a<br>
server and stream them to my tv, well that's cool and I think
a lot of<br>
people would find that a useful application. I might also
want to have<br>
the streaming app sync with other people on the internet for
some sort<br>
of comment streaming system. Maybe I can run a game server as
part of a<br>
broader internet community. That's also cool.<br>
<br>
Some of the things I probably will not do on a home server
which are<br>
listed on your proposal:<br>
<br>
Postfix<br>
Cyrus IMAP (or Dovecot)<br>
SpamAssassin<br>
ClamAV (from EPEL) (perhaps, but not for email)<br>
OpenSSL for user certificates<br>
<br>
I will almost definitely not run a home email server, and I
don't know<br>
anybody who runs a home email server. There are even
advocates of<br>
moving all business email to the cloud, and I frequently have<br>
conversations with my clients on that topic. However, there
are still<br>
important reasons for small businesses to run their own email
servers.<br>
It would also be very unlikely for a home user to run a public<br>
website/web application, but small business is likely to want
that for a<br>
number of reasons.<br>
<br>
Here is a list of things I think small business would use that
home<br>
users would not:<br>
<br>
1. Email server<br>
2. Single signon mechanisms<br>
3. File sharing/Samba in general (perhaps)<br>
4. Public web server (although private LAMP stack would be
useful).<br>
5. Client device management and backup (including PDC).<br>
6. VPN server<br>
7. LDAP<br>
8. RAID<br>
9. Replication & mirroring.<br>
<br>
<br>
Certainly not comprehensive, and of course some home users
would want<br>
these services, but they can always get the business version
if the 2<br>
versions are indeed separated.<br>
<br>
There's also this business of convincing people to use a Linux
based<br>
business server. I personally believe it would be an easier
sell if<br>
there were a special version very tightly targeted for just
business<br>
use. Yes, business owners can use the same coffee maker
that's in their<br>
home in their office, but for some reason they feel more
comfortable<br>
with something that looks like a commercial version.<br>
<br>
I think there certainly are a lot of areas of overlap, and
those areas<br>
should definitely be addressed, which is another topic. Of
course just<br>
my take, and thanks again.<br>
<br>
Omar<br>
<br>
<br>
<br>
On 5/2/2014 9:44 AM, Filippo Carletti wrote:<br>
>> One concern I have is how the project would be
"branded." I'm not sure<br>
>> exactly what you have in mind, but a generic name
that encompass both<br>
>> home and small office users might be too broad. It's
a subtle issue<br>
>> that may not be related to the technology, I know.<br>
> I agree with you, but we could be able to "solve" the
issue with more variants.<br>
><br>
>> Do you have a mailing list? I think I remember
reading that SIGs should<br>
>> have their own mailing lists. I can also talk here
if I don't wear out<br>
>> my welcome on this channel.<br>
> I think that SIGs do not have mailing lists at the moment
(you're<br>
> right, they're supposed to have them).<br>
> I hope to setup the wiki page for the SLS SIG later
today.<br>
> Meanwhile, I'm emailing you the SIG proposal.<br>
><br>
<br>
_______________________________________________<br>
CentOS-devel mailing list<br>
<a moz-do-not-send="true"
href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a><br>
<a moz-do-not-send="true"
href="http://lists.centos.org/mailman/listinfo/centos-devel"
target="_blank">http://lists.centos.org/mailman/listinfo/centos-devel</a><br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
CentOS-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a>
<a class="moz-txt-link-freetext" href="http://lists.centos.org/mailman/listinfo/centos-devel">http://lists.centos.org/mailman/listinfo/centos-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>