| 09:20.30 | *** join/#flyspray tda (n=tda@c222143.adsl.hansenet.de) |
| 09:24.15 | tda | good morning everybody |
| 09:49.36 | *** join/#flyspray kNIGits_ (i=tc@202-161-16-228.dyn.iinet.net.au) |
| 09:49.36 | *** mode/#flyspray [+o kNIGits_] by ChanServ |
| 09:50.11 | *** join/#flyspray kNIGits_ (i=tc@202-161-16-228.dyn.iinet.net.au) |
| 09:50.12 | *** mode/#flyspray [+o kNIGits_] by ChanServ |
| 09:50.46 | *** topic/#flyspray by kNIGits_ -> Flyspray bug tracking system | http://flyspray.rocks.cc | BTS upgraded to latest development code, try it! |
| 10:15.00 | *** join/#flyspray floele (n=Miranda@p508CB8FC.dip0.t-ipconnect.de) |
| 10:15.00 | *** mode/#flyspray [+o floele] by ChanServ |
| 10:24.17 | kNIGits_ | g'day mate |
| 10:24.23 | floele | Hi |
| 10:24.34 | kNIGits_ | I'm at work, night shift |
| 10:24.48 | kNIGits_ | I was about to take a look at your latest patch (view own tasks perm) |
| 10:25.45 | floele | ok. I noticed that the permission-checks are not always very efficient |
| 10:25.53 | kNIGits_ | more information? |
| 10:26.31 | floele | well, you call GetAssignees even if it is not needed |
| 10:27.46 | floele | && ($this->perms['manage_project'] || in_array($this->id, $assignees)); |
| 10:27.58 | kNIGits_ | which perm is that? |
| 10:28.11 | floele | just an example, the last one |
| 10:28.28 | floele | if $this->perms['manage_project'] is true, the second condition is not checked at all |
| 10:28.46 | floele | but you already called the GetAssignees function |
| 10:29.04 | kNIGits_ | hmm, did I do that? it doesn't make sense that a user can mark their opened tasks private and public |
| 10:29.35 | floele | tasks assigned to him |
| 10:29.47 | kNIGits_ | errr, |
| 10:30.12 | kNIGits_ | I'm even dumber than usual when I'm tired :-) |
| 10:30.22 | floele | :D |
| 10:30.31 | floele | but you get the point I make? |
| 10:31.08 | kNIGits_ | I see what you're saying |
| 10:31.25 | kNIGits_ | you want to only call GetAssignees() if the PM check is false |
| 10:32.34 | floele | only if it is necessary in generaö |
| 10:33.09 | floele | you could achive that by not creating $assignees at all |
| 10:35.41 | kNIGits_ | and how could we then check it? give me an example? |
| 10:36.02 | floele | && ($this->perms['manage_project'] || in_array($this->id, $fs->GetAssignees($task['task_id']))); |
| 10:37.13 | kNIGits_ | that could work |
| 10:37.24 | kNIGits_ | now I see what you meant |
| 10:37.34 | floele | good :) |
| 10:37.50 | floele | I can take care of that if you like |
| 10:37.59 | kNIGits_ | less permission checks = less sql queries = more efficient = better |
| 10:38.18 | kNIGits_ | please do |
| 10:38.30 | floele | in can_create_group |
| 10:38.33 | kNIGits_ | I am logged into my server over dialup, so editing is a little painful |
| 10:38.38 | floele | whatfor is && !Get::val('project'))? |
| 10:39.01 | kNIGits_ | I have no idea. weird |
| 10:39.18 | kNIGits_ | I certainly didn't put it there |
| 10:39.51 | floele | I'll remove it and see what happens ;) |
| 10:39.54 | kNIGits_ | if only MadCoder was around |
| 10:39.58 | kNIGits_ | heh, go for it! |
| 10:41.26 | kNIGits_ | your history query is very impressive, btw |
| 10:41.36 | floele | thanks :) |
| 10:42.03 | floele | it is still far from perfect though |
| 10:42.53 | floele | it seems to work without Get::val too |
| 10:43.29 | floele | if someone can manage a project I see no reason why he shouldn't be able to create a group |
| 10:43.41 | kNIGits_ | the whole history code is a mess. one day I might get to fixing it |
| 10:43.58 | floele | hm... |
| 10:44.41 | floele | ($this->perms['manage_project'] && $proj->id != 0) |
| 10:44.46 | floele | this is probably what is meant |
| 10:44.49 | kNIGits_ | that Get::val('project') checks for the project var on the URL... how could that be relevant for creating a group? |
| 10:45.00 | kNIGits_ | yeah, that's more likely |
| 10:45.42 | kNIGits_ | to stop PMs creating a global group |
| 10:49.21 | floele | it is not necessary though |
| 10:49.25 | floele | I just checked |
| 10:49.44 | floele | when the project is 0, the project manager does not get [manage_project] => 1 |
| 10:49.49 | floele | but [manage_project] => 0 |
| 10:52.23 | floele | btw, I noticed something in your BTS |
| 10:52.59 | floele | before I think I was able to edit comments, and now I am not able to do that. was I never able to do it? |
| 10:55.31 | kNIGits_ | I messed with permissions during the upgrade. I'll double check them now |
| 10:56.56 | kNIGits_ | hm, we have to do something about that error |
| 10:57.08 | kNIGits_ | Warning: ob_start(): output handler 'ob_gzhandler' cannot be used after 'URL-Rewriter' in /home/.jackaroo/knigits/flyspray.rocks.cc/bts/index.php on line 90 |
| 10:57.14 | floele | indeed ;) |
| 10:58.21 | floele | I got another idea bout the task statuses |
| 10:59.01 | kNIGits_ | do tell |
| 10:59.35 | kNIGits_ | hrmf, and logging in takes me to the error page |
| 10:59.37 | floele | *if* the user/admin deletes a status like "unconfirmed", "new" or "assigned" he can never add them again since the index value matters. I suggest to disable the possibility to delete them |
| 11:00.15 | floele | but those are quite important for flyspray |
| 11:00.48 | kNIGits_ | yes |
| 11:01.38 | kNIGits_ | your edit comment permission is restored |
| 11:01.47 | floele | ok :) |
| 11:02.53 | *** join/#flyspray _kNIGits (i=tc@202-161-16-228.dyn.iinet.net.au) |
| 11:02.53 | *** mode/#flyspray [+o _kNIGits] by ChanServ |
| 11:03.48 | _kNIGits | errr, wtf just happened... |
| 11:03.53 | floele | you can have a look at the change in my BTS now if you like |
| 11:04.01 | _kNIGits | damn, got disconnected |
| 11:04.10 | floele | lol, 3 kNIGits :) |
| 11:04.22 | _kNIGits | make that two |
| 11:05.38 | floele | in theory you could still dele the statuses, but not using the flyspray GUI so it is OK I think :) |
| 11:07.00 | kNIGatwork | you can delete anything using the commandline or phpmyadmin |
| 11:08.13 | kNIGatwork | interesting how that gzip error doesn't happen on your server |
| 11:09.03 | floele | does it happen on other servers than yours? |
| 11:09.40 | kNIGatwork | I can't see that I know of any others that run 0.9.9-devel |
| 11:10.03 | floele | what about mac? didn't he want to run it? |
| 11:10.18 | kNIGatwork | yes, but I think his is private |
| 11:10.31 | floele | but he can tell us ;) |
| 11:12.17 | kNIGatwork | yep, when america wakes up |
| 11:18.04 | kNIGatwork | ah, it's a good feeling to search google and see how many people are using Flyspray |
| 11:20.06 | floele | mine is among them too :) |
| 11:21.07 | floele | hm, interesting that turtoiseSVN uses it |
| 11:21.08 | kNIGatwork | yep, you didn't know? |
| 11:21.08 | floele | no |
| 11:21.08 | kNIGatwork | and dokuwiki :-) |
| 11:21.19 | kNIGatwork | and jpgraph, and archlinux |
| 11:21.54 | kNIGatwork | http://www.deltascripts.com/bugs/ |
| 11:23.02 | floele | is this something special? |
| 11:24.02 | kNIGatwork | I just liked the page wrapper |
| 11:24.45 | floele | yep, it's nice. and it future it will probably be easier to achieve that :) |
| 11:26.05 | kNIGatwork | yeah, now that we have templates |
| 11:28.42 | floele | hm, I just noticed a problem when looking at the SVN bug tracker. if the logo is not displayed the links top right are still not very useable... |
| 11:30.40 | floele | maybe we should replace "Open a new Task anonymously" with a button in the menu? |
| 11:37.01 | kNIGatwork | hell no |
| 11:37.22 | kNIGatwork | we've removed the "show logo" option, and we have templates |
| 11:37.38 | kNIGatwork | if someone wants to modify the templates to remove the logo, then they can also fix the link :-) |
| 11:38.24 | floele | oooookay ;) |
| 11:40.21 | kNIGatwork | that's how I see it, anyway |
| 11:41.11 | kNIGatwork | I'm not really working, you know. I'm at my workplace, but I'm watching a movie :-D |
| 11:41.23 | floele | lol |
| 11:41.39 | kNIGatwork | and talking to you on my laptop, dialed up |
| 11:43.49 | floele | I noticed that you are talking to me ;) |
| 11:58.58 | kNIGatwork | noticed that I"m not talking much now? :-) |
| 12:38.57 | kNIGatwork | but neither are you, so I guess that's ok |
| 12:39.09 | floele | it is ;) |
| 12:51.24 | kNIGatwork | so what are you doing? surely not school |
| 13:11.43 | *** join/#flyspray floele41 (n=Miranda@p508C9084.dip0.t-ipconnect.de) |
| 13:11.44 | *** mode/#flyspray [+o floele41] by ChanServ |
| 13:24.30 | kNIGatwork | what are you doing, floele41? surely not school |
| 13:24.48 | floele41 | no, I have holidays :) |
| 13:25.03 | floele41 | so I am learning for my abitur |
| 13:25.15 | floele41 | Biotechnology right now |
| 13:27.17 | kNIGatwork | http://bugs.ayende.com/index.php?tasks=all&project=3 a different colour scheme |
| 13:27.55 | floele41 | nice :) |
| 13:28.28 | kNIGatwork | it says 'modified by...', but I can't see any changes except the theme |
| 13:29.44 | floele41 | maybe he had to do some changes within the flyspray code |
| 13:30.47 | kNIGatwork | maybe |
| 13:31.51 | floele41 | this also has an interesting theme: http://www.agentur-simon.de/flyspray/ |
| 13:34.30 | kNIGatwork | yes, but I can't see much of it |
| 13:34.53 | kNIGatwork | and clicking 'show' results in a nasty error |
| 13:35.08 | kNIGatwork | silly Markdown |
| 13:35.18 | kNIGatwork | didn't I remove that for 0.9.8? |
| 13:35.56 | floele41 | I don't think so |
| 13:36.09 | floele41 | pierre did for 0.9.9 |
| 13:37.24 | kNIGatwork | I'm pretty sure that I did. there were many complaints about it in 0.9.7 |
| 13:37.42 | floele41 | but you didn't do for the project message |
| 13:38.57 | kNIGatwork | oh |
| 13:39.06 | kNIGatwork | I removed it for task details and comments |
| 13:41.12 | kNIGatwork | it's good to see that most installations I find are 0.9.8, but I'm unhappy to find a few 0.9.7, and even a couple of 0.9.6 |
| 13:41.39 | floele41 | like mine :) |
| 13:41.47 | floele41 | why are you unhappy? |
| 13:41.57 | kNIGatwork | because they have nasty bugs, including security |
| 13:42.11 | kNIGatwork | people should upgrade. it's free |
| 13:42.20 | floele41 | is that *your* problem? ;) |
| 13:42.48 | floele41 | btw, you could add a feature that checks if Flyspray is up-to-date |
| 13:44.33 | floele41 | or I could do it if you like such a feature ;) |
| 13:47.43 | kNIGatwork | I have often thought of adding it myself |
| 13:47.49 | floele41 | but? |
| 13:47.54 | kNIGatwork | however, most people don't like software that phone's home |
| 13:48.18 | kNIGatwork | and what about those installations that aren't connected to the internet? |
| 13:48.35 | floele41 | ?? |
| 13:48.49 | floele41 | those installations shouldn't suffer security problems |
| 13:49.01 | kNIGatwork | possibly |
| 13:49.09 | floele41 | most likely ;) |
| 13:49.41 | floele41 | if you can disable the update check, is it a problem then? |
| 13:49.55 | kNIGatwork | I have thought of adding a 'check for updates' feature that only appears on an Admin's login |
| 13:50.40 | floele41 | yes, something like that |
| 13:51.47 | floele41 | if(isLongTimeAgo($fs->prefs['last_check'])) { |
| 13:51.47 | floele41 | <PROTECTED> |
| 13:51.47 | floele41 | } |
| 13:52.11 | kNIGatwork | I would probably make it include_once() a file on the Flyspray webserver. that file would contain each version on a newline |
| 13:52.25 | kNIGatwork | the most recent version at the top. if the version they're using isn't at the top, then prompt them |
| 13:52.28 | floele41 | no, not include |
| 13:52.37 | kNIGatwork | no? |
| 13:52.51 | floele41 | imagine someone hacks your server |
| 13:52.58 | floele41 | and outs PHP code in that file |
| 13:53.00 | kNIGatwork | gah |
| 13:53.20 | floele41 | he could hack all FS installations at once then |
| 13:53.27 | kNIGatwork | nasty. how then? |
| 13:53.43 | floele41 | file_get_contents('http://etc.'); for example |
| 13:54.03 | kNIGatwork | oh, and if my server was offline or slow, then every flyspray install would hang |
| 13:54.32 | floele41 | we can also use fsockopen and a short timeout |
| 13:54.48 | floele41 | and of course it is not checked on *every* login |
| 13:55.28 | kNIGatwork | yep |
| 13:55.40 | floele41 | and you could also consider putting that file on another server |
| 13:55.47 | floele41 | which has a better internet connection |
| 13:57.14 | floele41 | why should the file contain all versions btw? isn't one enough? |
| 13:57.52 | kNIGatwork | better internet connection? better than the Flyspray site that's hosted in the USA? |
| 13:58.08 | floele41 | isn't that your home server? |
| 13:58.23 | kNIGatwork | the Flyspray website is not hosted on my dsl line :-) |
| 13:58.31 | floele41 | ah, ok |
| 13:58.44 | kNIGatwork | sometimes it seems that slow, but it isn't |
| 13:58.51 | kNIGatwork | only throw.rocks.cc is my dsl |
| 13:59.08 | kNIGatwork | I pay for hosting for flyspray.rocks.cc |
| 14:01.46 | floele41 | so do you want me to implement it? :) |
| 14:01.56 | kNIGatwork | speaking of paying... did you contact those people about them paying you to do Flyspray changes? |
| 14:02.10 | floele41 | I don't even know who hey are |
| 14:02.21 | kNIGatwork | oh. I thought that macnewbold told you |
| 14:04.10 | floele41 | he told me that there are people who are interested in etc, |
| 14:04.51 | kNIGatwork | ok. he actually told me privately first, and I said that you'd do a better, faster job |
| 14:05.18 | kNIGatwork | so as much as I could use the $$$, I told him to tell you |
| 14:06.57 | floele41 | hm, he didn't ell me anything than that what he announced here in the chat room |
| 14:08.39 | kNIGatwork | nor me |
| 14:09.30 | kNIGatwork | yes, you can implement the update check if you like. I will see how I like it, and how other people like it (or not) |
| 14:09.43 | floele41 | ok |
| 14:10.39 | floele41 | could you add a file to your server containing the latest version of FS? In this case 1.0 of course |
| 14:10.48 | floele41 | just for testing |
| 14:11.05 | kNIGatwork | if you're making changes, can you swap the 'assigned to' and 'opened by' in the search box please? |
| 14:11.15 | kNIGatwork | sure, I'll do that now |
| 14:11.19 | floele41 | why? |
| 14:11.38 | kNIGatwork | because it makes more sense to me. a task is 'opened' first,then 'assigned |
| 14:11.47 | kNIGatwork | you don't agree? |
| 14:12.04 | floele41 | of course I do :) |
| 14:12.35 | kNIGatwork | you don't have to agree with me. it's not like I'm going to fire you from a high-paying job :-) |
| 14:13.05 | floele41 | I only wanted to know if there are more reasons to do that ;) |
| 14:13.45 | floele41 | and I already disagreed on other topics with you :-p |
| 14:14.06 | kNIGatwork | http://flyspray.rocks.cc/version.txt |
| 14:14.22 | floele41 | good work ;) |
| 14:16.10 | kNIGatwork | I assume that you're going to compare the current version with the one the user is running in the $version variable? |
| 14:16.16 | tda | What we do is using a number like 100 for 1.00 so you can use > and < operators |
| 14:16.32 | tda | But then no alpha is possible. |
| 14:16.44 | kNIGatwork | and what if I make another Update like I did for 0.9.8 ? |
| 14:16.50 | floele41 | yes |
| 14:17.13 | floele41 | version_compare() maybe? |
| 14:17.20 | floele41 | or 0.9.8.1 |
| 14:17.33 | floele41 | "update1" is a stupid name |
| 14:17.43 | floele41 | (to my eye) |
| 14:19.12 | kNIGatwork | and 0.9.8.1 looks like a fresh release |
| 14:19.32 | kNIGatwork | I didn't want it to look like a new release, when it only had a few changed files |
| 14:20.50 | floele41 | it still is better. "update1" sounds like a last-minute-patch |
| 14:21.24 | floele41 | in any case it has a negative connotation |
| 14:22.01 | kNIGatwork | version_compare() looks good to me |
| 14:22.05 | floele41 | and you don't have to always ask "did you apply update1"? |
| 14:22.19 | kNIGatwork | we will have to try and use a standard naming convention now |
| 14:22.33 | floele41 | every update gets its own version and there is no confusion :) |
| 14:22.57 | kNIGatwork | I hate releases |
| 14:23.14 | kNIGatwork | especially when I didn't write the installer, and it doesn't operate how I want it to |
| 14:23.19 | floele41 | I guess after 1.0 we could use 1.1, 1.2 1.3 for major releases and 1.0.1 1.0.2 for (important) bugfixes |
| 14:23.35 | floele41 | indeed, releases can be a pain |
| 14:23.43 | floele41 | all the testing and packaging you have to do... |
| 14:24.04 | tda | We use even and odd numbers like linux does. |
| 14:24.21 | kNIGatwork | g'day tda |
| 14:24.34 | tda | Hello kNIGits |
| 14:25.07 | kNIGatwork | I don't like the linux versioning system much |
| 14:25.09 | tda | sorry, and of course hello floele |
| 14:25.13 | floele41 | probably we will end up with a version like 1.16.x then |
| 14:25.25 | tda | yep |
| 14:25.27 | floele41 | and this is always a little confusing |
| 14:25.29 | kNIGatwork | I also don't like that |
| 14:25.45 | floele41 | I have to eat, will be back in a few minutes |
| 14:25.53 | kNIGatwork | I really want to go 0.9.9 then 1.0 |
| 14:25.54 | tda | Guten Appetit |
| 14:27.47 | tda | kNIGatwork, do you have a jabber address too? |
| 14:28.12 | kNIGatwork | yes |
| 14:28.26 | tda | thank you. |
| 14:28.35 | tda | :-) |
| 14:28.48 | kNIGatwork | I mostly use Jabber to keep in contact with my friends in the other states I've lived in |
| 14:29.23 | tda | ok, I see. Is the OpenPGP plugin ok? I mean does it work as it should? |
| 14:29.29 | tda | sorry, I mean PSI |
| 14:29.46 | kNIGatwork | I've successfully used GnuPG with Psi on Linux |
| 14:30.19 | tda | I am using it but have no idea if msgs are en/decrypted or if it just tells so. |
| 14:30.52 | kNIGatwork | if you have the other person's public key, and they have yours.... click the 'encrypt' button and go for it |
| 14:32.07 | kNIGatwork | if you want to confirm that it really is encrypted, open the xml console window and see what's actually sent and received |
| 14:33.15 | floele41 | back, and danke :) |
| 14:34.12 | tda | Thanks, now I feel much better having seen the gpg encryption |
| 14:41.04 | kNIGatwork | np |
| 14:59.32 | floele41 | kNIGits, does your server always have the same IP? |
| 15:02.31 | floele41 | kNIGatwork rather |
| 15:03.15 | kNIGatwork | do you mean the Flyspray website? |
| 15:03.20 | floele41 | yes |
| 15:05.28 | floele41 | I guess it doesn't matter anymore :) |
| 15:06.21 | floele41 | have a look at my dev version. is the error-message div too "eye-catching"? |
| 15:06.42 | kNIGatwork | I don't know about the IP address, but the domain name never changes |
| 15:06.50 | floele41 | haha |
| 15:08.13 | kNIGatwork | I particularly like all the notices and warnings |
| 15:08.21 | floele41 | ? |
| 15:08.34 | floele41 | which are? |
| 15:09.21 | kNIGatwork | Notice: Undefined index: project_is_active in /www/htdocs/v111912/flyspray/includes/class.user.php on line 143 |
| 15:09.27 | kNIGatwork | Warning: Cannot modify header information - headers already sent by (output started at /www/htdocs/v111912/flyspray/includes/class.user.php:143) in /www/htdocs/v111912/flyspray/index.php on line 79 |
| 15:09.35 | kNIGatwork | and a few more warnings like that one |
| 15:09.47 | floele41 | I don#t get them |
| 15:10.47 | kNIGatwork | http://gosdaturacatala-zucht.de/flyspray/index.php?project=0&tasks=all&do=index&area=status&show=Show |
| 15:11.08 | floele41 | ah |
| 15:12.35 | floele41 | fixed |
| 15:13.10 | floele41 | so, what about the message? |
| 15:13.25 | kNIGatwork | yes, it's a bit obvious |
| 15:13.42 | floele41 | too obviuos? |
| 15:14.52 | floele41 | so it is? |
| 15:15.15 | kNIGatwork | yes, it's a bit much |
| 15:16.21 | floele41 | now better? |
| 15:17.53 | kNIGatwork | yes |
| 15:18.03 | floele41 | ok |
| 15:20.47 | kNIGatwork | perhaps it could be overlaid in the title image? |
| 15:21.08 | floele41 | and if it doesn't exist? |
| 15:21.33 | floele41 | you can't expect a user to fix the whole flyspray if he removes the header image ;) |
| 15:22.50 | kNIGatwork | yeah, good point |
| 15:24.14 | kNIGatwork | leave it where it is. now, I'll change version.txt and see what happens |
| 15:27.35 | kNIGatwork | now, see what happens |
| 15:27.51 | floele41 | hm.... |
| 15:28.07 | floele41 | probably the (devel) causes problems |
| 15:28.36 | kNIGatwork | indeed |
| 15:29.30 | floele41 | we could call it dev instead of devel |
| 15:30.51 | floele41 | is that OK? |
| 15:31.34 | kNIGatwork | 0.9.9dev? |
| 15:31.45 | floele41 | 0.9.9 dev |
| 15:32.06 | floele41 | 0.9.9dev also works |
| 15:32.26 | kNIGatwork | change it in your functions.inc.php and see if it works |
| 15:32.41 | floele41 | it does |
| 15:33.00 | floele41 | hm, in fact it does not |
| 15:33.11 | floele41 | 0.9.9dev should be lower than 0.9.9 |
| 15:35.15 | kNIGatwork | yes, but perhaps the function doesn't recognise it |
| 15:36.20 | floele41 | The function first replaces _, - and + with a dot . in the version strings and also inserts dots . before and after any non number so that for example '4.3.2RC1' becomes '4.3.2.RC.1'. Then it splits the results like if you were using explode('.', $ver). Then it compares the parts starting from left to right. If a part contains special version strings these are handled in the following order: dev < |
| 15:36.20 | floele41 | <PROTECTED> |
| 15:42.20 | floele41 | hm, now it works |
| 15:42.34 | floele41 | you have to call the final version "0.9.9 pl" then |
| 15:43.21 | kNIGatwork | hmm, I don't like that much |
| 15:43.55 | floele41 | otherwise we could write our own version compare function |
| 15:45.25 | floele41 | or even easier |
| 15:45.45 | floele41 | we add ' pl' to the version |
| 15:47.41 | floele41 | since the version in your file always ia a release and not a beta version |
| 15:49.02 | floele41 | anyway, I have to fo now. cya |
| 16:55.37 | macnewbold | kNIGits / kNIGatwork: I'm back now... I see you and flo were discussing my BTS |
| 16:56.08 | macnewbold | it's publicly accessible, but doesn't let anyone anonymous do anything, nor anyone sign up without my approval. |
| 16:58.21 | macnewbold | and I'm still waiting to hear back on the people who are potentially interested in paying for some flyspray work |
| 16:58.35 | macnewbold | so I'll need to talk to flo about it sometime soon |
| 17:01.11 | kNIGatwork | sure |
| 17:03.20 | macnewbold | and seriously, kNIGits - I know what you have done for flyspray, and if you want it, it's yours, just let me know how much you'd ask (in USD$ to your paypal acct, for example) |
| 17:03.53 | kNIGatwork | what do you mean? me customising Flyspray for your contacts? |
| 17:04.18 | macnewbold | yes |
| 17:04.25 | macnewbold | you say you wouldn't be that good, but you would |
| 17:04.28 | *** join/#flyspray floele (n=Miranda@p508C9084.dip0.t-ipconnect.de) |
| 17:04.28 | *** mode/#flyspray [+o floele] by ChanServ |
| 17:04.34 | macnewbold | morning, floele |
| 17:04.55 | macnewbold | guten morgen |
| 17:05.07 | macnewbold | I was just telling knigits as I was reading the backlog: |
| 17:05.13 | macnewbold | I'm back now... I see you and flo were discussing my BTS |
| 17:05.16 | macnewbold | it's publicly accessible, but doesn't let anyone anonymous do anything, nor anyone sign up without my approval. |
| 17:05.20 | macnewbold | and I'm still waiting to hear back on the people who are potentially interested in paying for some flyspray work |
| 17:05.28 | floele | Guten Abend eher ;) |
| 17:05.48 | floele | ok |
| 17:05.54 | kNIGatwork | perhaps we could do it together |
| 17:05.57 | macnewbold | so if you're interested, floele, let me know how much you'd ask, and how you'd want them to pay you (via paypal, perhaps?) and I'll give them your name too |
| 17:05.59 | macnewbold | sure |
| 17:06.13 | macnewbold | that actually wouldn't be a bad idea |
| 17:06.35 | macnewbold | especially if all the improvements they want could be part of the main flyspray version, rather than patches |
| 17:06.54 | kNIGatwork | I'd need a full list of what they want, and how soon they want it |
| 17:07.10 | floele | well, I prefer if I simply get a list of tasks and then I'll see if I want to work on anything which is on the list. *after* that we can talk about payment ;) |
| 17:07.20 | kNIGatwork | yeah, that too |
| 17:07.26 | floele | will be back in a moment, have to eat |
| 17:07.27 | macnewbold | I could coordinate with them and keep track of all the stuff they want done, and collect the money from them (they're already a client of ours), and split it up and send it to you two who are working on it |
| 17:07.36 | macnewbold | yes, very true |
| 17:07.49 | kNIGatwork | all our changes would be under the LGPL |
| 17:07.55 | kNIGatwork | remember the last person that wanted to hire me |
| 17:07.56 | macnewbold | so far they mentioned reports and perhaps some fine-grained permissions |
| 17:08.06 | macnewbold | yes, they know about that already |
| 17:08.10 | macnewbold | they're not trying to resell it or anything, |
| 17:08.14 | macnewbold | they want to adopt it in house |
| 17:08.24 | macnewbold | but there are some features they'd like in order to do so |
| 17:09.09 | kNIGatwork | the reports area is very lacking, I agree |
| 17:13.54 | floele | true...probably we would have to rewrite the whole code before we can add any features ;) |
| 17:14.55 | kNIGatwork | possibly |
| 17:15.47 | floele | what about the other person who wanted to hire you? |
| 17:17.52 | floele | I am away again now...cu later |
| 17:18.41 | kNIGatwork | the other person who wanted to pay me to do Flyspray enhancements wanted it under a different licence so that they could sell it |
| 17:20.25 | kNIGatwork | macnewbold, remind me what other features they were interested in? |
| 17:20.52 | kNIGatwork | (oh, and what time is it in USA right now?) |
| 17:44.50 | macnewbold | right now where I am (Utah, same timezone as Denver Colorado) it is 10:44am on jan 4 |
| 17:44.57 | macnewbold | I don't know what other features they had in mind |
| 17:56.27 | kNIGatwork | I'm sure that they'll tell us if they're serious |
| 17:58.06 | macnewbold | yeah |
| 17:58.11 | macnewbold | he was mostly just asking |
| 17:58.16 | macnewbold | it was his first time seeing flyspray |
| 17:58.22 | macnewbold | I didn't take notes though on his questions |
| 18:20.17 | *** join/#flyspray teranex (n=TeRanEX@d515284A5.access.telenet.be) |
| 18:20.56 | kNIGatwork | np mate |
| 18:21.53 | kNIGatwork | it's like this - if I can do what he's asking for, and I have time, I'm happy to take whatever he's paying. if I can't, I defer to Florian who will undoubtably do a stellar job |
| 18:35.51 | *** join/#flyspray macnewbold (n=mac@69.2.248.251) |
| 18:35.51 | *** mode/#flyspray [+o macnewbold] by ChanServ |
| 19:05.30 | *** part/#flyspray teranex (n=TeRanEX@d515284A5.access.telenet.be) |
| 22:24.07 | *** join/#flyspray odoc (i=odoc@is.borntobooze.de) |
| 22:55.45 | *** join/#flyspray kevinm (n=kvirc@adsl-69-209-19-30.dsl.emhril.ameritech.net) |
| 22:56.12 | kevinm | hello all, quick question |
| 22:56.40 | kevinm | I've been running 0.9.6 of Flyspray and want to upgrade to 0.9.8...do I have to upgrade to 0.9.7 first? |
| 22:59.56 | *** join/#flyspray floele (n=Miranda@p508C9084.dip0.t-ipconnect.de) |
| 22:59.56 | *** mode/#flyspray [+o floele] by ChanServ |
| 23:01.47 | *** part/#flyspray odoc (i=odoc@is.borntobooze.de) |
| 23:01.56 | *** join/#flyspray teranex (n=TeRanEX@d515284A5.access.telenet.be) |
| 23:05.07 | macnewbold | kevinm: yes, upgrade to 0.9.7, then to 0.9.8, then apply update1 |
| 23:06.09 | kevinm | Excuse me if I'm being dumb, but I move out of the way the 0.9.6 directory, put the 0.9.7 stuff in, connect via the web and go thru the steps, then do the same for 0.9.7->0.9.8? |
| 23:06.42 | macnewbold | you're fine - yes, I think that would work |
| 23:07.10 | kevinm | No way to do this from the command line? I need to recreate my flyspray.conf.php file every time? |
| 23:07.39 | macnewbold | I'm not sure what 0.9.7 does, but 0.9.8 will create the conf for you as part of the setup process |
| 23:08.14 | kevinm | ok, I'll give it a whirl...seems fairly cumbersom (sp?). |
| 23:08.14 | macnewbold | you can do it with a combination of web and command line stuff |
| 23:08.33 | macnewbold | 0.9.6 is extremely old, and very few people still use it |
| 23:08.43 | macnewbold | 0.9.7 is a year old, so 0.9.8 can upgrade from 0.9.7 |
| 23:08.47 | macnewbold | but not directly from 0.9.6 |
| 23:08.50 | macnewbold | unfortunately |
| 23:09.12 | macnewbold | most people who upgrade are upgrading from the immediately previous version |
| 23:09.45 | kevinm | cool, thanks for the help...I may be back with more questions (hope not but...) |
| 23:09.48 | macnewbold | there have just been too many database changes to do an upgrade very easily, and I don't think we had a really good way to test an upgrade from 0.9.6 to 0.9.8 anyway |
| 23:13.33 | kevinm | So it appears that, based on the 0.9.7 initial webpage, that I'm going to lose all of my data in my existing flyspray database. This from the comment "Note that you must have already created the database that you wish to use for Flyspray, and it must NOT have a Flyspray structure already inside it.". Is this the case? |
| 23:19.00 | macnewbold | I'm not sure |
| 23:19.10 | macnewbold | I've never installed 0.9.7 myself, kevinm |
| 23:19.15 | macnewbold | backup your database |
| 23:19.19 | macnewbold | and try the upgrade, I guess |
| 23:48.15 | *** join/#flyspray terane1 (n=TeRanEX@d515284A5.access.telenet.be) |