From: Igor <lanthruster@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Question, Portage QOS
Date: Fri, 10 Jan 2014 20:48:30 +0400 [thread overview]
Message-ID: <52d02460.431c980a.17aa.ffffad03@mx.google.com> (raw)
Hello All,
Thank you for all our feedback!
It's very good that we have all many different views on the same
subject. The nature designed us in a way that some part of us is
to survive in almost any situation. If everyone thought the same
they would make the same decisions and the probability of survival
would decrease. So it's all very natural and I didn't expect it
going easy.
In project like that I can't rush to programming it without
everyone's approval. This part of the project should have been
implemented with the first portage version by it's creator. But as
I'm not this person I'll need the expertise of the whole community.
Let's agree on following - I'll design the system in details on paper.
When it's ready (~ 1.5 months) I'll get back here and share the details.
Then we all review it again everyone could contribute it's own view
and part and help to avoid some design problems if there are.
And then when the final version is ready and there is support and
understanding of everyone and everyone says YES and sees that system
could be helpful - I'll get in running in ~ 1.5 years alone or if
I find some help - faster. I would anyway need this design to
effectively program the soft. It's the first step, no matter if
there is the second.
Do we have an agreement on this one from everyone of the list?
Please vote.
--
Best regards,
Igor mailto:lanthruster@gmail.com
next reply other threads:[~2014-01-10 16:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 16:48 Igor [this message]
2014-01-10 16:58 ` [gentoo-dev] Question, Portage QOS Jon Portnoy
2014-01-10 17:14 ` Peter Stuge
2014-01-10 17:16 ` Ian Stakenvicius
2014-01-11 11:32 ` Roy Bamford
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=52d02460.431c980a.17aa.ffffad03@mx.google.com \
--to=lanthruster@gmail.com \
--cc=gentoo-dev@lists.gentoo.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