Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-11 Thread Alexander Berntsen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 10/06/14 18:45, Andrew Savchenko wrote: > Why are you saying that git is inefficient with large projects? Because it is. > It was developed with efficiency in mind in the first place. Not for big projects. > And kernel guys will likely disagree

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-10 Thread Patrick Lauer
On 06/11/2014 01:39 AM, Andrew Savchenko wrote: > On Sat, 7 Jun 2014 23:08:15 +0200 Jeroen Roovers wrote: >> On Sat, 07 Jun 2014 15:35:04 -0500 >> Daniel Campbell wrote: >> [2]: Overview of bugs that involve OpenRC, most for the package itself. https://bugs.gentoo.org/buglist.cgi?quicks

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-10 Thread Rich Freeman
On Tue, Jun 10, 2014 at 3:58 PM, hasufell wrote: > > interesting read: > http://thread.gmane.org/gmane.comp.version-control.git/189776 > > Does any1 know what fb currently uses or if any of these issues have > been resolved? > Not sure, but I did a git status on the actual gentoo-x86 converted re

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-10 Thread Sergei Trofimovich
On Tue, 10 Jun 2014 19:58:36 + hasufell wrote: > Andrew Savchenko: > > On Tue, 10 Jun 2014 17:49:15 +0200 Alexander Berntsen wrote: > >> On 10/06/14 17:45, Andrew Savchenko wrote: > >>> I don't know why CVS is still used for Gentoo main repository, > >>> probably some infrastructure elements

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-10 Thread hasufell
Andrew Savchenko: > On Tue, 10 Jun 2014 17:49:15 +0200 Alexander Berntsen wrote: >> On 10/06/14 17:45, Andrew Savchenko wrote: >>> I don't know why CVS is still used for Gentoo main repository, >>> probably some infrastructure elements depends deeply on its >>> internals, because I see of no othe

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-10 Thread Jeroen Roovers
On Tue, 10 Jun 2014 21:39:30 +0400 Andrew Savchenko wrote: > On Sat, 7 Jun 2014 23:08:15 +0200 Jeroen Roovers wrote: > > On Sat, 07 Jun 2014 15:35:04 -0500 > > Daniel Campbell wrote: > > > > > > [2]: Overview of bugs that involve OpenRC, most for the package > > > > itself. https://bugs.gentoo

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-10 Thread Andrew Savchenko
On Sat, 7 Jun 2014 23:08:15 +0200 Jeroen Roovers wrote: > On Sat, 07 Jun 2014 15:35:04 -0500 > Daniel Campbell wrote: > > > > [2]: Overview of bugs that involve OpenRC, most for the package > > > itself. https://bugs.gentoo.org/buglist.cgi?quicksearch=openrc > > > I think working on OpenRC woul

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-10 Thread Peter Stuge
Rich Freeman wrote: > likely bikeshedding .. > Or we can just accept that those using overlays will have them > break from time to time. Maybe there's an in-between. It's very reasonable to ask from an overlay maintainer that they run overlint now and then. If overlint can be taught to report when

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-10 Thread Rich Freeman
On Tue, Jun 10, 2014 at 12:45 PM, Andrew Savchenko wrote: > > Why are you saying that git is inefficient with large projects? It > was developed with efficiency in mind in the first place. And > kernel guys will likely disagree with "git is not great with crazy > big projects" statement. The kern

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-10 Thread Andrew Savchenko
On Tue, 10 Jun 2014 17:49:15 +0200 Alexander Berntsen wrote: > On 10/06/14 17:45, Andrew Savchenko wrote: > > I don't know why CVS is still used for Gentoo main repository, > > probably some infrastructure elements depends deeply on its > > internals, because I see of no other reason why Git is s

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-10 Thread Alexander Berntsen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 10/06/14 17:45, Andrew Savchenko wrote: > I don't know why CVS is still used for Gentoo main repository, > probably some infrastructure elements depends deeply on its > internals, because I see of no other reason why Git is still not > used des

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-10 Thread Andrew Savchenko
Hello, On Mon, 09 Jun 2014 21:45:26 + hasufell wrote: > Thomas Kahle: > > then they stay in the overlay > > because people feel it is not worth the effort to fix the QA > > issues which in turn would be necessary before moving them to the > > main tree. > > > > Probably because no one mentor

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-10 Thread Tom Wijsman
On Tue, 10 Jun 2014 10:57:32 +0200 Thomas Kahle wrote: > I was mentored on the QA issues and have come to 'this attitude' > myself. Take sci-mathematics/singular: Upstream is genuinely not > interested in supporting distriutions or their petty QA unless > you can prove them that there is a probl

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-10 Thread Rich Freeman
On Tue, Jun 10, 2014 at 4:57 AM, Thomas Kahle wrote: > > My personal attitude: It is just not worth the effort to rewrite > their build systems for the ~10 users out there. I have better > things to do with my time and I think that these packages can > live forever in the overlay and that is comp

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-10 Thread Alexander Berntsen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 For what it's worth, I strongly oppose using GitHub or any other SaaSS that is not licensed using AGPL or under similar terms. My suggestion is Phabricator, which additionally beats GitHub on functionality by having proper code review support. I wil

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-10 Thread Christopher Schwan
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

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-10 Thread Thomas Kahle
On 09.06.2014 23:45, hasufell wrote: > Thomas Kahle: >> then they stay in the overlay >> because people feel it is not worth the effort to fix the QA >> issues which in turn would be necessary before moving them to the >> main tree. >> > > Probably because no one mentored them on how to fix these

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-09 Thread William Hubbs
All, just a quick update. I now have a box set up for installing gentoo on it so I will be able to take the lead on OpenRC again. I will have that up and running, probably tomorrow, then I also have a medical situation I have to take care of in a couple of weeks. I will continue to be inte

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-09 Thread heroxbd
Alexander Berntsen writes: > It would be cool if some of the OpenRC hackers had the time to set up > a developer's wiki or similar, where they share their workflow and > similar. Nice idea, on my list. pgp5kJikw7nfi.pgp Description: PGP signature

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-09 Thread Tom Wijsman
On Mon, 09 Jun 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

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-09 Thread hasufell
Thomas Kahle: > then they stay in the overlay > because people feel it is not worth the effort to fix the QA > issues which in turn would be necessary before moving them to the > main tree. > Probably because no one mentored them on how to fix these QA issues. Otherwise... if that's attitude, the

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-09 Thread Thomas Kahle
On 08/06/14 18:06, hasufell wrote: > I am not sure if that is a joke. You can pretty much ask most major > gentoo projects. The ones where I was involved more deeply definitely > suffer from that problem, including sunrise and games team. Science team > gave up importing major ebuilds to the tree a

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-08 Thread hasufell
Jeroen Roovers: > On Sun, 08 Jun 2014 14:41:04 + > hasufell wrote: > >> The amount of contributors (with real patches and real ebuilds) is >> constantly decreasing, > > As evidenced where exactly? > I am not sure if that is a joke. You can pretty much ask most major gentoo projects. The on

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-08 Thread Jeroen Roovers
On Sun, 08 Jun 2014 14:41:04 + hasufell wrote: > The amount of contributors (with real patches and real ebuilds) is > constantly decreasing, As evidenced where exactly? > because our workflow is horrible. I hope you > don't actually think that bugzilla is an appropriate review platform. A

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-08 Thread hasufell
Jeroen Roovers: > On Sun, 08 Jun 2014 03:05:28 +0200 > Alexander Berntsen wrote: > >> On 07/06/14 23:08, Jeroen Roovers wrote: >>> You can start fixing bugs immediately. You can check out the >>> sources, write patches and attach the patches to the bug reports. >>> Then all it takes is someone el

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-08 Thread Jeroen Roovers
On Sun, 08 Jun 2014 03:05:28 +0200 Alexander Berntsen wrote: > On 07/06/14 23:08, Jeroen Roovers wrote: > > You can start fixing bugs immediately. You can check out the > > sources, write patches and attach the patches to the bug reports. > > Then all it takes is someone else to review/commit the

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-07 Thread Alexander Berntsen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/06/14 23:08, Jeroen Roovers wrote: > You can start fixing bugs immediately. You can check out the > sources, write patches and attach the patches to the bug reports. > Then all it takes is someone else to review/commit the patches. Hacking an i

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-07 Thread Rick "Zero_Chaos" Farina
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/07/2014 04:59 PM, Anthony G. Basile wrote: > Related to this, I'd like to take care of sys-apps/gentoo-functions in > WilliamH's absence. There's a couple of items to fix and I'd like to > get them done. Any objections? > Knowing WilliamH fa

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-07 Thread Jeroen Roovers
On Sat, 07 Jun 2014 15:35:04 -0500 Daniel Campbell wrote: > > [2]: Overview of bugs that involve OpenRC, most for the package > > itself. https://bugs.gentoo.org/buglist.cgi?quicksearch=openrc > I think working on OpenRC would be a great learning experience for me > and would be a great opportu

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-07 Thread Anthony G. Basile
On 06/07/14 16:35, Daniel Campbell wrote: On 06/07/2014 01:19 PM, Tom Wijsman wrote: Hello developers and users The OpenRC project appears less active these days than it used to be. There are many commits per month the last years, but the amount of commits in 2014 per month has noticeably decr

Re: [gentoo-dev] The state and future of the OpenRC project

2014-06-07 Thread Daniel Campbell
On 06/07/2014 01:19 PM, Tom Wijsman wrote: > Hello developers and users > > The OpenRC project appears less active these days than it used to be. > > There are many commits per month the last years, but the amount of > commits in 2014 per month has noticeably decreased to a crawl [1]. > Alongside

[gentoo-dev] The state and future of the OpenRC project

2014-06-07 Thread Tom Wijsman
Hello developers and users The OpenRC project appears less active these days than it used to be. There are many commits per month the last years, but the amount of commits in 2014 per month has noticeably decreased to a crawl [1]. Alongside that, there appears to be around ~100 bugs open for Open