Meeting: 2007-11-11 17:00
Note
Meeting log from #sourcemage-admin by ElisamuelResto on Sunday November 11th 2007 for meeting scheduled at 1700UTC. All times represented in the logs (but those from other users) are in the AST (GMT -0400) timezone.
Meeting Log
| 12:59 | +_kaze_ | dim nov 11 16:59:47 UTC 2007 |
| 13:00 | * | BearPerson grabs his meeting chair |
| 13:00 | * | Enqlave grabs BearPerson |
| 13:00 | * | _kaze_ wears his dilbert suit |
| 13:01 | @emrys | who all do we have |
| 13:01 | * | abouter waves |
| 13:01 | * | lynxlynxlynx segfaults |
| 13:01 | * | novaburst jumps up and waves |
| 13:01 | * | qnr je suis ici |
| 13:01 | * | mar_s hides in his chair |
| 13:01 | * | Enqlave coredumps |
| 13:01 | * | flux_control sizzles |
| 13:01 | * | sobukus wavery waves |
| 13:02 | * | _kaze_ runs around in circles |
| 13:02 | * | emrys throws a chair at dkowis |
| 13:02 | * | BearPerson waves a paw |
| 13:02 | * | p3pilot waves |
| 13:03 | +Enqlave | dkowis will be late ;p |
| 13:03 | @emrys | sandalle? |
| 13:03 | +_kaze_ | yeah, it seems dkowis was headshot by a chair some minuets ago :) |
| 13:03 | +Enqlave | :) |
| 13:04 | +flux_control | _kaze_: so he's stuck in the respawn queue? |
| 13:04 | * | novaburst throws a milk soaked oreo at sandalle |
| 13:04 | -!- | lace [n=lace@sourcemage/lace] has joined [#sourcemage-admin] |
| 13:04 | * | flux_control jumps in front of it and cathes it with his mouth |
| 13:04 | +flux_control | mmm, milk-soaked orea... |
| 13:04 | @emrys | for the new people who haven't heard this before, keep the spam down during the meeting please |
| 13:05 | +qnr | sandalle was up about an hour ago |
| 13:05 | +ryuji | im here |
| 13:06 | +ryuji | 5min late, but i made it |
| 13:06 | +Enqlave | 6 |
| 13:06 | +Enqlave | :P |
| 13:06 | @emrys | well we'll get started anyway and the other few can catch up |
| 13:07 | +ryuji | roger |
| 13:07 | @emrys | who wants to go first? |
| 13:07 | @BearPerson | I guess I can, don't have that much important stuff to say |
| 13:07 | @sandalle | emrys: yep, hear |
| 13:07 | @sandalle | here |
| 13:08 | @emrys | BearPerson: go for it |
| 13:08 | @BearPerson | okay |
| 13:08 | @BearPerson | from cauldron team, I guess the main report is that there's not much to report |
| 13:09 | @BearPerson | due to trouble with the iso generation being too complicated, we're scaling back to simpler installer schemes until we can get a regular release schedule underway again |
| 13:09 | @BearPerson | which brings me to an announcement of a new developer |
| 13:10 | @BearPerson | I'd like to grab this opportunity to intruduce flux_control, aka flux, secretly also known as Justin Boffemmyer, to the valley as a cauldron developer |
| 13:10 | @BearPerson | I yet have to sign his gpg key and set up git access, but I'll probably do that during the rest of the meeting |
| 13:10 | @BearPerson | he's been helping us out so far evaluating our current stuff, and checking how well it is usable by someone who didn't write it in the first place |
| 13:11 | @BearPerson | and my hopes are that he'll prove to be a valuable help in getting ISO's where they belong again, which is to say, out to release ;) |
| 13:12 | @BearPerson | and that, i guess, is mostly what I have to say. As soon as we can, we'll start releasing test ISO's with a really basic "installer", and work our way back to what we're used to from there. |
| 13:12 | @emrys | flux_control, do you have anything to add briefly about what specifically you've been working on? |
| 13:12 | +wich | made it a little late |
| 13:12 | * | sobukus notes that that moment in time would be a good motivation to prepare the alpha ISO, finally |
| 13:13 | +flux_control | emrys: I've been getting accustomed to the current cauldron setup, and working on rolling out a test ISO. If there aren't any further "bumps" for me, I think I should have the test ISO ready this week. |
| 13:15 | @emrys | sandalle, how about the grimoire? |
| 13:15 | @emrys | well, first |
| 13:15 | @emrys | questions for cauldron? |
| 13:15 | @sandalle | flux_control: How easy has it been to create an ISO? |
| 13:15 | +novaburst | Will the next cauldron version be .97? |
| 13:16 | @sandalle | and will it become easier? |
| 13:17 | @BearPerson | as for the iso version, we'll have to see if we call it 0.9.7 or 0.10.1 due to how much changed |
| 13:17 | +flux_control | sandalle: it takes a bit to get used to the current setup, and where everything is. But I have plans to greatly simplify much of that, particularly by having some systematic documentation for everything somewhere. |
| 13:17 | +ryuji | will there be a x64 iso? |
| 13:17 | @sandalle | flux_control: Thank you. :) |
| 13:17 | @BearPerson | I'll also need to dig through old stuff for release names that were suggested but never used |
| 13:17 | +Enqlave | yep, very interested about x64 |
| 13:17 | +novaburst | BearPerson: thank you |
| 13:18 | @BearPerson | We'll focus on i486 and pals as that's our basic install, but we'll do our best to get an x64 out there as well once we get things going again |
| 13:18 | +flux_control | I don't have an x64 box to devel on personally. BearPerson ? |
| 13:18 | @BearPerson | I do, and I think we can get our hands on a few others if needed |
| 13:18 | +ryuji | works for me. |
| 13:19 | * | sobukus has x64, too |
| 13:19 | +flux_control | good good :-) |
| 13:19 | * | mar_s offers his x86_64 machine, too |
| 13:19 | +sobukus | Thing is, that x86_64 is becoming very major |
| 13:20 | +_kaze_ | I plan to invest on a x86_64 box for christmas, I could test ISO if cauldron team wants |
| 13:20 | +ryuji | morfic was the one working on a ISO for x64 last time, it's quite OK, but needs work |
| 13:20 | +wich | how much has to be different for the 64 bit platform? is it just a basic matter of recompiling the packages and stuff for 64 and putting it in an iso, or does the whole setup need more changing, and have you look at what needs chaning? |
| 13:20 | @BearPerson | yes, I think once we get stuff going I'll post a ML announcement about x64 development, so anyone willing to help out will have their turn then :) |
| 13:21 | @emrys | anything else for cauldron? |
| 13:22 | @BearPerson | as for the differences, that'll just be stuff built for 64 bits and probably changing the installer/instructions a bit (I remember stuff about grub not building, or something) |
| 13:22 | +sobukus | boot loader is the main difference for arches, generally |
| 13:23 | * | emrys wonders why we're having half the meeting specifics in #sourcemage ;-P |
| 13:23 | @ruskie | because it's discussion not meeting stuff :) |
| 13:23 | @emrys | moving on, anyway |
| 13:23 | @emrys | sandalle you're up |
| 13:24 | @sandalle | wich: it's a small list of differences. Most of the packages have been patched to work for x86_64 |
| 13:24 | @sandalle | for grimoire our main changes lately have been new developers, which we've been getting quite a few of (relatively) lately. :) |
| 13:24 | @sandalle | I'm not sure where they find us, but I'm glad they do |
| 13:24 | @sandalle | our latest is Enqlave |
| 13:24 | -!- | Codex [i=stealth@unaffiliated/codex] has joined [#sourcemage-admin] |
| 13:25 | @sandalle | who's been a user for about 4 years or more |
| 13:25 | Codex | yep |
| 13:25 | @sandalle | We have a few issues on my team, mostly due to my lack of free time lately (moved 900mi): |
| 13:25 | * | Codex <- Enqlave's server a.k.a. Enqlave @ the kitchen |
| 13:25 | @sandalle | * Bugs are being submitted faster than they are being fixed |
| 13:25 | @sandalle | * Timelines are slipping (e.g. stable releases) |
| 13:26 | @sandalle | * Developer list is not being purged according to our policy |
| 13:26 | @sandalle | They are listed in order of what I think most important to least |
| 13:26 | @lynxlynxlynx | bug count is pretty stable |
| 13:26 | +_kaze_ | sandalle: maybe these are signs that the project grows quickly recently, maybe too quickly ? |
| 13:26 | @lynxlynxlynx | some 15 over the recent minimum, but that's not so bad |
| 13:26 | @sandalle | lynxlynxlynx: It might just be all my mail catching up to me, then, but I've seen a lot of new bugs and not as many fixes (feeling, not objective) |
| 13:27 | +ryuji | sandalle: I could provide you with help on the huntung for inactive developers, i did provide you with a tool to help in that iirc |
| 13:27 | @sandalle | The developer list will be easy to prune, I just need to take the time to do it. ryuji even gave me a script to help. ;) |
| 13:27 | @emrys | it's a git one liner to see who is inactive |
| 13:27 | @sandalle | ryuji: yes you did. :) |
| 13:27 | @lynxlynxlynx | sandalle: i always have a tab open with all the bug listing and follow the count ;) |
| 13:27 | @emrys | I haven't worried about it much because there aren't that many past the year |
| 13:27 | @emrys | if we move it down to 6 months like we're supposed to it will be more |
| 13:27 | @sandalle | lynxlynxlynx: :) |
| 13:28 | @sandalle | emrys: I thought it was 6 months for a Lead and 1 year for a dev? |
| 13:28 | @lynxlynxlynx | yep |
| 13:28 | @emrys | well, yes |
| 13:29 | @emrys | it should be 6 months for devs as long as that's not the same 6 months for a lead (so leads get 12 months before they're out entirely) |
| 13:29 | @emrys | anyway |
| 13:29 | @sandalle | the list I'm not too worried about either, it's just the easiest to fix |
| 13:29 | @emrys | hasn't affected votes yet |
| 13:29 | @sandalle | emrys: correct |
| 13:29 | @ruskie | someone needs to contact the idle ones to get their status(Unet for example will try to start contributing end of the month...) |
| 13:29 | @emrys | which is the only place it matters |
| 13:29 | @emrys | ruskie: talk is cheap :-) |
| 13:29 | @sandalle | for the timelines, I need to delegate to my assistants in a more timely fashion |
| 13:30 | @lynxlynxlynx | yeah! |
| 13:30 | @sandalle | rather than last minute |
| 13:30 | @ruskie | well if anyone doesn't mind I can do that bit... |
| 13:30 | @lynxlynxlynx | sandalle: it is not just about delegation, they are sentient beings |
| 13:30 | -!- | alley_cat [i=AlleyCat@sourcemage/elder/alleycat] has quit [Read error: 145 (Connection timed out)] |
| 13:30 | @lynxlynxlynx | i would expect some initiative from them |
| 13:30 | @sandalle | lynxlynxlynx: correct, but we don't want to have several people trying to tag a branch or push a tarball. ;) |
| 13:30 | @sandalle | and they've been busy as well |
| 13:31 | @sandalle | so I need to plan more. I had thought I'd have more free time than I do |
| 13:31 | @sandalle | which is part of the planning failure |
| 13:31 | @sandalle | ruskie: the delegation or being delegated to? |
| 13:31 | @ruskie | the contacting of idlers |
| 13:32 | @sandalle | ruskie: If you'd be so kind, please do. :) Thanks! |
| 13:32 | @ruskie | will do |
| 13:32 | @sandalle | To fix the timelines I wil be looking for volunteers much sooner (as in right after the prior release is done at the latest) |
| 13:32 | @emrys | it was mostly the latest one that was missed, right? |
| 13:33 | @sandalle | emrys: yes, but the one before, 0.14, I did at the last minute as well. ;? |
| 13:33 | @sandalle | So the last two have been a stretch |
| 13:33 | @sandalle | and we missed one |
| 13:33 | @sandalle | All my fault. :/ |
| 13:34 | @sandalle | I planned on a weekly hacking group to allocate time for SMGL, but we've had some delays in starting it |
| 13:34 | @sandalle | so perhaps I'll just set aside that evening for SMGL at home. :) |
| 13:34 | @sandalle | as for the bug list, I will be going through it to find outstanding bugs and point them out |
| 13:35 | @sandalle | I would like our bug count to decrease, rather than increase (or remain stable as lynxlynxlynx says it is :)) |
| 13:35 | @sandalle | or at least have feedback on the bugs so the user knows we're aware of it |
| 13:35 | @lynxlynxlynx | i can help there, i have a good overview of our bug infestation |
| 13:35 | @sandalle | I've heard complaints that bugs are filed then ignored |
| 13:36 | @sandalle | lynxlynxlynx: If you're already knee deep, please do |
| 13:36 | +ryuji | theres no helping that :/ |
| 13:36 | @sandalle | lynxlynxlynx: and thanks. :) |
| 13:36 | @lynxlynxlynx | for stable we need to revert/fix this hal/hal-info bug |
| 13:36 | @lynxlynxlynx | some integrations remain |
| 13:36 | @sandalle | ryuji: I'd at least like it to be Assigned or a comment saying "thanks, we'll look into it" so they have *some* feedback |
| 13:36 | @sandalle | lynxlynxlynx: I have a queue of security fixes to integrate |
| 13:36 | @lynxlynxlynx | or better said, requests for approval |
| 13:36 | @lynxlynxlynx | yeah |
| 13:36 | @sandalle | lynxlynxlynx: the hal/hal-info is only in test and stable-rc, correct? |
| 13:37 | @lynxlynxlynx | on this topic, i'd like to become a gatekeeper to facilitate things |
| 13:37 | @emrys | assigning things no one is actually working on is not wise, but telling them a human saw it isn't bad |
| 13:37 | @lynxlynxlynx | sandalle: yes |
| 13:37 | @sandalle | emrys: any objections for lynxlynxlynx? |
| 13:37 | @emrys | no |
| 13:37 | @sandalle | emrys: right, I didn't mean to Assign it willy-nilly. ;) |
| 13:37 | @sandalle | lynxlynxlynx: Thanks! :) I'll add you to the List. ;) |
| 13:38 | @sandalle | Any other comments/ideas for the bugs or releases? |
| 13:38 | +ryuji | lure more devs into being your minions |
| 13:39 | @lynxlynxlynx | it would be good to have more general folk |
| 13:39 | @emrys | all things considered I'm still happy with how stable grimoire releases have been relative to other things |
| 13:39 | @sandalle | ryuji: I've thought of that, but I see two problems (perhaps non-issues): |
| 13:39 | @lynxlynxlynx | but i think things are going well yeah |
| 13:39 | +abouter | lynxlynxlynx: more general folk with more free time |
| 13:39 | @sandalle | * I don't want to overload our long-term developers with more work |
| 13:39 | @sandalle | * I don't want to scare away new developers with too much work |
| 13:39 | +ryuji | voluntary work, man |
| 13:39 | @sandalle | so I'll need to ask nicely and check what I'm dishing out to whom |
| 13:40 | @sandalle | lynxlynxlynx: more general developers? I think the MagePower articles might be helping. :) |
| 13:40 | +ryuji | yeah, yeah. talk for another time :) |
| 13:40 | @sandalle | ryuji: yep. :) |
| 13:40 | @emrys | any more grimoire talk? |
| 13:40 | @sandalle | That reminds me of one last item |
| 13:40 | @lynxlynxlynx | sandalle: i meant it more in the fill-in-the-gaps sense |
| 13:40 | @sandalle | section developers |
| 13:40 | @sandalle | I would like to find more developers to take over a section, as some sections seem to get ignored |
| 13:41 | Codex | well, yea. we have some open sections for the maintainance |
| 13:41 | +wich | Would we perhaps want to do some active soliciting? over mailinglist or something? |
| 13:41 | @sandalle | while general devs pick up a few here and there, the section developers primary task is to check for bugs in that section and get them fixed |
| 13:41 | @lynxlynxlynx | <insert quill ad here> |
| 13:41 | @sandalle | wich: yes, I will be doing that. :) |
| 13:41 | @sandalle | lynxlynxlynx: I will also be mentioning that to make it easy |
| 13:41 | +ryuji | sandalle: sign me up for php-pear :P |
| 13:41 | @sandalle | but my main need for section devs is not updates per-se, but bug triage |
| 13:42 | @sandalle | ryuji: you have the power, go for it. ;) |
| 13:42 | +abouter | sandalle: e-type is still listed for windowmanagers, mind if i take on that one? |
| 13:42 | @sandalle | abouter: please do |
| 13:42 | @sandalle | feel free to ping me an e-mail if you'd like a section. :) |
| 13:42 | @sandalle | so we don't fill up the log with requests. ;) |
| 13:42 | +wich | bugs don't go to the maintainers directly anmore do they? |
| 13:42 | @sandalle | wich: nope, sm-grimoire-bugs |
| 13:43 | @sandalle | since about half the sections were unmaintained at one point |
| 13:43 | +wich | I think that might be too much for some people |
| 13:43 | @sandalle | emrys: That's all I have for grimoire |
| 13:43 | +abouter | i guess the size of some sections scares people from becoming maintainer |
| 13:43 | @emrys | sending them to maintainers directly is unworkable with the reality of how most of our people work |
| 13:43 | @lynxlynxlynx | as a last thing, I'd like to express some awe at our diligent grimoire updaters, especially treeve, lace and p3pilot! |
| 13:44 | +wich | I mean, I wouldn't mind taking care of i18n bugs, but I don't really have the time to wade through all bugreports in a list, and I always forget to search on a regular basis |
| 13:44 | @sandalle | wich: that's what I'd want a section maintainer to do. ;) |
| 13:44 | @sandalle | wich: you can setup a link that does the search for you |
| 13:44 | @emrys | bugs get lost entirely because people wander off and I end up with thousands of spams a day to maintainer addresses |
| 13:44 | @sandalle | wich: http://wiki.sourcemage.org/Stable-0.15 has an example of links for bug searches |
| 13:45 | @sandalle | emrys: I get those, too. ;) |
| 13:45 | -!- | alley_cat [i=AlleyCat@sourcemage/elder/alleycat] has joined [#sourcemage-admin] |
| 13:45 | -!- | mode/#sourcemage-admin [+o alley_cat] by ChanServ |
| 13:46 | +wich | sandalle: well, problem is I'd do that search a couple of times, but after a while I end up forgetting it |
| 13:46 | @emrys | wich: so write a cron job that runs it and mails you the results |
| 13:46 | @sandalle | lynxlynxlynx: yeah, they've been doing a lot of updates. :) |
| 13:47 | +wich | It would be nice if you could have some filter type thing in bugzilla which collects the bugs you are interested in and mails you whenever there is something in the filter, but then doesn't mail you again until after some time or after you've logged in and seen them, but I don't think bugzilla does that |
| 13:47 | @ruskie | we should first consider updating bugzilla... |
| 13:47 | @lynxlynxlynx | just check every so often |
| 13:48 | @ruskie | latest is 3.x something |
| 13:48 | +wich | Would a different bug system be better suited to our approach, are there any workable alternatives to bugzilla? |
| 13:48 | @lynxlynxlynx | if you want, i can ping you when i see a japanese bug |
| 13:48 | +wich | lynxlynxlynx: :) |
| 13:48 | @lynxlynxlynx | ruskie: i'd wait for dkowis ;) |
| 13:48 | @sandalle | qnr: :) |
| 13:48 | @emrys | when I move it to the other datacenter stuff should get updated if not before |
| 13:48 | @ruskie | wich, most of us like bugzilla |
| 13:49 | @emrys | but that means someone is finally going to have to make time to make sure the db update stuff all goes correctly |
| 13:49 | @emrys | anyway, this is going off topic from grimoire status |
| 13:49 | +flux_control | emrys: when does the move to the new data-center happen? |
| 13:50 | @emrys | when I have a day to spend out there building the box back |
| 13:50 | @ruskie | emrys, I belive sandalle already said he's done with grim details |
| 13:50 | @emrys | lynxlynxlynx? |
| 13:50 | @emrys | sorcery? |
| 13:51 | @lynxlynxlynx | not much news here |
| 13:51 | +sobukus | Is 1.14 coming? |
| 13:52 | @sandalle | lynxlynxlynx: I saw a new -rc :) |
| 13:52 | @iuso | lynxlynxlynx: anything happening with the transaction commit failure bug? |
| 13:52 | @lynxlynxlynx | a short progress report: devel received a few fixes, but not in the blocker category; the focus is still on the new stable and the wierd regression blocking it |
| 13:52 | @iuso | what's the weird regression? |
| 13:52 | @lynxlynxlynx | iuso: i'm investigating it now |
| 13:52 | @iuso | lynxlynxlynx: good to know, thanks |
| 13:53 | @lynxlynxlynx | that zlib trigger queue takes ages gap |
| 13:53 | Codex | i noticed it |
| 13:53 | @lynxlynxlynx | ... yes, test is basically the next stable, just waiting for a confirmation of the fix |
| 13:53 | @sandalle | lynxlynxlynx: You don't love that bug? |
| 13:54 | @lynxlynxlynx | then i will integrate a few of the changes from devel |
| 13:54 | @sandalle | I'm just glad someone else could reproduce it |
| 13:54 | @lynxlynxlynx | yep |
| 13:54 | @lynxlynxlynx | ... and then 1.14 gets all the attention |
| 13:54 | @iuso | i wish castfs would get some attention too |
| 13:55 | @lynxlynxlynx | this transaction commit failed isn't so troublesome, i rank the deletion of configs higher |
| 13:55 | @ruskie | yup |
| 13:55 | @lynxlynxlynx | and delve needs some basic docs and a plug and the end of cast |
| 13:55 | @lynxlynxlynx | err, confmeld |
| 13:55 | +sobukus | Especially, I heard something about castfs being re-developed again? |
| 13:55 | @lynxlynxlynx | sobukus: proof-of-concept is what i heard |
| 13:55 | @iuso | deletion of configs sure sounds like it's more serious. but the transaction commit bug regularily breaks casts for me |
| 13:56 | +sobukus | I am somewhat waiting for castfs being stable for the fixing of account handling (one of my loooong-term projects) |
| 13:56 | @iuso | sobukus: proof-of-concept thing that dmlb2000 plans to write in python to investigate the option |
| 13:56 | @emrys | why? |
| 13:56 | @lynxlynxlynx | ... and then it is time for a few tweaks and some cool stuff i can't wait to work on :) |
| 13:56 | +sobukus | iuso: but the current one not being challenged yet... |
| 13:57 | @iuso | sobukus: i don't thin kso |
| 13:57 | +sobukus | k |
| 13:58 | @iuso | current castfs has some memory handling issues, and dmlb2000 says it's due to the complexity of managing in-memory metadata |
| 13:58 | @iuso | at least that's how i understood it |
| 13:58 | @lynxlynxlynx | also, anmaster cleaned up half of the bashdoc pipeline and it now produces valid xhtml with css support |
| 13:58 | @lynxlynxlynx | so the goal of having the apis somewhere on the site is closer |
| 13:58 | +sobukus | goooood |
| 13:58 | @sandalle | lynxlynxlynx: nice. :) He still doesn't want to become a dev for us, though? |
| 13:59 | @emrys | we already have the bashdoc stuff on the site |
| 13:59 | @lynxlynxlynx | where? |
| 13:59 | @emrys | http://www.sourcemage.org/api/ |
| 13:59 | @lynxlynxlynx | sandalle: no |
| 13:59 | @lynxlynxlynx | emrys: the second half needs fixing though |
| 13:59 | @lynxlynxlynx | bashdoc is not linking well |
| 14:00 | @emrys | ok |
| 14:00 | @lynxlynxlynx | i'll start a repo to facilitate development |
| 14:00 | @lynxlynxlynx | wink wink |
| 14:00 | @emrys | I'm working on it right now |
| 14:00 | @lynxlynxlynx | when i can |
| 14:00 | @lynxlynxlynx | :) |
| 14:01 | @lynxlynxlynx | any questions? |
| 14:02 | * | sandalle has none |
| 14:02 | +ryuji | not from me |
| 14:03 | @lynxlynxlynx | any help is of course welcome |
| 14:03 | @emrys | ok, we lack a tome lead, but some people have been working on stuff there...let's here from some of them, briefly |
| 14:03 | @sandalle | lynxlynxlynx: on the open bugs, testing, or both? |
| 14:04 | @lynxlynxlynx | all of that plus development |
| 14:04 | @lynxlynxlynx | if you want a particular feature, no need to wait for 1.14 to unfreeze |
| 14:05 | +eekee | I'm wondering if it might help to promote smgl a bit, to get more devs, an maybe some users that might fix a few bugs |
| 14:05 | @lynxlynxlynx | eekee: it does and it did :) |
| 14:05 | +eekee | ok ^^ |
| 14:06 | @lynxlynxlynx | so, what's up with the website |
| 14:06 | @emrys | ruskie has been doing something with getting everything back on the wiki |
| 14:06 | @lynxlynxlynx | eekee was involved with the drupalish theme for the wiki |
| 14:06 | @emrys | eekee made a theme |
| 14:06 | @emrys | which currently is the default but I haven't moved all the old users over to it yet |
| 14:06 | @emrys | there were a couple issues someone should look at |
| 14:07 | @lynxlynxlynx | is a wiki upgrade planned like the bugzilla? |
| 14:08 | @emrys | lynxlynxlynx: yes |
| 14:08 | @emrys | that one might happen sooner if I get a chance for it |
| 14:08 | @emrys | ruskie, anything to say? |
| 14:08 | @emrys | about the wiki work? |
| 14:09 | @lynxlynxlynx | for things like categorisation it would be easier if we could sed a few pages |
| 14:09 | @lynxlynxlynx | but i don't know if moinmoin would like that |
| 14:09 | @emrys | it better |
| 14:09 | @lynxlynxlynx | :) |
| 14:09 | @emrys | I've edited moinmoin files from the shell before |
| 14:10 | @emrys | so anyway, yes, we're probably close to being able to turn drupal off |
| 14:10 | @lynxlynxlynx | no borked history? |
| 14:10 | @lynxlynxlynx | wiki spam is also a problem |
| 14:10 | @emrys | the main hole is always the forums, which hardly really get any use, but should get replaced with something that links to the sm-users list |
| 14:10 | @BearPerson | I initially created the moinmoin setup from a sql dump, but I didn't worry about history back then |
| 14:10 | @emrys | I'm not concerned about that happening before we move back to the wiki, it doesn't need to hold it up |
| 14:11 | -!- | Phoul [i=AOS@sourcemage/guru/Phoul] has joined [#sourcemage-admin] |
| 14:11 | -!- | mode/#sourcemage-admin [+v Phoul] by ChanServ |
| 14:11 | +eekee | do we need the forums at all? |
| 14:11 | @lynxlynxlynx | people like them |
| 14:11 | +eekee | ya.. ok |
| 14:11 | @iuso | i need to leave soon, i'm at my girlfriend's parents and they all need my attention too :) |
| 14:11 | @lynxlynxlynx | and there is software for intertwining a forum with a ml |
| 14:11 | @emrys | we may as well offer forums as a way to interact with the ml but they can go away for a while as far as I'm concerned |
| 14:11 | +ryuji | lynxlynxlynx: fudforum is one |
| 14:11 | +novaburst | some users complain and don't want to sign up for a mailing list to post a quick question, so the forum is good for them. |
| 14:11 | @emrys | they aren't worth the security hole of running drupal |
| 14:11 | @lynxlynxlynx | iuso: anything to say? |
| 14:12 | * | eekee acknowledges novaburst's point |
| 14:12 | @iuso | lynxlynxlynx: not really after the sorcery stuff has been discussed |
| 14:13 | @iuso | lynxlynxlynx: though i'd like to see our package files' list updated |
| 14:13 | @lynxlynxlynx | the what? |
| 14:13 | @iuso | the one you can query scry with .from |
| 14:13 | @iuso | the files that spells install |
| 14:13 | @iuso | it'd come in handy with my recent pkgconfig patch |
| 14:14 | @lynxlynxlynx | send them to scry, you can upload via the webterface |
| 14:14 | @lynxlynxlynx | and if that doesn't handle a lot of input good, ask odin to fix it |
| 14:15 | @lynxlynxlynx | but this is a bit off-topic |
| 14:15 | @iuso |