[04:07] <littlegirl> I'm sorry I missed the meeting, pleia2.
[04:11] <pleia2> littlegirl: no problem
[04:11] <littlegirl> pleia2: My brain and UTC don't go together. (:
[04:11] <pleia2> meetings tend to be just sync up times anyway, we can always discuss any of the topics on the mailing list
[04:11] <pleia2> haha, I use Xubuntu and have UTC time in one of my panels :)
[04:11] <pleia2> humans are terrible at timezones
[04:12] <littlegirl> My Kubuntu has it when I hover over the time in my panel, but it's not in 24 hour mode. I'm better with words than numbers. (:
[04:12] <pleia2> and I make use of my calendar, so for important meetings it emails me 10 minutes before
[04:13] <pleia2> ah yeah, I moved to 24-hour time a few years back almost exclusively because of open source meetings
[04:13] <pleia2> my brain is so conditioned now that I have to convert 24 to 12 hour time these days (was funny when I realized that)
[04:13] <pleia2> 7pm... what is that, 1900!
[04:14] <littlegirl> Yeah, I used to be in the military. You'd think I'd remember it, but I happily forgot it and went on to pursue other (more interesting to me) things. (: (: (:
[04:14] <pleia2> hehe
[04:14] <littlegirl> I'd like to comment on some of the stuff that was discussed in the meeting if it's not too late. I read the minutes.
[04:15] <pleia2> sure
[04:16] <littlegirl> I worry when I often see so many people recommending adding things, like more wiki pages or new software to manage what already seems to be overwhelming at times because of the shortage of people or what's already working just fine. Hopefully this happens from time to time and just passes on its own. If not, I'd like to find a diplomatic way of discouraging it. (:
[04:17] <pleia2> I tend to agree, I don't want to discourage too strongly and drive folks away from good solutions, but where we stand now leveraging our existing team members to manage our existing tools more efficiently is where I'm leaning
[04:18] <littlegirl> Yeah. I think you and bkerensa were doing well with that by keeping to the topics at hand and focusing on working with what is already there, and bkerensa's idea of sending out a status message weekly (a brilliant idea, in my opinion!). (:
[04:19] <pleia2> thanks, and yeah I do love the status message idea
[04:19] <pleia2> I think a lot of people want to contribute but don't have the time to wade through lots of history or instructions, a weekly email of status and small tasks would rock
[04:19] <pleia2> "this week, we're doing grammar review, here's how: ..."
[04:19] <littlegirl> Most people (myself included) like some sort of direction rather than to be just turned loose and allowed to do whatever we like, and the status message is a great way for someone to say this, this, and this need doing. (:
[04:19] <pleia2> yeah, totally
[04:20] <littlegirl> Agreed, and the mailing list is great because we can all read it at our convenience. (:
[04:22] <littlegirl> And yeah, the explanation of how to do something that needs to be done is an awesome addition, especially since you could template grammar review instructions and use them again in future when grammar review comes up again. (:
[04:22]  * pleia2 nods
[04:26] <littlegirl> Also, and this wasn't mentioned at the meeting (but might have been if I had attended it), I'm curious why the Launchpad blueprints aren't used by all the teams? The Kubuntu documentation team uses Trello and the Ubuntu documentation team uses a Google document. Is there a flaw or flaws to the Launchpad blueprints?
[04:27] <pleia2> launchpad blueprints are good for specific tasks like "open documentation for 14.04" "put out call for contributing to 14.04 docs" and similar, less so for going through something page by page
[04:27] <pleia2> not sure why kubuntu uses trello, blueprints can be used for that, maybe it's just what their contributors prefer
[04:28] <littlegirl> I supppose that makes sense. (:
[04:34] <littlegirl> Last, but not least, I hope you guys don't mind that my contributions are a bit sporadic. Even though I sometimes am off doing other things, I will always come back and see if there's anything that needs doing. (:
[22:18] <belkinsa> Just a though, can anyone "bug" a community wiki page if they don't know how to edit it?
[22:31] <pleia2> I don't think it has a bug tracker, people typically just email the list if they want to fix something but can't log in
[22:31] <pleia2> mostly people just edit themselves though
[22:32] <belkinsa> True, true.  I don't know why this came up in my mind.
[22:33] <pleia2> looks like people do sometimes submit bugs here https://bugs.launchpad.net/ubuntu-docs/+bugs
[22:34] <pleia2> https://bugs.launchpad.net/ubuntu-docs/+bug/876113 for instance
[22:34] <ubot2> Launchpad bug 876113 in Ubuntu Documentation "bug reporting wiki page says run "ubuntu-bug" with no arg, but it fails" [Undecided,New]
[22:36] <pleia2> I agree that https://help.ubuntu.com/community/ReportingBugs#Filing_a_general_bug_against_no_particular_package should be fixed if you're looking for something to do ;)
[22:37]  * pleia2 updates the bug
[22:37] <belkinsa> I can take this job
[22:38] <pleia2> there, updated bug with a text proposal
[22:38] <pleia2> might want to doublecheck the behavior though so we make sure it's accurate :)
[22:39] <belkinsa> Okay, I will
[22:39] <pleia2> you rock \o/
[22:39] <belkinsa> And thank you for pointing that bug out
[22:40] <pleia2> honestly all these bugs could use going through
[22:40] <belkinsa> I agree, some are outdated.