Perl 6 - the future is here, just unevenly distributed

IRC log for #gluster-dev, 2014-12-11

| Channels | #gluster-dev index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
03:45 rafi joined #gluster-dev
03:47 bharata-rao joined #gluster-dev
03:53 atinmu joined #gluster-dev
03:59 itisravi joined #gluster-dev
04:04 kanagaraj joined #gluster-dev
04:19 bala joined #gluster-dev
04:22 jiffin joined #gluster-dev
04:27 soumya_ joined #gluster-dev
04:30 ndarshan joined #gluster-dev
04:32 rafi joined #gluster-dev
04:34 hagarth joined #gluster-dev
04:38 jiffin1 joined #gluster-dev
04:42 anoopcs joined #gluster-dev
04:47 badone joined #gluster-dev
04:50 bala joined #gluster-dev
05:04 Gaurav_ joined #gluster-dev
05:05 kdhananjay joined #gluster-dev
05:17 ppai joined #gluster-dev
05:29 lalatenduM joined #gluster-dev
05:32 sachin joined #gluster-dev
05:41 raghu` joined #gluster-dev
05:57 overclk joined #gluster-dev
05:57 bala joined #gluster-dev
06:07 kshlm joined #gluster-dev
06:50 soumya_ joined #gluster-dev
06:56 prasanth_ joined #gluster-dev
07:13 ndarshan joined #gluster-dev
07:15 lalatenduM hagarth, http://review.gluster.org/#/c/9264/ is ready to be merged , gothos has submitted these patches
07:15 lalatenduM ndevos, ^
07:17 lalatenduM gothos, I think this is also fixed by your patch https://bugzilla.redhat.co​m/show_bug.cgi?id=1165133
07:17 glusterbot Bug 1165133: medium, high, ---, lmohanty, ASSIGNED , logrotate script in glusterfs package tries to rotate non-existant directories
07:20 nishanth joined #gluster-dev
07:43 lalatenduM gothos, ndevos I have closed https://bugzilla.redhat.co​m/show_bug.cgi?id=1170814 as a duplicate of https://bugzilla.redhat.co​m/show_bug.cgi?id=1165133 as 1165133 is raised earlier. Updated the commit message with 1165133.  Assigned 1165133 to gothos
07:43 glusterbot Bug 1170814: unspecified, unspecified, ---, bugs, CLOSED DUPLICATE, GlusterFS logrotate config complains about missing files
07:43 glusterbot Bug 1165133: medium, high, ---, zab, ASSIGNED , logrotate script in glusterfs package tries to rotate non-existant directories
08:04 ndevos lalatenduM: okay, mainline merged
08:05 ndevos lalatenduM: I normally keep the one open which has a patch, when I close/duplicate bugs
08:06 ndevos lalatenduM: otherwise the patch needs to be update (which *you* can do, but not everyone), so it saves a step
08:14 lalatenduM ndevos, I also thought the same , but was not sure hence went by book i.e. keeping the old bug and closing the new bug
08:28 ndevos lalatenduM: sure, I understand that, but we're flexible :)
08:30 anoopcs1 joined #gluster-dev
08:33 anoopcs1 joined #gluster-dev
08:33 lalatenduM ndevos, yes :)
08:35 Debloper joined #gluster-dev
08:37 yusuf joined #gluster-dev
08:38 yusuf left #gluster-dev
08:40 anoopcs joined #gluster-dev
08:48 atinmu joined #gluster-dev
08:49 Guest10972 joined #gluster-dev
09:05 atalur joined #gluster-dev
09:10 kaushal_ joined #gluster-dev
09:20 Guest10972 joined #gluster-dev
09:29 overclk joined #gluster-dev
09:53 vimal joined #gluster-dev
09:53 ppai joined #gluster-dev
10:12 rgustafs joined #gluster-dev
10:18 kshlm joined #gluster-dev
10:30 kanagaraj joined #gluster-dev
10:32 overclk joined #gluster-dev
10:33 atinmu joined #gluster-dev
10:39 ppai joined #gluster-dev
10:47 hagarth joined #gluster-dev
10:50 topshare joined #gluster-dev
11:32 kkeithley1 joined #gluster-dev
11:47 vimal joined #gluster-dev
11:49 soumya joined #gluster-dev
11:59 overclk joined #gluster-dev
11:59 jiffin joined #gluster-dev
12:02 jiffin1 joined #gluster-dev
12:03 ppai joined #gluster-dev
12:04 atinmu joined #gluster-dev
12:22 itisravi joined #gluster-dev
12:22 anoopcs joined #gluster-dev
12:24 prasanth_ joined #gluster-dev
12:24 anoopcs joined #gluster-dev
12:31 anoopcs joined #gluster-dev
12:33 overclk joined #gluster-dev
12:36 topshare joined #gluster-dev
12:59 bala joined #gluster-dev
13:12 edward1 joined #gluster-dev
13:13 topshare joined #gluster-dev
13:56 soumya joined #gluster-dev
14:25 shyam joined #gluster-dev
14:43 lalatenduM joined #gluster-dev
15:00 lpabon joined #gluster-dev
15:06 wushudoin joined #gluster-dev
15:18 tdasilva joined #gluster-dev
16:16 jobewan joined #gluster-dev
16:49 vimal joined #gluster-dev
16:50 ppai joined #gluster-dev
17:02 hagarth joined #gluster-dev
17:54 lalatenduM joined #gluster-dev
18:22 ppai joined #gluster-dev
19:26 rafi joined #gluster-dev
20:10 JustinClift hagarth ndevos: Seen this? http://gerrithub.io
20:19 ndevos JustinClift: oh, thats cool!
20:19 ndevos JustinClift: we already have a gerrit interface, I'm not sure if it makes sense to move away from that
20:20 ndevos but, for new projects, or projects that do not use Gerrit yet, it is definitely great
20:20 JustinClift ndevos: https://www.youtube.com/watch?v=jeWTvDad6VM
20:20 JustinClift 3 mins.  Worth watching. ^ :)
20:20 JustinClift ndevos: So, I'm thinking of how we're going to replace the Forge with Forge v2.
20:21 JustinClift The thing that (I reckon) is stopping us from moving to GitHub, is mainly that we have a Gerrit workflow for the main project
20:21 JustinClift And I'd not seen a way to resolve that.  GitHub workflow is obviously pretty different to the Gerrit one, and we likely wouldn't want to "take a few steps backwards" by moving to GitHub only for that
20:22 JustinClift ndevos: My thinking at the moment is that we could do something like:
20:23 JustinClift a) For the existing projects on the Gluster Forge - those not using Gerrit - they could just be migrated to straight GitHub
20:23 JustinClift b) For the projects on the Forge that do use Gerrit, GerritHub may be the solution
20:24 JustinClift Possible downsides do exist: We lose direct control of our data, unless we put in place some form of backup solutoin (recommended :>)
20:24 JustinClift solution even
20:25 ndevos JustinClift: hmm
20:25 JustinClift ndevos: I'll probably muck around with GerritHub a bit first with some other minor project, just to see how it actually operates and get a feel for it.
20:26 JustinClift It's always possible it could be a bad implementation, which we'd like to know about up front (and avoid). ;)
20:26 JustinClift ndevos: Thoughts?
20:26 ndevos JustinClift: Gerrit for Forge projects could be overkill?
20:26 JustinClift Kinda
20:27 ndevos I think many forge projects only have one contributor :)
20:27 JustinClift I was thinking we only use Gerrit for the ones already using it
20:27 JustinClift The rest, we just migrate to straight GitHub ;)
20:27 ndevos I think we should use Gerrit for all the 'core' projects, which would include the qa/regression scripts and the like
20:28 JustinClift Sure
20:28 ndevos maybe you could do a test migration of the qa/regression-script repository to gerrithub?
20:28 JustinClift I'm personally not bothered by which.  I think the specifics of which should be Gerrit is a good topic for mailing-list discussion.
20:28 JustinClift ndevos: Aha, good idea.
20:29 JustinClift ndevos: I was trying to think of a good example repo we could try it out on
20:29 JustinClift That's a good one to try stuff out on
20:29 * JustinClift will do that
20:29 ndevos yeah, something where we as gluster developers can contribute and test it
20:29 ndevos JustinClift: propose that to the mailinglist, and see if you get any positive reactions?
20:30 JustinClift I'll run through the initial sign-up process myself to get it in there, just to see how the GerritHub process works first.
20:42 JustinClift Hmmmm, I'm not sure GerritHub would work for us.  The concept seems sound, but we'd need some ability to communicate results back to it using SSH (for our regression runs)
20:42 * JustinClift keeps investigating
20:46 JustinClift The people behind it seem to have lost interest too
20:46 JustinClift GerritForge hasn't been updated in ages. :(
20:54 JustinClift Heh, ironic.  I was staying in a hotel only a few miles away from the dev's, until yesterday.
21:02 * JustinClift emailed their dev's to find out if GerritHub is still being actively developed or not
21:02 JustinClift It's running the latest RC of Gerrit, so it's definitely not totally unmaintained
21:15 JustinClift Hmmm, GerritForge blog says they're really just a mix of Gerrit with a specific set of Enterprise plugins.  So completely open source.
21:26 badone joined #gluster-dev
21:44 badone joined #gluster-dev
23:08 shyam joined #gluster-dev

| Channels | #gluster-dev index | Today | | Search | Google Search | Plain-Text | summary