krytarik | knome: Also, would you be fine with "Common Tasks", rather than "How to..."? | 00:05 |
---|---|---|
knome | mmmmmh. | 00:07 |
knome | maybe. | 00:07 |
knome | the current title isn't meant to be final | 00:07 |
krytarik | Yeah, just looks and feels weird. | 00:09 |
krytarik | knome: "<para>Bazaar is a version control system and is commonly referred to as Bzr.</para>" - what should I use for "Bzr" there? I see that flocculant uses '<emphasis>' for the QA docs, but that also makes the text bold. | 00:17 |
knome | hmm. | 00:18 |
knome | <application>? | 00:18 |
knome | makes it bold too, but meh | 00:18 |
krytarik | Also, was that a "Yes, meh, go ahead."? :P | 00:18 |
knome | i would probably put this inside a <note> | 00:19 |
knome | i think <app is better | 00:19 |
krytarik | Isn't that a bit too much? | 00:19 |
knome | nah, it's fine | 00:19 |
knome | it's not a section you are likely to read over and over again | 00:19 |
knome | at least from the beginning to the end | 00:19 |
krytarik | Alright, I'll do as you suggested then. | 00:20 |
krytarik | Just to be clear, that's on the top just under the "Bazaar" header. | 00:21 |
knome | yep | 00:21 |
knome | also, what about calling the howto section "Reference" ? | 00:21 |
krytarik | Hmm. | 00:21 |
krytarik | Well, I can just leave that to you for later. :P | 00:22 |
krytarik | Seriously though, I guess that'd be still be than "How to". :D | 00:25 |
krytarik | - be | 00:25 |
krytarik | "Common Reference" at least? | 00:26 |
knome | wfm | 00:26 |
krytarik | Alright. | 00:27 |
krytarik | knome: Fine if I rename "processes-release-cycle.xml" to just "release-cycle.xml", consistent to its title and HTML file name? | 01:16 |
knome | the filename is referring to a potential structure for the docs, so let's keep it as it is for now | 01:20 |
krytarik | Alright. | 01:20 |
* krytarik reverts | 01:20 | |
knome | time to go to bed | 01:21 |
knome | thanks for all the work :) | 01:21 |
krytarik | Well. :D | 01:22 |
krytarik | And night. | 01:22 |
knome | ttyl -> | 01:22 |
krytarik | And if no one wants to beat me to it, I might include command line instructions for the MP part. | 01:36 |
=== mhall119 is now known as mhall119|fossetc | ||
krytarik | (Done.) | 05:53 |
krytarik | flocculant: This is just for again now, updated: http://paste.openstack.org/show/E3wgCHbwYFoQRZcJrpKf/ | 06:01 |
flocculant | krytarik - "tell me if you're fine with the some additional changes" can't tell the difference between green, darker green, pink, darker pink, if something changed, what changed on that pastebin thing - so no. | 07:38 |
flocculant | really can't see what's going on with the light green/pink stuff :( | 08:26 |
flocculant | I find MPs a whole lot easier to read :) | 08:31 |
knome | flocculant, actually, i find the pastebin better to read than the MPs in most of the places | 12:27 |
knome | flocculant, glossary: | 12:27 |
knome | flocculant, light pink -> line that has been changed or removed | 12:27 |
knome | flocculant, light green -> line that has been changed (the new version) or added | 12:28 |
knome | these are basically the pink/green colors of MP | 12:28 |
knome | flocculant, the dark pink/green areas highlight the spot in the line(s) that has been changed | 12:28 |
knome | flocculant, so you don't exactly have to review the whole line | 12:28 |
flocculant | krytarik - mmm actually what's "bzr commit --fixes" about and why the need to change that? Given that none of anything else I've read requires that | 12:49 |
flocculant | knome: but what about lines where there's no dark pink/green | 12:49 |
knome | flocculant, context, like in the MP | 12:49 |
flocculant | anyway - whatever - when there's actually an MP for it - I'll look then properly | 12:49 |
flocculant | knome: this is what's confusing me then - because there are at least 2 cases where there are changes and no dark green/red | 12:51 |
knome | yeah :) | 12:51 |
flocculant | anyway - whatever - when there's actually an MP for it - I'll look then properly :) | 12:51 |
knome | yep | 12:51 |
flocculant | until I see that I'm not approving anything from my side | 12:51 |
knome | lol | 12:52 |
flocculant | obviously I don't care about the <!Entity stuff :) | 12:59 |
knome | yeah | 13:00 |
flocculant | too care about that I'd need an explanation of something that I don't care to know about :p | 13:01 |
krytarik | flocculant: "this is what's confusing me then - because there are a | 15:47 |
krytarik | t least 2 cases where there are changes and no dark green/red" - yeah, those are the annoying cases where it doesn't figure out what really changed, for some reason. :P | 15:47 |
krytarik | Bleh. | 15:47 |
krytarik | Also, the '--fixes' option for commits should set the referred bug report status to 'Fix Committed' automatically, while for the MP it just links it to the bug report - as mentioned in both text parts. | 15:51 |
krytarik | flocculant: And of course, I didn't do any *factual* changes, only DocBook syntax, link anchor texts as mentioned before, consistency, wording, and typos. | 15:56 |
slickymasterWork | krytarik, did you push the MP yet? | 16:01 |
krytarik | Well, the bug status is only changed when the concerning commit is merged into the main branch, of course - and for no packages it should be set to 'Fix Released' then immediately. | 16:02 |
krytarik | slickymasterWork: Nope, just started the day. :P | 16:03 |
slickymasterWork | good life :P | 16:03 |
krytarik | Well, 3 hours ago, but... :D | 16:03 |
krytarik | Also, just doing some minor improvements on my yesterday's changes/additions. | 16:05 |
slickymasterWork | drop a link after you made them, please | 16:06 |
krytarik | Also, I have no particular idea yet how to include all the recent stuff in the commit message, or changelog even. :P | 16:07 |
krytarik | slickymasterWork: Nope, I'm never dropping a link to you! :D | 16:07 |
slickymasterWork | whatever | 16:07 |
* krytarik pats slickymasterWork | 16:07 | |
slickymasterWork | :P | 16:08 |
flocculant | krytarik: ok - so with --fixes definitely don't want to use that | 17:14 |
krytarik | flocculant: Umm, I don't get it. | 17:14 |
flocculant | "And of course, I didn't do any *factual* changes," yes you did ^^ | 17:14 |
krytarik | Where? | 17:14 |
flocculant | please leave that bzr line as I had it - thanks | 17:15 |
krytarik | *Changes*. | 17:15 |
flocculant | ^^ | 17:15 |
flocculant | other than that - the rest is fine with me once I'd fought my way through the pink and green :) | 17:15 |
krytarik | Heh, alright. | 17:16 |
krytarik | flocculant: So, you aren't fixing the bug you just reported with the changes you are doing? | 17:18 |
flocculant | krytarik: there is a reason - pretty much pointless marking it Commited - nothing really happens to anything until someone physically edits the tracker side - at that point it's immediately fix released | 17:18 |
krytarik | Alright - so for you, it's just not 'needed'. | 17:19 |
flocculant | so all that marking them committed does is annoy me with pointless LP messages as I'm subscribed to it - as it's more or less me dealing with it | 17:19 |
flocculant | krytarik: not interested in a discussion on it - please lose that change in my qa docs ;) | 17:19 |
flocculant | but thanks for all the other bits and bobs - helps the readability :) | 17:22 |
krytarik | \o/ | 17:22 |
flocculant | ha ha | 17:23 |
flocculant | it's always useful for someone else to read things - you never 'read' what you wrote, you 'read' what you think you wrote :) | 17:23 |
flocculant | krytarik: and ftr - nice to know about --fixes, just doesn't really do much more than spam mailboxes in this particular thing | 17:24 |
krytarik | Well, you can read it, but extra work. :P | 17:24 |
krytarik | So, I have 'bzr commit -m "Fix LP bug #BUGNO."' now - fine? | 17:25 |
flocculant | no idea - if that's what it said before then yep :) | 17:26 |
krytarik | Well, it says 'bzr commit -m "Change re bug#' right now. | 17:28 |
flocculant | ok - happy with that newer wording :) | 17:28 |
krytarik | \o/ again. | 17:29 |
flocculant | it was the " those are the annoying cases where it doesn't figure out what really changed" which completely threw me :) | 17:29 |
krytarik | Yeah, like I said, it's annoying. :D | 17:30 |
flocculant | yep | 17:30 |
krytarik | I might try and use a plain one the next time then. :P | 17:30 |
flocculant | hah | 17:30 |
flocculant | well others like it that way - so don't change on my behalf ;) | 17:31 |
flocculant | I found that if I pretended to reply it sorted those things out | 17:31 |
krytarik | Yeah, it kind of worked. :D | 17:34 |
krytarik | Added the '--fixes' part to the Common Reference now instead. | 17:37 |
flocculant | ok - that's probably useful stuff | 17:39 |
flocculant | ochosi: jenkins is getting closer for the image tests | 18:30 |
krytarik | flocculant: And sorry, I was more thinking there of how I'm mentioning the '--fixes' option in the MP part of the Common Reference - that was a factual change indeed. | 18:47 |
flocculant | krytarik: yea understand that - but Common Reference isn't something I'm too bothered about :) | 18:48 |
krytarik | You mean not? :D | 18:48 |
krytarik | Oh wait, no. :P | 18:49 |
flocculant | no - I mean what I said :D | 18:49 |
flocculant | :) | 18:49 |
flocculant | the QA pages isn't something I'm not too bothered about :D | 18:49 |
krytarik | Hence I didn't think of having changed the command there, that is. | 18:50 |
flocculant | :) | 18:50 |
krytarik | hahaha | 18:50 |
krytarik | flocculant: Noticed what I did with the <para>'s there though? | 18:52 |
flocculant | ish | 18:52 |
flocculant | no - not really | 18:53 |
flocculant | if I was to be more honest :p | 18:53 |
krytarik | That is, rather than enclosing lists and such, just end it where the current paragraph ends. | 18:54 |
flocculant | yea sort of noticed | 18:54 |
flocculant | but as I'm unlikely to be doing much more didn't do more than *shrug* don't know why that is :) | 18:55 |
krytarik | It was fine on the other two pages though. | 18:56 |
sidi | is there any known problem with the lock screen on Xubuntu Trusty? keeps tellng me "This session is locked, youll be redirected bla bla" on my Trusty VM after I unlock the session | 19:40 |
knome | sidi, you should know better that this is no support channel | 20:52 |
flocculant | ochosi: so is this a gtk3 fail? http://i.imgur.com/1KLCHmU.png | 21:56 |
flocculant | guessing so - got some updates for it today | 21:57 |
Unit193 | Go to GTK3 they said, it'll be better they said... | 21:58 |
flocculant | :) | 21:58 |
flocculant | I'd report it if I knew which one out of thousands to report it against ... | 21:59 |
flocculant | calc is awesome :p http://i.imgur.com/guBwH2V.png | 22:00 |
krytarik | flocculant: How about 'gtk+3.0'? | 22:01 |
Unit193 | Unless, the theme... | 22:02 |
flocculant | http://i.imgur.com/eWl3d8R.png | 22:03 |
flocculant | calc in numix | 22:03 |
flocculant | adwaita it's the same as greybird | 22:04 |
flocculant | krytarik: can't ubuntu-bug gtk3.0 | 22:05 |
krytarik | flocculant: With the plus even? | 22:06 |
flocculant | nope | 22:06 |
pleia2 | knome: if you have some time this afternoon, I'm around | 22:08 |
knome | pleia2, "afternoon"? | 22:10 |
flocculant | :) | 22:10 |
pleia2 | knome: well, whatever time it is right now :) | 22:12 |
knome | just past midnight | 22:13 |
knome | but i'm here | 22:13 |
pleia2 | what are we supposed to talk about? | 22:13 |
knome | lol | 22:13 |
knome | wait, i'll untangle my headphones first | 22:14 |
knome | ok | 22:14 |
knome | so, i guess the first thing is getting the contributor docs live/online | 22:15 |
pleia2 | ok | 22:15 |
knome | they are in the docs branch | 22:15 |
knome | we don't have a completely workflow yet for that | 22:15 |
* pleia2 updates local copy | 22:15 | |
knome | +ready | 22:15 |
knome | but krytarik is working on some last fixes for some of the issues | 22:15 |
knome | one question i have | 22:16 |
knome | as they are in the same branch/package as the regular docs, they are "release-specific" - even if they aren't | 22:16 |
pleia2 | which branch? | 22:16 |
knome | lp:xubuntu-docs | 22:16 |
pleia2 | i mean, not like wily/ | 22:16 |
knome | ^ that's xenial | 22:16 |
knome | so the newest | 22:16 |
pleia2 | k | 22:17 |
knome | the wily branch has outdated stuff already | 22:17 |
knome | one of the cons of having them in the same branch | 22:17 |
pleia2 | yeah | 22:17 |
knome | otoh, this way we can share the build stuff | 22:17 |
knome | and stylesheets | 22:17 |
knome | and everything docbook | 22:17 |
* pleia2 nods | 22:17 | |
knome | and only have to maintain one set of that | 22:17 |
knome | so, the question: | 22:17 |
knome | do we want to set up the online docs startpage so that we have a link, that we manually update, that points to the newest contributor docs? | 22:18 |
pleia2 | different from the index of docs.x.o itself? | 22:19 |
knome | or - my preferred option - do we set up the Makefiles so that you can build the newest contributor docs directly in a subdirectory | 22:19 |
knome | no, that thing | 22:19 |
knome | my vision is that the contributor docs would be at http://docs.xubuntu.org/contributors/ | 22:19 |
knome | but obviously feel free to disagree | 22:19 |
knome | maybe if we have more stuff coming for developers, we could consider another location too | 22:19 |
pleia2 | so, speaking to my own process, whenever I build docs I do it locally (build tools are local, not on the webserver) and then upload what I need | 22:19 |
knome | ok | 22:20 |
pleia2 | so as long as I have instructions about how to build and what to upload, I don't really mind where we put things | 22:20 |
knome | well, actually | 22:20 |
knome | one option is this: | 22:20 |
knome | set up another subdomain, like contributors.xubuntu.org (or whatever), host it on the same server as the tracker | 22:20 |
knome | then the maintaining burden can be shared | 22:20 |
pleia2 | I think docs.x.o makes more sense | 22:21 |
knome | yeah | 22:21 |
knome | in that case, on the building quickly: | 22:21 |
knome | "make" | 22:21 |
pleia2 | :) | 22:21 |
knome | then see build/contributor-docs | 22:21 |
pleia2 | so, just what I do for the regular docs | 22:22 |
knome | that's currently skewed - we need the stuff from krytarik before we are ready to "just do it" | 22:22 |
knome | basically so | 22:22 |
knome | the main change we are making is that both of the docs have the same depth | 22:22 |
pleia2 | right | 22:22 |
knome | so that ../../libs-common is always the same place | 22:22 |
knome | this helps us build the contributor docs in the shipped package too | 22:23 |
knome | but that's kind of minutiae | 22:23 |
knome | once krytarik has done the merge proposal, and the stuff is merged, we'd like an initial push ASAP | 22:23 |
knome | so we can start ripping the wiki stuff down | 22:23 |
knome | and make the website more user-oriented again (and just link to this documentation) | 22:24 |
pleia2 | I'm home through Tuesday of next week (fly out for the holiday on Wednesday), back on Nov 30 | 22:24 |
knome | we should have it up by then | 22:25 |
knome | that is, tuesday | 22:25 |
pleia2 | ok, just lmk and I'll make time :) | 22:25 |
knome | related: https://wiki.ubuntu.com/Xubuntu/DeveloperDocumentation | 22:25 |
knome | basically, i'm trying to make most of the wiki useless :P | 22:25 |
knome | not all, but most of it | 22:25 |
knome | i've even ACK'd moving the strategy document there by simon | 22:26 |
pleia2 | reminds me, https://wiki.ubuntu.com/Artwork/Official#Xubuntu | 22:26 |
knome | then we can have history and sensible diff's | 22:26 |
pleia2 | link should be updated | 22:26 |
knome | i'll do that | 22:26 |
pleia2 | thanks | 22:26 |
knome | so, anything else on this subject? | 22:26 |
pleia2 | DD wiki page lgtm | 22:27 |
pleia2 | I think that's it | 22:27 |
knome | great, we'll poke you when we need an upload | 22:27 |
pleia2 | perfect | 22:27 |
knome | so the other thing is basically "plan/set up blueprints for community/marketing/website" | 22:27 |
knome | and i guess we could talk about that sticker giveaway idea for twitter | 22:28 |
knome | and get it done | 22:28 |
* pleia2 nods | 22:28 | |
knome | and with that, other potential social media campaigns | 22:28 |
knome | could be nice to do one giveaway for every biggish outlet | 22:29 |
pleia2 | outlet, social media platform? | 22:29 |
knome | yeah | 22:29 |
knome | shorter | 22:29 |
knome | <- lazy | 22:29 |
pleia2 | hehe | 22:29 |
pleia2 | yeah, would be nice to do stuff for the lts | 22:29 |
knome | maybe G+, twitter, fb | 22:29 |
knome | so the question is: | 22:30 |
pleia2 | right | 22:30 |
knome | what do we do with the xubuntu memories or whatever we ask | 22:30 |
pleia2 | or #loveXubuntu | 22:30 |
knome | it could be with that | 22:30 |
pleia2 | I'm inclined to collect our favorites in a series of blog posts | 22:30 |
knome | yes, something like that | 22:31 |
pleia2 | I'd also like to collect a bunch of favorites, and then do a random drawing of which gets a prize | 22:31 |
knome | but we need an approval from the participants | 22:31 |
pleia2 | to share? | 22:31 |
knome | well at least from those who "win" | 22:31 |
* pleia2 nods | 22:31 | |
knome | yeah | 22:31 |
knome | i'd think it would be fair | 22:31 |
knome | also, | 22:32 |
knome | if we do this, just collect any ones that we might want to use | 22:32 |
pleia2 | we can just request that they write "CC BY-SA" on whatever they submit | 22:32 |
knome | and ask for permission to use in "any marketing for xubuntu" | 22:32 |
knome | so we can use them later | 22:32 |
pleia2 | otherwise it's not eligible | 22:32 |
knome | without the need to ask/collect again | 22:32 |
knome | i'm thinking flyers too | 22:32 |
pleia2 | yeah, that's why a license is nice | 22:32 |
knome | yes, wfm | 22:32 |
knome | so, should this be a blog article after all? | 22:33 |
pleia2 | which bit? :) | 22:33 |
knome | the "competition" info | 22:33 |
knome | tell what we do, ask for the CC bit, etc. | 22:33 |
pleia2 | yeah, probably | 22:33 |
knome | we should probably also mention which platforms we are looking at | 22:33 |
knome | and if we take submissions via email | 22:34 |
knome | (and in which list/address) | 22:34 |
pleia2 | my inclination is to ignore facebook because it's so closed | 22:34 |
pleia2 | you can view tweets and g+ things without logging in, not so with facebook | 22:34 |
knome | yeah... | 22:34 |
knome | http://pad.ubuntu.com/lovexubuntu | 22:34 |
knome | let's try to get something there | 22:34 |
pleia2 | ok | 22:35 |
pleia2 | hee, look at all that content so far | 22:35 |
knome | well... i just created it | 22:35 |
knome | we have some old pad with some content | 22:35 |
pleia2 | yeah, I thought we did | 22:35 |
knome | i'll try to find that next | 22:35 |
pleia2 | I have it, sec | 22:35 |
* pleia2 lies | 22:36 | |
knome | i have it | 22:37 |
knome | http://pad.ubuntu.com/Nl1LbS6DqL | 22:37 |
knome | i'm copying that over | 22:37 |
knome | sec | 22:37 |
pleia2 | great name | 22:37 |
pleia2 | :D | 22:37 |
knome | done | 22:37 |
pleia2 | thanks | 22:37 |
knome | yes, isn't it | 22:37 |
pleia2 | ok, I need to reprocess this, I'll work to add notes over the next few days | 22:38 |
pleia2 | but lets add doing this to our blueprint | 22:38 |
* pleia2 pulls up | 22:38 | |
knome | yeah, i'm quickly trying to add the things we just talked about so there's something to build on | 22:39 |
knome | yeah... | 22:40 |
knome | now, talking about BP's | 22:40 |
knome | is there something else we want to set up for 16.04? | 22:41 |
pleia2 | flyer, lovexubuntu and continuing "xubuntu at" may be enough | 22:42 |
knome | kind of related, how do *you* feel about a wallpaper contest? | 22:42 |
pleia2 | oh, we should do one | 22:43 |
knome | ok | 22:43 |
knome | i should write mail about it | 22:43 |
pleia2 | we learned some things from last time | 22:43 |
knome | but laaazyyy | 22:43 |
pleia2 | should recommend resolution, license | 22:43 |
knome | we remembered license | 22:43 |
knome | but people... | 22:43 |
pleia2 | we collected on a wiki page last time, right? | 22:43 |
knome | yes | 22:43 |
pleia2 | that was kind of awful | 22:43 |
pleia2 | ubuntu uses flickr | 22:43 |
knome | and we kind of recommended resolution too, at least we had a minimum | 22:44 |
knome | but people.. | 22:44 |
pleia2 | heh, right | 22:44 |
knome | bluesabre said he'd look at creating a tool for us | 22:44 |
pleia2 | even better :) | 22:44 |
knome | so, since you are our legal expert | 22:44 |
pleia2 | that's a frightening statement | 22:45 |
pleia2 | :) | 22:45 |
knome | if a form says with BIG RED letters | 22:46 |
pleia2 | that's purple | 22:46 |
knome | whatever | 22:46 |
pleia2 | hehe | 22:46 |
knome | that if you submit, you submit with a certain license | 22:46 |
knome | is that good enough? | 22:46 |
pleia2 | I radio button would be better, even if it's default selected what we want | 22:46 |
knome | because surely bluesabre can make the tool autocheck the resolution | 22:47 |
knome | radio button with what alternatives? | 22:47 |
pleia2 | or maybe just a checkbox saying they agree to our TOS | 22:48 |
knome | yeah | 22:48 |
pleia2 | which is... agreeing to the license | 22:48 |
knome | hehe | 22:48 |
knome | and no titties | 22:48 |
knome | :| | 22:48 |
pleia2 | agree to license, abide by CoC | 22:48 |
knome | yes | 22:48 |
knome | whatever terms we had the last time | 22:48 |
pleia2 | we can work on the language for that | 22:48 |
pleia2 | yeah | 22:48 |
knome | sounds good | 22:48 |
knome | do we want to work with this: | 22:49 |
knome | [xubuntu-website] Community fund funded hosting for the development area: TODO | 22:49 |
pleia2 | that just made my brain explode | 22:49 |
knome | sorry :( | 22:49 |
pleia2 | what's the development area? | 22:49 |
knome | currently, the tracker | 22:50 |
knome | and i would like to set up a wiki too... | 22:50 |
pleia2 | ah yes, I hate wiki | 22:50 |
pleia2 | hehe | 22:50 |
pleia2 | (hosting them) | 22:50 |
knome | heh | 22:50 |
Unit193 | doku isn't so bad if you need smaller. | 22:51 |
knome | yeah, i was trying to remember the name | 22:51 |
pleia2 | upgrade management, spam/user authentication handling, it sucks | 22:51 |
knome | i would most likely go with dokuwiki, it's relatively easy to maintain | 22:51 |
Unit193 | Sean and I both use it. | 22:51 |
knome | and i've used it | 22:51 |
knome | we could probably look at having multiple admins for the server | 22:52 |
knome | virtual, likely | 22:52 |
pleia2 | definitely | 22:52 |
knome | so it wouldn't be that bad | 22:52 |
knome | bluesabre already needs to handle dokuwiki updates | 22:52 |
knome | and Unit193 already pokes him about them | 22:52 |
knome | soooo... | 22:52 |
bluesabre | oh | 22:52 |
bluesabre | is there another update? | 22:52 |
bluesabre | :o | 22:52 |
knome | i don't know | 22:52 |
bluesabre | :D | 22:53 |
knome | we're talking about setting one for xubuntu | 22:53 |
bluesabre | gotcha | 22:53 |
bluesabre | dokuwiki is nice | 22:53 |
knome | i'm also familiar enough with the theming so i could probably set up a sensible xubuntu-specific theme relatively quickly | 22:53 |
bluesabre | No update notification, phew | 22:53 |
knome | but i don't want to push people to do things they don't want | 22:54 |
knome | so if it isn't realistic to have time/motivation for that, then we just postpone | 22:54 |
knome | or rethink stuff | 22:54 |
knome | the ubuntu wiki has been horrible lately :( | 22:54 |
Unit193 | bluesabre: No you're good. | 22:54 |
knome | previously it has been just everybody else that has had problems with it | 22:55 |
knome | now i've been in problems too | 22:55 |
knome | brb | 22:55 |
pleia2 | anyway, that action item sounds fine, I'm ok with being lead sysadmin on such a server as long as I have help with the service specific things | 22:56 |
knome | totally | 22:57 |
knome | and ideally, we'd move docs. and static. there too | 22:57 |
knome | so you would have less work in keeping them updated | 22:58 |
pleia2 | ++ | 22:58 |
pleia2 | having me not the only one with access would be great | 22:58 |
knome | (and it would all be smoother, the doc team could poke whichever admin is available) | 22:58 |
knome | and with a virtual server, we can probably dump some scripts server side | 22:58 |
* knome hides from pleia2 and the rolling pin | 22:59 | |
pleia2 | well, we could install all the doc build tools, as long as they'll work on the lts | 22:59 |
knome | they should | 22:59 |
knome | and will, really | 22:59 |
knome | i can preliminary volunteer on taking care of some of the social side | 23:00 |
pleia2 | https://www.linode.com/pricing is my recommendation | 23:00 |
pleia2 | probably the 2G one if we're running a wiki | 23:00 |
knome | mhm | 23:00 |
pleia2 | but 1G is probably ok too, I've not done doku | 23:00 |
knome | though note that it's low-use | 23:00 |
knome | doku is very light | 23:00 |
pleia2 | what is it written in? | 23:01 |
knome | and really, we won't have more than a few dozen pages | 23:01 |
pleia2 | yeah | 23:01 |
knome | guess? | 23:01 |
Unit193 | pleia2: You mean you're not on the DO bandwagon? | 23:01 |
pleia2 | Unit193: DO? | 23:01 |
Unit193 | DigitalOcean. | 23:02 |
pleia2 | knome: ah, php | 23:02 |
knome | pleia2, yeah :) | 23:02 |
pleia2 | Unit193: heh, no | 23:02 |
knome | i'm ok with *any* hosting | 23:02 |
pleia2 | Unit193: if they're more stable now, that's fine too | 23:02 |
knome | i *really* couldn't care less :] | 23:02 |
Unit193 | pleia2: From what I hear they are better, but yeah. | 23:02 |
knome | well that is, as long as it works etc... | 23:02 |
knome | but no clicks for/against any provider | 23:02 |
pleia2 | could also approach my buddy at gandi to see if they want to give us one | 23:03 |
knome | \o/ | 23:03 |
pleia2 | actually, let me email her right now | 23:03 |
knome | as long as that doesn't mean 1000x600 ads on every page ;)) | 23:03 |
knome | woohoo | 23:03 |
Unit193 | So you're going with Gentoo right? | 23:03 |
pleia2 | knome: can you add the item to the blueprint? | 23:04 |
knome | which exactly? | 23:04 |
knome | the one i pasted is *on* the blueprint | 23:04 |
knome | it was carried on from W | 23:04 |
pleia2 | nm, it's there | 23:04 |
pleia2 | yeah :) | 23:04 |
knome | haha | 23:04 |
knome | yep | 23:04 |
knome | we can split it up when we have a clearer idea of smaller actionable items | 23:04 |
pleia2 | opposed to a text footer on pages saying it's hosted by gandi? | 23:06 |
pleia2 | (it's ok to say yes) | 23:06 |
knome | it's not ideal, and i would personally say no, but we should consult simon too | 23:06 |
knome | i mean, when i say "no", i mean "yes" to opposing | 23:07 |
* knome sighs | 23:07 | |
knome | but "no" for the ads... | 23:07 |
knome | also, that would likely mean we'd need to change stuff | 23:08 |
pleia2 | right | 23:08 |
knome | think: add the footer note in the docs source | 23:08 |
knome | which is a bit icky | 23:08 |
knome | pleia2, oh, another thing to talk about: saw the -contacts mail? | 23:09 |
pleia2 | gabor? | 23:10 |
knome | yes | 23:10 |
pleia2 | yeah, I think it's a fine idea | 23:10 |
knome | ok, then i'll approve the message and reply him telling that | 23:10 |
pleia2 | hanks | 23:10 |
pleia2 | thanks too | 23:10 |
knome | t. hanks | 23:11 |
knome | (^tom) | 23:11 |
pleia2 | har | 23:11 |
pleia2 | ok, request has been emailed | 23:13 |
knome | ok, replied to gabor (and CC list) | 23:18 |
pleia2 | ty | 23:18 |
knome | so... anything else for the blueprints? | 23:19 |
knome | any improvements you would like to see re: the release pages on the website? | 23:20 |
pleia2 | I'm good | 23:20 |
knome | hmm, am i not autoapproved | 23:20 |
knome | sigh | 23:20 |
pleia2 | hee | 23:20 |
knome | i am | 23:20 |
knome | the list just sends the email anyway | 23:20 |
knome | i guess i'm done then with stuff for now :) | 23:23 |
knome | thanks | 23:23 |
pleia2 | thanks ;) | 23:23 |
knome | updated the artwork wikipage | 23:24 |
pleia2 | cool | 23:24 |
knome | oh heh, i've broken the resources page | 23:25 |
pleia2 | gg | 23:25 |
knome | will go fix that next | 23:25 |
knome | aaand done | 23:27 |
knome | alexkuck, hello | 23:32 |
alexkuck | knome: hello. how are you ? | 23:33 |
knome | i'm fine | 23:33 |
knome | looking for something? :) | 23:33 |
alexkuck | nope ! i am just a silent lurker.. | 23:34 |
knome | aha ;) | 23:34 |
alexkuck | (a proud user of xubuntu for a couple years) | 23:34 |
knome | we can alwaus use a pair of helping hands if you ever decide that you want to help :) | 23:35 |
knome | ^ as you can see, we totally need help with typing :P | 23:36 |
pleia2 | hehe | 23:36 |
alexkuck | knome: i've never been involved with operating system dev. what would be some initial opportunities ? | 23:46 |
knome | alexkuck, testing the development release, for example | 23:46 |
knome | and/or new software versions | 23:46 |
alexkuck | is there a formal test process ? or just report what breaks during normal usage? | 23:47 |
knome | it's described in http://xubuntu.org/contribute/qa | 23:47 |
knome | but we're also planning a session for people interested in testing in this channel | 23:48 |
knome | let me dig up the link.. | 23:48 |
knome | https://lists.ubuntu.com/archives/xubuntu-devel/2015-November/010966.html <- there | 23:48 |
knome | OR you could just ask flocculant for details :) | 23:48 |
knome | but long story short - both | 23:48 |
knome | we specifically need to do certain tests with new ISOs to make sure xubuntu is installable | 23:49 |
alexkuck | fantastic ! | 23:49 |
knome | and tbe, many more people on this channel can answer questions | 23:49 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!