| ../irclogs/#mantishelp.2010-07-01.log | ||
| --- scribe started --- | 00:00 | |
| hellonull | hey all. working on configuring my first mantis installation and need a bit of help. i'm looking to disable the "reproducibility," "severity," and "steps to reproduce" fields since they aren't applicable to the purpose for which we are using mantis. is there a way to take care of each of these with a single config option? for severity, i came across $g_severity_enum_string... i tried values of "", '', and NULL, but the field's dropd | 01:31 |
|---|---|---|
| daryn | hellonull: are you using 1.2? | 01:34 |
| hellonull | daryn: yes, 1.2.1 | 02:56 |
| daryn | there are several variables to select which fields to display on which pages but I don't think there is a way to completely disable a field in all locations with one change | 03:04 |
| daryn | the easiest is probably to set these g_bug_report_page_fields, g_bug_view_page_fields, g_bug_print_page_fields, g_bug_update_page_fields,g_bug_change_status_page_fields | 03:06 |
| daryn | the complete list of fields for each page is in config_defaults_inc.php | 03:07 |
| daryn | copy the variables into config_inc.php and remove any fields you don't want | 03:07 |
| daryn | config_inc.php overrides values in config_defaults_inc.php | 03:07 |
| hellonull | sounds good, thanks daryn | 03:18 |
| daryn | yw | 03:18 |
| davidinc | Hi | 08:05 |
| dhx_m | hi | 12:12 |
| nuclear_eclipse | howdy dhx_m | 12:22 |
| dhx_m | nuclear_eclipse: howdy | 12:22 |
| nuclear_eclipse | seems like paulr is our only dev who doesn't like github... | 12:24 |
| dhx_m | "paulr> using github probably helps as git.mantisbt.org can be less stable" | 12:24 |
| nuclear_eclipse | yeah, that made me laugh | 12:24 |
| dhx_m | it seems he's for :) | 12:24 |
| dhx_m | but 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 change | 12:25 |
| nuclear_eclipse | yeah, be he's also for moving *everything* to his mantisforge system, too... | 12:25 |
| nuclear_eclipse | that's possible, but that's what announcements are for :P | 12:26 |
| dhx_m | I'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 infrastructure | 12:26 |
| nuclear_eclipse | heh | 12:26 |
| dhx_m | but we don't have the manpower to setup 2-3 servers in a cluster and maintain them through faults, upgrades, etc | 12:27 |
| dhx_m | my main concern is that sourceforge changes something and we don't like the change | 12:27 |
| dhx_m | oops github | 12:27 |
| dhx_m | we lose control but gain reliability | 12:28 |
| nuclear_eclipse | well, 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 :P | 12:28 |
| nuclear_eclipse | or *shudder* set up gitorious... | 12:29 |
| dhx_m | no thanks :D | 12:30 |
| nuclear_eclipse | hehe | 12:31 |
| dhx_m | note to self: don't watch jquery project on Github... SNR is low | 12:31 |
| nuclear_eclipse | haha | 12:32 |
| nuclear_eclipse | I laughed when I saw that in my feed | 12:32 |
| nuclear_eclipse | there 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 :P | 12:33 |
| dhx_m | and don't follow daryn because I'll get 1001 forked repository messages :p | 12:33 |
| dhx_m | haha | 12:33 |
| nuclear_eclipse | I 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/plugins | 12:36 |
| dhx_m | I guess Github doesn't support that yet so I think it'd be better to stick with mantisforge for now | 12:37 |
| dhx_m | with an aim towards having a system where good quality plugins can become "first class citizens" of the MantisBT org? | 12:38 |
| dhx_m | ie. github repository under the MantisBT name, project on our bug tracker, etc | 12:38 |
| dhx_m | we'd need to write up some documentation on that idea though (what expectations are of plugin authors, etc) | 12:39 |
| dhx_m | the 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 org | 12:40 |
| dhx_m | much like how Wikipedia tries to avoid having people "own" articles | 12:40 |
| dhx_m | so 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) | 12:41 |
| * nuclear_eclipse nominates dhx_m to write up that process for official review :P | 13:11 | |
| dhx_m | I'm up for that :) | 13:11 |
| nuclear_eclipse | we need a new wiki | 13:11 |
| dhx_m | I'll place it at position 150 on the agenda :p | 13:11 |
| nuclear_eclipse | one that doesn't suck ass | 13:11 |
| nuclear_eclipse | lol | 13:11 |
| dhx_m | idd | 13:11 |
| dhx_m | I really like this website: http://www.mono-project.com/Main_Page | 13:12 |
| nuclear_eclipse | hmm, we could use the Github wiki :P | 13:12 |
| dhx_m | it's MediaWiki... but it doesn't look like it :) | 13:12 |
| nuclear_eclipse | hmm, that oes look like a pretty nice template | 13:12 |
| dhx_m | steal it please :p | 13:13 |
| nuclear_eclipse | lol | 13:13 |
| dhx_m | I couldn't find it anywhere last time I looked | 13:13 |
| dhx_m | perhaps I should ask :) | 13:13 |
| nuclear_eclipse | it's probably a one-off template done just for mono | 13:13 |
| dhx_m | it'd be nice to use as a reference if we were to do a similar thing | 13:14 |
| dhx_m | Mediawiki templates are publicly accessible via Special: pages | 13:14 |
| dhx_m | but that doesn't cover the changes needed to Mediawiki's PHP files (used for templating each style) | 13:14 |
| CIA-22 | Mantisbt: s.mazeland master-1.2.x * ra16cd8abcbae / (6 files in 2 dirs): Localisation updates from http://translatewiki.net | 17:20 |
| paulr | moo | 17:44 |
| * paulr pokes dhx_m | 17:44 | |
| paulr | nuclear_eclipse: I've had an idea regarding github | 17:58 |
| nuclear_eclipse | uh oh | 18:00 |
| nuclear_eclipse | (hi paulr) | 18:00 |
| * daryn thinks this could be good... | 18:01 | |
| paulr | diner brb | 18:03 |
| nuclear_eclipse | /sigh | 18:03 |
| * daryn ...again? | 18:03 | |
| paulr | bk | 18:23 |
| paulr | thinking of setting up github to mirror whats on mantisforge | 18:23 |
| paulr | that way | 18:23 |
| paulr | we get benefits both ways | 18:23 |
| nuclear_eclipse | paulr: the point is so that github is the primary access point | 18:24 |
| paulr | (we still need to work out how people release plugins | 18:24 |
| paulr | well | 18:24 |
| paulr | can't really do that for plugins | 18:24 |
| nuclear_eclipse | if we just have github as a mirror, we might as well not use it at all | 18:24 |
| nuclear_eclipse | we're not planning to use it for anything except the core mantis repos... | 18:24 |
| paulr | yea | 18:24 |
| paulr | hence why I can mirror mantisforge plugins to github | 18:25 |
| paulr | as a nice 'backup' | 18:25 |
| nuclear_eclipse | I'm not sure why that would be useful -- they are really discoverable at all on github | 18:25 |
| nuclear_eclipse | arent* | 18:25 |
| paulr | yea, i've not played to see how github works | 18:25 |
| paulr | but I was more thinking of it could be useful to have a backup somewhere | 18:26 |
| daryn | we'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 organization | 18:26 |
| daryn | then they can be discoverable and manageable through github | 18:26 |
| nuclear_eclipse | trying to automate mirroring/syncing between two separate public endpoints just sounds like it will cause norhing but pain and frustration | 18:28 |
| nuclear_eclipse | theres multiple different ways where it can go wrong without any warning | 18:29 |
| paulr | well, I've actually found I tend to prefer gitweb's interface for browsing source then github's (for annotating/diffing etc) | 18:32 |
| paulr | but where one pushes to is irrelevant | 18:32 |
| paulr | all 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 gitweb | 18:32 |
| paulr | that would be fine with me | 18:32 |
| paulr | but right now, need to fix some stuff | 18:33 |
| paulr | and try and catch dhx I guess on sunday now | 18:33 |
| nuclear_eclipse | well, I was going to update the mantisbt.org tracker so that everything points to the github repos | 18:34 |
| nuclear_eclipse | itd be silly to be inconsistent IMO | 18:34 |
| paulr | :(( | 18:34 |
| nuclear_eclipse | why use github if you're not going to have everything point to the same place? | 18:34 |
| paulr | well, lets not bother then :) | 18:35 |
| paulr | I dont really see point of changing | 18:35 |
| nuclear_eclipse | we'd bother because of the benefits I listed in theemail | 18:35 |
| paulr | given that mantisbt.org doesn't play up | 18:35 |
| paulr | git's distributed | 18:35 |
| nuclear_eclipse | so then why do you care if we change wher the canonical repo is hosted at? | 18:36 |
| paulr | I prefer the speed of http://git.mantisbt.org/?p=mantisbt.git;a=commitdiff;h=a16cd8abcbaeca39fcc6ec57a6fd8d159f8f0179 | 18:36 |
| paulr | it's cleaner, and loads faster | 18:37 |
| paulr | despite the server being in the US | 18:37 |
| nuclear_eclipse | the point is to offload the repo management and collaboration to a site that simplifies all of that | 18:37 |
| paulr | well, I'd still carry on trying to improve repo management for plugins on mantisforge | 18:37 |
| paulr | and mirroring core repo | 18:37 |
| paulr | so all that github would be is a push location | 18:38 |
| paulr | that we can't then control as easily | 18:38 |
| nuclear_eclipse | but we can | 18:38 |
| paulr | for example | 18:38 |
| nuclear_eclipse | it's easier to control a github repo than to control a gitweb repo | 18:38 |
| paulr | i'd like to build a release tarball of each commit in trunk so that if users grab a tarball | 18:38 |
| paulr | they always get docs etc | 18:38 |
| nuclear_eclipse | that's what we already do with the nightlies paul | 18:39 |
| paulr | yea | 18:39 |
| nuclear_eclipse | you're a bit late to that party | 18:39 |
| paulr | but we don't keep them for ever | 18:39 |
| paulr | nor link them to specific commits | 18:39 |
| nuclear_eclipse | why would we need to keep them forever? | 18:39 |
| paulr | well, a while at least | 18:39 |
| nuclear_eclipse | who wants to download a tarball of an old commit, unless it's a release? | 18:39 |
| paulr | also | 18:41 |
| paulr | more to point is github reliable | 18:42 |
| paulr | I just put into github search 'mantis' | 18:42 |
| paulr | clicked first link which goes to : http://github.com/jreese/mantisbt/tree/9f8516e83a9871077ea98ce2df2db8659b896667/core/classes/MantisCorePlugin.class.php | 18:42 |
| paulr | and got: | 18:42 |
| paulr | "That page doesn't exist!" | 18:42 |
| nuclear_eclipse | that's because I deleted that repo | 18:43 |
| nuclear_eclipse | I'd imagine their search results get cached for a while, so they haven't flushed old data yet | 18:43 |
| paulr | when did you delete it? | 18:44 |
| nuclear_eclipse | when I search for mantis, I get victor's mantis-plugins as the top result | 18:44 |
| nuclear_eclipse | yesterday | 18:44 |
| paulr | so 24 hours? | 18:44 |
| nuclear_eclipse | actually, when I search for mantis, I get mantisbt/mantisbt (the new repo) in the result set at #4 | 18:45 |
| nuclear_eclipse | yes, < 24hours | 18:45 |
| paulr | tbh, i'd rather we just pointed bugtracker to the git.mantisforge.org and used git.mantisbt.org as central point or whatever | 18:46 |
| paulr | then we can build git/testing/plugins into one place | 18:46 |
| nuclear_eclipse | that doesn't even make any sense | 18:47 |
| paulr | rather then having one place for viewing git and one place for test results | 18:47 |
| paulr | i've got 3 weeks off in a month when I plan to start pushing mantisforge and fixing automation issues | 18:49 |
| paulr | or well when I say that | 18:50 |
| paulr | setting up mantisforge to run your release tarball scripts etc | 18:50 |
| nuclear_eclipse | I'm still not sure what you think you're getting at that we don't already have with the nightly builds... | 18:50 |
| nuclear_eclipse | the nightly builds already compile docbook and everythign | 18:51 |
| paulr | yes, but if we are doing testing/continous integration | 18:51 |
| paulr | should build tarballs as part of that also | 18:51 |
| nuclear_eclipse | whatever, I'm still not sure what any of that has to do with why you don't like the idea of using github... | 18:52 |
| paulr | we could take some load off of mantisbt.org box as that's apparently struggling :P | 18:52 |
| nuclear_eclipse | it's not struggling at all | 18:52 |
| paulr | as I say, I prefer working with the simplicity of gitweb's user interface | 18:53 |
| nuclear_eclipse | so 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 mirror | 18:54 |
| paulr | hence why when I normally resolve bugs I normally include a link to git.mantisbt.org in the resolution | 18:54 |
| paulr | for the patch | 18:54 |
| paulr | as I said, don't mind core going to git hub | 18:54 |
| paulr | but it would be good if bug tracker carried on pointing at a gitweb interface | 18:55 |
| paulr | so I can just click on links to patches | 18:55 |
| nuclear_eclipse | that wouldn't make ansy sense at all paul | 18:55 |
| paulr | why? | 18:55 |
| nuclear_eclipse | if we have github as our primary repository, we're going to have the tracker point at github urls | 18:55 |
| paulr | you wanted github to ease admin | 18:55 |
| nuclear_eclipse | because it makes no sense to have the tracker point at some repo host that's not where our primary repo is hosted at | 18:55 |
| paulr | then in which case, i'd rather not use github | 18:56 |
| nuclear_eclipse | nevermind paul | 18:56 |
| paulr | as I tend to waste more time trying to find stuff on it | 18:56 |
| paulr | I'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 github | 18:57 |
| nuclear_eclipse | you're totally insane | 18:57 |
| paulr | incidently, since you typed: | 18: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... | 18:57 |
| paulr | i'm still waiting for a page to load looking at 'Loading commit data...' | 18:57 |
| paulr | so i've made 10 webrequests so far to github in last 48 hours | 18:58 |
| nuclear_eclipse | what? | 18:58 |
| paulr | and 3 have failed | 18:58 |
| paulr | ;) | 18:58 |
| paulr | when I go to view a repo | 18:58 |
| nuclear_eclipse | you're the only one I know of who can find so many "errors" with github | 18:58 |
| paulr | there's a column that says 'message' | 18:58 |
| paulr | which shows in it 'Loading commit data... ' and an hour glass | 18:58 |
| nuclear_eclipse | I've never seen an error message from them in the two years I've been using them | 18:58 |
| paulr | maybe i've just picked a bad day or something :P | 19:00 |
| paulr | but so far i'm being really unlucky :P | 19:00 |
| nuclear_eclipse | are you *trying* to break it? | 19:00 |
| paulr | not really | 19:01 |
| paulr | I went to github.com | 19:01 |
| paulr | put 'mantisbt' in search and clicked the top link for first test | 19:01 |
| paulr | I then went back and looked down list for more sensible link | 19:01 |
| paulr | and it's not loading the ajax commit messages in | 19:01 |
| paulr | Don't really think that's trying to break it :) | 19:02 |
| paulr | I could understand if I was trying to open a filename with a ' in or something :P | 19:03 |
| nuclear_eclipse | it loads everything for me almost instantly... | 19:03 |
| paulr | ;/ | 19:03 |
| daryn | oh I see that on the .gitignore file | 19:04 |
| paulr | daryn: yes, that's where I see it | 19:04 |
| paulr | and then it shows nothing in messages for rest of page | 19:05 |
| paulr | as I think it loads them in order? | 19:05 |
| * nuclear_eclipse is not seeing it at all | 19:05 | |
| daryn | but only for my forked repo and only for that file. all the rest of mine load | 19:05 |
| * paulr is glad he's not only one | 19:05 | |
| paulr | hmm | 19:05 |
| nuclear_eclipse | I 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 forever | 19:06 |
| paulr | anyway, If you change where we push to | 19:06 |
| paulr | just add my ssh key | 19:06 |
| paulr | from existing box | 19:06 |
| nuclear_eclipse | paulr: that's the point, using github, I don't have to be the one to deal with everyone's ssh keys | 19:06 |
| nuclear_eclipse | I just add somebody's github account to the team | 19:06 |
| nuclear_eclipse | and then the user can manage their own ssh keys | 19:07 |
| paulr | maybe in 3 weeks we can try and plan something sensible out | 19:10 |
| paulr | would be nice to link test results into mantis bugtracker | 19:11 |
| paulr | when a commit is added | 19:11 |
| paulr | I proably need to explain my point more there at some point :P | 19:11 |
| paulr | nuclear_eclipse: will you be around when dhx is on sunday? | 19:13 |
| nuclear_eclipse | no clue | 19:13 |
| nuclear_eclipse | you can always ping me though, and see if I respond | 19:14 |
| paulr | ever used app-v btw? | 19:14 |
| nuclear_eclipse | never heard of it | 19:14 |
| paulr | MS windows tech | 19:14 |
| nuclear_eclipse | that would be why | 19:15 |
| nuclear_eclipse | I don't run Windows | 19:15 |
| paulr | nuclear_eclipse: still there? | 21:37 |
| nuclear_eclipse | I am now | 22:28 |
| nuclear_eclipse | paulr: | 22:28 |
| paulr | I dont get the github's branch stuff | 22:30 |
| paulr | if someone has a fork | 22:30 |
| paulr | when it shows branches | 22:30 |
| Github | mantisbt: master-1.2.x Siebrand Mazeland * a16cd8a (6 files in 2 dirs): Localisation updates from http://translatewiki.net - http://bit.ly/amn4e1 | 22:30 |
| paulr | is that forward/behind the fork or the non-fork? | 22:30 |
| nuclear_eclipse | huh? | 22:30 |
| paulr | http://github.com/redhog/pad/tree/postgres | 22:31 |
| paulr | that's 300 behind but 19 ahead | 22:32 |
| paulr | is that based on where the fork is | 22:32 |
| paulr | or where the original is? | 22:32 |
| paulr | as it's a branch of a fork | 22:32 |
| paulr | btw | 22:32 |
| paulr | * Github (~Github@sh1-ext.rs.github.com) has joined #mantishelp | 22: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/amn4e1 | 22:32 |
| paulr | * Github (~Github@sh1-ext.rs.github.com) has left #mantishelp | 22:32 |
| paulr | that needs to sit on channel | 22:32 |
| paulr | to not be annoying | 22:32 |
| nuclear_eclipse | probably based on where that branch is compared to the original fork's version of that branch | 22:32 |
| nuclear_eclipse | I can set it up to use our existing CIA project | 22:33 |
| paulr | i'm still not sure tbh what we're trying to fix :P | 22:34 |
| paulr | not like people change ssh keys every week after all | 22:35 |
| nuclear_eclipse | we're not *fixing* things paul; we're taking advantage of some things that github automates for us | 22:35 |
| nuclear_eclipse | and other various benefits that we don't have from using our own home-rolled services | 22:36 |
| nuclear_eclipse | btw paulr, if you find join/part info to be annoying, you should just have your IRC client filter those out | 22:41 |
| nuclear_eclipse | 90% of the time this channel is just a series of join/part messages anyways... | 22:41 |
| paulr | yea | 22:41 |
| paulr | that's annoying too | 22:41 |
| paulr | people should run shells/bnc's ;) | 22:42 |
| nuclear_eclipse | so filter them out if they annoy you -- any client worth its salt will do that for you | 22:42 |
| paulr | but join/parts are useful for seeing when daryn or whatever times out | 22:42 |
| nuclear_eclipse | so stop complaining! :P | 22:43 |
| paulr | things that join, 'advertise' a url and part tend to hit my ircop spam filters at some point | 22:43 |
| nuclear_eclipse | so add an exception to ircop... | 22:43 |
| paulr | i.e. at some point it'll probably trigger an auto ban | 22:44 |
| paulr | It didn't then though | 22:44 |
| * paulr has spent too long diffing java app makefile tonight | 22:47 | |
Generated by irclog2html.py