From: "Usspookes Lovesystemd" <usspookslovesystemda@muchomail.com>
To: hellekin <hellekin@dyne.org>
Cc: <dng@lists.dyne.org>
Subject: Re: [Dng] About separate mailing lists - What systemd sounds like.
Date: Thu, 12 Feb 2015 11:01:15 -0800 [thread overview]
Message-ID: <20150212110115.39DD8CE3@m0005297.ppops.net> (raw)
I wish debian was like that! There WOULD NOT be this SITUATION NOW!
https://www.youtube.com/watch?v=UoqoYVntZAA
https://www.youtube.com/watch?v=UoqoYVntZAA
!!!
https://www.youtube.com/watch?v=UoqoYVntZAA
THIS IS WHAT SYSTEM DEE SOUNDS LIKE.
! ! ! ! ! !
--- hellekin@dyne.org wrote:
From: hellekin <hellekin@dyne.org>
To: dng@lists.dyne.org
Subject: Re: [Dng] About separate mailing lists
Date: Thu, 12 Feb 2015 15:57:50 -0300
On 02/12/2015 06:35 AM, Jaromil wrote:
>
> However we have started setting up a listserver with some volunteers and
> soon or later decisions will be made.
>
> Perhaps the first list to be born should one to discuss on how to
> structure the communication architecture?
>
*** I think we have it already: here :)
My take on this is very simple: if we don't need it, we don't do it.
When we need it, we try not to do it, for organic alternate solutions to
emerge, or for the bubble to break and the problem to fade away. If the
problem sticks around, then we have a real problem to tackle. Until
then, it's just wasting time. Sooner or later, we end up dead, better
not create problems that don't exist, we already have our plates full IMHO.
==
hk
--
_ _ We are free to share code and we code to share freedom
(_X_)yne Foundation, Free Culture Foundry * https://www.dyne.org/donate/
_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
_____________________________________________________________
The Free Email with so much more!
=====> http://www.MuchoMail.com <=====
reply other threads:[~2015-02-12 19:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150212110115.39DD8CE3@m0005297.ppops.net \
--to=usspookslovesystemda@muchomail.com \
--cc=dng@lists.dyne.org \
--cc=hellekin@dyne.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®