/srv/irclogs.ubuntu.com/2006/12/12/#ubuntu-doc.txt

=== theCore [n=alex@modemcable229.181-131-66.mc.videotron.ca] has joined #ubuntu-doc
=== Ubugtu [n=bugbot@ubuntu/bot/ubugtu] has joined #ubuntu-doc
=== david_corrales [n=david@ip247-10.ct.co.cr] has joined #ubuntu-doc
=== jjesse [i=user@69-87-142-66.async.iserv.net] has joined #ubuntu-doc
=== dsas [n=dean@cpc2-stok6-0-0-cust37.bagu.cable.ntl.com] has joined #ubuntu-doc
=== dsas_ [n=dean@cpc2-stok6-0-0-cust37.bagu.cable.ntl.com] has joined #ubuntu-doc
=== MagicFab [n=magicfab@montreal.canonical.com] has joined #ubuntu-doc
MagicFabwhat's the licence of content at https://help.ubuntu.com/community ? Like https://help.ubuntu.com/community/DialupModemHowto/ScanModem ?02:47
dsas_MagicFab: funny subject. See https://wiki.ubuntu.com/WikiLicensing02:49
=== david_corrales [n=david@ip247-10.ct.co.cr] has joined #ubuntu-doc
dsas_hi david_corrales Are you having any luck with scrollkeeper?02:50
david_corralesheya02:50
david_corralesactually I got the advice I was looking for02:50
MagicFabdsas, so it's currently *unlicensed* ???02:51
david_corralesthanks for your interest :)02:51
MagicFab(well, (C) Canonical)02:51
david_corralesit was all about putting the docs inside /usr/share/gnome/help02:51
david_corralesto get them available through ghelp:name02:51
dsas_MagicFab: Theoretically it's copyright Canonical yes.02:52
MagicFab!02:53
dsas_MagicFab: At least as far as I understand, I've not had anything to do with the discussions... the spec drafters are your best bet...02:53
jjessei thought we were moving to cc-by-sa or something02:55
jjessei can't keep it striaght eitehr02:55
tonyyarussoMagicFab: You get a glimpse of the headaches this is causing ;)02:55
tonyyarussojjesse: They're trying to straighten it out, yes.02:55
MagicFabWell, I just came across a translation of those docs with a more restrictive licence02:55
MagicFabI just assumed it was all GFDL !02:56
dsas_jjesse: We are for the non-wiki docs, and I think it was/is intended to move the wiki docs to that license too02:56
jjessei just let mdke_ take care of the licensing ;)02:57
jjessei trust him02:57
jjessei know the docs got/are getting relecincesd to match the official ubuntu book02:57
dsas_MagicFab: No-one ever stuck a license on the wiki. Hence all the problems it's causing, the "everything is owned by canonical" is something that's been thrown into the argument since I was last up to date with it.02:58
tonyyarussodsas_: The way I've heard it is that it legally belongs to the vague legal entity of "the doc team", but I dunno02:59
dsas_tonyyarusso: That goes for the shipped docs, but not the wiki docs afaik02:59
=== dsas_ knows as little about this as everyone else
tonyyarussoSome of the wiki docs are the shipped docs though03:00
tonyyarussoClear as a whirlpool in a mudpuddle03:00
=== dsas_ shrugs
dsas_tonyyarusso: heh, exactly.03:00
dsas_david_corrales: Cool, how are the jokosher docs coming along?03:01
MagicFabFound the thread: https://lists.ubuntu.com/archives/ubuntu-doc/2006-November/007322.html03:02
david_corralesdsas_: well, I'm doing the final installation bits. Then, I'll have to tag the manual itself03:02
MagicFabSeems the spec was not accepted for a sprint at UDS, so it's been delayed03:02
david_corralesit needs updating and new secionts03:02
david_corralessections*03:02
dsas_MagicFab: that thread is about the shipped docs (the ones not in h.u.c/community)03:05
MagicFabhuh03:05
dsas_at least as I understand it...03:05
dsas_MagicFab: There should be threads (and CC meeting logs) about the wiki licensing somewhere, though it's been going on for ages..03:06
=== nixternal [n=nixterna@ubuntu/member/nixternal] has joined #ubuntu-doc
jjessemdke_ has been working for a long time on licesnign the wiki03:08
jjessethat's preety much all i know :)03:08
MagicFabAren't the shipped docs bases on the community docs ?03:11
jjessesome of them are03:12
=== dsas [n=dean@cpc2-stok6-0-0-cust37.bagu.cable.ntl.com] has joined #ubuntu-doc
=== Madpilot [n=brian@ubuntu/member/madpilot] has joined #ubuntu-doc
=== theCore [n=alex@modemcable229.181-131-66.mc.videotron.ca] has joined #ubuntu-doc
=== david_corrales [n=david@ip247-10.ct.co.cr] has left #ubuntu-doc ["Ex-Chat"]
=== Burgundavia [n=corey@ubuntu/member/burgundavia] has joined #ubuntu-doc
=== bhuvan [n=bhuvan@ubuntu/member/bhuvan] has joined #ubuntu-doc
=== bojicas [n=bojicas@ner-as11977.alshamil.net.ae] has joined #ubuntu-doc
=== Burgundavia [n=corey@ubuntu/member/burgundavia] has joined #ubuntu-doc
=== mihakriket [n=mihakrik@68-235-112-223.kntnny.adelphia.net] has joined #ubuntu-doc
mdke_morning08:45
Madpilothi mdke_08:45
LaserJockhi mdke_08:46
somerville32hi mdke_08:48
mdke_how's it going?08:55
LaserJockit's going :-)08:56
mdke_good08:57
somerville32:] 08:59
=== Starting logfile irclogs/ubuntu-doc.log
-ChanServ(ChanServ@services.)- [#ubuntu-server] Ubuntu Server Discussions (development and support)10:02
=== ubuntulog [i=ubuntulo@ubuntu/bot/ubuntulog] has joined #ubuntu-doc
=== Topic for #ubuntu-doc: Ubuntu Documentation Team http://doc.ubuntu.com or https://wiki.ubuntu.com/DocumentationTeam | backlog at http://people.ubuntu.com/~fabbione/irclogs | SVN - https://docteam.ubuntu.com/repos | Please observe the Ubuntu CoC @ http://www.ubuntu.com/community/conduct | Next meeting: https://wiki.ubuntu.com/DocumentationTeam/MeetingAgenda | Ubuntu's docs in dead-tree format: http://www.lulu.com/ubuntu-doc
=== Topic (#ubuntu-doc): set by Seveas at Sun Nov 26 11:57:46 2006
=== Starting logfile irclogs/ubuntu-doc.log
=== willvdl [n=will@vc-196-207-41-253.3g.vodacom.co.za] has joined #ubuntu-doc
=== motin [n=motin@c-138472d5.09-32-73746f42.cust.bredbandsbolaget.se] has joined #ubuntu-doc
=== Seveas [n=seveas@ubuntu/member/seveas] has joined #ubuntu-doc
=== tonyyserver [n=anthony@d235-240-148.home1.cgocable.net] has joined #ubuntu-doc
=== tonyyserver [n=anthony@d235-240-148.home1.cgocable.net] has joined #ubuntu-doc
=== tonyyarusso [n=anthony@d235-240-148.home1.cgocable.net] has joined #ubuntu-doc
=== dgold [n=aiden@dsl-51-63.dsl.netsource.ie] has joined #ubuntu-doc
=== bhuvan [n=bhuvan@ubuntu/member/bhuvan] has joined #ubuntu-doc
=== jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #ubuntu-doc
=== motin [n=motin@c80-217-109-98.bredband.comhem.se] has joined #ubuntu-doc
=== twosouls82 [n=twosouls@cc100614-b.assen1.dr.home.nl] has joined #ubuntu-doc
twosouls82hi all :)01:10
willvdlhi there01:10
twosouls82I edited https://help.ubuntu.com/community/EdgyUpgrades01:18
twosouls82can someone check it?01:18
twosouls82I saved it a couple of times, my bad, sorry01:19
twosouls82I edited because I had to use "sudo apt-get install --reinstall xserver-xorg" to get x working after upgrade instead of what was stated there01:20
tonyyarussoWhat did it say before?  *curious*01:22
twosouls82sudo apt-get install xserver-xorg, I left that notice below my edit ;)01:23
twosouls82so you could revert01:23
tonyyarussoHmm.  I'm not familiar with the case in question, but seems to me 'sudo dpkg-reconfigure xserver-xorg' would be preferred to reinstalling.  Don't know though.01:24
twosouls82tonyyarusso: true, that was below the reinstall option, so I moved it up one01:24
tonyyarussoah01:25
twosouls82tonyyarusso: should I make it clearer that the reconfiguration is sufficient? (was on the phone)01:41
tonyyarussotwosouls82: If one works for sure, simplify it to only that.  If it usually works, but the other may be necessary, say it like that.01:42
twosouls82I will go for the last on e:)01:43
=== theCore [n=alex@modemcable229.181-131-66.mc.videotron.ca] has joined #ubuntu-doc
=== lionel_ [n=lionel@ip-61.net-82-216-103.rev.numericable.fr] has joined #ubuntu-doc
twosouls82tonyyarusso: https://help.ubuntu.com/community/EdgyUpgrades02:07
twosouls82fixed, finally, a lot of phone calls which I couldn't ignore02:08
twosouls82grrr02:08
twosouls82and I am not a multitasker02:08
tonyyarussotwosouls82: Looks pretty good02:09
twosouls82good02:09
twosouls82merci tonyyarusso for the feedback02:09
twosouls82btw, I am allowed to edit and add documentation? who coordinates this?02:09
twosouls82I just did without asking =)02:10
tonyyarussoThat's basically how it works yes, although if you haven't done it much having folks look over your work is a great idea.  (There's also a doc-team mailing list you may be interested in)02:11
twosouls82tonyyarusso: I am looking for a regulation on the docs, does it exist too?02:12
tonyyarussotwosouls82: There's a Howto and guidelines, but I don't have the URLs handy02:12
tonyyarussoI'd start at /DocumentationTeam02:13
twosouls82np, I will Google harder now that I know it does exists02:13
twosouls82kay02:13
=== twosouls82 found all he need at https://wiki.edubuntu.org/CategoryDocteam 's children
tonyyarussoyay02:16
twosouls82s/need/needs/02:16
twosouls82w00t w00t02:16
=== kalon33 [n=kalon33@i02v-62-34-145-118.d4.club-internet.fr] has joined #ubuntu-doc
=== Burgundavia [n=corey@S0106000fb085cc63.gv.shawcable.net] has joined #ubuntu-doc
=== kalon33 [n=kalon33@i02v-62-34-145-118.d4.club-internet.fr] has left #ubuntu-doc ["Kopete]
=== somerville32 [n=somervil@fctnnbsc15w-156034086016.nb.aliant.net] has joined #ubuntu-doc
=== mihakriket [n=mihakrik@68-235-112-223.kntnny.adelphia.net] has joined #ubuntu-doc
=== mihakriket [n=mihakrik@68-235-112-223.kntnny.adelphia.net] has left #ubuntu-doc []
=== froud [n=froud@dsl-242-191-132.telkomadsl.co.za] has joined #ubuntu-doc
=== dsas [n=dean@host-84-9-170-34.bulldogdsl.com] has joined #ubuntu-doc
=== kalon33 [n=kalon33@i02v-62-34-145-118.d4.club-internet.fr] has joined #ubuntu-doc
=== kalon33 [n=kalon33@i02v-62-34-145-118.d4.club-internet.fr] has joined #ubuntu-doc
=== tonyyarusso [n=anthony@d235-240-148.home1.cgocable.net] has joined #ubuntu-doc
=== dsas_ [n=dean@cpc2-stok6-0-0-cust37.bagu.cable.ntl.com] has joined #ubuntu-doc
=== ragnar_123 [n=ragnar@217.172.86.46] has joined #ubuntu-doc
=== dsas_ [n=dean@host-84-9-170-34.bulldogdsl.com] has joined #ubuntu-doc
=== kalon33 [n=kalon33@i02v-62-34-145-118.d4.club-internet.fr] has left #ubuntu-doc ["Kopete]
=== Gwaihir [n=Gwaihir@ppp-145-108.25-151.libero.it] has joined #ubuntu-doc
=== mihakriket [n=mihakrik@68-235-112-223.kntnny.adelphia.net] has joined #ubuntu-doc
mihakriketI am working on some of the wiki documents but I have a general question. The wiki documents are the purpose of the wiki to provide the user with a howto on the subject or where to find information on the subject?09:30
=== theCore [n=alex@unaffiliated/thecore] has joined #ubuntu-doc
LaserJockmihakriket: well, they could be a bit of both09:33
LaserJockdepends on the subject and how big it is09:34
theCoreLaserJock: hi09:35
LaserJocksorry I missed the CC meeting, congrats09:36
somerville32Hi09:36
theCoreLaserJock: thanks09:36
LaserJocktheCore: for some reason I thought the meeting was tomorrow09:37
mihakriketI am working on a document in reguards to the commandline. I asked for feedback from people on features they would like to see in the document. My feedback I received had to do with BASH scripting. During my research on the subject, I found alot of already written guides.09:37
=== ragnar_123 [n=ragnar@217.172.86.46] has left #ubuntu-doc []
LaserJockmihakriket: I think a bit of both would be good09:37
theCoremihakriket: or the one doing the Advanced Command Line guide?09:38
LaserJocklike have a few common examples in the wiki and then link to "For more information try:"09:38
theCoremihakriket: oh, yes it's you09:41
theCoreI'm the guy who sent the list of suggestions on the mailing list :)09:42
mihakrikettheCore: that is the reason why I asked the question, I wanted to get an idea of how to present the info.09:42
mihakriketOh, ok. Did you get my email back on that?09:42
theCoremihakriket: yes09:42
theCoremihakriket: Obviously, writing a such guide will be hard09:43
mihakrikettheCore: What did you think of the idea of having a seperate document on just BASH scripting?09:45
theCorethe biggest challenge is to make the guide easy to read, so people without much experience can understand the content09:45
theCoremihakriket: I think you shouldn't cover BASH scripting09:45
theCorethere's a lot of good guides out there about Bash scripting09:46
theCoreyou should really focus on the command line power tools09:46
theCoreso, it should focus on "being productive with the command line"09:48
mihakriketThat's what I was thinking too. I was going to use the suggestion about the different shells in a section.09:49
theCoreI loves Zsh09:49
LaserJockI've seen a lot of bash scripting documentation09:50
LaserJockit would be nice to have a "Command-Line Productivity" guide09:50
theCoreI think Bash scripting should be forbidden ...09:50
theCoremihakriket: where will you write the document?09:52
mihakriketI have added command line navagation, such as keystrokes as well as info on the history command. I was going to add a section about alias and env variables as well. I was going to remove the section on scripting.09:52
mihakrikettheCore: I am updating the current document in the wiki.09:53
theCoreURL?09:53
mihakrikettheCore: https://wiki.ubuntu.com/AdvancedCommandlineHowto?highlight=%28commandline%2909:54
theCorethanks09:54
=== willvdl [n=will@vc-196-207-41-253.3g.vodacom.co.za] has joined #ubuntu-doc
mihakrikettheCore: what do you think of the document?10:04
theCoremihakriket: not bad. I need some structure, tough10:05
mihakriketI have just started to edit the document, so I am just brain storming.10:08
theCoremihakriket: have you seen: http://learnlinux.tsf.org.za/courses/build/shell-scripting/index.html ?10:09
mihakrikettheCore: thanks, I will look at the doc. I was thinking of removing the scripting portion of the doc, this was in their before I starting editing the doc.10:12
theCoremihakriket: I'm writing something about shell globbing and regex10:15
=== dsas_ [n=dean@host-84-9-170-34.bulldogdsl.com] has joined #ubuntu-doc
mihakrikettheCore: I added a wildcard section in the CommandLine howto on the wiki. Maybe I can add a link to your document in the advance commandline doc?10:20
mihakrikettheCore: I was going to add a section about regex but I will not, no use in redundancy in the wiki.10:24
theCore?10:26
theCorethe wiki doesn't contain a regex guide...10:26
mihakrikettheCore: I was going to add a section on regex in the advance commandline doc. regex is used by some commands such as grep or awk correct?10:29
theCoremostly grep10:30
theCorenot in AWK10:30
LaserJock?10:33
LaserJockI think regex are used in awk, sed,  a lot of tools10:33
mihakrikettheCore: ok.10:33
mihakriketLaeserJock: that was what I was thinking, I was just double checking on that as we speak.10:34
theCoremihakriket: nevermind, awk uses regex10:34
theCorejust a very weird type of regex10:34
mihakrikettheCore: let me know when the document is completed, I will add a link in the Advanced commandline doc.10:35
theCoremihakriket: ok10:35
=== ompaul [n=ompaul@gnewsense/friend/ompaul] has joined #ubuntu-doc
nixternali will say this everyone, we are definitely better doc wise then our mother Debian11:20
nixternali have been scouring their docs today looking for some info, and it isn't that great11:21
willvdlhey nixternal, I remember seeing a discussion on why docs are not in bzr but can't seem to locate it anymore.11:30
willvdlany pointers?11:30
LaserJockwillvdl: why the ubuntu docs aren't?11:30
LaserJockwe had a dicussion at our last meeting and a little follow up on the mailing list11:31
mihakriketnixternal: Do you mean the quality of the docs are the amount of docs?11:31
willvdlLaserJock, ubuntu-docs etc. yeah11:32
willvdlI'll check minutes and mailing list. I jsut rememebr _something_ on the wiki11:32
LaserJockhmm11:32
willvdlI'm grappling with the seperation of "release docs" and "dynamic docs"11:33
LaserJockmhm11:33
willvdlmeaning e.g. About Ubuntu is a release doc.11:33
nixternalmihakriket: both actually11:33
=== enrico_ [n=enrico@debian/developer/enrico] has joined #ubuntu-doc
willvdlit gets packaged and appears on CD, etc.11:34
nixternalwe have more info on pbuilder than debian does in our system docs (packaging guide) and definitely our wiki11:34
LaserJockwillvdl: what would be a dynamic doc? generally I would think of wiki pages as dynamic docs11:34
willvdland then dynamic docs appear on the wiki (or pilfered from forum)11:34
willvdlLaserJock, yeah11:34
LaserJocknixternal: it depends, they have much better policy documentation. We have better "guides"11:35
willvdlbut... some docs (or planned docs) are going to be dynamic11:35
willvdlfor example Edubuntu School Advocacy: needs to reflect releases but is also going to be constantly updates as marketing material11:35
=== trappist [i=trappist@tra.ppi.st] has joined #ubuntu-doc
LaserJockyep11:36
LaserJockI think you'll always have that to some degree11:36
willvdlso where does one keep it?11:36
LaserJocksame place11:36
willvdlnot on the wiki and the svn is too release specific11:36
willvdlso was wondering about bzr11:36
LaserJockwe use svn for it11:36
LaserJockwell, I'm not sure that bzr has an advantage over svn in that regard exactly11:37
LaserJockit's more of the packaging and build structure11:37
=== crimsun [n=crimsun@dargo.trilug.org] has joined #ubuntu-doc
willvdlLaserJock, currently the svn contains ubuntu-doc11:37
willvdlwhich gets packaged and shipped11:37
LaserJocknot all of it11:38
=== nnonix [n=brad@xeon.bkjohnson.com] has joined #ubuntu-doc
willvdlgood point11:38
LaserJockyou could have both release and dynamic docs in there11:38
LaserJockyou just branch and build for release docs11:38
LaserJockwhile the dynamic docs are just built as needed11:39
willvdlhmmm11:39
LaserJockbzr might give you a more flexibilty11:40
willvdlwhere would one put dynamic docs? in the trunk under seperate directory or seperate branch?11:40
LaserJockdoesn't matter11:40
willvdlwell, it's not really a branch per se11:41
LaserJockto build the release docs we have Makefiles, you just don't build/install the dynamic ones11:41
LaserJockfor instance currently ESA isn't shipped11:41
LaserJockso it's a dynamic doc in that sense11:41
willvdlbut it is built in the makefile11:41
LaserJocknot in any package11:42
LaserJockso we build it for the website I believe11:42
willvdlaha11:42
LaserJockbut it's not a release doc currently by your definition11:42
willvdlright11:43
willvdleven though ti uses the same makefile11:43
LaserJockso it's more about how you build them then where you put them11:43
LaserJockwell, a single makefile can do many different things11:43
LaserJockmore importantly in this case is the packaging11:44
willvdlokie. I need to read up on the reasoning behind bzr vs svn. imagine it's an interesting read11:44
willvdlI see your point11:44
LaserJockI think the bzr site has some interesting stuff11:44
willvdlwho does the packaging?11:44
LaserJockwell, generally mdke or I for ubunt-docs11:45
LaserJockmostl Riddell for kubuntu-docs11:45
theCoremihakriket: I think I'm done11:45
willvdland where is it tracked what is packaged?11:45
LaserJockit's in the svn repo11:45
LaserJockunder debian/ and kubuntu/debian/11:46
=== enrico [n=enrico@debian/developer/enrico] has joined #ubuntu-doc
=== crimsun [n=crimsun@pdpc/supporter/silver/crimsun] has joined #ubuntu-doc
=== crimsun_ [n=crimsun@dargo.trilug.org] has joined #ubuntu-doc
willvdlaha11:46
willvdldoes https://launchpad.net/distros/ubuntu/feisty/+source/ubuntu-docs enter into it?11:47
LaserJockwell, that is the source package that get's uploaded11:47
LaserJockit's a snapshot of the svn repo11:48
mihakrikettheCore: good deal. What is the url?11:48
theCoremihakriket: I didn't uploaded yet11:48
theCorejust a sec11:48
willvdlbrill. LaserJock, thanks11:48
LaserJockwe'll have an edubuntu-docs package soon enough11:49
willvdlcool.11:49
mihakrikettheCore: Are you posting the document into the wiki?11:49
LaserJockwe mostly just need to get enough content to replace ubuntu-docs11:50
willvdlLaserJock, it gets tricky when some of our docs are essentially marketing stuff11:50
LaserJockwell, we can have release and dynamics docs side-by-side no problem11:50
willvdlhow is the automatic inclusion of ubuntu-doc material (for sake of reducing duplication) going to work?11:50
LaserJockwe won't11:51
willvdlby hand then at snapshot time11:51
willvdluntil Topic-Based comes into effect11:51
LaserJockwell, what I'm saying is the idea is to totally replace the ubuntu-docs with edubuntu-docs11:51
theCoremihakriket: https://help.ubuntu.com/community/ShellGlobbing11:51
willvdlLaserJock, so edubuntu-doc being only value-add info11:53
LaserJockedubuntu-doc being complete documentation for an Edubuntu system11:53
LaserJocki.e. ubuntu-doc won't be installed11:54
willvdledubuntu being based on ubuntu, there is bound to be overlap of info11:54
LaserJockyep11:54
LaserJockbut the idea was that the Edubuntu Handbook would be that11:54
LaserJockperhaps we will need to copy over the Ubuntu desktopguide I'm not sure11:55
LaserJockdepends on how far along the handbook gets11:55
willvdlLaserJock, it is bound to go that way11:55
willvdlit is impractical for the handbook to cover edubuntu & base ubuntu info11:56
willvdlimpractical for the authors11:56
LaserJockyeah, well ...11:56
LaserJockwe could install ubuntu-docs as well11:57
LaserJockbut then we start getting into space issues11:57
willvdlnot necessarily install ubuntu-doc11:57
willvdlbut at least pull sections11:58
LaserJockit'll be some work, but doable11:58
willvdlless work than rewriting11:58
LaserJocksomebody needs to lead some effort there ;-)11:58
willvdlthat's what I'm trying to do :)11:58
willvdlbut need to understand the history etc.11:59
LaserJockI think pygi's original goal was to create a full-fledged Edubuntu book11:59
LaserJockthat would go to a publisher11:59
LaserJockand be shipped as the complete Edubuntu documentation11:59
theCoremihakriket: the foo, bar examples should be changed to "real world" examples11:59
willvdlLaserJock, still the goal only we're going broader11:59
willvdlwe want to target specific audiences with specific information12:00
=== cbx33 [n=pete@ubuntu/member/cbx33] has joined #ubuntu-doc
LaserJockok, so I think it'd be a wise thing to do to use the doc team for the release docs and non-marketing stuff12:00
willvdlcbx33, jsut in time :)12:01
LaserJockand then set up a bzr repo tied to an LP team for the marketing stuff12:01
willvdlwas my thinking12:01
cbx33sounds good12:01
mihakrikettheCore: Where do you upload your docs? I have been editing docs on the wiki.12:01
cbx33was what we were thinking right willvdl ?12:01
LaserJockwe've consistently had trouble getting Edubuntu people to contribute to the doc team12:01
willvdlone way is to continue authoring of handbook as original goal12:01
willvdlcbx33 yeah12:01
theCoremihakriket: ^^12:01
theCorehttps://help.ubuntu.com/community/ShellGlobbing12:02
willvdland then draw info from it for other purposes as needed.12:02
willvdlLaserJock, this way I hope to leverage more contribution from the marketing team12:02
LaserJockyeah, that would be good12:03
willvdland don't want to dilute the doc team too much12:03
willvdlthere is an edubuntu doc team12:03
LaserJockIMO, there shouldn't be12:03
LaserJockon LP anyway12:03
mihakrikettheCore: I saw the doc, I mean how do people upload docs to the help.ubuntu.com site?12:03
willvdlexactly12:03
theCoremihakriket: just invent your own url12:03
theCoremihakriket: then, edit and post12:04
willvdlin effect it appears, but we miss the boat by seperating from it12:04
LaserJockthe doc team has very good resources for documentation12:04
willvdland many reviewers12:04
LaserJockand Edubuntu has kind of been the last team to get onboard12:04
willvdlso keep LP doc team12:05
willvdlwith ubuntu-doc project12:05
willvdland edubuntu-doc as another product12:05
LaserJockI'm not sure how it all works12:05
cbx33;)12:05
LaserJockbut the issue is less with LP and more with people12:06
willvdlLaserJock, spent an hour with salgado :)12:06
LaserJockwith Kubuntu, the doc guys are a part of the doc team12:06
willvdlbut it still needs to be tracked with minimum effort12:06
cbx33totally12:07
willvdlso intelligent use of LP and wiki is key12:07
LaserJockwe just need people working and joining the team, I really have had a hard time understanding why Edubuntu people seem to not get that12:07
cbx33:( - I have to get off to bed now....12:07
cbx33up in about 6 hours12:07
willvdlcbx33, up in 5 hours :P12:08
cbx33please please willvdl could you send me a quick mail about what we decide ;)12:08
cbx33then I'll get it fleshed out for the summary page ;)12:08
willvdlcbx33, will do and check ubuntu-doc logs tomorrow12:08
willvdlLaserJock, technical docs are always tedious12:09
willvdlbut I think we can curry favour on the marketing side12:09
LaserJockwell, we get people and then nothing happens12:10
LaserJockthat's been my issue12:10
LaserJockthey need to be joining the doc team and getting involved12:10
willvdlwell, our community is smaller12:10
LaserJockwhat I'm saying is don't think of it as edubuntu docs12:11
willvdlLaserJock, was suggesting to cbx33 an open letter - call for contributions to doc-team community12:11
LaserJockbut as ubuntu doc people working on edubuntu12:11
willvdlLaserJock, that's been my take since the beginning12:11
mihakrikettheCore: How do create a url?12:11
LaserJockI think that's what we've missed for a while12:11
willvdlI'm slowly populating the doc team wiki with edubuntu references12:11
dsasmihakriket: Just type it in your browsers address bar12:12
willvdland eventually specs into LP12:12
dsasmihakriket: Or you can create a link using [:PageName: page name]  syntax12:12
LaserJockwhat seems to happen is a few people get all excited but they just stay a closed little team12:12
cbx33nn12:12
cbx33see ya willvdl and LaserJock12:12
willvdlnn12:13
willvdlLaserJock, I'm here to try and track/manage that.12:14
LaserJockyeah12:14
LaserJockI'm glad you're here :-)12:14
willvdlwon't have time to author much unfortunately12:14
willvdlwhich I'd like since I've done a looot of that in the past12:14
LaserJockI guess what I'm saying is that the biggest problem from my standpoint is not a technological one, but a social one12:14
willvdlI hear you12:15
LaserJockwe have everything in place for an edubuntu doc team12:15
LaserJockwe just need people to join and work12:15
LaserJockinstead of wandering off trying to reinvent the wheel12:15
willvdlwell, lemme look deeper at LP, maybe we can keep the edubuntu doc SUB-team12:16
LaserJockso I think if you can push people toward the doc team12:16
LaserJockperhaps12:16
willvdland move subscriptions up12:16
LaserJockbut you can do the whole thing without LP if you want12:16
willvdlactually, nah, still makes no sense12:16
LaserJockI think the an edubuntu-marketing team might be better to house the marketing stuff12:17
willvdlLaserJock, LP works nicely for bugs, reviewing, proofing etc.12:17
=== cbx33 [n=prochat1@84-45-238-195.no-dns-yet.enta.net] has joined #ubuntu-doc

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