From: Christopher Schwan <cschwan@students.uni-mainz.de>
To: <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] The state and future of the OpenRC project
Date: Tue, 10 Jun 2014 12:30:09 +0200 [thread overview]
Message-ID: <3439561.dz4noWu4c3@cschwan-laptop> (raw)
In-Reply-To: <53962AF6.1050500@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2818 bytes --]
On Monday 09 June 2014 21:45:26 hasufell wrote:
> Probably because no one mentored them on how to fix these QA issues.
> Otherwise... if that's attitude, then that's just sad and has to be
> fixed by those who run that overlay (review, contribution guidelines).
>
> And I still think that the top 1 reason people run an overlay is because
> it's easier than contributing directly.
> A lot of overlay maintainers I tried to convince on getting more
> involved even said that.
>
> Even sunrise workflow has proven too slow and cumbersome... look at the
> commit history, it's constantly decreasing.
>
> Sure, reasons may vary, but there is not much positive to say about
> current gentoo workflow.
Since I was mentioned here - I am one of sage overlay[1] developers - it is
maybe worth sharing my point of view as someone that is not a Gentoo
developer. The recent discussion[2] with hasufell on our overlay might also be
interesting.
I have to agree that indeed it is easier to contribute to an overlay, in my
case because of
a) git and
b) github.
As far as I am up-to-date the main Gentoo repository is still managed by cvs,
right? Thats something I really would not like to work with. Not because cvs
is inferior to git (I hope no one feels offended) but because now I am so used
to and pleased with the workflow that comes with git that I can not even think
of changing that.
What I really love about github (and I don't think that similar platform
differ much here) is the fact that it allows me to comment on /everything/. I
can comment on commits that maybe lack something, which could then result in a
new Issue; a user could be faster than I and create a pull request that fixes
this problem. Maybe there is another mistake which I tell him there so he
adjusts his commit and I finally accept it. Sometimes, after some months I
wonder why we decided about some things the way we did and I can look it up in
the Issue. There is the _complete_ discussion with direct references to the
code and all people involved.
If there is a lession that I learned here, than that centralizing
communications and development in one place was beneficial for us. Whether
this also applies to the Gentoo project - well, I don't know. Right now there
are several mailing lists, IRC channels and the Bugzilla so in comparison to
our little overlay it is quite decentralized. Adding another way, e.g. via
github, could complicate the situation but it will defintely get the project
more user contributions (if that is needed).
In any case, I believe that the migration to git would be a huge step forward
and it would attract at least one pontential new developer ;). Any update on
this?
[1] https://github.com/cschwan/sage-on-gentoo
[2] https://github.com/cschwan/sage-on-gentoo/issues/294
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2014-06-10 10:30 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-07 18:19 [gentoo-dev] The state and future of the OpenRC project Tom Wijsman
2014-06-07 20:35 ` Daniel Campbell
2014-06-07 20:59 ` Anthony G. Basile
2014-06-07 21:29 ` Rick "Zero_Chaos" Farina
2014-06-07 21:08 ` Jeroen Roovers
2014-06-08 1:05 ` Alexander Berntsen
2014-06-08 11:56 ` Jeroen Roovers
2014-06-08 14:41 ` hasufell
2014-06-08 15:15 ` Jeroen Roovers
2014-06-08 16:06 ` hasufell
2014-06-09 19:52 ` Thomas Kahle
2014-06-09 21:45 ` hasufell
2014-06-09 22:12 ` Tom Wijsman
2014-06-10 8:57 ` Thomas Kahle
2014-06-10 11:44 ` Rich Freeman
2014-06-10 17:11 ` Peter Stuge
2014-06-10 12:09 ` Tom Wijsman
2014-06-10 10:30 ` Christopher Schwan [this message]
2014-06-10 10:42 ` Alexander Berntsen
2014-06-10 15:45 ` Andrew Savchenko
2014-06-10 15:49 ` Alexander Berntsen
2014-06-10 16:45 ` Andrew Savchenko
2014-06-10 17:09 ` Rich Freeman
2014-06-11 4:10 ` [gentoo-dev] " Ryan Hill
2014-06-11 4:17 ` Patrick Lauer
2014-06-11 11:38 ` Rich Freeman
2014-06-11 4:18 ` Duncan
2014-06-10 19:58 ` [gentoo-dev] " hasufell
2014-06-10 20:36 ` Sergei Trofimovich
2014-06-10 21:32 ` Rich Freeman
2014-06-11 12:59 ` Alexander Berntsen
2014-06-10 22:59 ` [gentoo-dev] The infinite git migration Patrick Lauer
2014-06-10 23:15 ` Rich Freeman
2014-06-11 0:48 ` Duy Nguyen
2014-06-11 0:55 ` Greg Turner
2014-06-11 9:38 ` Sergey Popov
2014-06-11 13:35 ` Duy Nguyen
2014-06-11 12:54 ` Alex Xu
2014-06-11 14:34 ` Rich Freeman
2014-06-11 18:46 ` Rich Freeman
2014-06-11 0:50 ` [gentoo-dev] The state and future etc. etc Patrick Lauer
2014-06-08 15:36 ` [gentoo-dev] Re: The state and future of the OpenRC project Michael Palimaka
2014-06-08 16:38 ` Alexey Shvetsov
2014-06-08 17:20 ` Alexander Berntsen
2014-06-10 2:53 ` heroxbd
2014-06-10 4:05 ` William Hubbs
2014-06-09 8:57 ` Amadeusz Żołnowski
2014-06-09 10:40 ` Rich Freeman
2014-06-09 12:36 ` Amadeusz Żołnowski
2014-06-10 2:30 ` [gentoo-dev] " heroxbd
2014-06-10 3:14 ` William Hubbs
2014-06-10 4:46 ` [gentoo-dev] " Duncan
2014-06-10 17:39 ` [gentoo-dev] " Andrew Savchenko
2014-06-10 18:18 ` Jeroen Roovers
2014-06-10 23:05 ` Patrick Lauer
2014-06-08 4:35 ` [gentoo-dev] " Duncan
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=3439561.dz4noWu4c3@cschwan-laptop \
--to=cschwan@students.uni-mainz.de \
--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