/srv/irclogs.ubuntu.com/2007/10/24/#ubuntu-doc.txt

=== j1mc is now known as j1mc|afk
=== j1mc|afk is now known as j1mc
ubotuNew bug: #156630 in ubuntu-docs (main) "typo in "hardware" template" [Undecided,New] https://launchpad.net/bugs/15663011:56
=== tonyy is now known as tonyyarusso
tuxcrafterhello everybody13:50
tuxcrafterIs it possible to get a ubuntu wiki mentor?14:10
seisenDid you do all of this:  https://wiki.ubuntu.com/DocumentationTeam/Mentoring14:18
tuxcrafterseisen: ah perfect14:30
seisenno problem14:31
tuxcrafterseisen:  now I just have to wait until my latest HOW TO's are approved by a forum administrator.14:31
seisenwhat are they about??14:31
tuxcrafterthan i can create a wiki backed for them14:31
tuxcrafterseisen: pff a lot14:31
tuxcrafterlets see14:31
seisenyou can create the wiki pages without anybody's approval14:32
tuxcrafterseisen: no point for me to make wiki without a full support background :-p14:32
tuxcrafterInstall openchrome video drivers from cvs source14:33
tuxcrafterSetting up xfce font rendering settings14:33
tuxcrafterSetting up xorg monitor settings14:33
tuxcrafterInstallation of the SCR335 smartcard reader14:33
tuxcrafterInstallation of hellanzb nzb downloader14:33
tuxcrafterInstallation of lib-xine based multimedia codecs14:33
tuxcrafterInstallation of vmware server14:33
tuxcrafterthat are them for now I have a lot more but they are still in beta phase14:34
tuxcrafterthis scripts has been tested and used in production for almost a year now14:34
tuxcrafters/this/these/14:34
tuxcrafterI also have a lot not so universal scripts but these are not published yet14:35
tuxcraftertherefor I could use the wiki backand14:35
tuxcrafters/backand/backend/14:36
tuxcrafterI also would like a mentor for ubuntu packaging14:36
tuxcrafteri got a awesome set of scripts for thunar file manager that have also been tested, i am preparing a complete support system for them14:37
seisensounds to me like you have been a little busy14:37
tuxcrafterseisen: yes the last years has been busy indeed14:38
=== TLE is now known as ubatbot
=== ubatbot is now known as TLE
=== TLE is now known as TLE_
=== TLE_ is now known as TLE
=== TLE is now known as TLE_
=== TLE_ is now known as TLE
=== TLE is now known as TLE_
=== TLE_ is now known as TLE
=== nixternal_ is now known as nixternal
tuxcrafterI think i am forgetting something but i want to remove all leading spaces until the first character, what am i forgetting? (tabs are next)15:55
tuxcrafterdescription=${description#* }15:56
* tuxcrafter is losing it maybe the syntax is already correct15:57
tuxcrafterdescription=${description#*$'\t'}15:57
tuxcraftergot dammit again the wrong channel15:59
tuxcraftersorry guys16:00
tuxcrafterhaha16:00
LaserJockmdke: around?18:30
mdkeLaserJock: (In case I'm not around at the moment, please provide a bit of information about what you want and I will respond when I get back)18:30
LaserJockmdke: I was just thinking of a way that might make the initial branching a bit easier for people. LP allows projects to have tarballs for downloads. We could tar up the .bzr and have LP host  it.18:33
mdkeLaserJock: might work yeah. I don't know much about bzr. The branching is going to be substantial given that each branch (as I understand it) is going to have the whole revision history for the repository in it...18:36
mdkeI believe LP doesn't support shared repositories over branches18:36
LaserJockright18:37
LaserJockso if we had a tarball of the .bzr/18:38
LaserJockeven 1 per release18:38
LaserJockit's save people downloading the vast majority of history18:38
mdkehow does that work? you download the .bzr then branch and it is fast?18:38
mdkealternatively, cant you just avoid downloading all the history?18:39
LaserJockyes18:39
LaserJockalthough for a lot of people the history might be nice as well18:39
mdkewell, not much of it :)18:39
mdkeit's handy to have around but probably the old svn history is not very helpful18:40
LaserJockall you do is tar -czf hardy_docs.tar.gz .bzr/ and there you go18:40
LaserJockthen people download the tarball like any normal file18:40
mdkedoesn't bzr compress already over the download?18:40
LaserJocksome18:40
LaserJockbut the killer is that you are downloading so many individual files18:40
LaserJockwith this you just download one file18:40
LaserJockuntar it, abd bam, you have the branch18:41
mdkealright, i suggest we do both then; recommend people to branch without the history and keep the history in a tarball for those who want it18:41
LaserJock*and18:41
LaserJocksure18:41
LaserJockbut doing stuff in history I think is easier with bzr18:41
mdkebtw just to clarify about the different branches, the idea is to have the common and generic documents in *every* branch, are you clear on that for the purposes of creating the edubuntu ones?18:41
LaserJockso we might find it useful more than the svn history18:42
LaserJockyep18:42
LaserJockbasically I'm just going to make the branch how I package it18:42
mdkegood. I'm going to try and do an xubuntu-hardy one now as an example18:42
mdkedoes the naming scheme work for you?18:42
LaserJockyep18:42
mdkeok18:43
LaserJockone question I had was if you're going to keep the whole history for xubuntu, etc.18:43
LaserJockwe *could* make the derivative branches much smaller by starting fresh18:43
LaserJockif the ubuntu branch has the complete history then if we really needed it would could use that branch18:43
mdkehow does one get rid of history? just by exporting and starting a new repository?18:44
LaserJockI wonder if it's useful to have 4 copies of the entire svn history18:44
LaserJockyeah, that's what I would do18:44
mdkehmm18:44
LaserJockI just wondered what you thought of that18:44
mdkegood question. I don;t know the right answer18:44
LaserJockgiven that we've never really "gone back in history" much18:45
mdkevery true18:45
LaserJockI wonder if it's just wasteful to have multiple copies18:45
LaserJockwe for sure should have at least one18:46
mdkeperhaps we should just have a dump of the whole svn repo somewhere and start from scratch with all the new branches18:46
mdkeI don't see why ubuntu should be heavy and the others not... :)18:47
mdketbh, I dont' really mind what we do about this, I don't know18:47
LaserJockwell, what we *could* do is have an ubuntu-archive branch18:48
LaserJockand then start fresh18:48
LaserJockfor all18:48
mdkeis LP clever enough to avoid me uploading all the history 20 times if I'm just creating branches from others already present?18:48
mdkeif not it will take weeks to upload all these :)18:49
LaserJockI don't think so but I don't know for sure18:49
LaserJockto LP they are separate branches18:49
mdkempt: got any views on all this? We could do with some advice from someone who uses bzr and knows Launchpad18:49
mdkeLaserJock: problem with having an ubuntu-archive branch is that we'd need one for trunk, for gutsy, for feisty, for edgy etc because I don't think it's possible (or advisable) to import the whole svn repo to a single branch18:51
LaserJocktrue18:52
mdkeI might ask lifeless, he's the man for this stuff18:52
LaserJockalthough, if we did just do the archvies as tarballs I wonder if that'd be ok18:52
LaserJockmdke: that'd be a good idea, before we go and spend a week pushing branches18:56
LaserJockfor almost all activity I can think of we don't need the complete history around18:56
dsas_I've just done a bzr branch on ubuntu-hardy and it appears bzr tries to download the branch as a tarball anyway19:16
dsas_(when using bzr+ssh transport)19:16
dsas_though my laptop just ran out of memory and died when attempting it.19:17
LaserJocklol19:18
mdkeLaserJock: ok, getting solutions from #bzr19:39
mdkefrom our side, someone will help with the uploads of the branches to LP by doing it from somewhere close (i assume inside the DC)19:39
mdkefor downloads, you can just download the revision history once with multiple branches by using a shared repository19:40
mdkei think that gets round the problems19:41
LaserJockmdke: ok, great19:42
nothlithey guys, i'm wondering what license everything in the wiki is under?19:56
mdkenothlit: the help wiki is under cc-by-sa (see the footer)19:57
nothlitmdke: is there a preferred method of attribution or would a commented link do?19:58
mdkegood question, we should add that to the License page. I'm sure a commented link will work19:59
mdkeah, there is something about it on the page already :)19:59
mdkenothlit: see the page, does it answer your question?20:01
nothlitmdke: ahh ok, great20:03
LaserJockmdke: so are we doing a shared repository then?20:04
mdkeLaserJock: I need to find out how it's done. then we can add it to the instructions for getting the branches20:05
nothlitmdke: those small footer links are a bit misleading next to the web badge, they look like generic company stuff rather than places to look wiki-relevant info20:05
mdkenothlit: I tend to agree20:06
mptmdke, did you get answers to your Bazaar questions?21:06
mpt(bbiab, replacing battery)21:09
mdkempt: yes, from #bzr. However there seems to be an issue with storing so much revision history on LP; it will take up a lot of disk space and so we're considering just splitting the branches for derivatives from hardy, leaving a single branch for the previous releases21:09
mdkegah21:09
mptmdke, ok21:19
mptRevision history can be useful to find out when a particular part was written/revised21:19
mptand by whom21:19
mptbut I guess that needs to be weighed against download time21:20
mdkethe issue seems to be more about server side disk space21:21
mdkeusers can download without history, right?21:21
=== dsas_ is now known as dsas
* mdke tickles mpt21:33
mptmdke, sure, that's what lightweight checkouts are for22:21
mdkempt: right22:24
mdkeso the issue is more a question of space on the LP side22:24
mptHow big is the history in bzr format?22:24
mptubuntu-docs should be tiny in comparison with some projects Launchpad dreams of hosting :-)22:25
mdkesomething like 200MB (would be 16 branches)22:25
mptwow22:25
mptWhy is that? Lots of images?22:25
LaserJockonly 200MB?22:25
mdkeI suspect the revision history is text only22:26
LaserJockI would have thought closer to >500MB at least22:26
mdkeLaserJock: per branch?22:26
LaserJockyeah22:26
LaserJockmaybe bzr is more efficient then I thought ;-)22:27
mdkethe ubuntu-hardy branch is 220MB22:28
mdkeactually proably the branches are with translations  a lot bigger22:28
mdkebut the ubuntu-hardy branch has all the revisions relevant to svn trunk22:29
mdkeLaserJock: anyway, we have an edubuntu-hardy branch now so feel free to go and clean it up, remove whatever you don't want22:31
LaserJockmdke: awesome, thanks22:33
mdkeprobably for the other previous releases we won't have separate branches for derivatives, due to this space issue22:33
LaserJockyeah22:34
LaserJockwe mostly just need to move forward :-)22:34
mdkewhen LP implements shared repositories, then we can do whatever we want22:34
* tuxcrafter is broken, see you all over 8 hours23:24
tonyyarussoI know the appropriate response is "So fix it", but until I magically find time I'd like to point out that https://help.ubuntu.com/ still lacks a 7.10 tab.23:26

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