[03:36] <pep> good night
[03:36] <Flannel> night pep.  See you tomorrow.
[08:01] <meoblast001> sweet
[08:01] <meoblast001> hi ppl
[08:02] <Flannel> Howdy meoblast001 
[08:02] <meoblast001> ok
[08:02] <meoblast001> i have ideas
[08:02] <meoblast001> i've been supporting this since forever and just learned a team for this exists today
[08:02] <meoblast001> i has skills
[08:03] <meoblast001> music
[08:03] <meoblast001> animation
[08:03] <meoblast001> web design
[08:03] <meoblast001> can i be in?
[08:03] <Flannel> meoblast001: yes
[08:03] <meoblast001> sweet
[08:03] <meoblast001> =D
[08:03] <meoblast001> Flannel: is there a special mini-site or something yet?
[08:04] <meoblast001> i also have 3D modeling skills
[08:04] <Flannel> meoblast001: mini site?
[08:04] <meoblast001> like
[08:04] <meoblast001> a marketing site or something
[08:04] <Flannel> meoblast001: https://wiki.ubuntu.com/MarketingTeam
[08:05] <meoblast001> im there right now
[08:05] <meoblast001> i'd like to start up a mini-site
[08:05] <meoblast001> something thats like.... uhhh
[08:05] <Flannel> what is a mini site?
[08:05] <meoblast001> how do i explain this
[08:05] <meoblast001> i'll give you an example of a minisite
[08:06] <meoblast001> hmm
[08:06] <meoblast001> sytrus mini-site must have been closed
[08:06] <meoblast001> cant use that as an example
[08:07] <meoblast001> Flannel: a minisite is usually done in Flash and tells you the basics of a project or product.... it throws out the most important details and is usually full of clean looking eyecandy to make the visitor think "thats professsional"
[08:09] <meoblast001> welcome
[08:10] <meoblast001> Flannel: do you want to hear some of my musical work or see some of my web/animation work?
[08:11] <Flannel> meoblast001: That's not necessary, but you can share if you'd like.
[08:11] <meoblast001> Flannel: ok... ill show you my breakbeat i made for the next release of Nexuiz
[08:13] <meoblast001> Flannel: http://www.fileden.com/files/2007/3/19/904700/theheartofinsanity.mp3
[08:13] <meoblast001> dang it
[08:13] <meoblast001> nevermind
[08:14] <meoblast001> thats the old one.. the not good one
[08:14] <meoblast001> Flannel: here http://www.fileden.com/files/2007/3/19/904700/thebeastofinsanity.mp3
[08:15] <meoblast001> Flannel: webdesign and my old animations are at www.mysticgalaxies.com
[08:15] <meoblast001> i can animate better now
[08:22] <meoblast001> Flannel: did you look at those?
[08:23] <Flannel> Yep
[08:23] <meoblast001> what do you think
[08:23] <meoblast001> i want to make something more suddle for any Ubuntu stuff
[08:24] <Flannel> sounds good
[08:29] <meoblast001> Flannel: ive never been good at slow music though
[08:31] <meoblast001> i just made a sweet begining to a song
[08:53] <meoblast001> well im out
[08:54] <meoblast001> time to go to bed
[08:54] <Flannel> night meoblast001
[10:08] <meoblast001> hi
[10:08] <meoblast001> is anyone available right now... i have a sweet idea
[10:15] <elkbuntu> for what?
[10:20] <meoblast001> elkbuntu: i have an idea
[10:20] <meoblast001> elkbuntu: i printed off all the Ubuntu flyers, and next year im gonna give them all to my comptuer teacher and hope it goes up to administration
[10:20] <meoblast001> i have a small school so its worth a shot
[10:24] <elkbuntu> meoblast001, it's also worth writing letters to the politicians in your local area :)
[10:24] <meoblast001> elkbuntu: should i get edubuntu or ubuntu?
[10:24] <elkbuntu> meoblast001, depends on the current setup
[10:25] <meoblast001> of our school?
[10:25] <meoblast001> our school runs mainly IBM's with Windows XP Professional
[10:25] <elkbuntu> as thin clients?
[10:26] <meoblast001> elkbuntu: whats a thin client?
[10:26] <meoblast001> oh dang it
[10:26] <meoblast001> i have a question
[10:27] <elkbuntu> networked computers that dont have harddrives of their own
[10:27] <meoblast001> our computer has this big hard disk everyone knows of as the Z drive...... it basically stores all users stuff
[10:27] <meoblast001> and all users are on that
[10:27] <meoblast001> and yes... the computers have harddisks
[10:27] <meoblast001> but they clean them all off every night
[10:29] <meoblast001> elkbuntu: is that possible?
[10:30] <elkbuntu> sure. but then we get into technical aspects and this is a marketing channel
[10:30] <meoblast001> yeah
[10:30] <meoblast001> elkbuntu: one other question
[10:31] <meoblast001> elkbuntu: my school uses a web filter known as bess and a remote monitoring program that monitors all computers... is that possible
[10:31] <elkbuntu> sure
[10:31] <meoblast001> elkbuntu: do you know the apps?
[10:31] <meoblast001> that do that
[10:32] <meoblast001> i want to try them out
[10:32] <elkbuntu> not off the top of my head
[10:32] <meoblast001> what do you recommend looking up then?
[10:32] <elkbuntu> typing "ubuntu web filter" is a good place to start, then replacing "web filter" with whatever you want to know about for other topics
[10:33] <elkbuntu> (into google, that is)
[10:34] <meoblast001> elkbuntu: dang it.... my school is too retarded to configure stuff
[10:36] <meoblast001> elkbuntu: im gonna try dansguardian out
[11:09] <meoblast001> im going to bed
[11:09] <meoblast001> its late
[11:09] <meoblast001> night
[22:02] <Flannel> Anyone alive?
[22:02] <pep> Yes
[22:02] <pep> coming
[22:02] <pep> right
[22:02] <pep> Who's here for the Spread Ubuntu meeting?
[22:02] <Flannel> You and me, looks like.
[22:02] <pep> no
[22:02] <Flannel> Its less of a meeting, more of a discussion.
[22:02] <pep> there are people just watching too :)
[22:03] <pep> yes
[22:03] <pep> of course
[22:03] <pep> we don't have an agenda anyway
[22:03] <pep> Do you know if Onno planned to come?
[22:03] <Flannel> I don't
[22:04] <pep> Nvm
[22:07] <pep> maybe someone will turn up in a couple of minutes ;)
[22:07] <Flannel> Even if they don't, we can still get stuff done
[22:07] <pep> Flannel: any comments about the project specs thread?
[22:07] <pep> (jupp)
[22:07] <cody-somerville> :]
[22:07] <Flannel> pep: Those specs need to be decided at a discussion like todays
[22:08] <Flannel> pep: I think a large problem we seem to have is everyone sends out "announcement" type emails instead of discussion type emails
[22:08] <pep> i'd have liked to see Mike feravolo, onno and joshua chase here actually (and hubuntu obviously but that's not souch a problem :-)
[22:09] <pep> Flannel: yeah, I'm constantly trying to get people to comment my e-mails and give their part, like Ruben did with the specs e-mail...
[22:09] <Flannel> We're not really *talking* about the project
[22:09] <pep> oh right
[22:09] <pep> well, I'd like to... :)
[22:09] <Flannel> pep: I'd personally like to see a lot more discussion here on a day to day basis.
[22:10] <Flannel> I realise with timezones thats not always possible, but still
[22:10] <Flannel> IRC is much less formal, people are more likely to justsit down and toss ideas around
[22:10] <Flannel> instead of feeling the need to write up elaborate emails that cover large things
[22:10] <pep> We discuss regularly with Ruben when we see each other on IRC
[22:10] <pep> yeah
[22:10] <Flannel> That might just be my perception though
[22:10] <pep> that' was what was behind this meeting
[22:10] <pep> no you're right
[22:10] <pep> that's why I really wanted a meeting to
[22:10] <pep> +day
[22:11] <Flannel> right
[22:13] <pep> I think we're doing a little too much objective thinking :)
[22:14] <Flannel> Which objective thinking?
[22:14] <pep> it's time to stop talking about methods and getting things done you see? we have to get more subjectif now, into it
[22:14] <pep> actively flourishing ideas
[22:14] <pep> and sharing them
[22:15] <Flannel> What sort of methods?
[22:15] <pep> well, we're not yet into it...
[22:15] <pep> we are trying
[22:16] <pep> but don't just *do* it.. and then we keep saying how we should take the next steps instead of taking them
[22:16] <pep> now don't take this bad :)
[22:16] <Flannel> If the "methods" youre talking about are planning how to code and stuff, we haven't done that (but that doesn't necessarily have to happen first).  If its... some other methods... I dont know
[22:16] <pep> this is not relative to what you just said
[22:16] <pep> it's all of us that are each in their corner
[22:16] <Flannel> Mhmm
[22:16] <pep> like onno's commentary that followed the design mockups
[22:16] <pep> he's right
[22:16] <Flannel> Oh, while we're here.  What is  https://launchpad.net/spreadubuntu
[22:16] <pep> totally
[22:17] <pep> but then we have to start putting answers ;à
[22:17] <pep> Flannel: it is the Site part
[22:17] <pep> jsut read the title
[22:17] <pep> just*
[22:17] <Flannel> pep: No no.  but why does it have its own launchpad project?
[22:17] <pep> Because it is the old spreadubuntu project
[22:17] <Flannel> these aren't separate projects, they certainly don't need separate code branches.  They can both live on the same code branch
[22:17] <pep> we didn't create it
[22:17] <Flannel> Ah, thats the old one.
[22:18] <Flannel> ok
[22:18] <pep> I just changed the details
[22:18] <Flannel> Whats the new one then? or is there not a new one?
[22:18] <pep> and made out of the diy website the diy.su project and out of the oroginal spreadubuntu the site part
[22:18] <pep> now we're working on diy-spreadubuntu (used to be ubuntu-diy-marketing project) 
[22:18] <Flannel> I say remove one of them, and use the other.  the other is... diy-website? or what?
[22:19] <pep> diy-spreadubuntu
[22:19] <Flannel> I say ditch diy-spreadubuntu, use spreadubuntu as the entire project, it can hold both codes.
[22:19] <pep> yeah, I wanted to
[22:19] <Flannel> So, just do it?
[22:19] <pep> actually a launchpad admin has to
[22:19] <pep> and we came to keep it finally to not loose the code and such...
[22:19] <pep> but now that you say it
[22:20] <pep> I still think the best is to ditch it
[22:20] <Flannel> Well, change spreadubuntu to talk abotu the whole project, and in the team time, change the description on the other one to say "old, don't use" or whatever
[22:20] <pep> but which one? :)
[22:20] <pep> diy-spreadubuntu then
[22:20] <pep> stupid question
[22:20] <Flannel> pep: spreadubuntu to keep, since its the overarching theme.  diy-spreadubuntu doesn't maek sense to have both parts in it
[22:20] <pep> yeah sure, my bad
[22:21] <Flannel> I'm glad you wanted to ditch one... since sometimes I worry we're balkanizing this project way too much.  Worrying too much about structure and stuff.
[22:22] <Flannel> Howdy hubuntu
[22:22] <pep> I worry that there is not enough energy :)
[22:22] <pep> ah there he is ;)
[22:22] <hubuntu> Good evening.. I came as soon as i could
[22:23] <pep> hubuntu: we are 3
[22:23] <Flannel> pep: I wouldn't worry about the energy.
[22:23] <pep> Flannel and I jsut talked about having 2 projects on LP, and came back to the conclusion that we might as well ditch diy-spreadubuntu and only work in spreadubuntu, hosting both codes and everything
[22:24] <pep> so I'm going to take care of that
[22:24] <hubuntu> Ok. Is Onno here? Mike? Meisok?
[22:24] <pep> Nope
[22:25] <hubuntu> ;)
[22:25] <hubuntu> Ok
[22:25] <pep> meisok is eating I think
[22:25] <pep> and jchase is not here either
[22:25] <hubuntu> Let's get on. What have you guys discussed till now?
[22:25] <pep> nothing essential
[22:25] <pep> basically what I said about the project in LP
[22:25] <hubuntu> Ok
[22:25] <pep> and that we would like more discussion on IRC, more ideas
[22:26] <Flannel> hubuntu: plus the need to talk more on IRC (or casual emails), and less in "announcement" type emails
[22:26] <pep> Flannel: can you repeat for hubuntu?
[22:26] <Flannel> I'll post a log
[22:26] <Flannel> actually
[22:26] <hubuntu> Shall we introduce ourselves and give keypoint of our skills and roles in the community?
[22:27] <pep> o.O
[22:27] <hubuntu> So we can get an idea of where we stand and what we can contribute actively with
[22:27] <Flannel> hubuntu: http://paste.ubuntu.com/28545/
[22:27] <pep> Ah right
[22:28] <hubuntu> I'm rwading the log
[22:29] <pep> I think we should get on with discussing the project specs thread
[22:29] <pep> hubuntu: sure, do so
[22:32] <hubuntu> Ok. I'm on
[22:32] <hubuntu> We are here to define the diy site part rigth?
[22:33] <Flannel> hubuntu: We're here to talk about whatever
[22:33] <pep> well, Flannel, you did not reply to the thread about the specs, would you like to comments anything?
[22:33] <Flannel> pep: Uh, let me refresh my memory
[22:34] <pep> it's about three e-mails...
[22:34] <pep> no
[22:34] <pep> yes
[22:34] <pep> sorry :)
[22:34] <Flannel> Let me just summarize what my answers to the questions would be.  That might be simpler.
[22:35] <hubuntu> Go flannel
[22:35] <pep> hubuntu: you got time?
[22:35] <pep> or anything before you?
[22:35] <pep> I mean, for me you can take your time Flannel 
[22:36] <hubuntu> Yes
[22:36] <hubuntu> I have the whole evening
[22:36] <pep> yeah Flannel it is good that every person gives his answers
[22:36] <pep> and then find a nice middle
[22:36] <pep> :)
[22:37] <Flannel> It offers download stuffs for arbitrary people, upload stuff for arbitrary people (maybe not arbitrary? some sort of moderated? thing? whatever).  Both of these are handled by bzr, so you can also use that as an interface.  With bzr comes a form of version control, and other flexibility.  We'll support any filetypes, including the final projects and their source.
[22:38] <Flannel> version control for the site itself will also be done in bzr, since thats what we have readily available
[22:38] <Flannel> We also support languages.  Either through rosetta or not (I'm not familiar with how rosetta works).
[22:38] <pep> (tell us when you're about done)
[22:38] <Flannel> I... think that's about it?  As for the sort of use case things...
[22:39] <Flannel> random person (org, loco, whatever) comes, finds whatever they need, uses it.  If they have materials they want to share, they upload/share.
[22:39] <Flannel> Pretty simple.
[22:39] <Flannel> I'm done.  I think I covered it all.  Anything I missed?
[22:39] <pep> it musn't be rosetta for me I think, would be nice, but probably difficult for every type of document... but we should investigate this
[22:40] <pep> like all the concrete launchpad use we do
[22:40] <pep> what exactly is a document in lp, a project?
[22:40] <pep> etc..
[22:40] <Flannel> pep: document?
[22:40] <pep> well, a material.
[22:40] <pep> I don't know how to call it
[22:40] <hubuntu> A document in LP thrfough bzr is a document with version control tracking
[22:40] <Flannel> Materials range from images, icons, posters, brochures, etc.
[22:41] <Flannel> I imagine a lot of our stuff will be SVG
[22:41] <hubuntu> Bzr is the key
[22:41] <hubuntu> Indeed Flannel. I believe svg will be our man 'standard'
[22:41] <hubuntu> *Main
[22:42] <Flannel> pep: Again, I have no idea how rosetta works, but maybe we put all the textin a file, and then people can translate through rosetta, and then someone goes through andtakes the translated text and puts it back into the files?
[22:42] <pep> pff, seems long..
[22:42] <Flannel> I mean, if rosetta can only deal with semi-unformatted text
[22:42] <pep> just to say "we used it"
[22:42] <pep> no?
[22:42] <Flannel> pep: I don't care about using it.  I was under the impression that others wanted to.
[22:43] <Flannel> I have no idea how it works, so it might not be worth it.
[22:43] <hubuntu> Rosetta is wonderfful in that that anyone can translate everything
[22:43] <pep> yes, I'd like to, but we have to see what is more effective once we've got a clearer view of the type of documents and how we handle them in bazaar exactly
[22:43] <Flannel> If not, then things get trnaslated by people who then upload the translated things as a translation of the original
[22:43] <hubuntu> And yes, a svg file would have a .po file for transllation
[22:43] <pep> maybe it's easuier to download the svg/png , translate and upload the new one next to the old
[22:43] <pep> yes, for svg it's ok true :)
[22:43] <pep> but then comes the placement problem
[22:44] <hubuntu> That's why the SUgui is central
[22:44] <Flannel> hubuntu: po files don't really work for non-compiled things, right?
[22:44] <pep> in different languages you place it differently, we'll have to see how we review things that have been translated
[22:44] <Flannel> For the moment, I don't mind dealing with translations "manually", with the prospect of integrating somehow with rosetta later
[22:44] <hubuntu> They work for a svg or anything really, depends on how far we are willing to work with this
[22:45] <Flannel> manually being, someone downloads the file, translates, re-uploads as a translation
[22:45] <hubuntu> Flannel i agree
[22:45] <Flannel> just like all the content in the wiki is translated currently
[22:45] <hubuntu> But I think that we should have the translation platform ready by september
[22:45] <pep> I think we should discuss translation point after having completely cleared and confirmed and proved possible the exact process we use for the documents, in bzr I mean
[22:46] <pep> no?
[22:46] <Flannel> hubuntu: I think deadlines are a bit premature at this point
[22:46] <hubuntu> True
[22:47] <Flannel> pep: the ability to have multiple versions (different languages) of a resource is something that is easy to build into our system if we do it from the start.  Might not be easy to revamp later though
[22:47] <pep> ok, if you think
[22:47] <pep> it is maybe because I'm not familiar with bazaar :)
[22:47] <pep> and you not with rosetta ;)à
[22:47] <Flannel> pep: Well, bzr is just files.  bzr won't be dealing with our translations.  The system we build ontop of bzr will.
[22:48] <Flannel> as far as bzr is concerned, they're all more or less "just files"
[22:48] <pep> ok
[22:48] <pep> so a database entry would be associated with a document, it's translations, the bzr address for updates, and a metafile... what else?
[22:49] <Flannel> pep: Um, not quite like that, but sort of.
[22:49] <pep> huh :D
[22:49] <pep> ok
[22:49] <Flannel> let me see if I cant quickly throw something together to illustrate
[22:51] <Flannel> no, thats not going to work in the time constraints of the meetingn
[22:51] <hubuntu> I'm gonna ask the launchpad people about rodetta
[22:52] <Flannel> pep: Basically, everything in bzr includes a metafile, which describes the resource, and also points to its various files (that are in the same directory, or subdirectories).  Then our server program thing takes the info from bzr, and puts it into the DB (I know that poster1 has this description, and this creator, and this english file, this french file, this english source file, etc)
[22:53] <Flannel> pep: the server program reads the metafile to know what files in that directory/subdirectories are what
[22:53] <Flannel> and each resource gets its own directory (probably in a heirarchy) inside of bzr.  so, like /posters/installfest/my-poster-1
[22:54] <Flannel> pep: Basically, everything in bzr includes a metafile, which describes the resource, and also points to its various files (that are in the same directory, or subdirectories).  Then our server program thing takes the info from bzr, and puts it into the DB (I know that poster1 has this description, and this creator, and this english file, this french file, this english source file, etc)
[22:54] <pep> sorry I had a freeze -_-
[22:54] <Flannel> pep: the server program reads the metafile to know what files in that directory/subdirectories are what
[22:54] <Flannel> and each resource gets its own directory (probably in a heirarchy) inside of bzr.  so, like /posters/installfest/my-poster-1
[22:55] <pep> ok
[22:55] <Flannel> so, /posters/installfst/my-poster-1/Metafile my-poster-1/poster-blah.svg my-poster-1/poster-blah2.svg etc
[22:55] <pep> that's about what I imagined, thanks for precising that! =)
[22:55] <Flannel> and then in the Metafile, it knows that potser-blah is the english source version, poster-blah2 is the french one, etc.
[22:56] <pep> are you familiar with writing these type of database server programs? I suppose Onno will give us a hand....
[22:56] <Flannel> pep: Yeah, it shouldn't be a big deal.
[22:56] <Flannel> Basically when we update, we get a diff from bzr, showing which files have changed, and then take the changed information and update it in our DB
[22:57] <Flannel> Its a pretty simple DB structure and process
[22:57] <pep> good
[22:57] <pep> now it is clear! :)
[22:57] <pep> I really didn't see through this tbh
[22:58] <pep> and I understand why the translation is more important..
[22:58] <pep> what else is there important to clarify?
[22:58] <Flannel> pep: through this tbh?
[22:59] <pep> to be honest*
[22:59] <pep> uhm
[22:59] <pep> I didn't understand everything until now to be honest
[22:59] <Flannel> Oh
[22:59] <Flannel> Well, glad to clarify
[22:59] <pep> I thought about clearly defining a classification system for one... deciding on which entries...
[23:00] <pep> which comments on this? => https://wiki.ubuntu.com/MarketingTeam/SpreadUbuntu/diy#head-7b73d553a3987aaab369cd5c7eeb0d35e071e71e
[23:01] <hubuntu> Let me see pep
[23:01] <pep> it mustn't be finished tonight
[23:01] <pep> but I'd like to get the completion rolling
[23:02] <Flannel> I don't think anything will ever be finished.  If we wait for that, we really will never get anything done
[23:02] <hubuntu> True, but we can agree on something to work with
[23:03] <pep> yes Flannel :)
[23:04] <pep> yes, start discussing, so , what do you think? what jumps to your developer eyes? what do you think *must* be a criteria of sorting, what not? etc... we will be able to work on the logs of our discussion if we don't remember all
[23:04] <pep> I thought about something to add to my paragraph this afternoon: n° of downloads, just a detail but important
[23:05] <hubuntu> Analytics will aid us theere pep
[23:05] <hubuntu> ;)
[23:06] <pep> true, but I'm talking about the interest for the user, of it being a column and a criteria of sorting
[23:06] <pep> not for us
[23:06] <Flannel> I think "type" and "category" (type being the type of material, category being what its purpose is) are important for classification.  Description is also important, but not really a "classifier"
[23:06] <pep> and we can use piwik, open source variant of google analytics, we are setting it up for ubuntu-be and possibly the belgian indymedia site (7000 visits/day)
[23:07] <hubuntu> Is it as good as analytics?
[23:07] <pep> right, description will come in the profile page (that's how I call it)
[23:07] <Flannel> I'm not sure analytics will be of much use
[23:07] <hubuntu> Works with drupal?
[23:07] <pep> hubuntu: well analytics is more ad-sense oriented
[23:07] <pep> yes hubuntu there is a module
[23:07]  * Flannel isn't sure we'll be using drupal either, but that's a topic for another day.
[23:07] <pep> it is quite good we discussed it today
[23:07] <hubuntu> I believe analytics will be vital when we move to the campaign site aprt
[23:08] <pep> but it's still quite young
[23:08] <hubuntu> I believe drupal is the way to go
[23:08] <pep> yeah... we'll write it down for a decision to take
[23:08] <pep> ok that's a discussion too
[23:08] <hubuntu> As the rest of the community is based on that
[23:08] <pep> are we taking about classification now or going over to drupal?
[23:08] <Flannel> I think drupal is overkill and not really necessary.  But that's a frontend thing.  I think I'm going to concentrate on the backend more.
[23:08] <pep> ok, drupal :)
[23:08] <Flannel> pep: We're tlakigna about whatever
[23:08] <hubuntu> And is a platform so we don't have to reinvent the whell
[23:09] <pep> Flannel: yeah, but we'll come back to the classification system
[23:09] <pep> I am for drupal too
[23:09] <pep> using it for ubuntu-be now
[23:10] <Flannel> Like I said, I'm going to ignore the frontend, since I'm very much against using a general use CMS for this.
[23:10] <Flannel> that way you won't have to listen to my ranting, and I'll get some work done ;)
[23:11] <pep> well elt's not keep it latent and talk about it now, wy not drupal, what would you use? a custom cms?
[23:11] <pep> let's*
[23:11] <pep> or something like that specialised cms for libraries and such... forgot the name
[23:11] <Flannel> I think writing a custom site will be a whole lot faster than kluding something into a CMS
[23:11] <hubuntu> Ok flannel
[23:11] <pep> we talked about it
[23:12] <Flannel> But, that's just me
[23:12] <hubuntu> But since we are to maintain it too t makes more sense to use drupal, and to get it canonical hosted
[23:12] <Flannel> It just seems to me like theres not a whole lot of site around the content, all its going to be is "search DB, display results, show details of results, upload new stuff"
[23:12] <pep> I think we should use drupal... it's not going to be much harder to immplement something in a drupal site than in a custom one is it? and drupal offers many ready-made modules...
[23:12] <hubuntu> Like the openID
[23:13] <pep> Flannel: +comments + openid + profiles (stats about number of uploads, etc...)
[23:13] <Flannel> pep: When you use drupal, or some other thing like that, you wind up spending more time getting your code to play nicely with the CMS than writing your code to begin with
[23:13] <pep> and acess levels to are easy to manage
[23:13] <pep> mhh yeah I see your point...
[23:14] <Flannel> Do we want to allow comments?
[23:14] <pep> definitely
[23:14] <hubuntu> I am not sure
[23:14] <Flannel> as far as profiles go, we use LP IDs, and we're done.
[23:14] <hubuntu> Yes, LP is the way
[23:14] <pep> http://www.gnome-look.org/content/show.php/Moomex-Theme?content=57063&PHPSESSID=86fe2ce23770349ab3464545a6a72e90 I like this concept...
[23:14] <hubuntu> OpenID is the *only * way to log in
[23:15] <pep> ah yes hubuntu but openid doesn't exclude profiles 
[23:15] <pep> not a list of uploaded things per user? or something like that?
[23:15] <Flannel> OpenID doens't mean just LP though
[23:15] <hubuntu> That way everybody is bounded to LPP
[23:15] <Flannel> hubuntu: LP isn't the only place to get openID
[23:15] <pep> but openID is just the login hubuntu...
[23:15] <Flannel> With open ID you can use *any* open ID provider.  Unless we're going to limit it to LP only.
[23:15] <hubuntu> I know, but LP should be the only provider
[23:15] <Flannel> Which we may wish to do.
[23:16] <pep> hubuntu: we use openID at ubuntu-be, but it's normal openID, not just LP: www.ubuntu-be.org/drupal
[23:16] <Flannel> but thn we're not really using "open ID" but just "launchpad accounts"
[23:16] <hubuntu> That way all reg users are LP nusers and have upload *rights*
[23:16] <pep> yes Flannel that's it
[23:16] <pep> we're using both
[23:16] <pep> launchpad accounts through openID
[23:16] <Flannel> which is fine, we just shouldn't say "open ID"
[23:16] <pep> yes, technically you're right
[23:16] <pep> :)
[23:16] <hubuntu> LP OpenID
[23:16] <hubuntu> ;)
[23:16] <Flannel> hubuntu: No, just LP accounts
[23:16] <pep> yes
[23:17] <pep> lp accounts, via openID provider restriction
[23:17] <hubuntu> Flacoste will work with us in the integration
[23:17] <pep> whatever :)
[23:17] <Flannel> We're not trying to buzzword compliant, ditch the "open ID" as it'll just confuse, because we're not actually doing the open ID thing
[23:17] <pep> whatever was for my phrase 
[23:17] <pep> ;)
[23:17] <pep> we are doing openID too Flannel 
[23:17] <pep> why not?
[23:18] <pep> I thought we are lp accounts, via openID provider restriction
[23:18] <hubuntu> We are doing it limiting it to LP
[23:18] <Flannel> pep: If we restrict it to LP accounts only, it's not really open ID.  but a limited version
[23:18] <pep> sure
[23:18] <hubuntu> Many openID relying sites do such things
[23:18] <pep> then we can call it differently, but we should use the technology
[23:18] <pep> call it launchpadID
[23:19] <Flannel> Seems like that completely defeats the purpose of open ID if you have to sign up with *their* site's open ID
[23:19] <Flannel> I agree.  Its a LP ID login
[23:19] <pep> yes
[23:19] <hubuntu> I believe we should use LP OpenID, but we can discuss that later... The name can be decided later
[23:19] <pep> lpID
[23:19] <hubuntu> LP ID will do forme
[23:19] <pep> we will have to modify the openID module, to make an lpID one
[23:19] <pep> good
[23:19] <Flannel> We could even possibly check/require the CoC to be signed
[23:20] <pep> Flannel: yes, we can check that through lp accounts
[23:20] <Flannel> pep: No, I know its possible.  Not sure if we want to make that restriction.
[23:20] <pep> as well as preferred languages for showing only relevant documents to the users
[23:20] <Flannel> But, that's... not really important at this point in time
[23:20] <pep> I don' want to make that restriction od CoC personally
[23:20] <hubuntu> True. And a LP account should suffice
[23:20] <pep> yes
[23:20] <pep> but4
[23:21] <Flannel> pep: signing the CoC requires them to behave and have knowledge of the rules
[23:21] <Flannel> but, I'm not really heart set on it
[23:21] <Flannel> just an idea
[23:21] <hubuntu> The language trick will be done either through browser recognition of languazge and/or with the flags
[23:21] <pep> what we can add, on our site, is maybe the list of submitted material, and of pending material so ppl can see if their document is in the database yet... thought about that in the train...
[23:22] <hubuntu> We could require it for members of our project
[23:22] <Flannel> hubuntu: does LP not provide a preferred language profile bit?
[23:22] <pep> hubuntu: no... if we translate, we must show to the user all the languages he translates in lp, no? so in the downlad list there are only docs in the preferred anguages (not talking about site interface)
[23:22] <hubuntu> It does, but i'm not sure  yhou can get that from their OpenID implemengtation
[23:22] <hubuntu> AFAIK it only gives the user name
[23:23] <pep> we don't care, we just *look* in the lp account that's associated..
[23:23] <pep> it's accessible no?
[23:23] <Flannel> yeah, we can grep the site, I'm not sure its available.
[23:23] <pep> we've got the user name so we'll get the info about the account with no problems I think
[23:23] <hubuntu> Rosetta gives option to translate from any available language to(already translated) to any other
[23:24] <Flannel> Oh, you can set it.  Its new though
[23:24] <hubuntu> It's been there for 6 months I think
[23:24] <pep> hubuntu: yes, but you are rarely going to translate in languages that aren't in your preferred ones I think :/
[23:24] <hubuntu> Yes but translating from them ;)
[23:25] <hubuntu> Which language you translate to itås a totally different issue
[23:25] <pep> mhh.. I'm not translating into a language I don't know
[23:26] <pep> I do english-french, french-english, german -french, etc.. with my preferred languages only
[23:26] <hubuntu> Of course , but you get info on what is available in flemish and then you decide what to translate to
[23:26] <pep> yes
[23:26] <pep> that's why you see all preferred languages in the "download" list... where's the problem?
[23:26] <hubuntu> Let's just think about it. The language thing should be a problem
[23:27] <Flannel> shouldn't
[23:27] <hubuntu> Np
[23:27] <pep> ok
[23:27] <hubuntu> Thx F
[23:27] <hubuntu> Meisok are you there?
[23:27] <pep> it is because I fear that you have dozens of entries of the same popular document in all languages... I mean, how else do you want to show the docs in the list?
[23:28] <pep> nah he's still eating
[23:28] <meisok> hubuntu: yes :)
[23:28] <pep> oh
[23:28] <pep> haha
[23:28] <Flannel> pep: We'll be able to sort that out easily enough, don't worry
[23:28] <pep> I was whois'ing you ;)
[23:29] <hubuntu> Flannel when it comes to the backend
[23:29] <hubuntu> How will it work in practice?
[23:29] <Flannel> hubuntu: What do you mean
[23:29] <hubuntu> I mean we will have a place for the drupal code
[23:29] <hubuntu> And a place for the diy rfepo content
[23:29] <hubuntu> 2 diff places
[23:30] <Flannel> One repo for the content, and a separate one for the website, yes.
[23:30] <hubuntu> Drupal and backend code
[23:30] <Flannel> backedn code is going to have to be python, I believe.
[23:30] <hubuntu> Ok, bot a project under LP, right?
[23:30] <Flannel> but, thats not relevant
[23:30] <hubuntu> Django?
[23:31] <Flannel> hubuntu: no.  Just that libbzr is in python
[23:31] <hubuntu> Maybe we could move the wholething to django and move along with the loc-django-website team
[23:31] <hubuntu> Ok
[23:31] <Flannel> No, I dont think thats necessary
[23:31] <hubuntu> What about bzr upload?
[23:31] <hubuntu> Will we be using it?
[23:31] <Flannel> What do you mean bzr upload?
[23:32] <pep> we have to think long-term... if we're successful we will have a big load..
[23:32] <Flannel> like regular bzr interface? yeah.  We'll have bzr accessible via bzr, and also the website
[23:32] <hubuntu> I'll shoow you
[23:33] <Flannel> hubuntu: as far as "separate projects" the backend stuff will be owned by the spreadubuntu project, and the content itself can be managed by the marketing team.  Those can be the main branches, as far as how LP handles bzr repo creation... I'm less sure.
[23:34] <hubuntu> https://wiki.ubuntu.com/MarketingTeam/SpreadUbuntu/diy#head-d7a37f4ed2cf354f341731e9c4ce5f6e376dd495
[23:34] <hubuntu> See bzr upload
[23:35] <hubuntu> It could be an idea.. I don't know
[23:35] <Flannel> hubuntu: No, I don'tthink we'll need that.
[23:35] <hubuntu> Ok
[23:35] <pep> yes, I like the idea that the content itself, launchpad-ownership speaking, would be handled by the marketing team.
[23:36] <pep> well, "owned"
[23:36] <hubuntu> No and yes
[23:36] <hubuntu> we are thw MT too
[23:36] <pep> yes
[23:36] <Flannel> What?
[23:36] <Flannel> Oh
[23:37] <hubuntu> So it should be under the SU team
[23:37] <Flannel> hubuntu: No.  Because then anyone who wants to upload to it will be required to join this team.  Doesn't make sense
[23:37] <pep> but the documents themselves are still *for* the marketing team's goals
[23:37] <hubuntu> And members of the SU team being ubunteros and part of the MT
[23:37] <hubuntu> Uploading doesn't require anything else than An LP account
[23:37] <pep> Flannel: no need to be in the marketing team tp upload!
[23:37] <pep> no?
[23:37] <pep> to*
[23:38] <pep> any LP account
[23:38] <pep> imo
[23:38] <Flannel> pep: To a BZR branch, yes.
[23:38] <Flannel> pep: or rather, to an official bzr branch, yes.
[23:38] <pep> ok, but what's with the submit form on the site?
[23:38] <pep> that comes to us and we upload it?
[23:38] <pep> then ok.
[23:38] <Flannel> For example, the SU team will "own" the branch that the SU code is in.  We are the only ones with bzr access
[23:38] <Flannel> pep: No, it automatically uploads
[23:39] <Flannel> but, for anyone who wants to just use bzr, instead of going through the site, they need to be a member of Marketing Team
[23:39] <pep> Ok, yes... but persons taht are not in the marketing team can submit of course, they just need a launchpad account to sign in :)
[23:39] <Flannel> Or rather, need to be a member of the team that owns the branch
[23:39] <pep> ok Flannel
[23:39] <pep> yes
[23:39] <pep> then ok.
[23:39] <Flannel> Which is why it makes sense for that to eb the marketing team
[23:39] <Flannel> and not spreadubuntu
[23:39] <pep> exactly
[23:39] <pep> but of course a team, from SpreadUbuntu will manage/admin this
[23:40] <pep> but that's not the point
[23:40] <pep> hubuntu: what do you think?
[23:40] <pep> uploading to the site will still be open to any LP account
[23:41] <Flannel> because the commits themselves will go through libbzr on the site
[23:42] <hubuntu> Mmm,  have you tried leonov Flannel?
[23:42] <pep> yes leonov is a good thing, I checked it out a bit :)
[23:42] <hubuntu> A client (qt&gtk) for LP
[23:43] <Flannel> hubuntu: No
[23:43] <hubuntu> Can a official brand be accessed by people outside of any given project?
[23:43] <hubuntu> I mean commited to
[23:43] <pep> no
[23:44] <Flannel> hubuntu: but the website will take care of that for website uploads
[23:44] <Flannel> hubuntu: Its only for direct bzr commits
[23:44] <pep> but they just need to join the marketing team to do it if we do it this way, so ppl who really want to use leonov can do without problems as the marketing team is not moderated
[23:45] <hubuntu> I believe the bzr access should not be restricted in any way
[23:45] <pep> it's not possible hubuntu
[23:45] <pep> I think
[23:45] <Flannel> hubuntu: you can *get* stuff without a problem.  You can't commit without being a member AFAIK
[23:45] <hubuntu> Is that possible? I mean as long as it involves an LP account
[23:45] <Flannel> but still, MT membership is as simple as clicking a link
[23:45] <pep> yeah
[23:46] <pep> it's an open team
[23:46] <hubuntu> But it may be too much for new comers
[23:46] <Flannel> hubuntu: OR if youre really against it, just do it through the website
[23:46] <Flannel> hubuntu: Whats wrong with the website then?
[23:46] <pep> so website upload without marketing team membership, else you do what you want
[23:47] <hubuntu> Then it's cool
[23:47] <hubuntu> If you manage to set up bzr and commit to the branch you should be able to click on the membership icon;)
[23:47] <pep> hehe yeah
[23:47] <pep> it means you know your way around LP
[23:48] <Flannel> eh, or at least know a little ;)
[23:48] <Flannel> remember, if you're committing to bzr yourself, it means you're setting up your own metafiles and stuff.
[23:48] <pep> pff yeah, that should be super-vised :/
[23:49] <Flannel> Its not going to be difficult.  And we could always write a desktop script to do it.
[23:49] <Flannel> but, those are extras we don't need to be concerned with at the moment
[23:49] <pep> jupp
[23:49] <pep> no
[23:50] <hubuntu> Indeed
[23:50] <pep> back to the classification system? I will process the log... hubuntu what do you think *must* be in?
[23:50] <pep> or if you think it is +- covered we can move on
[23:50] <Flannel> pep: I think anything we haven't covered will make itself apparent via testing
[23:51] <hubuntu> I like your classification system
[23:51] <hubuntu> But exclude the comments
[23:51] <pep> from the profile page?
[23:51] <hubuntu> We should instead have a system for giving points to some material
[23:51] <pep> I thought that would push to approvements, as we have a version control system
[23:51] <pep> that too
[23:52] <hubuntu> Having a rating systema
[23:52] <pep> I thought about description, (little pic?), rating, comments and number of downloads to judge a document
[23:52] <pep> for the user
[23:53] <hubuntu> Yes a social based system a la youtube/flickr/amazon
[23:53] <pep> jupp
[23:53] <pep> it pushes evolution In my sense
[23:53] <pep> approvement
[23:53] <hubuntu> ;)
[23:53] <pep> like in gnomelook
[23:54] <hubuntu> But having categories (newly added, best rated, most downlaoded) should help too
[23:54] <BHSPitLappy> What are we talking about, exactly?
[23:54] <Flannel> those are all classifications that are dealt with on the site side, not the backend side.
[23:54] <pep> mhh.. that you can sort by when you click on column titles in my scheme... as date, rating and umber of dls are criteeria..)
[23:55] <pep> Flannel: that's for the front-end yes
[23:55] <pep> sorry :)
[23:55] <Flannel> pep: No need to be sorry. Just wanted to make sure we were on the same page.
[23:55] <Flannel> That's more or less, an entirely different set of tables in the DB
[23:56] <pep> yes, these things stay on the site
[23:56] <pep> and version is updated by bzr I suppose...
[23:56] <Flannel> pep: Well, the otehr DB is on the site too.
[23:56] <pep> well yes, I mean not inthe metafile
[23:56] <Flannel> BHSPitLappy: The DIY part of spreadubuntu
[23:57] <pep> actually all dynamic things, obviously :)
[23:57] <pep> BHSPitLappy: https://wiki.ubuntu.com/MarketingTeam/SpreadUbuntu/
[23:57] <Flannel> We ought to move that to /Projects/SpreadUbuntu at some point
[23:57] <pep> yeah
[23:58] <pep> but the old one was still there ;à
[23:58] <pep> :)
[23:58]  * Flannel doesn't mention the fact that he hasn't written the "how to start a project" stuff.
[23:58] <pep> we can do it fo rme, just have to put the old as a subpage of the new ine
[23:58] <pep> one*
[23:58] <Flannel> pep: yeah, or move it to /Projects/Spreadubuntu/Old
[23:58] <Flannel> hmmm, I think thats what you said.
[23:59] <pep> jupp
[23:59] <pep> my bad