From: Igor <lanthruster@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] A constructive reommendation on stablity improvemt
Date: Sat, 9 Aug 2014 20:18:44 +0400 [thread overview]
Message-ID: <53e649e6.c8a1980a.2941.4762@mx.google.com> (raw)
Hi all,
Hereby the summary of my personal suggestions to increase GENTOO stability and help it's maintainers
and developers.
1. make.conf
Add
BUG_REPORT_URL "http://"(or similar name)
BUG_REPORT ON/OFF
BUG_REPORT_LEVEL
to make.conf
(several URLs should be supported for several sever-side contributors versions)
by default reporting is turned off.
2. USE flag
use some flag like curl for emerge to disable bug reporting functionality for those
who are not trusting, afraid of leaks or who is not willing to participate.
3. Python URL reporting class
Add HTTP based bug reporting mechanics to emerge WITHOUT implementing
server-side mechanics.
4. Carefully document bug reporting mechanics.
5. Wait for server-side implementations to appear. They will appear once
emerge can report. And once it's clear for the rest that there is seriously
going to be a change soon.
I do honestly believe it should be started by portage team, not by any one else.
They're the key. Reporting callbacks are not difficult and not time consuming.
But only the emerge team has the experience to start it right. They have to get
into this idea themselves, approving it by introducing the interface.
In my point of view - it's fair.
Expecting:
Once interface is there several teams would develop sever side platform. I know there
are people out there who will present their own versions.
The platforms would be tested with existing emerge reporting interface and emerge reporting
interface will evolve with time.
With time the best server platform will be adopted by http://bugreport.gentoo.org (or
something like that).
When this stage is over:
The new tools will be developed, like developer e-mail notifications, automated bug reporting,
difficult to imagine that far.
GENTOO would get over portage hell and a new sub-system addressing GETNOO functional
stabilization are developed.
I expect we all get many new users for GENTOO,
Common guys GENTOO has a lot of potential, problems are fixable once you know more about
them, GENTOO just needs a little love, some statistics based stabilizations tools,
a compass for developers, a lot of experienced developers here - they will use gathered data
to make changes nobody even can think about now. Turn your friendly face to the users -
they're afraid of gentoo only because it's difficult to assemble packages, if this
shortcoming is fixed - it might be the best linux distro on the planet. All it requires
is a small reporting class in portage from an experienced portage developer. 1000 lines
of code max and there is a new future for everyone.
--
Best regards,
Igor mailto:lanthruster@gmail.com
next reply other threads:[~2014-08-09 16:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 16:18 Igor [this message]
2014-08-09 17:42 ` [gentoo-dev] A constructive reommendation on stablity improvemt Kent Fredric
2014-08-09 18:15 ` Igor
2014-08-09 19:22 ` Jeroen Roovers
2014-08-09 19:59 ` Kent Fredric
2014-08-10 0:41 ` Tim Boudreau
2014-08-10 18:53 ` Igor
2014-08-10 21:05 ` Thomas Kahle
2014-08-09 19:49 ` Kent Fredric
2014-08-10 19:02 ` Igor
2014-08-10 21:03 ` Thomas Kahle
2014-08-12 14:13 ` Ian Stakenvicius
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=53e649e6.c8a1980a.2941.4762@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