[01:59] hello :) this is a really quiet channel! [01:59] I'm interested in helping the documentation team so i thought i would drop by and introduce myself [02:00] normally you introduce yourself via the mailing list [02:00] but its all good [02:02] I did last night :) at least unless i sent it to the wrong address I think I did lol [02:02] ubuntu-doc@lists.ubuntu.com ? [02:09] hey guys, thinking of joining this team, i signed up for the mentorship :) [02:10] new blood coming in from the beginner and unanswered posts teams for you folks [02:11] im not an unanswered Old_Soldier :P [02:12] lol easily fixed :) just post before anyone answers [02:12] lol [02:13] trying to do that is harder than it sounds [02:24] Hi all, have a look here https://wiki.ubuntu.com/DocumentationTeam to see where you would like to work on the Documentation [02:24] Technical Reviewing is often the place where beginners start out: https://wiki.ubuntu.com/DocumentationTeam/TechReview [02:26] that is where i had planned on starting out nickellery it sounded like the best way to ease into the team [02:27] You can get started anytime; Get a hold of the repository using these instructions https://wiki.ubuntu.com/DocumentationTeam/Repository [02:27] if you have any questions, feel free to ask [02:27] tech review sounds great to me too. [02:28] It would also be good to subscribe to the mailing list: http://lists.ubuntu.com/mailman/listinfo/ubuntu-doc [02:29] Ping Old_Soldier Alan_M [02:29] im here :) [02:29] im doing what you were telling us [02:30] ive already subbed to the mailing list [02:30] alright [02:30] getting used to the repository and bzr takes time [02:30] and i just did, i just gotta click my linkage in email [02:30] so feel free to ask any questions [02:31] sure [02:31] i'm assuming i need to install bzr and do the work inside my intrepid vm? [02:32] you will need to get a hold of the repository via Ubuntu, but the pages are all in .xml text files, so they can be imported to any operating system [02:33] and if you just proofreading for mistakes, you generally dont need to using the latest development release [02:33] the current documentation most likely doesn't have any technical errors. It will generally be grammatical, spelling, etc.. errors [02:34] yeah, thats what im doing, grammar and stuff nickellery [02:34] ah thats good to know , my intrepid isn't very usuable yet im happy enough starting on the stable stuff [02:35] creating things i suck at, editing work, im good with (if you could believe that) [02:36] Alright guys, If you'll excuse me, I must be off. If you have any future questions, please direct them to the mailing list, or here on the IRC [02:36] Good luck! [02:37] sure thing nickellery :D [02:37] thank you! [02:38] thanks! have a good one :) [05:17] I'm needing to implement a google search for a team mailing list on the team wiki page, but I'm unsure how best to achieve that in such a way that I get an input box and a search button, rather than a link to a google page. [05:33] i'm totally confused :/ is there a document somewhere that correlates a xml files in the repos to its position in the yelp browser? [06:15] Old_Soldier, they are generally under the same name [06:16] for example, Music, Videos and Photos, is in the musicvideosphotos folder in the repo [06:16] thanks nickellery I plodded along and figured out the problem, I was in the wrong branch i found the tech review status page [06:16] and downloaded the proper branch. doh! [06:17] Old_Soldier, yes, I was about to mention that that page had both the codenames and the public ones [09:45] Anyone else having problems editing/creating wiki pages? on both h.u.c/community and w.u.c? [10:12] I have a quick question I just finished my first technical review and the wiki says to send the diff to the mailing list. Is this still the proper thing to do? [14:20] mdke: are u there? === Admiral_laptop is now known as Admiral_Chicago