Tuesday, 2010-10-05

*** Parts: AlexM600 (~Miranda@192.109.140.36)00:17
*** Quits: mariusvw (~mariusvw@dhcp-077-248-080-122.chello.nl) (Read error: Connection reset by peer)00:52
*** Joins: mariusvw (~mariusvw@dhcp-077-248-080-122.chello.nl)00:52
*** Joins: HerVonW (~mariusvw@dhcp-077-248-080-122.chello.nl)00:57
*** Quits: mariusvw (~mariusvw@dhcp-077-248-080-122.chello.nl) (Ping timeout: 265 seconds)00:58
*** HerVonW is now known as mariusvw00:58
*** Joins: HerVonW (~mariusvw@dhcp-077-248-080-122.chello.nl)01:02
*** Quits: mariusvw (~mariusvw@dhcp-077-248-080-122.chello.nl) (Ping timeout: 240 seconds)01:04
*** HerVonW is now known as mariusvw01:04
*** Joins: kirillka (~Miranda@195.242.142.17)01:08
*** Quits: siebrand (~beis@sm.xs4all.nl) ()01:19
*** Joins: Cupertino (~Cupez@unaffiliated/cupertino)02:32
*** Joins: giallu (~giallu@fedora/giallu)02:35
*** Joins: Al_Chapone (~chatzilla@ATuileries-152-1-38-202.w82-123.abo.wanadoo.fr)03:27
*** Quits: mariusvw (~mariusvw@dhcp-077-248-080-122.chello.nl) (Quit: pff :-))03:34
*** Quits: kirillka (~Miranda@195.242.142.17) (Read error: Connection reset by peer)03:35
*** Joins: kirillka (~Miranda@195.242.142.17)03:37
*** Quits: kirillka (~Miranda@195.242.142.17) (Read error: Connection reset by peer)04:08
*** Joins: kirillka (~Miranda@195.242.142.17)04:11
*** Quits: Al_Chapone (~chatzilla@ATuileries-152-1-38-202.w82-123.abo.wanadoo.fr) (Ping timeout: 240 seconds)04:36
*** Joins: Al_Chapone (~chatzilla@ATuileries-152-1-25-64.w82-123.abo.wanadoo.fr)04:39
*** Joins: tavasti (~tavasti@217.152.202.220)05:04
*** Quits: dhx1 (~anonymous@c122-107-170-247.eburwd5.vic.optusnet.com.au) (Read error: Connection reset by peer)05:28
*** Joins: dhx1 (~anonymous@c122-107-170-247.eburwd5.vic.optusnet.com.au)05:34
*** Joins: Rixie (~Rixie@0x4dd7390e.adsl.cybercity.dk)06:29
*** Quits: Al_Chapone (~chatzilla@ATuileries-152-1-25-64.w82-123.abo.wanadoo.fr) (Quit: ChatZilla 0.9.86 [Firefox 3.6.10/20100914125854])06:35
dhx1Am I the only person receiving multiple duplicate emails from Robert?08:08
nuclear_eclipseno08:14
dhx1good :)08:27
*** Joins: paulr (~a@212.85.5.19)08:36
paulri'm wondering whether to resist or join in08:36
dhx1:)08:37
paulryou recall a month ago discussing what would be involved to change licnese? ;p08:38
paulrmaybe now's a good time to discuss!08:38
dhx1CC0!08:42
dhx1:)08:42
paulrcc0?08:43
dhx1basically some legal text from creative commons to place work in the public domain08:43
dhx1but in some countries that isn't possible, so the legal text tries to work around that :)08:44
paulrcan you remember date?08:44
dhx1?08:44
paulrfor our licensing chat08:44
dhx12-3 months ago08:45
*** Joins: mantisbt_64743 (ca58ed87@gateway/web/freenode/ip.202.88.237.135)08:47
paulrbtw dhx it's not that simple08:57
paulrsoap api in some places has copy/paste code blocks from core08:57
paulrwhich could be written by someone else08:58
paulr:)08:58
dhx1the licensing thing is stupid anyhow08:58
paulrI personally want to relicense mantis08:58
paulreverytime we have this debate08:58
dhx1at least in Australia, courts look at the amount of infringement (accidental copy+paste of 10 lines of code vs ripping off 20k LoC), the cost of the 'victim', the amount gained by the infringer, etc08:59
paulrI think the best way forward is:09:00
dhx1at the purest form you'd have to worry about what constitutes a derivative work (is it even possible to rewrite code to change the license?)09:00
paulra) attempt to contact everyone and tranfer copyright to09:00
paulrsomething/one09:00
paulrb) make a list of what we dont have copyright on09:00
dhx1someone might have contributed GPLv2 code which is then rewritten out into code with a new license09:00
paulrc) dual license the code09:00
paulrthat's fine though?09:00
dhx1not sure09:01
dhx1the rewritten code would be replicating the existing code and hence could be a derivative work?09:01
dhx1or other parts of the codebase may have become "infected" with the older code by their reliance (or copy/paste) of parts of the older code09:02
paulrok right09:04
paulrthere's probablyabout 20 people max we'd need to contact to do 90%+09:04
paulresp. if you split manual + code + language files09:04
*** Joins: rolfkleef (~rolf@82-69-198-84.dsl.in-addr.zen.co.uk)09:08
dhx1yep09:11
*** Joins: daryn (~daryn@h158.249.190.173.static.ip.windstream.net)09:14
paulrfrom what I can tell, we'd be better off having core code under a different license09:19
paulreven if it's only to stop debates for which we dont know outcome09:20
nuclear_eclipseBSD/MIT license and be done with it all09:21
dhx1why BSD/MIT instead of public domain though?09:22
killefizpublic domain doesn't really exist outside of the united states.09:22
nuclear_eclipsebecause BSD/MIT at the very least prevents someone from ripping off your project wholesale and saying they did it themself; public domain does not protect you from that09:22
nuclear_eclipsekillefiz: on the contrary, public domain doesn't exist *inside* the US09:22
dhx1I'm not so sure I care about someone claiming it as their own09:23
dhx1it's pretty obvious where it came from (mantisbt.org)09:23
nuclear_eclipsebecause US copyright law grants copyright privileges de facto to any work created in the US09:23
dhx1killefiz: CC0 caters for that by providing legal text to effectively remove copyright protections09:24
nuclear_eclipsedhx1: the point is that with BSD/MIT license, they at least have to acknowledeg that you were the original author09:24
gialludhx1, solution is simple, we're going to rewrite everything in the long term. start by adding the BSD license to all new files and wait ;)09:24
nuclear_eclipsegiallu: not possible if those new files rely on GPL code...09:25
dhx1nuclear_eclipse: only if they play by the rules, and if they don't... who is going to chase them up over attribution?09:25
giallunuclear_eclipse, since when?09:26
gialluBSD code can surely use GPL stuff09:26
dhx1giallu: the patches would be considered derivative works of the original and hence maintain the original copyright09:26
gialluthe resulting license is GPL of course09:26
nuclear_eclipsegiallu: that's the whole point of GPL, you can't link against GPL code without using a GPL license09:26
giallubut new code is BSD09:26
gialluwhen everything is new, BAM! welcome in BSD09:27
nuclear_eclipseno, that would be breaching the copyright of anyone who contributed to the GPL code09:27
gialluno09:27
gialluI'm not talking about relicensing09:27
gialluI'm talking about new code09:27
nuclear_eclipseI know that09:27
gialluanyway09:28
gialluif someone wants to chase all contributors for relicensing, be my guest ;)09:28
gialluI'm okay with BSD09:28
dhx1it won't really work IMO09:28
dhx1too many people, too many years of development09:28
dhx1I'm happy with BSD too, but would prefer no license at all (public domain) to prevent license compatibility issues from ever arising again09:30
paulrgiallu: i've already made a list09:30
paulra month ago ;p09:30
nuclear_eclipsedhx1: using something like BSD *would* prevent license compatibility issues from ever arinsing again, it basically permits everything as long as you maintain the copyright attributions09:31
giallubut please note. we're talking about our API. If I write a completely new Issue class, make it BSD09:33
gialluthen everything else _uses_ that new code09:33
gialluthat's GPL code using BSD code09:33
nuclear_eclipsegiallu: yes, that's correct09:34
nuclear_eclipsebut if that class uses a GPL API at all, that's breaking the GPL copyright....09:34
nuclear_eclipseeither way, I think it would be easier to email everyone requesting permission to change the license that to try and incrementally rewrite the codebase to use BSD license09:35
paulrnuclear_eclipse: can I? :)09:36
paulrplssssssss09:36
dhx1http://www.freebsdnews.net/2009/01/21/software-licensing-gpl-bsd-public-domain/09:36
dhx1post it to the developer mailing list before emailing anyone privately09:37
nuclear_eclipsepaulr: what dhx1  said09:37
dhx1it'd work better to invite people to contribute to the mailing list discussion rather than ask them directly09:37
*** Quits: giallu (~giallu@fedora/giallu) (Ping timeout: 240 seconds)09:37
dhx1nuclear_eclipse: BSD is still "viral" in the sense that people forking the software need to maintain the original restrictions09:38
*** Joins: giallu (~giallu@fedora/giallu)09:38
nuclear_eclipsedhx1: but the only restriction is to maintain the copyright attributions09:39
* giallu got disconnected, sorry09:40
nuclear_eclipseBSD has long been seen as the "most free" license because it allows you to o anything you want with the code as long as you maintain that copyright statement09:40
dhx1nuclear_eclipse: yep, one could add extra restrictions to their modified code09:40
nuclear_eclipsewhich is exactly why businesses like BSD code more than GPL code, because you can link against BSD code without needing to license your own code as BSD, and you can redistribute BSD code without having to make the sources available, and you can use it and change however you like as long as you keep the original copyright statements in tact, but you don't even need to let people know that you're using that BSD code because you don't have to give source code with your porject09:42
dhx1nuclear_eclipse: the problem would be people copying 4 lines of code from a BSD project into a project with a different license as those 4 lines of code would need to bear the BSD license text09:44
dhx1AFAIK09:44
nuclear_eclipsedhx1: so what? when are four lines of code ever useful without the context of the parent file/codebase?09:44
nuclear_eclipseif you want a function, you copy the function wholesael along with the license header, big deal?09:44
dhx1it would be a lot of maintenance for another project to keep track of which functions have which license09:46
dhx1every time code is copy+pasted, the license text would need to go with it09:46
nuclear_eclipsedhx1: I really think you're splitting hairs09:47
dhx1and if someone modifies the copy+pasted code later such that it no longer resembles the original code, does the BSD license still apply?09:47
nuclear_eclipseit's really not a lot of maintenance, we do it on mantis just fine...09:47
nuclear_eclipsedhx1: of course it does; it only goes away if you rewrite the code from scratch09:48
nuclear_eclipseotherwise all of those modifications are based on the original copyright code, and wouldn't be possible without that original code09:48
dhx1my point really is that uncertainty still exists with the BSD license09:48
nuclear_eclipsedhx1: I think you're making uncertainty out of nothing09:49
dhx1there is no black and white answer to whether something is infringing09:49
*** Quits: kirillka (~Miranda@195.242.142.17) (Quit: kirillka)09:50
nuclear_eclipsedhx1: I could probably come up with just as many uncertainties about CC0 if I wanted to, especially given the US's penchant for not liking the public domain09:51
*** Quits: daryn (~daryn@h158.249.190.173.static.ip.windstream.net) (Quit: Ex-Chat)09:54
*** Joins: daryn (~daryn@h158.249.190.173.static.ip.windstream.net)09:56
dhx1nuclear_eclipse: I guess CC0 specifically grants all moral rights of the original author (ie. it allows anyone to assign copyright of the work to themselves)09:57
paulri've got an idea09:57
dhx1plus it has a fallback mechanism in case any of the clauses are struck down in a court as being invalid09:57
dhx1(in the event of it not being possible to waive certain rights)09:58
paulrin terms of my nusoap contributions09:58
paulrI'm only happy for them to be relicensed under any license agreement that follows the principles of the following license agreement "Usage of the works is permitted provided that this instrument is retained with the works, so that any entity that uses the works is notified of this instrument."10:03
paulr:)10:03
dhx1not quite legalese enough for my liking :p10:03
nuclear_eclipsepaulr: so MIT license?10:03
nuclear_eclipsedhx1: maybe even MIT would be more satisfactory to you than BSD?10:04
dhx1nuclear_eclipse: I still don't like clauses like "The above copyright notice and this permission notice shall be included in10:05
dhx1all copies or substantial portions of the Software."10:05
dhx1"substantial" is vague and undefined10:05
nuclear_eclipsesigh10:05
* daryn thinks 'who cares'10:05
dhx1there is no specification of how and when the copyright notice shall be included10:05
nuclear_eclipseso if you hate everything that isn't public domain, why do you contribute to mantis? :P10:05
dhx1daryn: exactly why I like public domain :p10:06
darynbut that's you caring10:06
dhx1it's more just a case of pushing it towards a "who cares" attitude ;)10:06
nuclear_eclipseI care about getting credit for what I've worked on, and not allowing people to take credit for what I've done10:07
dhx1and making it easier for people to reuse code without having to understand and adhere to viral licenses10:07
nuclear_eclipsedhx1: BSD isn't viral though10:07
nuclear_eclipseneither is MIT10:07
nuclear_eclipsehaving to maintain copyright of code you use isn't viral10:08
*** Joins: leetcode_70058 (d53c7df8@gateway/web/freenode/ip.213.60.125.248)10:08
dhx1nuclear_eclipse: derivative works have to bear the BSD license header though?10:08
leetcode_70058Hi10:08
*** leetcode_70058 is now known as Spk_10:08
nuclear_eclipsedhx1: anything that uses that code doesn't have to be BSD licensed though10:08
Spk_anyone can help me with mantis + remote svn?10:08
dhx1nuclear_eclipse: right, so it solves the problem of linking... but not of copy+pasting code from MantisBT into another PHP project (for example)10:09
nuclear_eclipseGPL is viral because anything that links against GPL code must itself be GPL licensed10:09
nuclear_eclipsedhx1: who the hell would copy paste only a small part of our code without expecting to give us credit?10:09
dhx1I understand why you need BSD if you want to maintain the attribution clause10:09
nuclear_eclipseSpk_: "Just Ask!"10:10
Spk_jejeje10:10
dhx1I personally don't see the need for attribution given that you can just point people to git.mantisbt.org where they can see your contributions10:11
dhx1then you can point to other projects copying your code10:11
Spk_i didn't know how start... checkin.php is not on the same server that svn :S10:11
nuclear_eclipseSpk_: you don't need to call checkin.php directly10:11
Spk_i follow google, and search a "plugin" or anything, but without lucky10:11
Spk_xD10:11
Spk_(sorry about my bad english)10:12
dhx1is the attribution argument one of ensuring that other people don't attempt to "cheat"?10:12
Spk_mmm i dont understand10:13
nuclear_eclipseSpk_: sec10:13
Spk_this is my mantis version:10:13
Spk_Versión de MantisBT1.2.3 Versión de esquema18310:13
nuclear_eclipseSpk_: http://leetcode.net/blog/2009/01/integrating-git-svn-with-mantisbt/10:13
nuclear_eclipsehttp://leetcode.net/blog/2009/10/detailed-integration-of-subversion-in-mantisbt/10:13
Spk_thanks nuclear_eclipse10:14
Spk_other thing is that our svn are in a different port10:14
Spk_this is important?10:14
nuclear_eclipseshouldn't be10:15
Spk_ok, i try10:15
Spk_million of thanks!10:15
nuclear_eclipsedhx1: the point of using a license that maintains the copyright attribution, and BSD in particular, is to have legal recourse if someone redistributes your code with their name on it instead of yours10:16
nuclear_eclipseakin to saying that somebody can't just take an obscure artist's painting, and put their own signature on it and sell it as if they created it10:17
dhx1I would have thought that concern is far outweighed by the popularity of the official source being superior to that of redistributors10:18
nuclear_eclipsethey still have the right to sell and modify the painting, they just aren't allowed to say they created the work without also mentioning the original artist10:18
nuclear_eclipsedhx1: but that's not always the case10:18
dhx1ie. people wouldn't see the distributor as being the author when a far more popular/known/authoritative source also claims ownership (with evidence strongly supporting these claims)10:19
*** Parts: mantisbt_64743 (ca58ed87@gateway/web/freenode/ip.202.88.237.135)10:20
nuclear_eclipseif someone takes mantis, renames it, improves on it in some fashion, but then removes all of our copyright attributions, and releases it as their own product, you've just been ripped off, but BSD would give you legal recourse10:20
nuclear_eclipseversus public domain or CC0, where you can't do anything about it10:20
nuclear_eclipseother than whine10:20
* giallu notes CC licenses are not for code, but content10:21
dhx1I guess the difference in opinion here is that I wouldn't really care if someone ripped it off (but I can see why you and many others do)10:21
nuclear_eclipsegiallu:  I believe CC0 is an exception to that10:21
giallubesides, dhx1, where that "substantial" claim comes from? cna't see that in http://www.opensource.org/licenses/bsd-license.html10:22
nuclear_eclipsegiallu: MIT uses the "substantial" clause10:22
dhx1giallu: was referring to MIT @ http://en.wikipedia.org/wiki/MIT_License10:22
gialluah sorry ;)10:22
giallumissed the switch in my 9 minutes blackout10:23
giallu:)10:23
nuclear_eclipsebluh, I just realizzed that I've been using a font on my site that renders like ass on winxp10:23
dhx1I contribute to MantisBT to encourage others to do likewise10:23
dhx1and to expand, improve and test features developed for my own needs10:23
nuclear_eclipseand winxp accounts for >25% of my visitors...10:23
dhx1perhaps others will see likewise and share their contributions in return (thus receiving further improvements and testing from others)10:24
dhx1perhaps they'll take it, rename it and sell it under their own name10:24
nuclear_eclipsedhx1: similar motives for myself, but I want to be able to protect my name and credit of contribution when I release open source works10:24
dhx1I understand where you're coming from10:25
dhx1although I think the self-marketing potential of open source (putting it down on a CV) is unaffected by people ripping you off10:25
dhx1thus it becomes more of a philosophical argument about fairness/respect for others10:26
nuclear_eclipsedhx1: perhaps so10:26
paulrHI've got an idea for a license agreement10:28
nuclear_eclipseoh no10:29
paulrit's short10:29
paulryou'll like it10:29
nuclear_eclipsethat's better :P10:30
dhx1:)10:30
paulr"You can do whatever you like with mantisbt.org code. If you want to remove this line, you need to pay 1000$ to mantisbt.org"10:30
nuclear_eclipsefreenode needs to alias their `quiet` command as `muzzle` :P10:31
nuclear_eclipsepaulr: that's probably not legally enforceable.....10:31
paulrYou have been unquieted on10:31
paulrthat's also not a word10:31
paulrnuclear_eclipse: who cares :010:31
* nuclear_eclipse does10:31
paulryou gonna sue me when I release your subversion plugin as mine?10:32
nuclear_eclipseyes, actually10:32
paulrhave fun10:32
paulr:P10:32
nuclear_eclipseespecially if you do it10:32
nuclear_eclipseanyone else I might bitch at first, but you, I have a lawyer on retainer just for you10:32
paulrcool10:33
nuclear_eclipsejust for *things you do10:33
paulrwow10:33
paulrwhats this php code do10:33
paulr:(10:33
dhx1paulr: he's particularly concerned about the number of bugs you'd introduce :p10:33
nuclear_eclipseexactly, I don't want my code getting a bad rap10:33
paulrheh10:33
paulrdid my language stuff break anything new? :)10:33
paulrnuclear_eclipse: I actually fixed your plugins language stuff whilst I was breaking stuff10:34
dhx1too late, already posted to dailywtf.com :p10:34
nuclear_eclipsepaulr: I saw that in the commit message, but still haven't had time to investigate10:34
paulryou didn't fallback to english if german didn't exist in a plugin10:34
nuclear_eclipsemaybe you broke the fallback, because I'm pretty sure it was working10:35
paulrindeed10:36
paulrit's possible I broke then fixed10:36
paulrhowever, I think it was broken before10:36
paulrcould have been anything tbh10:36
paulrcould have been anything tbh010:36
paulr:)10:36
nuclear_eclipsemeh10:36
nuclear_eclipseone of the downsides of not speaking anything but english is not getting to properly understand and test the i18n/l10n stuffs10:37
paulr:)10:38
*** Quits: Cupertino (~Cupez@unaffiliated/cupertino) (Quit: I give up...)11:01
*** Quits: Rixie (~Rixie@0x4dd7390e.adsl.cybercity.dk) (Quit: Rixie)11:32
*** Quits: giallu (~giallu@fedora/giallu) (Read error: Operation timed out)12:05
*** Quits: rolfkleef (~rolf@82-69-198-84.dsl.in-addr.zen.co.uk) (Quit: Leaving.)12:27
*** Joins: moto-moi (~hylke@cara.xs4all.nl)12:40
*** Joins: siebrand (~beis@sm.xs4all.nl)12:58
*** Joins: cobexer (~cobexer@88-117-61-118.adsl.highway.telekom.at)13:09
*** Quits: micahg (~micah@ubuntu/member/micahg) (Ping timeout: 255 seconds)13:19
*** Quits: paulr (~a@212.85.5.19) ()13:37
*** Joins: giallu (~giallu@fedora/giallu)14:04
*** Joins: micahg (~micah@66.146.192.96)14:34
*** Quits: micahg (~micah@66.146.192.96) (Changing host)14:34
*** Joins: micahg (~micah@ubuntu/member/micahg)14:34
*** Quits: micahg (~micah@ubuntu/member/micahg) (Remote host closed the connection)14:35
*** Joins: micahg (~micah@ubuntu/member/micahg)14:37
*** cobexer is now known as \cobexer|away15:10
*** Joins: paulr (~IceChat09@2001:470:9310:aaaa:290b:b5bc:41f0:9238)15:13
*** Joins: thraxisp (~thraxisp@24.139.16.154)15:22
thraxisphi daryn: I was just catching up on the redesign thread.15:36
darynhello15:36
thraxispIs there a plan for a smaller group to walk through the decision points and plan a way forward?15:37
darynthat's kinda what i was thinking.  i wanted to put together an overview of how i see it working and then present that to core devs15:37
daryni have a good bit in my head but haven't had time to put it all in writing yet15:38
thraxispI may have time to help in the next 6 months.15:38
darynawesome15:38
paulrthraxisp: you've been around for awhile15:39
thraxispFWIW, my last web project was built from Zend/PHPTal/Doctrine (DBAL).15:39
darynmy local mods allow me to use both template system and standard html_api output side by side sometimes even in the same page (template system could = php )15:39
paulrthraxisp: can you recall what prescience's view on licensing were?15:39
thraxispI've been busy.15:40
paulrthraxisp: i.e. why mantis was gpl15:40
darynthraxisp: i like the sound of that (DBAL)...i've looked at that myself but not enough to get very far15:40
paulrdaryn: lang?15:41
* paulr goes to cook15:41
darynpaulr: BAH!15:42
darynno time yet15:42
darynsorry but last week of testing/bug fixes on mantis mods before go live15:42
thraxispI suspect that GPLv2 was the most common thing around at the time. It opens the door to a number of distros like Debian.15:42
thraxispPersonally, I'm not sure about GPLv3. If it's not good enough for the linux kernel, there is a problem.15:43
nuclear_eclipsethraxisp: it's not a matter of "good enough"15:43
nuclear_eclipseit's a matter of Linus doesn't want to waste time tracking down 10,000 contributers to get explicit permissions to change from GPLv2-only to GPLv2/3+15:44
thraxispI thought that there were other issues (e.g., no DRM or compiled code)15:45
nuclear_eclipsethraxisp: last I heard, Linus said he would prefer GPL3, but that it would be impossible to get all those contributers to either agree or even respond to requests to relicense the kernel, so he just doesn't deem it necessary15:46
thraxispok15:46
nuclear_eclipseeither way, we have an exponentially smaller set of contributers to deal with15:47
nuclear_eclipseand IMO, just moving to GPL3 doesn't really get us anywhere, because the normal GPL doesn't really "protect" webapps, which is why the AGPL was created15:48
nuclear_eclipsebut tbh, while I used to be a fan of GPL/AGPL, I've actually had a change of opinion due to multiple incidents that have made me favor the BSD/MIT licenses instead15:50
* thraxisp wishes there was a licenses for non-lawyers site16:03
* daryn wishes lawyers were required to write in plain $user_lang or face severe punishment16:05
*** Quits: pferate (~pferate@173-10-116-125-BusName-Washington.hfc.comcastbusiness.net) (Ping timeout: 264 seconds)16:23
*** Joins: pferate (~pferate@173-10-116-125-BusName-Washington.hfc.comcastbusiness.net)16:23
*** Joins: udait (~yeh@DSL212-235-111-166.bb.netvision.net.il)16:57
paulrdaryn: ok17:02
paulrthraxisp: do we still have any contact with presience?17:03
darynpaulr: ok what?17:03
*** Parts: udait (~yeh@DSL212-235-111-166.bb.netvision.net.il)17:03
darynpaulr: ok what?17:03
paulr[08:42.05] <daryn> no time yet17:03
darynah17:03
thraxisppaulr: Victor might have better contact info. I haven't tried in years.17:04
darynsorry for the double post.  moving too quickly between windows17:04
darynthraxisp: what are you most interested in working on for redesign?17:05
thraxispdaryn: I looked at templates a long time ago, and have done some work in that area since. The issue if that most of the current APIs need rework. It's a huge job.17:07
thraxispchanging to a MVC style would be good.17:08
*** Quits: siebrand (~beis@sm.xs4all.nl) ()17:08
darynyes17:08
daryni think we just have to do it incrementally to get there though17:09
thraxispI'm wondering if a good approach would be to pick a subset of the pages, and re-implement it as a start, then add back the missing ones, while keeping some things static (e.g., plug-ins).17:11
* thraxisp must let the dogd out17:11
darynpossibly.  thinking there are some logical ways to separate...most visible pages first, view all, bug view/edit, my view17:12
darynthen manage pages, config pages17:12
thraxispsounds right17:21
daryni'd like to see a nice ux for configs17:22
gialluconfig sucks :)17:23
*** Quits: moto-moi (~hylke@cara.xs4all.nl) (Ping timeout: 272 seconds)17:27
thraxispWith the MVC projects I've done, new pages come very quickly once the base structures are built and database access is established.17:29
thraxispI was doing one functional page per day, once I had the database done.17:29
darynyeah...i've wondered if we shouldn't just start a new repo for complete redesign...17:30
daryngiallu: Zend? :)17:30
thraxisp(with a PHPTal HTML template, CSS, and PHP implementation).17:30
thraxispgiallu: yes (Zend + PHPTal + Doctrine 1.x)17:30
daryngiallu: did you research that project skeleton link I sent you any more?17:31
gialludaryn, yeah. I had some complaints about it, but you know, not real issues. The point is, if we agree on using Zend, we can just start from the simple approach in their manual, then improve later17:34
darynyeah. i just like that his skeleton had a bunch of stuff ready to go.  like acl17:34
gialluif we are careful, I think we can also move to another license at the same time17:34
* nuclear_eclipse throws his vote behind CodeIgniter :P17:35
daryn:)17:35
daryni've heard good things about that too. never used it though17:35
giallulike in. any new class we write must not use existing apis, no cut&paste from existing API. Existing API will be rewrote to use new classes17:36
nuclear_eclipsealthough tbh, there's quite a lot that Zend brings to the table that you'd have to implement from scratch in CI17:36
darynwow...what happened to this list?  support for a framework? no one screaming yet?17:36
nuclear_eclipsemy biggest complaint with Zend is that it's MVC system seems really heavyweight17:36
micahgnuclear_eclipse: you can use Zend w/out MVC17:37
nuclear_eclipseyeah, but then what's the point? :P17:37
darynyeah, there are certainly things I haven't liked in my initial attempts at using it.17:37
giallunuclear_eclipse, possibly. but I bet when we have MVC, any MVC, changing to another implementation will be much faster17:37
micahgnuclear_eclipse: not recreating the individual  components17:38
thraxispnuclear_eclipse: I found that you don't need to use a lot of it. The problem seems to be that a lot of things are bound together and harder to use individually.17:38
nuclear_eclipsemicahg: if we use any framework for anything, I'd rather just straight up use the framework for everything we possibly can rather than pulling in four different frameworks and three major libraries to get everything that Zend offers in one package17:39
micahgnuclear_eclipse: true, I was originally against MVC, but once you start using it, it's easier to make changes IMHO17:39
* giallu notes in his HD some Mantis_Table_* classes extending Zend_Db_Table_Abstract17:39
nuclear_eclipsemicahg: yeah, my complaint is just in Zend's particular implementation of MVC; ie, I really like CI's lightweight, hands-off MVC system 17:40
giallucascading updates FTW17:40
*** Quits: \cobexer|away (~cobexer@88-117-61-118.adsl.highway.telekom.at) (Read error: Connection reset by peer)17:41
paulr nuclear_eclipse17:42
paulrso anyway17:42
paulrhow do I fit my local git repo17:42
paulr?17:42
paulrfix*17:42
nuclear_eclipsepaulr: delete it and start over ;)17:42
nuclear_eclipsebut seriously, you need to give me more info17:43
paulrwell17:43
paulrI need to see what i've got stashed17:43
paulrcan I do a diff of what's in a stash?17:43
nuclear_eclipsea stash is just a patch, so just show the stash item...17:44
paulrok, how can i delete stash@{0} ?17:45
nuclear_eclipsea stashed item doesn't have any history associated with it, so you can apply it anywhere17:45
nuclear_eclipse`git help stash`17:45
paulrcan i diff two stashes?17:47
nuclear_eclipsethat doesn't even make sense...17:47
nuclear_eclipsehow would you diff two patches?17:48
paulrapparently you can17:48
paulrwell17:49
nuclear_eclipsethe best I can imagine is to apply the two stashed items to different branches and diff the branches...17:49
paulrI think all 3 stashes are the same diff17:49
paulrI think git diff stash@{0} stash@{1} might work17:49
nuclear_eclipseah, so yes, what you said bascally does what I mentioned: it applies the two patches to separate copies of the current branch, and diffs the result17:52
nuclear_eclipseactually, I'm wrong17:53
nuclear_eclipseapparently git stores the original commit ref context for stashed items and uses that as the base point for the diffs17:54
* paulr thinks17:59
paulrgit stash apply aplies from stack?17:59
darynpaulr: but leaves it on the stack...i think git pop applies and then removes it from the stack... check the docs18:00
paulrmaybe that's the proper18:00
paulrerm problem18:00
paulri'm knackered18:00
paulrhmm18:10
darynheading home...cya18:10
*** Quits: daryn (~daryn@h158.249.190.173.static.ip.windstream.net) (Quit: Ex-Chat)18:11
paulrnuclear_eclipse: still there/18:23
*** Quits: paulr (~IceChat09@2001:470:9310:aaaa:290b:b5bc:41f0:9238) (Quit: Light travels faster then sound, which is why some people appear bright, until you hear them speak)18:56
*** Quits: giallu (~giallu@fedora/giallu) (Ping timeout: 245 seconds)19:03
*** Quits: Ragnor (~Ragnor@dslb-188-100-044-146.pools.arcor-ip.net) (Remote host closed the connection)19:39
*** Joins: Ragnor (~Ragnor@dslb-188-100-044-146.pools.arcor-ip.net)19:39
*** Quits: scribe9343423 (~scribe934@static.96.23.63.178.clients.your-server.de) (Remote host closed the connection)20:00
*** Joins: scribe9343423 (~scribe934@static.96.23.63.178.clients.your-server.de)20:00
*** Quits: micahg (~micah@ubuntu/member/micahg) (Ping timeout: 264 seconds)20:36
*** Quits: thraxisp (~thraxisp@24.139.16.154) (Quit: thraxisp)21:38
*** Joins: daryn (~daryn@h1.146.16.98.dynamic.ip.windstream.net)22:14
*** Joins: micahg (~micah@ubuntu/member/micahg)22:14
*** Joins: thraxisp (~thraxisp@24.139.16.154)22:29
*** Quits: thraxisp (~thraxisp@24.139.16.154) (Quit: thraxisp)22:52
*** Quits: daryn (~daryn@h1.146.16.98.dynamic.ip.windstream.net) (Quit: Ex-Chat)23:32

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