[00:41] <ScottL> falktx, what do you envision -controls doing?
[01:13] <ScottL> falktx__, what do you envision -controls doing?
[01:14] <ScottL> would this be like cadence and control studio usage?
[01:14] <falktx__> ScottL: yes
[01:14] <ScottL> what about helping users set up (or tune) their systems like ailo would like?
[01:14] <ScottL> i would like it to also control installing and removing work flows as well
[01:15] <ScottL> or at least assist doing that
[01:15] <falktx__> ScottL: yes, I plan to do most of that
[01:16] <ScottL> oh good !
[01:18] <falktx__> ScottL: I was looking for a list of features to do
[01:20] <ScottL> that's about all i can think of at this time
[01:20] <falktx__> adding/removing worksflows seems like a nice option
[01:21] <ScottL> i think that and the set up are the best for the use case where people want to use a ubuntu install for studio work
[01:21] <ScottL> makes sure they have the right kernel and are in the audio group (and creates it if necessary)
[01:22] <falktx__> yep, system checks
[01:28] <ScottL> knome, when you get back can we talk about website update?  i would like to talk to you and stochastic to clear up a plan of action
[01:28] <ScottL> falktx__, i talked to some people about how edubuntu and kubuntu website pull information from wiki.ubuntu.com
[01:28] <ScottL> i think that is the 'iframe' stuff you were talking about
[01:29] <ScottL> after we get the website implemented we might look into that for adding the user documentation to the website
[01:29] <falktx__> cool
[04:38] <stochastic> hey everyone what's the current suggested xfce theme to start building upon
[04:39] <stochastic> or what are the contenders?
[04:39] <holstein> stochastic: greybird
[04:54] <stochastic> holstein, has a particular Ubuntu Studio set been started anywhere?  bzr or anything?
[04:54] <holstein> stochastic: i dont think so
[04:55] <holstein> i wanted to go to greybird, and put our old wallpaper in
[04:55] <holstein> and if we get to more at some point, great! :)
[04:55]  * stochastic recalls there was a recent e-mail suggesting a darker theme...
[04:55] <holstein> stochastic: it was more of a fight
[04:55] <holstein> about whats too dark
[04:55] <holstein> greybird is darkish, without messing things up
[04:56] <stochastic> okay
[04:56] <holstein> stochastic: we have a plymouth theme to put in somewhere too
[04:57] <stochastic> holstein, where is that?  or do you mean we need to build one too?
[04:58] <holstein> stochastic: ScottL said we already had one made
[04:58] <holstein> stochastic: and im not sure where that stuff is
[05:02] <stochastic> gotcha
[05:43] <stochastic> holstein, I notice greybird isn't even packaged yet
[05:43] <stochastic> or am I not seeing it?
[05:44] <holstein> stochastic: should be... im using it in xubuntu 11.10
[05:44] <holstein> not sure how things work though
[05:45] <holstein> madnick might know
[05:45] <holstein> or knome 
[05:48] <stochastic> there is a ppa listed on the site
[05:48] <stochastic> but when I apt-cache search for greybird I get nothin'
[05:49] <holstein> stochastic: me too
[05:49] <holstein> so its gotta be some other package
[05:49] <holstein> default-themes
[05:50] <holstein> xubuntu-themes
[05:50] <holstein> something like that maybe?
[05:50]  * stochastic will look
[05:50] <micahg> I think it's in murrine-themes
[05:53] <stochastic> that it is.
[05:54] <stochastic> perfect.
[10:55] <knome> stochastic, greybird is in murrine-themes
[10:55] <knome> right, somebody answered that already :)
[10:56] <knome> for the darker version: https://github.com/shimmerproject/Blackbird (very WIP)
[10:56] <knome> it's been worked on by ochosi and DAZ1 now
[10:56] <knome> ScottL, sure, go ahead
[11:57] <ScottL> knome, stochastic: i wanted to make sure progress continues on the ubuntustudio website
[11:57] <ScottL> stochastic, are you still waiting for me to review the rest of the website?
[11:58] <ScottL> stochastic, the changes that i suggest in the blueprint spec, can you do those or do you need knome 's input?
[12:00] <ScottL> look at "website content", first image:  https://wiki.ubuntu.com/UbuntuStudio/update-website-spec
[12:00] <ScottL>  
[12:01] <ScottL> stochastic, what are you concerns about social media on the website?  don't think we need any at all?  want to only support open ones (i.e. not twitter, etc)?
[12:03] <ScottL>  
[12:04] <ScottL> as far as the changes i suggested, i'm not sure i can some/most/any/all of them but i also didn't want to move unilaterally and wanted some feedback at least from you two, stochastic, knome 
[12:04] <ScottL> "note sure i can MAKE some/most/any/all"
[12:05] <ScottL> basically i'm pretty sure it would take me a while to make significant changes to make changes to borders or padding or whatever required for minimizing vertical height
[12:06] <ScottL> and at this point i am unsure that i know how to add a "Blog" menu item on the front page and then make the additional page for it :P
[12:07] <ScottL> i'm sure i could figure it out but probably either of you could do it much, much faster ;)
[12:21] <knome> blog menu item in the tabs, or just in the top navigation?
[13:07] <ScottL> knome, i was going for something like the first image under "website content" section:  https://wiki.ubuntu.com/UbuntuStudio/update-website-spec
[13:14] <ScottL> sorry, trying to get kids ready for school/daycare right now as well
[13:20] <ScottL> knome, to be more explicit, i don't want to make all these changes at this time, i was hoping for feedback, if none is coming then i suppose we will move forward then
[13:21] <ScottL> i think stochastic was going to email the list with his concerns over social media on the website
[14:21] <len_> Re: social media - I personally find it annoying.
[14:22] <len_> I don't use it. 
[14:23] <astraljava> FB was annoying, G+ works okay-ish.
[14:33] <holstein> len_: morning!
[14:34] <holstein> astraljava, len_, stochastic, ScottL
[14:34] <holstein> i agree with jussi that it should be opt in
[14:34] <holstein> i dont think that is optional
[14:34] <holstein> i think it should be something that the 'purist' can easily ignore/tolerate
[14:35] <holstein> i also dont think it would be out of place to have a note "why is an open project using closed avenues like FB and G+?... to reach and recruit users in the mainstream"
[14:36] <holstein> i can go either way on it really because i can see and appreciate both arguments
[14:36] <holstein> i know i have actually seen and reponded to some questions on twitter
[14:39] <len_> Is there an overhead to maintain/generate the extra content?
[14:40] <holstein> len_: resource-wise?
[14:40] <len_> People wise
[14:40] <holstein> i mean, i think we can handle making the embeddables or whatever
[14:40] <holstein> i think it depends on just what all in entails
[14:40] <holstein> len_: thanks for actually testing that iso and reporting in such detail
[14:40] <len_> Does every website update eqire something sent  or added ?
[14:41] <holstein> i would give it a week or so at least before trying again
[14:41] <len_> No peroblem
[14:41] <holstein> len_: theres an email i get that talks about what is broken
[14:41] <len_> There are dialy reports but the site still shows the no7 build
[14:41] <holstein> let me see if i can figure out how to get you that
[14:42] <holstein> len_: it might not build if there are errors?
[14:42] <len_> I get the daily build repot
[14:42] <holstein> im still not 100% on how it all works
[14:42] <holstein> len_: OK... cool :)
[14:42] <holstein> the watson report... i read it like the NYtimes ;)
[14:43] <holstein> len_: you mean, will every site update be this intense?
[14:43] <holstein> depends on what we are doing i think
[14:43] <len_> Hmm I am thinking I can ty changing the options to install everything even with erors to see what else is wong. the daily build report did not mention the ubuntu 1 thing
[14:43] <holstein> AFAIK simple content edting will be easy
[14:45] <jussi> holstein: which cms are you using(if at all) ?
[14:45] <len_> CMS?
[14:46] <jussi> Most CMS's have twitter and other feed plugins
[14:46] <jussi> len_: content management system - aka drupal, joomla et al
[14:46] <holstein> jussi: we're doing to have drupal?
[14:46] <holstein> pretty sure its drupal
[14:46] <jussi> holstein: Ive no idea, Im asking? 
[14:46] <len_> Not, I do hand coding of my html
[14:46] <holstein> knome: thats correct?
[15:00] <len_> oops, sorry for interupting, Just realized I was answering questions dirrected at someone else. Not used tom this yet.
[15:01] <knome> it's wordpress
[15:03] <knome> and yeah, there is plugins for twitter for wordpress
[15:03] <knome> ..but all those need to go through canonical IS review :P
[15:20] <scott-work> good morning (again)
[15:20] <madnick> morning :)
[15:24] <holstein> i just knew it wasnt joomla ;)
[15:29] <scott-work> holstein: what wasn't joomla?
[15:31] <scott-work> oh and holstein, do you have time to line a few things out for the blueprints with me today?  this morning or afternoon?
[18:56] <scott-work> question for anyone who would like to answer (and i really would like feedback on this)
[18:56] <scott-work> i've been thinking long term about goals for ubuntu studio
[18:57] <scott-work> i will be extremely happy to share my thoughts on this with this group later when i have it firmed up and in a presentable form, however...
[18:57] <scott-work> do you think it will be beneificial to share this also with the community at large?
[18:58] <astraljava> But of course. Transparency will be welcomed, even though it will generate a lot of debate. But in the end, being open will be welcomed.
[18:58] <astraljava> That came out really bad, but I hope you get the picture.
[18:59] <knome> astraljava, try to behave the next time scott asks you something
[19:00] <astraljava> knome: I think he knows better not to ask me anything anymore.
[19:00] <astraljava> But I keep responding. I'm like that.
[19:01] <knome> :(
[19:02] <astraljava> Did I forget the smileys? Silly me.
[19:02] <scott-work> lols
[19:02] <scott-work> well, i suspect i really had a different question in my mind than the one i really asked
[19:03] <scott-work> astraljava: i welcome your comments, there are insightful and extremely useful :)
[19:03] <astraljava> I doubt it, but hey, who's counting.
[19:04] <scott-work> i suspect what i really meant to ask would be, "would it increase confidence in the distribution and encourage involvement if we present a comprehensive road map with staged goals and required task per goal?"
[19:04] <scott-work> i stress the "encourage involvement" part
[19:04] <scott-work> and perhaps "staged" would be more explantory as "scheduled"
[19:05] <astraljava> Again, I would say absolutely. We discussed about this with jussi the other day. People are much more likely to take on a task that's specified, than coming around and being pointed at the repository or, say, the wiki, and asked to "be helpful".
[19:05] <jussi> ++
[19:08] <astraljava> Naturally there needs to be the people with the initiative, but most of the contributors don't have the vision.
[19:09] <scott-work> jussi: why did you type "++"?
[19:10] <scott-work> i've seen this before from someone else and wondered about this
[19:10] <falktx__> ++
[19:10] <jussi> scott-work: means I agreed with the last comment
[19:10] <jussi> like $comment - plus plus to that.
[19:11] <scott-work> astraljava:  "more likely to take on a task that's specified"  that's why i did this page:  https://wiki.ubuntu.com/UbuntuStudio/ContributeToDevelopment
[19:11] <scott-work> i'm going to finish another page first then i'll post to the list about it
[19:11] <astraljava> Sounds good.
[19:11] <scott-work> jussi: i've only seen it as "+1" so far
[19:12] <astraljava> scott-work: That's like +1, but a traditional coding convention.
[19:14] <scott-work> oh, this is a python thing, isn't it?  ++ to add one
[19:16] <astraljava> Works in C/C++ and probably in lots of others as well.
[19:16] <astraljava> Java, perl etc.
[19:19] <scott-work> having done the blueprints for this cycle ties into my nature to organize and plan and i've been inspired to collate my generalized and random thoughts for improving ubuntu studio
[19:20] <scott-work> i believe a natural delineation between tasks exists and i want to further this concept into a more structured plan
[19:21] <scott-work> what i would like to find at some point is a way to graphically convey this information as well, although i would rather not resolve to a static chart made in inkscape
[19:21] <scott-work> it would be nice if there was an online tool to do this
[19:22] <scott-work> i should note that i am speaking about using something other than launchpad as it doesn't seem to have the graphical conceptual presentation that i would like
[19:28] <astraljava> Hmm... I dunno, have to think about that. I'm sure some exist, but probably most of them aren't free.
[19:30] <scott-work> dont worry about it right now astraljava, i've got some more thinking to do ;)
[19:34] <astraljava> Sure.
[20:01] <holstein> scott-work: hey!
[20:01] <holstein> i was trying to tell jussi what CMS the site was on earlier... thats what the joomla comment was about
[20:02] <scott-work> oh crap, i don't remember what i pinged you about :P
[20:02] <holstein> i had forgotten it was wordpress
[20:02] <holstein> anyways...
[20:02] <holstein> scott-work: im eating dinner, but i can look at some things
[20:02] <scott-work> oh, yeah, reading backscroll it seems it was about the blueprint stuff
[20:02] <holstein> and im home in a bit for probably a few hours before rehearsal
[20:02] <scott-work> eat dinner, i'll catch you in a few holstein 
[20:04] <astraljava> Dinner? Isn't it late lunch-time for you?
[20:04] <scott-work> holstein: when you get back look at : https://blueprints.launchpad.net/ubuntustudio/+spec/other-p-ubuntustudio-misc-improvements
[20:05] <scott-work> i would like you to lead the multi-head tasks please
[20:05] <scott-work> i'll be happy to help with documenting it since i know you generally do not like wiki stuff
[20:05] <holstein> cool
[20:06] <scott-work> but i also wanted to discuss use cases with you about multi-head
[20:06] <holstein> right now, im thinking arandr and the included tool
[20:06] <holstein> theres not really one thing to do both mirroring and cloneing
[20:06] <scott-work> so, let's say currently we can think of two use cases 1) spanning the desktop across multiple monitors and 2) cloning for use with a projector
[20:07] <holstein> arandr looks really nice too
[20:07] <holstein> simple, clean
[20:07] <scott-work> i wouldn't think #2 would be a very common use case for us, but i do think that #1 is
[20:07] <scott-work> and you are suggesting we use arandr for #1?
[20:07] <holstein> and, this would be easy for us too
[20:07] <holstein> just add arandr and we're done
[20:07] <holstein> make some documentation
[20:08] <holstein> scott-work: right
[20:08] <scott-work> cool :)  has this been testing with ait and radeon cards?
[20:08] <scott-work> err, ati
[20:08] <holstein> scott-work: nah
[20:08] <astraljava> scott-work: With laptops getting more powerful all the time, I could see someone using Studio on one that is sometimes connected to a projector at times.
[20:08] <holstein> nvidia is going to be the hassle i think
[20:08] <holstein> i can test ati easy enough
[20:08] <astraljava> Then again, I always like to use separate desktops in those cases as well.
[20:09] <holstein> for me, i dont mind the spanning on the projector as well
[20:09] <holstein> thats my preffered way of connecting
[20:09] <scott-work> astraljava: i was thinking that too but i wonder if we should start simple
[20:09] <holstein> but, i think we should support both since we can
[20:09] <astraljava> ++
[20:09] <holstein> all of this stuff comes down to hardware though at some point
[20:09] <scott-work> holstein:  is the setup automatic for you? or did you have to go to the menu and start 'arandr'?
[20:10] <holstein> i mean, if an ati card or nvidia is not supported, theres nothing we can add to fix that
[20:10] <holstein> scott-work: i started it
[20:10] <scott-work> i think i used the ati or radeon driver to do mine actually
[20:10] <astraljava> I have to use xrandr, forgot to test arandr, sorry.
[20:10] <holstein> astraljava: no worries
[20:10] <scott-work> holstein: "ati or radeon card not supported" but we shoudl test this and document it for the users so they don't bang their heads trying to get it to work though
[20:10] <holstein> i dont have my nvidia hardware moved yet
[20:11] <holstein> and i have to install xubuntu on the ati hardware i have
[20:11] <holstein> scott-work: yeah... its challening
[20:11] <holstein> gets into why is it not supported?
[20:11] <holstein> i mean, it works
[20:11] <holstein> everything on our end works
[20:11] <scott-work> i wonder if having a card with digital and analog vs two digitial outputs generates different results as well
[20:12] <holstein> scott-work: i know some folks locally with hdmi, but i think thats even more scarry depending on driver support
[20:12] <scott-work> ooh, yeah, i don't want to get into that right now ;)
[20:13] <scott-work> astraljava: do you have an radeon card?
[20:13] <holstein> we could just have a general statement about non-supported hardware, and who's 'fault' that is
[20:13] <scott-work> i wonder if falktx has one?
[20:13] <scott-work> holstein: absolutely
[20:13] <holstein> we could link to those support addresses for nvidia
[20:13] <holstein> maybe get some acutal feedback where it should be going
[20:14] <holstein> that can be down the road
[20:14] <holstein> im just saying... we cant test every case.. as long as the overall process is sound
[20:14] <astraljava> scott-work: I do, if I get the laptop to switch to it. It now goes to use the integrated intel GPU by default.
[20:14] <holstein> and we are doing all we can to provide support...
[20:14] <astraljava> scott-work: I also have nVidia on the desktop.
[20:19] <scott-work> holstein: well, i suppose where i am going with this is...
[20:20] <scott-work> can you please lead this while doing a good cross section of testing so we know what to expect
[20:20] <scott-work> i'll be happy to test any specific test cases you would like, i can check which hardware i have available
[20:21] <scott-work> and if you can summarize what packages we should use, the testing results, and how to set it up i will be happy to document it all in the wiki
[20:21] <holstein> scott-work: sure
[20:22] <holstein> i think next week i can suggest a plan
[20:22] <holstein> right now im leaning towards the included too, and arandr
[20:22] <scott-work> i have a lot of other tasks falling on me (live dvd, ubiquity patch, website stuff, probably theme as well) so this is something i would really like someone else to direct
[20:22] <holstein> and labeling arandr well in the menu
[20:22] <scott-work> good :)
[20:22] <holstein> i still say for the theme..
[20:23] <holstein> right now, put that login theme, and our old wallpaper in
[20:23] <astraljava> scott-work: We can discuss in the meeting about sharing your load a bit, I still haven't looked at them at all, assigning-wise.
[20:23] <holstein> and just greybird or whatever
[20:23] <holstein> and be done for now
[20:23] <holstein> if we get to more, great
[20:23] <holstein> if not, that'll do
[20:23] <scott-work> holstein:  there is more to it than that, we need to integrate those things into our bzr branche and packages
[20:23] <scott-work> and there isn't necessarily a 1:1 match
[20:23] <holstein> great
[20:23] <scott-work> so it's not necessarily a drop in replacement
[20:24] <scott-work> i'm not saying there isn't, but no one has looked yet
[20:24] <scott-work> (i don't think)
[20:24] <holstein> can we just take what xubuntu has? and drop the panel and add our wallpapre?
[20:24] <holstein> drop the bottom panel*
[20:24] <scott-work> i think that is an agreed approach, at least in some small circles
[20:24] <scott-work> although i'm not sure we should drop the bottom panel, is it?
[20:24] <holstein> depends
[20:24] <holstein> whatever is easy
[20:25] <holstein> its not right for us as-is
[20:25] <holstein> and we've never had one
[20:25] <holstein> so, i was thinking it would be easy to just drop it at first, and if we get to workflows down there, thats gravvy!
[20:25] <holstein> wavvy gravvy
[20:39] <scott-work> i've been thinking about priorities and my involvement
[20:40] <scott-work> i was really, really thinking of completing some misc. documentation and my involvement in the website by end of next week to focus on the theming
[20:41] <scott-work> alpha 1 is dec 1st, i was hoping to have the theming done before that
[20:41] <scott-work> we are waiting on the kernel crew for the -lowlatency bit (i plan to poke them shortly after alpha 1)
[20:41] <scott-work> and we can slot the livedvd and ubiquity patch for before alpha 2 then
[20:42] <scott-work> i was secretly hoping falktx would do the bulk of the work on the theming issues (theme, ui, icons, lightdm) because he is alreay pretty knowledgeable about them
[20:43] <scott-work> but i don't know that he will be available before alpha 1
[20:43] <scott-work> ochosi has volunteered to help with the transition from the xubuntu-devel team
[20:57] <astraljava> scott-work: I need to pick up the slack and get done with the testing documentation I didn't do last cycle, but I can add some other tasks as well.
[20:57] <scott-work> astraljava: which testing documentation was that?  i'm doing some stuff already
[20:58] <holstein> yeah... i like that time frame on the theme
[20:58] <astraljava> scott-work: The stuff we talked about copying from Xubuntu. Dailies, milestones etc.
[20:58] <scott-work> my overarching goal was to develop an infrastructure of docuement to transition people into helping us with testing
[20:59] <scott-work> all in an effort to reduce our work load throughout the cycle
[20:59] <astraljava> Yep, that's what I'm talking about as well.
[20:59] <scott-work> a persistant place that acts as a repository of knowledge so that when people leave, others can easily come in and assist as well
[21:00] <scott-work> astraljava: okay then, tomorrow i will have a broad outline to you about my thoughts on it then and we can collaborate and get it done twice as fast ;)
[21:00] <astraljava> scott-work: Sounds like a plan.
[21:04] <scott-work> i was parsing some of the documentation efforts that i would like to accomplish so that this cycle we were addressing documentation that might benefit our development
[21:05] <scott-work> astraljava: can you think of any other documentation that might reduce our work load or benefit us in any other ways?
[21:05] <scott-work> i dont' really want to touch user documentation for this cycle, perhaps start it later in the cycle if our scheduled tasks are done
[21:10] <astraljava> scott-work: I'll look up the dailies spreadsheet we used for Xubuntu last cycle.
[21:16] <astraljava> You should have mail.
[21:33] <scott-work> astraljava: what does the red cells mean in that spreadsheet?
[21:40] <astraljava> scott-work: They were used to indicate which tests Charlie wanted us to concentrate on that day.
[21:40] <scott-work> ah, okay
[21:40] <astraljava> So we didn't have to stress about doing them all each and every day.
[21:45] <scott-work> that certainly makes sense
[21:45] <scott-work> i'm surprised at the robustness to test the dailies everyday
[21:45] <scott-work> i'm not sure we can provide that level of testing
[21:48] <astraljava> We don't have to, at least outside of milestones approaching.
[21:48] <astraljava> But we can use that as an example.
[22:28] <scott-work> astraljava:  do have you a minute to discuss the purpose of the wiki page(s) for ubuntu studio testing?
[22:28] <scott-work> i suppose this defines the scope and maybe the philosophy of what you and i want to accomplish
[22:37] <astraljava> Sure.
[22:40] <scott-work> astraljava: do you have a brief minutes to discuss our goal for the ubuntu studio testing wiki page(s)?
[22:41] <scott-work> this would be an almost philosophical discussion i suppose
[22:42] <astraljava> Yep, I'm free now.
[22:43] <scott-work> good
[22:43] <scott-work> here's my thoughts
[22:44] <scott-work> i don't know that we need to expansively define what testing is or all the testing that _could_ be done
[22:44] <scott-work> my thoughts have been that we should frame this as getting people to help us with important testing, not all testing
[22:44] <scott-work> i.e. the qa iso testing
[22:44] <scott-work> be very specific to minimize our time spent on the documentation that will hopefully generate the most return
[22:45] <scott-work> also, to just get it done :)
[22:45] <scott-work> that's about it as far as purpose or philosophy at this point
[22:45] <scott-work> astraljava: what did you envision?
[22:46] <astraljava> Well, there's a lot of docs out there about what testing is about. We'd probably just wanna specify the things important for our derivative specifically.
[22:47] <astraljava> I agree that just a few of us can do dailies or on-demand testing when we know something has just changed, that's probably affecting us.
[22:48] <astraljava> But get more people involved with ISO testing when milestones are approaching.
[22:48] <scott-work> astraljava: also considering that we would be asking people unfamiliar with some aspects of ubuntu studio, we should not ask them to do dailies IMO
[22:48] <astraljava> Yeah, that's too heavy a burden, and quite frankly, not that interesting.
[22:48] <scott-work> we should try to focus their efforts to the milestone testing
[22:48] <scott-work> yeah, they get to test and go to a soon to be updated website to log their results :)
[22:49] <astraljava> I just got a spare HD for dailies, so I can take a lot of that on me.
[22:50] <scott-work> so do you feel okay with the immediate wiki page to focus on people not currently involved helping with qa testing?
[22:50] <astraljava> I'm not that keen on virt, even though I acknowledge the speed advantage they give us.
[22:50] <astraljava> Yep, seems to me we're on the same page here.
[22:51] <scott-work> good
[22:51] <scott-work> :)
[22:51] <scott-work> i wouldn't mind other documentation and threading this one so it would fit within a larger structure
[22:51] <scott-work> "other documentation" = other testing documentation
[22:52] <scott-work> but i am unsure how that would affect this particular documentation for new users doing qa testing
[22:52] <scott-work> most likely the audience would remain the same even if we had other documentation for testing i suppose
[22:55] <astraljava> Yeah. And I don't think we need to re-invent the wheel there. We can point to already existing ones, and encourage people to ask if they find something puzzling or whatever.
[22:55] <scott-work> oh yeah, i definitely agree
[22:55] <scott-work> but i did kinda want to do some very low level explanation as well
[22:55] <astraljava> Just get the certain Studio-specific cases there, that are important for our work flows.
[22:55] <scott-work> stuff like...
[22:55] <scott-work> * purpose of qa testing
[22:56] <scott-work> * contrast against dailies
[22:56] <scott-work> * links to qa website and daily images
[22:56] <scott-work> * methods of testing (i.e. vm or iron)
[22:56] <scott-work> there are other things, but i think most of these can be one sentence descriptions
[22:57] <scott-work> but i defintely want to link to other pieces of information for the testers
[22:57] <astraljava> I don't think we should even confuse anyone doing QA ISO testing with the daily concept at all. Maybe explain the difference elsewhere, if needed.
[22:57] <scott-work> oh, oh, oh...maybe we can tie this in with stochastic 's -testers team
[22:58] <scott-work> astraljava: hmmmmm, that is a good point
[22:58] <astraljava> Yeah, that sounds wiser.
[22:58] <scott-work> i know that i found the two confusing and didn't understand their purposes and wanted to contrast them in a very topical manner
[22:59] <scott-work> but if we are considering having complimentary documentation then i agree that we don't need to mention it here and it would confuse things
[23:00] <astraljava> I agree it's important to make the distinction, but to the people who we only point to the QA ISO testing pages, they shouldn't need to know about it, until (and only if) they become interested about further contributing.
[23:06] <scott-work> agreed
[23:06] <scott-work> or...
[23:06] <scott-work> ++
[23:06] <scott-work> ;)
[23:06] <scott-work> okay, getting ready to go home, talk to you later :-)
[23:06] <astraljava> Alrighty.