[15:00] <dpm> #startmeeting
[15:00] <MootBot> Meeting started at 09:00. The chair is dpm.
[15:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[15:00] <adiroiban> hi o/
[15:00] <dpm> so hello everyone, and welcome to this translations meeting
[15:01] <dpm> hi adiroiban :)
[15:01] <happyaron> hi
[15:01] <dpm> hi happyaron o/
[15:01] <dpm> we've got a bit of a bad timing today, because we're on the same time as OpenWeek
[15:02] <adiroiban> yep
[15:02] <dpm> but we can just go along now
[15:02] <happyaron> ok
[15:02] <dpm> so just before we start, is there anyone else present for the meeting?
[15:03] <dpm> ok, it seems there are no more people around. That's fine, let's kick off the first topic
[15:03] <dpm> [TOPIC] Promoting and using the Ubuntu Translations project
[15:03] <MootBot> New Topic:  Promoting and using the Ubuntu Translations project
[15:04] <dpm> We've talked about this in previous meetings
[15:04] <dpm> so far the feedback has been positive on the u-t project
[15:05] <dpm> and now that we're confident that it is working well
[15:05] <dpm> we'd like to let people know about it
[15:05] <adiroiban> before making the big announcement we still need to define the bug reporting process
[15:06] <dpm> ok, so we want to focus on bug reporting
[15:06] <dpm> first
[15:06] <dpm> we've got https://wiki.ubuntu.com/Translations/KnowledgeBase/ReportingBugs as groundwork
[15:07] <dpm> but we should discuss other aspects as well
[15:07] <dpm> like which tags we use and
[15:07] <dpm> e.g. how do we triage them
[15:07] <dpm> adiroiban, I think you made some suggestions on the agenda page
[15:07] <adiroiban> yep. I tryind to experiment with various practice in handling bugs
[15:07] <adiroiban> tried
[15:08] <adiroiban> one suggestion was not to mark „also affect this project” for bugs or errors in translations
[15:08] <adiroiban> „l10n” bugs
[15:08] <adiroiban> for packages in main
[15:08] <dpm> yep, I think it's a good idea
[15:09] <adiroiban> if the package is not in main... then we need support from the developer/package maintainer
[15:09] <adiroiban> also, I think we can stop using l10n and i18n tags
[15:09] <adiroiban> or make them optional
[15:10] <adiroiban> with the new Ubuntu Translation project
[15:10] <dpm> on the first item, yes, then we can add the bug task for the relevant Ubuntu package
[15:10] <adiroiban> i was not using them
[15:10] <adiroiban> ok. sorry for not finalizing
[15:10] <adiroiban> ok
[15:11] <adiroiban> so back to first issue - project assignation
[15:11] <adiroiban> if the package is in main, the bug is for Ubuntu Translations only and we can assign the ubuntu-l10n-CC team
[15:12] <adiroiban> we can suggest/link in the description the string that needs to be fixed
[15:12] <dpm> I basically agree - we should then define a process for when the package is in universe, etc -> open a bug task for the ubuntu package, one for the upstream project, report it upstream and link the upstream bug to the upstream project
[15:13] <adiroiban> also agree with bugs in universe :)
[15:13]  * happyaron agreed
[15:13] <dpm> ok, so we should probably add a section on this to the ReportingBugs page
[15:14] <dpm> [ACTION] Add section on project assignation to the ReportingBugs page
[15:14] <MootBot> ACTION received:  Add section on project assignation to the ReportingBugs page
[15:14] <adiroiban> for the UserDocs (ReportingBugs wiki) i was thinking only to add the info for opening but to Ubuntu Translations
[15:15] <adiroiban> and create another doc for handling bugs
[15:15] <adiroiban> I see 2 docs ReportingBugs and HandlingBugs
[15:16] <adiroiban> ReportingBugs is the general audiance page
[15:16] <adiroiban> with minimun info on it
[15:16] <adiroiban> just the required info for users to open a new bug
[15:17] <adiroiban> I assume that many of Ubuntu users just want to underline an error in the translation
[15:17] <adiroiban> no need to explain them about universe / upstream / etc
[15:18] <dpm> adiroiban, ok, it makes sense to me. Documentation for the general audience should be concise and eays to read
[15:18] <adiroiban> the HandlingBugs page is useful for Ubuntu translators and for people helping with QA / bug triage
[15:18] <adiroiban> yep
[15:18] <adiroiban> https://help.ubuntu.com/community/ReportingBugs#Filing%20translation%20bugs
[15:18] <happyaron> sounds good
[15:19] <adiroiban> that is the place were we should put the general audience info
[15:20] <dpm> adiroiban, I agree. One thing I'd like to do is to check out with the QA team the wording used in the main page, so that they agree on the text we put there as well
[15:20] <adiroiban> dpm: I agree
[15:21] <dpm> so, let's take this to actions:
[15:21] <dpm> [AGREED] Separate pages on reporting (general audience) and handling (translations team) bugs
[15:21] <MootBot> AGREED received:  Separate pages on reporting (general audience) and handling (translations team) bugs
[15:21] <adiroiban> I have added those info on the ReportingBugs page, just to have some information while we discuss the final version
[15:21] <dpm> great
[15:22] <dpm> [ACTION] Contact the QA team to review the text on the main community/ReportingBugs page
[15:22] <MootBot> ACTION received:  Contact the QA team to review the text on the main community/ReportingBugs page
[15:23] <dpm> I can take care of that one ^
[15:23] <dpm> ok, what I think we need to discuss as well
[15:23] <dpm> is tags, as Adi was mentioning
[15:24] <dpm> and Triaging (priorities and assignment)
[15:24] <dpm> these would be good candidates for sections on the the HandlingBugs page
[15:25] <adiroiban> yep
[15:25] <dpm> Let's go on with tags, then
[15:25] <dpm> adiroiban, you were saying that the l10n and i18n tags might not be useful?
[15:25] <adiroiban> just a general note: before seting the final version, maybe we should gain a little more experience with working with bugs.
[15:26] <adiroiban> I don't find them useful
[15:27] <adiroiban> all i18n bugs would be marked as also affecting a project
[15:27] <dpm> yeah, good point. I think we'll learn as we go along. And since the HandlingBugs page content is basically still for the translations team use only, I think we can be flexible
[15:27] <adiroiban> an l10n would only affect Ubuntu Translations
[15:27] <dpm> (my comment^ was for the point on bug handling experience)
[15:28] <adiroiban> right now this is my only comment for bugs... but maybe while working with Ubuntu Translations bugs
[15:28] <adiroiban> I will discover some good usage for tags :)
[15:28] <dpm> but do the i18n tags really bring any disadvantage? It's easy to add them, and I find them useful for filtering
[15:28] <happyaron> I wonder if we need to track bugs for cjk fonts, for example
[15:29] <adiroiban> I was thinking at using a „need-lang-pack” update for bugs l10n in Hardy , Intrepid
[15:29] <adiroiban> and other lang-packs that need manual updates
[15:29] <dpm> and getting an overview of what bugs are technical and which ones are translation only
[15:31] <dpm> what about creating a wiki page for everyone's proposal's on tags? We can add which tags we think could be useful and discuss anv even vote them
[15:31] <adiroiban> yep
[15:31] <happyaron> +1
[15:31] <dpm> the person proposing a tag should reason why they'd like to see that tag used
[15:31] <dpm> and why they think it'd be helpful
[15:31] <adiroiban> i agree
[15:32] <dpm> ok, I think this could apply as well for triaging and assigning priorities
[15:32] <dpm> i.e. we could create a HandlingBugsBrainstorm page or similar
[15:32] <dpm> with the points that need discussion
[15:32] <adiroiban> or just HandlingBugs
[15:33] <adiroiban> and create a braistorm section
[15:33] <dpm> yeah, that'd work as well
[15:33] <dpm> ok, I think we all agree on that, don't we?
[15:33] <happyaron> agree
[15:33] <adiroiban> yep
[15:34] <dpm> is there anything particular you'd like to point out or discuss on triaging or priorities at this point?
[15:34] <dpm> I think that might need a longer discussion
[15:34] <dpm> at least the "how do we assign priorities" part
[15:34] <dpm> but if there's anything you'd like to comment now
[15:34] <dpm> feel free
[15:35] <adiroiban> we should talk that after gaining some experience
[15:35] <adiroiban> I'm still trying to look over all new bugs and triage them
[15:35] <dpm> ok, we'll just add a section and add content as we go along
[15:35] <dpm> so
[15:35] <adiroiban> after that I plan to look at how we solve them :p
[15:36] <dpm> [AGREED] Add a brainstorm section to the HandlingBugs page, including: a tags section with proposals on which tags might be useful, a Triaging section with the agreed practices on triaging and assignments
[15:36] <MootBot> AGREED received:  Add a brainstorm section to the HandlingBugs page, including: a tags section with proposals on which tags might be useful, a Triaging section with the agreed practices on triaging and assignments
[15:37] <dpm> ok, is there anything else you'd like to discuss on that point? Or shall we go to the next topic?
[15:38] <adiroiban> we can go to the next topic
[15:38] <dpm> [TOPIC] Ubuntu Translations Announcements
[15:38] <MootBot> New Topic:  Ubuntu Translations Announcements
[15:38] <dpm> adiroiban, all yours :)
[15:38] <adiroiban> :)
[15:39] <adiroiban> the ideas is to write an announcement one
[15:39] <adiroiban> and let it spread over multiple communication channels
[15:39] <adiroiban> I saw David was using the LP announcement
[15:39] <adiroiban> but I don't know how many people are reading / receiving them
[15:40] <adiroiban> I just wanted a brainstorming session
[15:40] <dpm> it sounds like a brilliant idea to me :) Do you have any ideas for the implementation?
[15:40] <adiroiban> about how we can spread the word about Ubuntu Translations actions
[15:41] <adiroiban> right now, we send an email to ubuntu-translators ML
[15:41] <adiroiban> but I don't know if from there
[15:41] <adiroiban> it will also reach the ML for each team
[15:41] <happyaron> planet will be good
[15:41] <adiroiban> so maybe planet-ubuntu is a first step
[15:41] <dpm> one easy way to reach the planet is the Fridge
[15:41] <adiroiban> in letting translators know about various actions
[15:42] <adiroiban> dpm: we can just add the Ubuntu Translations Announcement RSS via to planet-ubuntu
[15:42] <adiroiban> dpm: we can just add the Ubuntu Translations Announcement RSS direclty to planet-ubuntu
[15:43] <dpm> that's a good point
[15:43] <dpm> I'd only have to have a look at how to do it :)
[15:43] <adiroiban> I don't know to much about how fridge works
[15:43] <dpm> but seems doable
[15:44] <adiroiban> dpm: all ubuntu member have access to planet.ubuntu.com config file
[15:44] <adiroiban> and RSS url is http://feeds.edge.launchpad.net/ubuntu-translations/announcements.atom
[15:44] <dpm> adiroiban, I know, but the ubuntu-translations project is not exactly a member :)
[15:44] <adiroiban> then we can look at the fridge :)
[15:45] <dpm> I'd have to ask around on what permissions and checks are made to feeds added to the config file
[15:45] <adiroiban> but debian package of the day
[15:45] <adiroiban> is not a member
[15:45] <adiroiban> same for Kubuntu feeds
[15:46] <dpm> adiroiban, I also think it's doable, I just would have to ask. I don't know right now if it's just a matter of adding the feed
[15:46] <adiroiban> ok
[15:46] <adiroiban> in planet.ubuntu.com
[15:46] <dpm> Anyway, just as additional info re: the Fridge, the news team publishes
[15:46] <adiroiban> we have a lot of announcement feeds from other Ubuntu teams
[15:47] <dpm> news people send to them
[15:47] <adiroiban> server / studio / screencast  / packaging / qa
[15:47] <adiroiban> ok
[15:48] <dpm> yes, this could be of course expanded. The RSS announcements from ubuntu-translations can only contain text
[15:49] <dpm> if we were to use a blog for the whole translations team or the Fridge, we could also post pictures and other content
[15:49] <adiroiban> I would start with small steps :)
[15:49] <adiroiban> and see the feedback
[15:50] <dpm> adiroiban, yeah, yeah :) I was just mentioning it
[15:50] <adiroiban> :p
[15:50] <adiroiban> but if there is a nice integration between a blog and LP teams
[15:50] <dpm> I think there isn't, but I'd have to check
[15:50] <adiroiban> we can use it :)
[15:50] <dpm> yep
[15:51] <adiroiban> we can look at Ubuntu server blog
[15:51] <adiroiban> and see how they manage it
[15:51] <adiroiban> ok
[15:52] <dpm> adiroiban, that would make for a good topic on the translations roundtable on UDS
[15:52] <adiroiban> :) if you say so :)
[15:52] <dpm> sure
[15:53] <adiroiban> I just want to make sure translators are aware of Ubuntu Translations annoucement
[15:53] <adiroiban> like the ubiquity string freeze
[15:53] <adiroiban> those are important announcements
[15:53] <dpm> anyway, for now I can look at adding the rss feed to p.u.c or directly publish the announcements on the Fridge
[15:54] <dpm> [ACTION] David to look at adding the ubuntu-translations rss feed to p.u.c or directly publish the announcements on the Fridge
[15:54] <MootBot> ACTION received:  David to look at adding the ubuntu-translations rss feed to p.u.c or directly publish the announcements on the Fridge
[15:54] <adiroiban> ok. If we agree to post announcment is a single place
[15:55] <adiroiban> the next step would be to add the feed in a public place
[15:55] <adiroiban> ok
[15:55] <dpm> adiroiban, I agree, but I still cannot see how this can be technically implemented
[15:55] <adiroiban> why ?
[15:55] <adiroiban> :p
[15:55] <adiroiban> or where do you see the problem
[15:55] <adiroiban> ?
[15:56] <dpm> which application would you use to write the announcement once and get it automatically published to the ML and p.u.c?
[15:56] <adiroiban> Launchpad
[15:56] <adiroiban> https://edge.launchpad.net/ubuntu-translations/+announce
[15:57] <dpm> adiroiban, which current LP feature would you use for that? AFAIK, we cannot automatically publish announcements there to the ML
[15:57] <adiroiban> as I workaround I will write a script for that
[15:58] <dpm> adiroiban, that was my question
[15:58] <adiroiban> and look into LP announcement code to also queue a message via email
[15:58] <adiroiban> ok
[15:59] <dpm> adiroiban, ok, but I think for now
[15:59] <dpm> it's just as easy as a woraround until such script is implemented, to:
[15:59] <dpm> 1) write the announcement on u-t
[16:00] <dpm> 2) copy the text and send an e-mail to the ML
[16:00] <adiroiban> yep
[16:00] <adiroiban> :)
[16:00] <dpm> A big improvement would be to additionally add the u-t feed to p.u.c
[16:00] <dpm> and I think that's something we could already look into
[16:01] <dpm> if it's as easy as adding the feed to the planet's config file
[16:02] <adiroiban> regarding planet.ubuntu.com, maybe we can ask for feedback from community-council
[16:02] <adiroiban> or you can ask your team for feedback :p
[16:02] <dpm> heh, yes, I can do that :)
[16:03] <dpm> [ACTION] David to talk to the Community team about translation feeds on p.u.c
[16:03] <MootBot> ACTION received:  David to talk to the Community team about translation feeds on p.u.c
[16:04] <dpm> ok, unless there are any other comments, let's have one last topic quickly, we're over time, but I think it is an interesting one
[16:04] <dpm> what do you say?
[16:05] <adiroiban>  :)
[16:05] <adiroiban> we can continue
[16:05] <happyaron> ok
[16:05] <adiroiban> uh... task ... that is one useful tag :)
[16:05] <dpm> [TOPIC] Current Translations tasks
[16:05] <MootBot> New Topic:  Current Translations tasks
[16:06] <adiroiban> https://bugs.edge.launchpad.net/ubuntu-translations/+bugs?field.tag=task
[16:06] <adiroiban> regarding kdelibs and other kde problems , I think we will talk at UDS
[16:07] <dpm> ok, let me add an action to remind us of that
[16:07] <adiroiban> same with APT. I think I will be in the same plane with mvo
[16:07] <adiroiban> and I will talk about apt / synaptic upstream translations
[16:08] <dpm> [ACTION] David to add kdelibs task to the Kubuntu UDS session
[16:08] <MootBot> ACTION received:  David to add kdelibs task to the Kubuntu UDS session
[16:08] <dpm> adiroiban, synaptic's upstream is now Ubuntu AFAIK
[16:08] <dpm> mvo is the maintainer
[16:08] <dpm> apt is still probably Debian
[16:08] <adiroiban> yep. so debian is not using synaptic ?
[16:09] <adiroiban> I don't know if mvo is exporting the LP translations into the synaptic source package
[16:09] <happyaron> adiroiban: AFAIK, yes, it is using
[16:10] <adiroiban> https://translations.edge.launchpad.net/ubuntu/karmic/+source/synaptic
[16:10] <dpm> adiroiban, we'd have to ask him if he's doing that, but we can just as well look at the bzr branch commits
[16:10] <adiroiban> better to look into commints
[16:10] <mvo> dpm, adiroiban: I'm not importing them automatically currently, I do import them if someone asks me
[16:10] <adiroiban> commits
[16:10] <adiroiban> :)
[16:11] <dpm> there you go :)
[16:11] <mvo> we should have a quick chat about it at the plane and/or uds :)
[16:11] <dpm> cool
[16:12] <mvo> I'm fine with moving synaptic to LP, apt is a bit different, debian is heavily involved in the translations there
[16:12] <mvo> but I got some questions myself, so uds is a good opportunity to discuss that :)
[16:12] <adiroiban> yep
[16:12] <adiroiban> no hurry
[16:12] <adiroiban> ‏‎next task bug 39581
[16:13] <adiroiban> hm...
[16:13] <adiroiban> :)
[16:13] <dpm> :)
[16:13] <adiroiban> https://bugs.edge.launchpad.net/ubuntu-translations/+bug/395812
[16:13] <dpm> ok, on the next task on the list, I've finally managed to contact the TB
[16:13] <dpm> regarding this, and I've created a page with all relevant information:
[16:14] <dpm> https://wiki.ubuntu.com/UbuntuTranslationsCoordinators/OngoingProjects/SwitchToRestricted
[16:14] <adiroiban> ok
[16:15] <happyaron> a question, if we turn to restricted, can people aren't in the respective translation teams make suggestions as well?
[16:15] <dpm> happyaron, that will only affect languages without a team assigned in the ubuntu-translators group
[16:15] <adiroiban> happyaron: everyone can make suggestions
[16:15] <happyaron> oh, I see, thanks
[16:16] <dpm> I'm sorry it's taking that long because it's been blocking on me, but I'll make sure it moves forward
[16:16] <adiroiban> ok
[16:16] <adiroiban> np
[16:17] <adiroiban> we have already talked about https://bugs.edge.launchpad.net/ubuntu-translations/+bug/455966
[16:17] <dpm> ok
[16:17] <adiroiban> next would be https://bugs.edge.launchpad.net/ubuntu-translations/+bug/395811
[16:18] <dpm> I haven't scheduled an extra session on that, but I think we could talk about this at UDS as well, and actually perhaps even bump the importance to High
[16:19] <adiroiban> the feedback is here https://wiki.ubuntu.com/Translations/TemplatesPriority
[16:19] <adiroiban> I think I will have to clean / format
[16:19] <adiroiban> the wiki page
[16:20] <adiroiban> and then set the priorities
[16:21] <dpm> adiroiban, yes, I know the page from the previous discussions. At the moment you are the only one working on that, and I think UDS will be a good chance to get together and get more people involved
[16:21] <dpm> in helping on that
[16:21] <adiroiban> ok
[16:22] <dpm> Anyway, I propose leaving the Wishlist items for a future discussion and end the meeting unless there are other comments or final points to discuss
[16:22] <adiroiban> yep
[16:23] <adiroiban> the new locale definitions are ok
[16:23] <adiroiban> for Chuvash I'm working with upstream developer to include it in glibc
[16:23] <happyaron> I think we can have a page on how to create new locale
[16:23] <happyaron> since I only have seen adiroiban working on that, and feel helpless myself
[16:23] <adiroiban> yep. I just wait to get more experience in working with locales
[16:24] <rustic_> hello, what do you think of Project Timelord? particularly, it states: the Launchpad Translations system is counter-productive to achieving the goal of a localized, human KDE experience"
[16:24] <adiroiban> and then I will try to write a wikipage / FAQ
[16:24] <happyaron> adiroiban: good, :)
[16:24] <dpm> happyaron, we've got https://wiki.ubuntu.com/Translations/KnowledgeBase/AddingNewLanguage, perhaps adiroiban can add more info on the experience he's gained on defining locales
[16:24] <adiroiban> rustic_: I think we can talk about that in #ubuntu-translators
[16:24] <adiroiban> I don't know anything about that project
[16:25] <rustic_> okay
[16:25] <adiroiban> and no aware of any discussion on ubuntu-translators mailing lists
[16:25] <dpm> rustic_, for the record, here are my thoughts -> https://lists.ubuntu.com/archives/kubuntu-devel/2009-November/003481.html
[16:25] <adiroiban> dpm: rustic_ do we have a link to the project ?
[16:25] <happyaron> adiroiban: kubuntu.org announcement
[16:25] <dpm> adiroiban, I CC'd ubuntu-translators, did you not get the e-mail?
[16:26] <adiroiban> but that is vague
[16:26] <adiroiban> dpm: I got that email
[16:26] <happyaron> adiroiban: there is a detailed PDF you can read
[16:26] <adiroiban> but I don't know how to put those info into context
[16:26] <dpm> anyway, let's finish the meeting and move this discussion to #ubuntu-translators
[16:26] <adiroiban> ok
[16:26] <happyaron> ok
[16:26] <dpm> Thank you everyone for your participation
[16:27] <dpm> and see you on the next one! :)
[16:27] <adiroiban> rustic_: please join #ubuntu-tranlators
[16:27] <adiroiban> yep
[16:27] <dpm> #endmeeting
[16:27] <MootBot> Meeting finished at 10:27.
[21:50] <bodhi_zazen> Technoviking: poke =)
[21:50] <jdong> ok i'm gonna take 10 minutes at the start of the meeting to grab some food
[21:51] <bodhi_zazen> I have an unexpected meeting today, I will miss the FC meeting, although if it goes long enough I may be back
[21:51] <Technoviking> owie
[21:51] <bodhi_zazen> 'lo jdong
[21:51] <jdong> but I'll have my iPhone on me
[21:51] <jdong> which gets IRC highlights pushed instantly
[21:51] <jdong> so I won't be terribly gone ;-)
[21:52] <bodhi_zazen> I just wanted to introduce the T&E team and it seems there is general agreement to close the 64 bit forum
[21:52] <bodhi_zazen> I am neutral on a video drier forum, tending to -1
[21:52] <Technoviking> do we have concenous on the #ubuntuforum irc
[21:52] <bodhi_zazen> and that is all that is on the agenda =)
[21:53] <bodhi_zazen> we are I think 1 shy at the moment
[21:53] <jdong> Technoviking: I think we're just missing input from Ryan
[21:53] <jdong> which I'd like to hear before sending out a reply
[21:53] <bodhi_zazen> gotta run, sorry =(
[21:54] <Technoviking> jdong: sounds good
[21:54] <Technoviking> bodhi_zazen: later
[21:54] <jdong> bodhi_zazen: see ya
[21:58] <jdong> ok, be back in 10 minutes.
[21:58] <Technoviking> ok
[22:04] <Technoviking> any ome else here for the Forums council meeting, we will start in a few
[22:10] <jdong> ok I have returned :)
[22:10] <Technoviking> think it is just us
[22:10] <jdong> sure looks that way
[22:10] <jdong> *looks at agenda*
[22:11] <jdong> of everything on the agenda, I think the only thing trivial that we can do with the turnout is close the 64-bit forum?
[22:11] <jdong> in the staff forum we've got pretty much universal consensus on that
[22:12] <Technoviking> An announcement has been posted and and 64 bit prefix have been added
[22:12] <jdong> *nods*
[22:12] <Technoviking> anyone else want to comment about this?
[22:14] <Technoviking> very good, I'm glad to see 64 bit is close enough to 32 bit that it does not need to be separate anymore
[22:15] <jdong> yeah, I am too
[22:16] <Technoviking> Anything else we can discuss?
[22:16] <jdong> I don't suppose TormodVolden is around to talk about the video driver forum...
[22:16] <Ms_Angel_D> Hello, I came to represent the T&E Team
[22:17] <jdong> ok I'm reading the pastebin right now
[22:18] <Ms_Angel_D> actually jdong we have this https://wiki.ubuntu.com/forestpixie/Sandbox
[22:18] <jdong> ah very nice; that should be added to the wiki replacing the pastebin
[22:20] <jdong> I'm generally positive on the idea
[22:21] <Ms_Angel_D> After many conversations the wiki represents what we as a group feel could help the issue's presented
[22:21] <jdong> but unfortunately I don't believe the council has enough of a presence to make decisions on it this meeting...
[22:21] <Ms_Angel_D> I understand jdong
[22:21] <Ms_Angel_D> I just wanted to float it out there
[22:22] <Technoviking> Ms_Angel_D: We will forward the link to them and get the discussion going
[22:22] <Ms_Angel_D> Thank you very much Technoviking
[22:25] <Technoviking> I have not heard from anyone else, should we call it
[22:26] <jdong> yeah, I agree
[22:26] <jdong> thanks for coming, Ms_Angel_D
[22:26] <jdong> hopefully we'll have a more lively turnout next time :)
[22:27] <Ms_Angel_D> Thanks for listening jdong, Technoviking
[22:27] <jdong> our pleasure
[22:27] <Ms_Angel_D> I understand ;)
[22:27] <Technoviking> Ms_Angel_D: thanks for coming
[22:27] <Ms_Angel_D> :D
[22:35] <bodhi_zazen> back =)
[22:35] <jdong> lol just a tad too late :)
[22:36] <bodhi_zazen> sorry about that ;)
[22:38] <bodhi_zazen> is there anything we really needed to decide ?
[22:41] <Technoviking> not now, we should vote on the video forum on the list, I feel it is a -1 for me
[22:42] <bodhi_zazen> -1
[22:43] <bodhi_zazen> I feel it is best in the current sections, it is very hardware specific