From: Igor <lanthruster@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Question, Portage QOS v3
Date: Fri, 10 Jan 2014 21:26:47 +0400 [thread overview]
Message-ID: <52d02d58.0b1a700a.1f2e.ffffad96@mx.google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2256 bytes --]
Hello All,
As there are more questions rose. See you can't just think of everything,
what you need is an ability to improve fast :-)
----------------------------------------------
Thank you for all our feedback!
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
but no code will be produced at this stage.
When it's ready (~ 1.5 months) I'll get back here and share the design
sketches with you.
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.
I need an agreement on this stage from the list.
If you consider PortageQOS is not necessary please vote NO.
If you consider PortageQOS might have a chance and it depends on
implementation say YES.
Please vote.
If NO there is no need to spend time even on sketches.
If YES - there will be a system design ready and we could at least
imagine how it might work as a whole and benefits it might bring.
------------------------------------------------------------------
BY VOTING WE MAKE NO ASSUMPTION that the PROJECT is going to be INTEGRATED
in GENTOO without further approval.
At this stage the design will serve only as a demonstration that such
system could actually be implemented and used for benefits of GENTOO
project.
If community finds the design worth trying we'll push it for approval
and then it will be implemented.
------------------------------------------------------------------
PS
No way PortageQOS will work without uniform agreement. That thing
was missing from portage design from the start and now with the legacy
it's either everyone is willing to give it a try or none. I don't want
to push somebody to something he doesn't see purpose for. There are
people here who spent lots of time on the project and it might be left
as is if they don't want any change.
--
Best regards,
Igor mailto:lanthruster@gmail.com
[-- Attachment #2: Type: text/html, Size: 3002 bytes --]
next reply other threads:[~2014-01-10 17:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 17:26 Igor [this message]
2014-01-10 17:40 ` [gentoo-dev] Question, Portage QOS v3 Jeroen Roovers
2014-01-10 21:12 ` [gentoo-dev] " Duncan
2014-01-10 21:39 ` [gentoo-dev] " Michał Górny
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=52d02d58.0b1a700a.1f2e.ffffad96@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