Thursday, 2010-07-01

*** Quits: siebrand (~beis@sm.xs4all.nl) ()01:41
*** Joins: kirillka (~Miranda@global01.vester.ru)01:54
*** Quits: kirillka (~Miranda@global01.vester.ru) (Read error: Connection reset by peer)01:54
*** Joins: kirillka (~Miranda@global01.vester.ru)01:55
*** Joins: tavasti (~tavasti@217.152.202.221)02:03
*** Joins: Cupertino (~Cupez@unaffiliated/cupertino)02:26
*** Quits: micahg (~micah@ubuntu/member/micahg) (Ping timeout: 265 seconds)02:38
*** Quits: Ragnor (~Ragnor@188.109.94.106) (Disconnected by services)03:01
*** Joins: Ragnor (~Ragnor@188.109.94.106)03:01
*** Quits: wolog (~wolog@wolog.info) (*.net *.split)03:02
*** Joins: giallu (~giallu@fedora/giallu)03:02
*** Joins: wolog (~wolog@wolog.info)03:04
*** Quits: kirillka (~Miranda@global01.vester.ru) (Ping timeout: 248 seconds)03:05
*** Joins: davidinc (d5374b0f@gateway/web/freenode/ip.213.55.75.15)03:06
*** Joins: kirillka (~Miranda@global01.vester.ru)03:09
*** Joins: Rixie (~Rixie@0x4dd7390e.adsl.cybercity.dk)03:37
*** Joins: fanno (~b3g@193.3.95.240)03:55
davidincHi04:05
*** Quits: davidinc (d5374b0f@gateway/web/freenode/ip.213.55.75.15) (Ping timeout: 252 seconds)04:12
*** Quits: Cupertino (~Cupez@unaffiliated/cupertino) (Quit: I give up...)06:17
dhx_mhi08:12
nuclear_eclipsehowdy dhx_m 08:22
dhx_mnuclear_eclipse: howdy08:22
nuclear_eclipseseems like paulr is our only dev who doesn't like github...08:23
dhx_m"paulr> using github probably helps as git.mantisbt.org can be less stable"08:24
nuclear_eclipseyeah, that made me laugh08:24
dhx_mit seems he's for :)08:24
dhx_mbut I think his concern was that people who had checked out the repositories from git.mantisbt.org will be left in the dark if they don't know about this change08:25
nuclear_eclipseyeah, be he's also for moving *everything* to his mantisforge system, too...08:25
nuclear_eclipsethat's possible, but that's what announcements are for :P08:26
dhx_mI'd actually prefer that approach if we were a larger project with 3-4 people minimum who were interested in actively looking after load balanced infrastructure08:26
nuclear_eclipseheh08:26
dhx_mbut we don't have the manpower to setup 2-3 servers in a cluster and maintain them through faults, upgrades, etc08:27
dhx_mmy main concern is that sourceforge changes something and we don't like the change08:27
dhx_moops github08:27
dhx_mwe lose control but gain reliability08:28
nuclear_eclipsewell, they've been continually pushing their support of open source projects, so I can't really see them doing anythign detrimental, and if anything, we can always just set up our own gitweb again :P08:28
nuclear_eclipseor *shudder* set up gitorious...08:29
dhx_mno thanks :D08:30
nuclear_eclipsehehe08:31
dhx_mnote to self: don't watch jquery project on Github... SNR is low08:31
nuclear_eclipsehaha08:31
nuclear_eclipseI laughed when I saw that in my feed08:32
nuclear_eclipsethere are very few projects that I watch on github, and they're all low traffic, which is the real reason I watch them, so I know when they've actually done something :P08:33
dhx_mand don't follow daryn because I'll get 1001 forked repository messages :p08:33
dhx_mhaha08:33
nuclear_eclipseI gotta head to work, but while I'm omw, Victor also mentioned interest in using github to replace the mantisforge repos -- can you ponder on ways to try and keep track of all of them without needing to fork/host repos under the mantisbt organization?  I'd like to keep the org for officially supported repos/plugins08:36
dhx_mI guess Github doesn't support that yet so I think it'd be better to stick with mantisforge for now08:37
dhx_mwith an aim towards having a system where good quality plugins can become "first class citizens" of the MantisBT org?08:38
dhx_mie. github repository under the MantisBT name, project on our bug tracker, etc08:38
dhx_mwe'd need to write up some documentation on that idea though (what expectations are of plugin authors, etc)08:38
dhx_mthe main problem I forsee with that approach is the possibility that a plugin author has ownership over their plugin once it's considered part of the MantisBT org08:39
dhx_mmuch like how Wikipedia tries to avoid having people "own" articles08:40
dhx_mso that anyone can improve a plugin (or in Wikipedia's case, an article) if there is consensus behind the change (rather than have a benovolent dictator approach)08:40
* nuclear_eclipse nominates dhx_m to write up that process for official review :P09:11
dhx_mI'm up for that :)09:11
nuclear_eclipsewe need a new wiki09:11
dhx_mI'll place it at position 150 on the agenda :p09:11
nuclear_eclipseone that doesn't suck ass09:11
nuclear_eclipselol09:11
dhx_midd09:11
dhx_mI really like this website: http://www.mono-project.com/Main_Page09:12
nuclear_eclipsehmm, we could use the Github wiki :P09:12
dhx_mit's MediaWiki... but it doesn't look like it :)09:12
nuclear_eclipsehmm, that oes look like a pretty nice template09:12
dhx_msteal it please :p09:12
nuclear_eclipselol09:13
dhx_mI couldn't find it anywhere last time I looked09:13
dhx_mperhaps I should ask :)09:13
nuclear_eclipseit's probably a one-off template done just for mono09:13
dhx_mit'd be nice to use as a reference if we were to do a similar thing09:14
dhx_mMediawiki templates are publicly accessible via Special: pages09:14
dhx_mbut that doesn't cover the changes needed to Mediawiki's PHP files (used for templating each style)09:14
*** Joins: daryn (~daryn@rrcs-76-79-4-2.west.biz.rr.com)09:29
*** Quits: kirillka (~Miranda@global01.vester.ru) (Quit: kirillka)09:32
*** Quits: fanno (~b3g@193.3.95.240) (Read error: Connection reset by peer)09:35
*** Quits: hellonull (~sean@c-68-40-112-255.hsd1.mi.comcast.net) (Quit: Leaving.)09:37
*** Parts: Rixie (~Rixie@0x4dd7390e.adsl.cybercity.dk)10:23
*** Joins: fanno (~Morten@90.184.93.233)10:42
*** Quits: giallu (~giallu@fedora/giallu) (Ping timeout: 240 seconds)11:46
*** Quits: mellen (~thansen@x1-6-00-22-02-00-0c-40.k253.webspeed.dk) (Ping timeout: 260 seconds)12:03
*** Joins: mellen (~thansen@x1-6-00-22-02-00-0c-40.k253.webspeed.dk)12:06
*** Joins: siebrand (~beis@sm.xs4all.nl)12:13
*** Joins: moto-moi (~hylke@cara.xs4all.nl)12:30
*** Joins: micahg (~micah@ubuntu/member/micahg)13:01
CIA-22Mantisbt: s.mazeland master-1.2.x * ra16cd8abcbae / (6 files in 2 dirs): Localisation updates from http://translatewiki.net13:20
*** Joins: paulr (~paul@cpc1-enfi9-0-0-cust389.hari.cable.virginmedia.com)13:44
paulrmoo13:44
* paulr pokes dhx_m13:44
*** Quits: micahg (~micah@ubuntu/member/micahg) (Ping timeout: 248 seconds)13:48
paulrnuclear_eclipse: I've had an idea regarding github13:58
nuclear_eclipseuh oh14:00
nuclear_eclipse(hi paulr)14:00
* daryn thinks this could be good...14:01
paulrdiner brb14:03
nuclear_eclipse /sigh14:03
* daryn ...again?14:03
paulrbk14:23
paulrthinking of setting up github to mirror whats on mantisforge14:23
paulrthat way14:23
paulrwe get benefits both ways14:23
nuclear_eclipsepaulr: the point is so that github is the primary access point 14:23
paulr(we still need to work out how people release plugins14:24
paulrwell14:24
paulrcan't really do that for plugins14:24
nuclear_eclipseif we just have github as a mirror, we might as well not use it at all14:24
nuclear_eclipsewe're not planning to use it for anything except the core mantis repos...14:24
paulryea14:24
paulrhence why I can mirror mantisforge plugins to github14:24
paulras a nice 'backup'14:25
nuclear_eclipseI'm not sure why that would be useful -- they are really discoverable at all on github14:25
nuclear_eclipsearent*14:25
paulryea, i've not played to see how github works14:25
paulrbut I was more thinking of it could be useful to have a backup somewhere14:26
darynwe're just waiting for the proper organization api's from github then write an interface for users to add themselves, teams, and new plugins to a mantis plugins organization14:26
darynthen they can be discoverable and manageable through github14:26
nuclear_eclipsetrying to automate mirroring/syncing between two separate public endpoints just sounds like it will cause norhing but pain and frustration14:28
nuclear_eclipsetheres multiple different ways where it can go wrong without any warning14:28
paulrwell, I've actually found I tend to prefer gitweb's interface for browsing source then github's (for annotating/diffing etc)14:31
paulrbut where one pushes to is irrelevant14:31
paulrall I'd say is if we push'd to github, if we could keep mantis bug tracker pointing at either git.mantisbt or git.mantisforge.org so when we click on a diff it goes to gitweb14:32
paulrthat would be fine with me14:32
paulrbut right now, need to fix some stuff14:33
paulrand try and catch dhx I guess on sunday now14:33
nuclear_eclipsewell, I was going to update the mantisbt.org tracker so that everything points to the github repos14:34
nuclear_eclipseitd be silly to be inconsistent IMO14:34
paulr:((14:34
nuclear_eclipsewhy use github if you're not going to have everything point to the same place?14:34
paulrwell, lets not bother then :)14:34
paulrI dont really see point of changing14:35
nuclear_eclipsewe'd bother because of the benefits I listed in theemail14:35
paulrgiven that mantisbt.org doesn't play up14:35
paulrgit's distributed14:35
nuclear_eclipseso then why do you care if we change wher the canonical repo is hosted at?14:36
paulrI prefer the speed of http://git.mantisbt.org/?p=mantisbt.git;a=commitdiff;h=a16cd8abcbaeca39fcc6ec57a6fd8d159f8f017914:36
paulrit's cleaner, and loads faster14:36
paulrdespite the server being in the US14:37
nuclear_eclipsethe point is to offload the repo management and collaboration to a site that simplifies all of that14:37
paulrwell, I'd still carry on trying to improve repo management for plugins on mantisforge14:37
paulrand mirroring core repo14:37
paulrso all that github would be is a push location14:37
paulrthat we can't then control as easily14:38
nuclear_eclipsebut we can14:38
paulrfor example14:38
nuclear_eclipseit's easier to control a github repo than to control a gitweb repo14:38
paulri'd like to build a release tarball of each commit in trunk so that if users grab a tarball14:38
paulrthey always get docs etc14:38
nuclear_eclipsethat's what we already do with the nightlies paul14:38
paulryea14:39
nuclear_eclipseyou're a bit late to that party14:39
paulrbut we don't keep them for ever14:39
paulrnor link them to specific commits14:39
nuclear_eclipsewhy would we need to keep them forever?14:39
paulrwell, a while at least14:39
nuclear_eclipsewho wants to download a tarball of an old commit, unless it's a release?14:39
paulralso14:41
paulrmore to point is github reliable14:41
paulrI just put into github search 'mantis'14:42
paulrclicked first link which goes to : http://github.com/jreese/mantisbt/tree/9f8516e83a9871077ea98ce2df2db8659b896667/core/classes/MantisCorePlugin.class.php14:42
paulrand got:14:42
paulr"That page doesn't exist!"14:42
nuclear_eclipsethat's because I deleted that repo14:43
nuclear_eclipseI'd imagine their search results get cached for a while, so they haven't flushed old data yet14:43
paulrwhen did you delete it?14:44
nuclear_eclipsewhen I search for mantis, I get victor's mantis-plugins as the top result14:44
nuclear_eclipseyesterday14:44
paulrso 24 hours?14:44
nuclear_eclipseactually, when I search for mantis, I get mantisbt/mantisbt (the new repo) in the result set at #414:45
nuclear_eclipseyes, < 24hours14:45
paulrtbh, i'd rather we just pointed bugtracker to the git.mantisforge.org and used git.mantisbt.org as central point or whatever14:46
paulrthen we can build git/testing/plugins into one place14:46
nuclear_eclipsethat doesn't even make any sense14:46
paulrrather then having one place for viewing git and one place for test results14:46
paulri've got 3 weeks off in a month when I plan to start pushing mantisforge and fixing automation issues14:49
paulror well when I say that14:49
paulrsetting up mantisforge to run your release tarball scripts etc14:50
nuclear_eclipseI'm still not sure what you think you're getting at that we don't already have with the nightly builds...14:50
nuclear_eclipsethe nightly builds already compile docbook and everythign14:51
paulryes, but if we are doing testing/continous integration14:51
paulrshould build tarballs as part of that also14:51
nuclear_eclipsewhatever, I'm still not sure what any of that has to do with why you don't like the idea of using github...14:52
paulrwe could take some load off of mantisbt.org box as that's apparently struggling :P14:52
nuclear_eclipseit's not struggling at all14:52
paulras I say, I prefer working with the simplicity of gitweb's user interface14:53
nuclear_eclipseso you can mirror the github repo to mantisforge and use the mantisforge interface; just because we switch to github doesn't mean you can't keep a mirror14:53
paulrhence why when I normally resolve bugs I normally include a link to git.mantisbt.org in the resolution14:54
paulrfor the patch14:54
paulras I said, don't mind core going to git hub14:54
paulrbut it would be good if bug tracker carried on pointing at a gitweb interface14:54
paulrso I can just click on links to patches14:55
nuclear_eclipsethat wouldn't make ansy sense at all paul14:55
paulrwhy?14:55
nuclear_eclipseif we have github as our primary repository, we're going to have the tracker point at github urls14:55
paulryou wanted github to ease admin14:55
nuclear_eclipsebecause it makes no sense to have the tracker point at some repo host that's not where our primary repo is hosted at14:55
paulrthen in which case, i'd rather not use github14:55
nuclear_eclipsenevermind paul14:56
paulras I tend to waste more time trying to find stuff on it14:56
paulrI'd rather invest my time to write a bot to post a bugnote to a bug linking to a gitweb interface when a commit references a bug number then try to compare diffs using github14:57
nuclear_eclipseyou're totally insane14:57
paulrincidently, since you typed:14:57
paulr<nuclear_eclipse> I'm still not sure what you think you're getting at that we don't already have with the nightly builds...14:57
paulri'm still waiting for a page to load looking at 'Loading commit data...'14:57
nuclear_eclipsewhat?14:57
paulrso i've made 10 webrequests so far to github in last 48 hours14:57
paulrand 3 have failed14:57
paulr;)14:58
paulrwhen I go to view a repo14:58
nuclear_eclipseyou're the only one I know of who can find so many "errors" with github14:58
paulrthere's a column that says 'message'14:58
paulrwhich shows in it 'Loading commit data... ' and an hour glass14:58
nuclear_eclipseI've never seen an error message from them in the two years I've been using them14:58
paulrmaybe i've just picked a bad day or something :P15:00
paulrbut so far i'm being really unlucky :P15:00
nuclear_eclipseare you *trying* to break it?15:00
paulrnot really15:00
paulrI went to github.com15:00
paulrput 'mantisbt' in search and clicked the top link for first test15:01
paulrI then went back and looked down list for more sensible link15:01
paulrand it's not loading the ajax commit messages in15:01
paulrDon't really think that's trying to break it :)15:01
paulrI could understand if I was trying to open a filename with a ' in or something :P15:03
nuclear_eclipseit loads everything for me almost instantly...15:03
paulr;/15:03
darynoh I see that on the .gitignore file15:04
paulrdaryn: yes, that's where I see it15:04
paulrand then it shows nothing in messages for rest of page15:05
paulras I think it loads them in order?15:05
* nuclear_eclipse is not seeing it at all15:05
darynbut only for my forked repo and only for that file. all the rest of mine load15:05
* paulr is glad he's not only one15:05
paulrhmm15:05
nuclear_eclipseI know they do eavy caching, so unttil the data has been pulled into cache, sometimes it can take a bit longer, but it still isn't forever15:05
paulranyway, If you change where we push to15:06
paulrjust add my ssh key15:06
paulrfrom existing box15:06
nuclear_eclipsepaulr: that's the point, using github, I don't have to be the one to deal with everyone's ssh keys15:06
nuclear_eclipseI just add somebody's github account to the team15:06
nuclear_eclipseand then the user can manage their own ssh keys15:06
paulrmaybe in 3 weeks we can try and plan something sensible out15:10
paulrwould be nice to link test results into mantis bugtracker15:10
paulrwhen a commit is added15:10
paulrI proably need to explain my point more there at some point :P15:11
paulrnuclear_eclipse: will you be around when dhx is on sunday?15:13
nuclear_eclipseno clue15:13
nuclear_eclipseyou can always ping me though, and see if I respond15:13
paulrever used app-v btw?15:14
nuclear_eclipsenever heard of it15:14
paulrMS windows tech15:14
nuclear_eclipsethat would be why15:14
nuclear_eclipseI don't run Windows15:14
*** Joins: orac1 (~jb_buldog@082-146-096-025.dyn.adsl.xs4all.be)15:33
*** Joins: orac1_ (~jb_buldog@082-146-096-038.dyn.adsl.xs4all.be)15:58
*** Quits: orac1 (~jb_buldog@082-146-096-025.dyn.adsl.xs4all.be) (Ping timeout: 260 seconds)16:00
*** orac1_ is now known as orac116:00
*** Quits: orac1 (~jb_buldog@082-146-096-038.dyn.adsl.xs4all.be) (Ping timeout: 240 seconds)16:43
*** Quits: daryn (~daryn@rrcs-76-79-4-2.west.biz.rr.com) (Quit: Ex-Chat)16:49
*** Quits: PennStater (Aaron@unaffiliated/pennstater) (Read error: Connection reset by peer)16:51
*** Joins: PennStater (Aaron@unaffiliated/pennstater)16:51
*** Joins: daryn (~daryn@rrcs-76-79-4-2.west.biz.rr.com)17:08
*** Joins: rolfkleef (~rolf@urtica.xs4all.nl)17:27
*** Joins: micahg (~micah@ubuntu/member/micahg)17:32
*** Quits: fanno (~Morten@90.184.93.233) (Quit: Leaving.)17:33
paulrnuclear_eclipse: still there?17:37
*** Quits: moto-moi (~hylke@cara.xs4all.nl) (Quit: Ex-Chat)17:45
*** Quits: siebrand (~beis@sm.xs4all.nl) ()17:50
*** Quits: daryn (~daryn@rrcs-76-79-4-2.west.biz.rr.com) (Quit: Ex-Chat)17:55
nuclear_eclipseI am now18:28
nuclear_eclipsepaulr: 18:28
paulrI dont get the github's branch stuff18:30
paulrif someone has a fork18:30
paulrwhen it shows branches18:30
*** Joins: Github (~Github@sh1-ext.rs.github.com)18:30
Githubmantisbt: master-1.2.x Siebrand Mazeland * a16cd8a (6 files in 2 dirs): Localisation updates from http://translatewiki.net - http://bit.ly/amn4e118:30
*** Parts: Github (~Github@sh1-ext.rs.github.com)18:30
paulris that forward/behind the fork or the non-fork?18:30
nuclear_eclipsehuh?18:30
paulrhttp://github.com/redhog/pad/tree/postgres18:31
paulrthat's 300 behind but 19 ahead18:31
paulris that based on where the fork is18:32
paulror where the original is?18:32
paulras it's a branch of a fork18:32
paulrbtw18:32
paulr* Github (~Github@sh1-ext.rs.github.com) has joined #mantishelp18:32
paulr<Github> mantisbt: master-1.2.x Siebrand Mazeland * a16cd8a (6 files in 2 dirs): Localisation updates from http://translatewiki.net - http://bit.ly/amn4e118:32
paulr* Github (~Github@sh1-ext.rs.github.com) has left #mantishelp18:32
paulrthat needs to sit on channel18:32
paulrto not be annoying18:32
nuclear_eclipseprobably based on where that branch is compared to the original fork's version of that branch18:32
nuclear_eclipseI can set it up to use our existing CIA project18:33
paulri'm still not sure tbh what we're trying to fix :P18:34
paulrnot like people change ssh keys every week after all18:35
nuclear_eclipsewe're not *fixing* things paul; we're taking advantage of some things that github automates for us18:35
nuclear_eclipseand other various benefits that we don't have from using our own home-rolled services18:35
nuclear_eclipsebtw paulr, if you find join/part info to be annoying, you should just have your IRC client filter those out18:41
nuclear_eclipse90% of the time this channel is just a series of join/part messages anyways...18:41
paulryea18:41
paulrthat's annoying too18:41
paulrpeople should run shells/bnc's ;)18:41
nuclear_eclipseso filter them out if they annoy you -- any client worth its salt will do that for you18:42
paulrbut join/parts are useful for seeing when daryn or whatever times out18:42
nuclear_eclipseso stop complaining! :P18:42
paulrthings that join, 'advertise' a url and part tend to hit my ircop spam filters at some point18:43
nuclear_eclipseso add an exception to ircop...18:43
paulri.e. at some point it'll probably trigger an auto ban18:43
paulrIt didn't then though18:44
* paulr has spent too long diffing java app makefile tonight18:47
*** Quits: rolfkleef (~rolf@urtica.xs4all.nl) (Ping timeout: 240 seconds)18:48
*** Quits: paulr (~paul@cpc1-enfi9-0-0-cust389.hari.cable.virginmedia.com) ()18:58
*** Quits: scribe9343423 (~scribe934@static.96.23.63.178.clients.your-server.de) (Remote host closed the connection)19:59
*** Joins: scribe9343423 (~scribe934@static.96.23.63.178.clients.your-server.de)20:00
*** Quits: dhx_m (~anonymous@c122-107-140-239.eburwd5.vic.optusnet.com.au) (*.net *.split)20:00
*** Joins: dhx_m (~anonymous@c122-107-140-239.eburwd5.vic.optusnet.com.au)20:11
*** Quits: dhx_m (~anonymous@c122-107-140-239.eburwd5.vic.optusnet.com.au) (*.net *.split)21:11
*** Joins: dhx_m (~anonymous@c122-107-140-239.eburwd5.vic.optusnet.com.au)21:22
*** Quits: micahg (~micah@ubuntu/member/micahg) (Ping timeout: 260 seconds)21:29
*** Joins: |HaruAFK| (~haruka@p54ACE980.dip.t-dialin.net)22:33
*** Quits: |Otter| (~haruka@p54ACE728.dip.t-dialin.net) (Ping timeout: 240 seconds)22:37
*** Joins: micahg (~micah@ubuntu/member/micahg)23:55

Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!