Session Start: Mon Nov 03 19:02:01 2008 Session Ident: #nextwiki [19:02] * Now talking in #nextwiki [19:02] * Topic is 'Agenda is at http://www.twikifork.org/Community/CommunityMeeting2008x11x03; if you are here for help, please visit #twiki_fork' [19:02] * Set by CDot on Mon Nov 03 18:46:06 [19:02] Hello there everyone [19:02] Good evening [19:02] My skype name is productbox if someone can do the honours [19:02] Are we on skype? [19:02] Where? [19:02] Hi Martin, [19:02] SamHasler: done [19:02] I was just wondering that too! ;) [19:02] some of us are on skype [19:02] If we do skype my name is kennethlavrsen on Skype [19:03] Do you have a conference? [19:03] My name is either kalyxo or mseibert. :-) [19:03] we are trying [19:03] * uebera|| in listening mode... will we have a recording or summary attached to the CommunityMeeting200x11x03 topic afterwards? ;) [19:03] who do I call on skype? [19:03] Who is hosting the Skype meeting? [19:03] Will anything go on in text? I've always disliked voice conference calls, you spend half the time trying to find out who's who and what they're saying :) Not trying to stop the call here tho', just saying [19:04] [off] CDot mymayer has started a call and CDot you are showing up offline so change your status [19:04] CDot: qry me with your name [19:04] RasmusPraestholm: as much as possible should be text [19:04] Cool [19:04] * pattdi has joined #nextwiki [19:04] my skype is playing silly buggers; may be academic. [19:04] Any sign of gmc? He [19:04] My skype name is "kalyxo". [19:04] said he would chair [19:05] manoman, the mac mini cpu fan cable really isn't a nice thing for someone that's sleep derprived [19:05] Why don't we simply stay on IRC? [19:05] hi :) [19:05] we will stay on IRC. [19:05] On Skype ONE must setup the conference and call the others in [19:05] Who does that? [19:05] we are just waiting for gmc to take the chair [19:05] i believe EugenEsch is trying to do that [19:06] OK [19:06] Lavr: And if somebody wants to join late you have to disconnect and do it again. Forget it. [19:06] can whoever's hosting the skype call invite me? Username: SamHasler [19:06] MartinSeibert, you just add it. it's pretty simple. [19:06] i do it all the time :) [19:06] yay, mac mini with osx server, skype starting - skypename : Sven Dowideit [19:06] SvenDowideit i means [19:06] be sure to change your skype status to available [19:06] am booting my trusted w2k fro skype. [19:07] There is Eugen, Travis, Andre, Rafael, Sam and Martin on skype right now. [19:07] howdy [19:07] I'm not on my home machine with Skype, but anybody who wants to add me for future reference feel free: Cervator [19:07] * ktwilight_ 's skype is keliew [19:07] Let's do that the next time. [19:07] i'm sonolo4 i think [19:07] skypename: productbox [19:07] * MartinCleaver has joined #nextwiki [19:07] working [19:07] The skype thing will keep us busy for 30 minutes without effect. [19:08] Lets stay on IRC! [19:08] MartinSeibert: +1 [19:08] i'm signed in.. [19:08] * Wolf_Marbach has joined #nextwiki [19:08] We are 7 ppl now [19:08] Everybody can write. Everybody knows how to get connected. [19:08] EugenEsch, add keliew [19:08] * GilmarSantosJr is at work and no skype here... [19:09] See ... [19:09] EugenEsch - did you get my skype id lynnwoodbrown? [19:09] 8 mins in, and counting [19:09] Who wants to facilitate the meeting? [19:09] gmc: said he would chair [19:09] Crawford: Would you please do that? [19:09] ok, so no skype? [19:09] Ah. [19:09] There he is. [19:09] No: No skype! [19:09] no skype, then i will chair :) [19:09] please do [19:09] 9 ow [19:09] Perfect. [19:09] sounds good. let's proceed [19:10] Let's start. [19:10] who's doing the minutes? [19:10] gmc: qry me with your name [19:10] and proper style minutes! not just irc log [19:10] * Jens__ has joined #nextwiki [19:10] We all could be working. Let's not waste valuable time. [19:10] I will summarise the log as minutes [19:10] I can minute. [19:10] ok [19:10] Lavr_: you have it [19:10] OK [19:10] * CDot cracks a beer [19:10] so lets start then.. [19:10] Perfect. [19:10] :) [19:10] :-) [19:10] we've got a lot of points to cover.. [19:11] 1. governance [19:11] interim figure head [19:11] and short-term project management [19:11] I say "no" to a BDFL and "no" to a core team [19:11] I think we can live without. [19:11] * SvenDowideit potters back to the lounge :) [19:11] * Jens__ is now known as Jens [19:11] I say "yes" to a task-team taking responsibility for media and new people comms, tho [19:11] If you want one, the only ones I see in this position are MichaelDaum and CrawfordCurrie. [19:12] second [19:12] * Jens is now known as Guest80855 [19:12] +1 [19:12] +1 [19:12] Crawford: But that is a task team. [19:12] where is michaeldaum btw? [19:12] gmc is chair, Lavr is taking minutes? [19:12] Soronthar: correct [19:12] Lavr is on minutes [19:12] k [19:12] and to clarify what is the motion? [19:13] I would apply to for a job to answer media inquiries. [19:13] TravisBarker: we're talking about a figure head, but thats being dismissed.. [19:13] I would help out with caring for new people. [19:13] isn't that the job of MarketingTaskTeam btw? [19:13] ok, i think the problem was the name [19:13] MartinSeibert: you are already doing a great job "meeting and greeting" [19:13] i wanted to suggest having _one_ person designated (for a period) [19:13] * ktwilight_ has quit IRC (Remote closed the connection) [19:13] But it sometimes takes me 1,5 weeks to process my mails. That is bad if 2 people cheer for us per day. :-) [19:13] as being the welcoming comitee [19:14] ok, then i designate martin, who has been doing a great job [19:14] who will spend time not being otherwise productive, even if they could be [19:14] ie, hangs out in irc [19:14] madated until our next meeting [19:14] +1 for marting for the "greeting and meeting" [19:14] mandated [19:14] +1 [19:14] +1 [19:14] and spends time telling new people what they can work on [19:14] +1 [19:14] +1 [19:14] +1 [19:14] which is not a task MartinSeibert has shown time to do - he has a business to run [19:15] I am dreaming of a task list for non-programmers for a long time. [19:15] I have done a bit of that, with people who come to me directly [19:15] +1 but I would like to have more personal answers [19:15] i also mean this to be a one month mandate type thing [19:15] So are we making one person have that role, or can we make a group? I'd suggest group, and be happy to be part of it (at least later when I know what tasks to hand out) [19:15] a mechanism i've used is having a second level team of greeters in different areas [19:15] you need a group to support the one person [19:15] Right: I cannot hang out on IRC. Sorry. :-) [19:15] I say, make Martin the point man, let him identify (co-opt) his backups [19:15] but the one person is to make it simple and obvious for new people [19:15] I would like a group for it [19:15] But who wants do to that as a job? [19:15] RasmusPraestholm: we are starting with one person until we have the infrastructure to coordinate a group [19:15] * ktwilight has joined #nextwiki [19:15] Then MartinSeibert could direct new person to one of these other folks to help based on area of interest [19:15] SvenDowideit: none of us can hang out on irc 24/7.. we sure try.. [19:15] I will happily back Martin up with techies [19:16] I nominate SvenDowideit for the IRC job [19:16] question is... once we have the person, what will be on the site to make it clear? [19:16] it'd have to be [19:16] +1 for Sven, if he wants. [19:16] "All your questions belongs to XXXXXXXX"? [19:16] On IRC we all need to share it. it is more the email part we need someone to do i [19:16] * ColasHome has joined #nextwiki [19:16] agreed [19:16] yep [19:16] indeed, and i think martin is our man, so lets move on? [19:16] and picking me or cdot will raise hell for us, cos peter will use it [19:16] ok [19:16] move on [19:16] Yep, I can take the email part. [19:16] stop [19:17] Guest80855: ? [19:17] who is Guest80855 ? [19:17] At least for the non-technicians. [19:17] :) [19:17] jens [19:17] Guest80855: do a /nick Wolfthing [19:17] oh yes.. [19:17] * gmc is now known as Jens [19:17] * Jens is now known as gmc [19:17] we need a nutral mail for answering questions [19:17] (sorry :) [19:17] Guest80855: i think we dont need to go into those details here and now [19:17] * Guest80855 is now known as Jens___ [19:18] I am confident with Martin doing it. He has done well so far [19:18] if you have an opinion re that mail, please contact MartinSeibert later by mail or chat [19:18] Are we following: http://twikifork.org/Community/CommunityMeeting2008x11x03 [19:18] ACTION: MartinSeibert to act as point man for queries and coordinate new folks; all others to provide backup and help out as he requires [19:18] MichaelCorbett: yes [19:18] Because if we are, then I am confused [19:18] MichaelCorbett: we are at 1.1 [19:18] or rather.. we were.. [19:19] we're now moving to 1.2 [19:19] project management [19:19] I will put up a document, that describes what I will do and how. [19:19] and you're doing great gmc [19:19] * CDot votes "no" to an IGT [19:19] what is IGT? [19:19] Interim Govenrance Team [19:19] * GilmarSantosJr +1 [19:19] (short description ) [19:19] No IGT needed. Agree only roles on specifics [19:19] project mgmt [19:19] not igt [19:19] What is IGT-like thingy? [19:20] someone to track what we want to do [19:20] and to remind us when we forgot something [19:20] that should be a group / team [19:20] do you have a proposal? [19:20] no to igt here [19:20] Action item for MartinSeibert: Create a document that describes the role of the "media man" in detail and make it transparent. Offer to be supported by others and actively ask for it. Create a backup-person as soon as possible. [19:20] it does not need to be a team [19:20] (igt was for setting up an association, ubt thats being handled already) [19:20] as its a task that does not need full time attention [19:20] just a seperate pov from the people doig the work [19:20] So, we need a person/group to monitor the activities of the task teams? is that it? [19:20] imho that is a TaskTeam [19:21] i'd love to ask if Wolf_Marbach could help us with it [19:21] No need for IGT at the moment. [19:21] it is a Team [19:21] its not an igt, stop bringing up igt [19:21] We will need a board for the association though ... [19:21] task coordinator? [19:21] CDot, ya [19:21] if the IGT is for setting up an assosiation, its done allready so we have a team [19:21] ewait [19:21] sheesh [19:21] Soronthar: we need someone who keeps a high-level overview of what needsd to be done, what is being done, and when it needs to be done [19:21] I am all for the controller of the TaskTeams! [19:21] what are we talking about? a governance body or a project management team? (different beasts) [19:21] Yes. The association has a task team. [19:21] ffs [19:22] Soronthar: project mgt team, igt has been skipped already [19:22] +1 [19:22] right [19:22] NOT IGT OR ANYTHING LIKE THAT [19:22] Somebody who bothers. [19:22] good [19:22] stay on topic [19:22] -> we're talking about project management <- [19:22] So, is a team that monitors other teams [19:22] someone to tick of things from the release plan [19:22] * IgorNikolic has joined #nextwiki [19:22] Who puts the finger in the wound. [19:22] Sven: Thanks for mentionoing me, what do you mean in detail? [19:22] Somebody who continously follows up. [19:22] HI [19:22] * sayotte has joined #nextwiki [19:22] hi IgorNikolic, we're discussing 1.2 from http://www.twikifork.org/bin/view/Community/CommunityMeeting2008x11x03#foo_42: project management [19:22] What about the TWiki-Janitor? [19:22] I think the rubber stamping of task teams never really worked on t.o. Let us let the task teams form them selves the next weeks and enjoy seeing work actually get done [19:22] Is it Rafael? [19:22] thanks. [19:22] SvenDowideit: that is the ReleaseManager [19:22] someone that can take an overview of what we'd like to do [19:22] someone who watches to make sure tasks gets done, and kicks up when they don't [19:22] no Soronthar its not [19:23] what projekts are we talking about [19:23] someone that is not busy trying to do the tasks [19:23] * ktwilight has quit IRC (Read error: 54 (Connection reset by peer)) [19:23] and the release mgrs are busy doing stuff [19:23] * carlo- has joined #nextwiki [19:23] CDot: +1 [19:23] technikal, fork, media [19:23] what is the motion on the floor? [19:23] Assign tasks and proactively ask people to solve them. [19:23] hi carlo-, we're discussing 1.2 from http://www.twikifork.org/bin/view/Community/CommunityMeeting2008x11x03#foo_42: project management [19:23] +1 [19:23] hello everyone [19:23] TravisBarker: no motion, just discussion [19:23] the idea is to have a small check&balance to get us out the door [19:23] * ktwilight has joined #nextwiki [19:23] the ticks in the todo list are made by the release manager as the task are finished, but someone must monitor that the tasks are being ticked [19:23] Hi Carlo. [19:24] without them distracted by working [19:24] & assoication forming [19:24] SvenDowideit: while I like the idea, I'm not sure I can put a finger on anyone in a position to do it. [19:24] * MartinRowe has joined #nextwiki [19:24] ok, i can't talk through all this off topic stuff [19:24] Someone suggested me as the release manager for the first urgent release. And I volunteer for this if OK. [19:24] GMD: +1, just coordination. [19:24] I am for the TWikiJanitor? [19:24] Wolf_Marbach: you've been nominated, do you understand what for and would you want to pick up that task? [19:24] CDot, as i suggested [19:24] Wolf_Marbach, is a PM [19:24] MartinSeibert: twikijanitor has nothing to do with this [19:24] if we can persuade him that we can give him enough details [19:24] *sight* [19:24] [off] this is gettin' annoying :/ [19:25] then perhaps he can offer us a different pov [19:25] Sven: Taht is true [19:25] we should release from other projects [19:25] i'm about to go back to bed [19:25] SvenDowideit: OK, if Wolf_Marbach is willing, I will help support. [19:25] [off] we have so much noice here. [19:25] I missed what Wolf would do??? [19:25] I'm still not clear what are we discussing, really [19:25] cos i cannot take the noise [19:25] Who was that? [19:25] I am for Lavr as release manager! [19:25] gmc: The TWikiJanitor has the skills to follow up. I think it is Rafael. [19:25] guys.. [19:25] please all stfu now [19:25] Its ok for me but have to clarify the scope of work [19:25] MartinSeibert, this is not release mgr [19:25] we are not talking about release manager.. we are talking about project manager [19:25] Wolf would be the project-management-office with the overview. :-) [19:26] MartinSeibert, that is the _only_ thing we are discussing right now [19:26] [off] People you are on flame to help but please reduce the written lines and also read. Please try to go for the topic one for one [19:26] Yes, but there will be more discussions [19:26] what should the project manager do? [19:26] Wolf_Marbach: do you accept the post of project manager? [19:26] about the actual scope within a smaller group [19:26] I think the activities on nextwiki.org are going wel since it's creation. [19:26] ar at least, for kicking of that post [19:26] * LarsEik has joined #nextwiki [19:27] Yes, but need some more communication [19:27] (me is thinking about +v :) [19:27] i don't see the need for a project manager in short term [19:27] Soronthar: http://en.wikipedia.org/wiki/Project_management [19:27] Wolf_Marbach: ok, lets do that outside this meeting! [19:27] GilmarSantosJr, we need to release fast [19:27] it's not a short answer [19:27] gmc: 100% agree. Moderate it [19:27] that requires strong focus [19:27] gmc: ok [19:27] and a PM will help us optimise that [19:27] yup [19:27] the release can be well isolated from all the other activities. [19:27] I know what PM is, but I'm not sure what we want to accomplish [19:27] are we talking about the first release? [19:27] i'm cofused [19:27] Lavr: agree [19:27] Suggestion: for side remarks, discussions, use #twiki_fork, to reduce noise here [19:27] Wolf_Marbach, we're going to have to refine the role elsewhere [19:28] GilmarSantosJr, yes [19:28] release is 2.4 point... [19:28] please shut up about the release. Different problem. [19:28] Sven : exactly [19:28] ------------------------> STOP [19:28] wolf accepted.. only if you think wolf is totally incapable of project management, speak up now [19:28] if not, we move on! [19:28] I still need to know what you mean with PM [19:28] :/ [19:28] yes [19:28] * MartinSeibert quiet. [19:28] right project manager for entire project [19:28] * MartinSeibert is quiet. [19:28] coordinate and track all t he task teams [19:28] and if wolf is willing to lead that, I say yea! [19:28] and would be willing to support that effort [19:28] +1 [19:28] do we have agreement on that? suddenly very quiet... [19:28] +1 [19:28] We were told to stfu. :-) [19:29] Lynnwood: yes [19:29] at minimum track the next release [19:29] +1 [19:29] Coordinate task teams PM. Then I am for [19:29] the rest is gravy [19:29] So, a coordinator for the task teams. [19:29] project manager: see who's doing what, what needs to be done, that it is actually done and when it needs to be done [19:29] then yes +1 [19:29] Track release then NO [19:29] we need a PM to make sure we get the release done well [19:29] no, not release, lavr=release manager, no discussion necesarry :) [19:29] ----------------------> no positive feedback guys, only "no i dont want that" ... its only noice then [19:29] gmc: good description [19:29] Lavr_, you can't do that job [19:29] release is a task team; different problem, already covered. [19:29] you're actually working o the release [19:29] i dont like having what appear to be votes during a discussion period [19:29] lavr. release manager [19:30] me too [19:30] discussion ended [19:30] next! [19:30] i asked, anyone against Wolf as project mgr, noone objecte, wolf = pm! [19:30] ----------------------------> 2. Short term priorities [19:30] gmc: ok [19:30] -------------------------> 2.1 name and logo [19:30] I am all for wolf to coordinate and follow up on the tasks others do not fulfill. [19:30] name > release > press release > party [19:31] i suggest 5 minutes of disucssion on the names [19:31] AndreU: has leetter to nextEngine gone? [19:31] free-form discussion [19:31] starting _now_ [19:31] collabra etc i like :) [19:31] seems familiar tho [19:31] letter to next engine [19:31] is there an existing wiki page on proposed names? [19:31] * CDot had his say by striking out nasty names in the topic [19:31] are we discussing names here? [19:31] yes. [19:31] http://www.twikifork.org/Community/FindingANewNameLocked [19:31] 2.1.1!! [19:31] are sticking to the flow? [19:32] http://twikifork.org/Community/FindingANewNameLocked#Meeting_references [19:32] I send the email out [19:32] My wife has a lot of experience on brand names. She has offered to make a short questionaire for US to help us select the right name once we are down to maybe 8 candidate names [19:32] please, refer to nams by their numbers [19:32] also, there's responsibility [19:32] ktwilight: we're on free-form discussion now.. i see 2.1 as one big point, not 3 smaller.. [19:32] We need a professional name not fancy stuff to take the project serious [19:32] 2.1.1.: I'd say it wouldn't hurt to say "hello", "sorry" and ask. [19:33] NextEngine: We have all to loose and nothing to win asking them. [19:33] english professional name not some alibabaalihubicrapola [19:33] gmc: Does it make sense to vote off half the suggestions on that list ? [19:33] Wolf_Marbach, y, shame 'professional' is different in everyones heads [19:33] voting on irc is not practical if you have 50 names [19:33] gmc, o [19:33] we are _not_ going to vote now i think [19:34] michaeldaum is not here.. [19:34] I agree, a name already free with an avialable .com would be much less hassles [19:34] And: ArthurClemens is not here. [19:34] On naming - we're probably not going to find a single name everybody will be thrilled to support. Next & Open have a fair degree of support, any opposition if trademark / domain issues are resolved? [19:34] Seven: what do you suggest instead? [19:34] i move to table the name issue to a discussion and vote on a wiki topic [19:34] but his suggestion was: put as much feedback on the wiki topic, he will go into another round with the copywriter [19:34] CDot, I sent the letter out to nextMachine [19:34] and then we vote asynchronous [19:35] AndreU: great. :) [19:35] i don't atm, we're pretty polarised atm [19:35] I would propose making a first vote on the name topic and define the top 8. And then take my wife's offer to help us choose the right. [19:35] "put it in mutunga" does not have a nice ring to it :) [19:35] * MartinSeibert is completely overwhelmed with what the community and the copywriter came up with. I do not have strong feelings about the name. That is why I will not join the discussion until we are down to a decent number, say 7 names. The current situation is way to complex for me. :-) [19:35] MartinSeibert: my sentiment exactly :) [19:35] we're pretty close to 7 [19:35] there are 22 as we speak. [19:35] if you ignore all strikeout [19:35] MartinSeibert: well said. [19:35] really? [19:35] ok, so time to strike some more [19:36] strikeout *wiki* [19:36] -------------> that was 5 minutes discussion time [19:36] Well - only because of the strike-throughs which are really more one opinion than a justified veto? [19:36] As suggested, I'd love to have a "-2..+2" rather than a "0/1" vote [19:36] so lets stfu again so i can put forward two proposals [19:36] i've heard two suggestions on how to move on: [19:36] any definitive date on when the name will be decided? [19:36] * ktwilight has quit IRC (Remote closed the connection) [19:36] Were anyone interested in my wife's offer? Noone commented [19:37] 1. put feedback on the ChoosingANameLocked topic [19:37] and give that back to the copywriter [19:37] i offer a 3rd suggestion if you will [19:37] * MartinSeibert will accept any suggestion as a name that had a decent discussion and thorough thoughts on it. I am completely confident, that you will not come up with a solution, that I can find problems in. :-) [19:37] 2. bring it down to about 8 now, and let lavr's wife help us with picking one [19:37] ok travisbarker (and ONLY travisbarker): 3. [19:38] Lavr: cool! [19:38] * MichaelDaum has joined #nextwiki [19:38] Lavr: Michael Daum is working on that with a copywriter. Please contact him [19:38] open all the names back up and do a moderation point style vote on the topic [19:38] the one that rises to the top wins [19:38] I got some "I am interested" on side channels [19:38] Hi there. Sorry for beeing late. Kids needed food and bed. [19:38] [19:38] Lavr: Please go for it, that is a good help for Michael in my opinion. Sorry for not commenting. [19:38] * ktwilight has joined #nextwiki [19:38] OK. I will ask her to make it. it will be a short easy one. [19:38] now i'm confused :( [19:38] Wolf_Marbach: doesn't hurt to have redundancy. The CopyWriter is paid to do that, maybe do "load balancing" to a certain extend? [19:38] thank you all for being QUIET during my suggestion [19:38] no fuckin dicipline [19:39] what travisbarker said.. [19:39] anyway [19:39] Hi Michael: Its your topic. :-) [19:39] I'd be happy with 2 or 3. [19:39] Diane will have it ready by Wednesday night. If we can have the list down to 8 max by then.. [19:39] shall we say that MichaelDaum and Lavr_ are going to coordinate in bringing it down to 7-8, perhaps with some more input frfom the copywriter [19:39] okay [19:39] Markus: Not redundance communication! [19:39] ? [19:40] gmc: fine. [19:40] may Isuggest a combination of 2 and 3, lets take all unstriked ones, and vte on those. we need to reduce, and fast. [19:40] shall we say that MichaelDaum and Lavr_ are going to coordinate in bringing it down to 7-8, perhaps with some more input frfom the copywriter [19:40] gmc: +1 [19:40] if you have opinions on how to do this, contact Lavr_ and MichaelDaum [19:40] Stephan the copywriter said never go with more than 10 [19:40] ACTION: MD and Lavr to lead reduction to 8 names and organise voting. [19:40] gmc:+1 [19:40] gmc - fine [19:40] gmc:+1 [19:40] ay [19:40] +1 [19:40] +1 [19:40] +1 [19:41] ACTION: DianeChayer to post questionaire Wednesday night latest. [19:41] k [19:41] Cool. That is productive now. :-) [19:41] ok.. [19:41] Time: +40 [19:41] ---------> 2 media plan [19:41] who is DianeChayer, sorry for asking [19:41] ACTION: All to return it 1-2 days later. Takes 10 minutes to complete [19:41] DianeChayer is Kenneth's wife [19:41] --------------> 2.1 google ads and such [19:41] Lavr: Will do. [19:41] MichaelDaum: take it off channel, chaps [19:41] That was my suggestion. [19:41] yes we want to market on the "TWiki" namespace [19:41] would be silly not to [19:42] I wanted to make sure, that we reach the twiki-searchers on google. [19:42] how much money would that cost ? [19:42] what are we trying to achieve? [19:42] it'd be confusing IMHO. [19:42] my 2cents: it'd be good, but lets wait till we have 1. a release, 2. an association to pay for it [19:42] agreed, but do we defer this til we have a name and an association [19:42] I'm with gmc on this one. [19:42] snap [19:42] Cost will be up to 150 Euro per month. [19:42] gmc: +1 [19:42] gmc: agree [19:42] * TravisBarker agrees with gmc a release must come first [19:42] it would achieve getting out word to folks who don't know about fork [19:42] +1 [19:42] thats a guess. [19:42] gmc: +1 [19:42] gmc: +1 [19:43] gmc: +1 [19:43] gmc, +1 [19:43] gmc +1 [19:43] ok, with your permission i move on [19:43] when doing google marketing you always advert on your competition "key words" its just how its done [19:43] /SEIBERT/MEDIA runs about a 8digit turnover with Google per year with clients. I will ask Google to give it to us for free. [19:43] -------------------> 2.2 [19:43] gawd this is turbulent in here [19:43] -------------------> 2.2 comunication to users [19:43] MichaelDaum: please use #twiki_fork for off-topic remarks [19:43] Okay for me. [19:44] need to draft a letter to existing TWiki clients that explains well the situation in clear and professional language [19:44] proposal is for specific actions to keep the "website" up to date [19:44] do we have a list of twiki users ? if not, where do we get one ? [19:44] users=clients [19:44] some sort of official status-blog would be nice. [19:44] CDot: i dont quite understand that item.. [19:45] i'm not comfortable spamming the t.o password list [19:45] SvenDowideit: me neither [19:45] but a blog and newslesster web would be GOOD [19:45] We will catch all TWiki-users with a great software to update to and an automatic update. [19:45] i was planning on writing a 7day summary [19:45] ok, a blog and a newsletter, that would indeed be good (and i'm not biased, i just started the blog and newsletter on tdo :) [19:45] but i've not gotten there - [19:45] gmc zactly :) [19:45] Sven, gmc +1 [19:46] Sven: need blog, newsletter and news page [19:46] actions needed: set up a blog web [19:46] I have the list of emails from the old twiki-announce if we dare abusing that in a good cause. [19:46] Lavr_, i think we shouldn't [19:46] gmc: +1 [19:46] actions needed: set up a mailing list [19:46] actions needed: someone to emai lthe newsletter based on blog posts once in a while [19:46] Sven. That is also my thought but I wanted to test my ethics.. [19:46] +1 [19:46] +1 [19:46] +1 [19:46] +1 [19:47] what are we +1'ing on? [19:47] +1 [19:47] definitely don't spam the announcements list, t.o will do a good enough job sinking itself that clietns who haven't heard of us yet will eventually go looking [19:47] gmc: +1 [19:47] So we need a Vicky replacement. Volunteer? [19:47] and we can ensure it sinks itself by being a stronger project that attracts more talent/contributions [19:47] sayotte: please stay on topic [19:47] Is Vicky going to come over? [19:47] Lavr_: Describe the task in short and all others should read it. [19:48] gmc, on mailing list, newsletter and blog [19:48] Task is to "compile" a news letter based on blog postings. [19:48] ok, so we agree on having a blog+newsletter+ml, we now are looking for a volunteer [19:48] * CDot sees that as a job the MarketingtaskTeam will "just do" [19:48] CDot: good suggestion indeed [19:48] CDot, +1 [19:48] CDot: +1 [19:48] Still good with ONE person responsible [19:49] marketing team can call on infra team or site facilitator team for setting things up [19:49] I am very bad at such things. But I will try to find help if you wish. [19:49] CDot, +1 [19:49] 1. Ok, we need a english-native speaker [19:49] 2. We need a "insider" [19:49] -> so let this be a group -> CDot: just perfect [19:49] +1 [19:49] we have MichaelCorbett [19:49] Would Michael do that for NextWiki? [19:49] Ask task team to identify individual who will manage that. [19:49] i think he could be persuaded [19:50] MichaelCorbett: is listed in the MarketingTaskTeam [19:50] He is here, isn't he? [19:50] he twittered pro nextwiki [19:50] ok.. [19:50] i think we should move on [19:50] Sorry, I've been distracted [19:50] he hates IRC, so probly isn;t listening [19:50] ah [19:50] Yes, I do hate IRC [19:50] MichaelCorbett: [19:50] But I'm sort of lurking [19:50] MichaelCorbett: would you be willing to coordinate a blog+newsletter for nextwiki? [19:50] ACTION: marketing task team to list newsletter etc jobs that need "just doing" for input [19:50] Thinks... [19:51] MichaelCorbett: if so, tell MartinSeibert offline :) [19:51] * MartinSeibert hopes ... [19:51] because we're a-moving-on (unless someone yells HALT! HAMMERZEIT! now) [19:51] Martin, I'm pretty OK with that but ploease can we chat about it [19:51] How about a skype call after this meeting? [19:51] Sure. Agreed. [19:51] Great [19:51] Next! [19:51] :-) [19:51] I will support where I can. [19:51] ------------------> 2.2.3 rapid response team for press inquiries [19:52] ACTION: MichaelDaumis going to coodinate the newsletter / blog -> move on [19:52] (damn ( MichaelCorbett ) [19:52] no [19:52] yea [19:52] :) [19:52] :-) [19:52] Daum? woops [19:52] i would vote MichaelDaum for rapid-response press person btw [19:52] rapid response team == marketing task team, otherwise they could fget confused [19:52] CDot, +1 [19:52] +1 [19:52] +1 [19:52] +1 [19:52] That is what I thought: +1 [19:53] +1 [19:53] ok.. [19:53] +1 [19:53] +1 [19:53] +1 [19:53] +1 [19:53] +1 [19:53] MichaelDaum: OK? [19:53] ACTION: marketing team sets up rapid-response email adress or phone no visible on site [19:53] erm what? [19:53] The main thing here is being ready for rapid response to negative statements from twiki.net [19:53] gmc - mailing list? [19:53] i think we should stop saying +1 unless i say VOTE: blablabla [19:53] um, does that mean the taskteams are in action? [19:53] i dont know what people are +1'ing to [19:53] ok [19:53] gmc: agreed. +1 ;-) [19:54] MichaelDaum: rapid response team == marketing task team, otherwise they could fget confused <- this should be your task [19:54] you are too fast - me too slow reading [19:54] gmc: yes [19:54] gmc, it was to CDot's rapid response team == marketing task team [19:54] EugenEsch: you are confusing us all! [19:54] Oh its me, sure thing. I shut up [19:54] * MichaelDaum does not know what he is buying signing down here [19:54] gmc: Ask a clear question that let people vote :) [19:55] VOTE: marketing team will coordinate rapid-response for press inquiries (possibly discussing with MichaelDaum ) [19:55] s/that/then/ [19:55] +1 [19:55] * GilmarSantosJr agrees [19:55] +1 [19:55] +1 [19:55] +2 [19:55] +1 to team, discussing with anyone they need to :) [19:55] +1 [19:55] +1 [19:55] +1 [19:55] +1 [19:55] +1 [19:55] okay, please mail around the relevant marketing hub so that we can coordinate offlineish [19:55] * niekie has joined #nextwiki [19:55] MichaelDaum: It was at the beginning when I was assigned to be the central contact for new people in the community. Now the question was about the press. People said, I should do that too. You were suggested also. Maybe you want to join the club? [19:55] allright.. lots of +1's.. [19:56] please take that offline [19:56] a suggest we move on, unless someone yells HALT! HAMMERZEIT! now [19:56] I will talk with Michael about that later. [19:56] we go to [19:56] -------------------_> 3. task teams [19:56] -------------------> 3.1 do we go for task teams [19:56] yes [19:56] seems like a passed station [19:56] Action item for MartinSeibert: Talk to MichaelDaum about press contacts. [19:56] yes [19:56] yes [19:56] does anyone want to say something on this? [19:56] no-brainer [19:56] yes [19:57] too late, we just did [19:57] no, [19:57] yrd [19:57] -------------------------> 3.2 what task teams are missing? [19:57] Task teams YES. Rubber stamp? No. No point stalling people [19:57] Task Teams are cool. Thanks to CDot for this idea. [19:57] I would like to suggest each team design and adopt a Team mascot for moral and identity. [19:57] http://nextwiki.org/Community/TaskTeam [19:57] good idea [19:57] +1 [19:57] if you know what task teams are missing, answer is simple; create them! [19:57] TravisBarker: how does this help [19:58] +1 to CDot [19:58] I like the idea. [19:58] CDot: yes [19:58] I am concious that there is no roadmap team [19:58] a same page layout for the task team pages would help as well [19:58] I think that is the key missing team [19:58] Yes we need roadmap team [19:58] * WillNorris has joined #nextwiki [19:58] is it actually a team job? [19:58] so that every task team has some similar sections [19:58] just the formal ones [19:58] Roadmap team to COORDINATE roadmap. [19:58] dunno; if not a task team job, who does it? [19:58] not decide it [19:59] roadmap = PM coordinate!? [19:59] roadmap is spanning over all of the project. I dont think we can solve it inside a small task team. [19:59] I took the step to copy it to our site. We had a roadmap team from Berlin. [19:59] is DocumentationTaskTeam missing? i can't seem to load twikifork to check [19:59] Wolf_Marbach +1 [19:59] coordinate roadmap == make sure that the roadmap reflects the feeling of the community (IIRC) [19:59] we already have 4.2.4, 4.3, 4.4 and 5.0 planned. what else is missing? [19:59] ktwilight: yes, is missing [20:00] Roadmap <> release plan [20:00] VOT: Wolf_Marbach to coordinate roadmap inputs as part of PM role [20:00] roadmap is for software development plan, PM is for project as whole [20:00] compiling a roadmap means coordinate vison+needs+abilities+realism [20:00] they are distinct [20:00] +1 [20:00] +1 [20:00] +1 [20:00] +1 [20:00] +1 [20:00] +1 [20:00] +1 [20:00] * GilmarSantosJr got it :) [20:00] -1 [20:00] yeah, we need that [20:00] 0 [20:00] Lynnwood: roadmap for release is a subpart and lavr will coordinate [20:00] -1 [20:00] *2 [20:00] Lynnwood: ? [20:00] http://www.twikifork.org/Development/RoadMap [20:00] ok we have two -1's [20:01] what are we voting for? :/ [20:01] everyone plz quiet except for Lynnwood and sayotte [20:01] 0 [20:01] roadmap for release is distinct from longer-term software roadmap [20:01] Roadmap is the technical / feature things we need long team. Release management is to define in which release each feature goes [20:01] w'ere talking long term roadmap [20:01] right [20:01] related but not the same [20:01] software roadmap => Task team [20:01] short term is more productive [20:02] short term == PM and release mgr jobs [20:02] Sven +1 [20:02] ok all cdot put to vote was that the project manager will coordinate the road map.. [20:02] different but similar task [20:02] Sven+1 [20:02] related, not the same. a long-term roadmap needs to be extremely circumspect [20:02] which isn't something that can be expected of one person [20:02] sayotte: true [20:02] sayotte, y, thats why having an independant PM manage the process [20:02] ok [20:02] is useful [20:02] we're not saying Wolf_Marbach will write it [20:02] hey guys roadmaps isnt something new. [20:03] long-term roadmap could be new task team. not as critical in short term [20:03] right so to be clear: a road-map should be developed by multiple people and executed by a PM [20:03] my opinion anyway [20:03] Clarify: i do not want to create the roadmap just coordinating [20:03] we _have_ a roadmap, Wolf_Marbach as project manager will see that it is executed and changed if needed [20:03] people, i need to go (hard stop at 1hr). [20:03] that is what we were proposing sayotte [20:03] Roadmap is not urgent. The one on http://www.twikifork.org/Development/RoadMap reflects Berlin output. Good enough for now [20:03] Soronthar, :) [20:03] sayotte: road map is for all the community to put together! [20:03] IMHO [20:03] keep the energy up [20:03] it was unclear if only to me [20:03] ok [20:03] +1 [20:03] for the records, i vote to continue the old numbering so the next release is 4.2.4 [20:03] bye [20:04] this was actually about what task teams are missing [20:04] Bye [20:04] QUESTION will Wolf_Marbach create a roadmap task team?? [20:04] * Soronthar has quit IRC ("ChatZilla 0.9.83 [Firefox 3.0.3/2008092417]") [20:04] Lets move to the next topic. [20:04] if any task team is missing, add it to http://nextwiki.org/Community/TaskTeam#current_task_teams [20:04] gmc, please put this back on course [20:04] which brings us to [20:04] ---------------------> 3.3 [20:04] gmc, just added DocumentationTaskTeam [20:04] ok, so we are agreeed, PM will coordinate LONG TERM roadmap (as distinct from release plan)? [20:04] rubberstamping of task teams [20:04] CDot: yes [20:04] ACTION: PM will coordinate LONG TERM roadmap (as distinct from release plan) [20:04] +1 [20:04] My proposal. RoadMap is what we have from Berlin. After association has a board they own the roadmap [20:04] Lavr_: take it up with the PM :) [20:05] offline [20:05] ---------------------> 3.3 rubberstamping of task teams [20:05] my original reason for rubber-stamping was to stop task teams getting "carried away" [20:05] i.e. to keep them "on plan" [20:05] and to prevent a proliferation of useless taskteams.. [20:05] aye [20:05] What do you mean by rubber-stamping? [20:05] eg a StopRacismOnNextWikiOrgTaskTeam or wahtever [20:05] MartinSeibert: a seal of approval.. [20:05] and stamp at meeting or at PM level [20:05] right, Q, is DocumentationTaskTeam useless? [20:05] MartinSeibert: 'yes the community acknowledges this task team' [20:06] Lavr_: take it up with the PM :) - NO! Too important to be decided by one person [20:06] I am against it until we need it. [20:06] MartinSeibert: read the TaskTeamGovernance again [20:06] ktwilight: offtopic [20:06] ... [20:06] i thought it's about rubberstamping task teams. [20:06] question: will the task team be approved by PM or community meetings? [20:06] ktwilight: we're discussing the process of rubberstamping, we're not actually rubberstamping now :) [20:06] Why should we rubberstamp something that is okay now. There is no big danger, is there? [20:06] I don;t think we need it yet; there is enough energy applying checks and cross-checks [20:06] guys sorry need to dash. will meet carlo soon. [20:06] gmc, oh right... [20:06] Rubberstamping. It worked badly on t.o [20:06] question: will the task team be approved by PM or community meetings? [20:06] 4th time [20:06] MichaelDaum: nice timing :) [20:07] why? [20:07] that's a q for the association, i think [20:07] ok.. [20:07] * carlo- needs to clean his flat quick [20:07] rubberstamping put off until we have an association [20:07] VOTE: delay rwequirement for rubber-stamping until association in place [20:07] +1 [20:07] for now, if 'dangerous' task teams emerge, we assume the community will step in [20:07] +1 [20:07] +1 [20:07] -1 [20:07] any other minuses? [20:07] sta+1 [20:08] +1 [20:08] oops +1 [20:08] +1 [20:08] +1 [20:08] Sven, explain? [20:08] oh, so current teans are now ratified [20:08] see y'all in about 1h on irc, then from carlo's (cleaned) flat. [20:08] allright.. so sven, unless you have something really really important against this [20:08] we're moving on [20:08] * MichaelDaum has quit IRC (Remote closed the connection) [20:08] (everyone byt sven quiet for a moment) [20:08] i don't want to see delay [20:09] i sort of agree [20:09] so i'd like the existing teams to be taken out of 'waiting for charter' [20:09] VOTE: this meeting rubberstamps all existing task teams [20:09] and so i don't see why we don't just rubber stamp them now [20:09] here [20:09] +1 [20:09] (including docco team) [20:09] +1 [20:09] +1 [20:09] +1 [20:09] +1 [20:09] all current task teams as of TODAY +1 [20:09] ACTION: CC to take existing teams "out of charter" until association is ready to review them [20:09] +1 [20:09] +1 [20:09] +1 [20:10] move on [20:10] CDot: i think that action was just overruled? [20:10] (association, content migration, infrastructure, marketing, release, user experience, website facilitator, documentation) are the task teams that are rubberstamped by this meeting as of now [20:10] association can review, revok and wikiact [20:10] -----------------------> release plan [20:10] ---------------------_> 4.1 version numbering [20:10] VOTE: our next release is 4.2.4 [20:10] -1 [20:10] Discuss first [20:10] please [20:11] y [20:11] Sorry, travis is right: clarification: ACTION: CC to take existing teams out of "out of charter" until association is ready to review them [20:11] allright, sorry [20:11] i wuld like to speak in favour of Y.M.p [20:11] VOTE: cancelled [20:11] -1 [20:11] Y.M.p. ? [20:11] yeah, month, patch [20:11] * MartinSeibert thinks this is minor. The most important thing is, that we have a working, bug-free and cool new release. [20:11] This is not minor [20:11] year, month, patch? [20:12] it's important in terms of "image" and "direction" IMHO. [20:12] as i have alot of clients that fail to know how old their software is [20:12] better not to be confused with twiki release number as they will diverge [20:12] We can end in a release war unless we start at 1.0 or other new release numbering [20:12] i.e. Allabra-8.12.0 [20:12] good point.. [20:12] its also where alot of projects are heading [20:12] Lavr_, +1 [20:12] -1 I think 4.2.x will introduce confusion with TWiki.net releases [20:12] We signal that WE are the real old project by staying at 4.2.4 ... [20:12] disagree [20:12] we do, but we'll always be causing confusion [20:12] It is the pros and cons of these two arguments. [20:12] disagree [20:12] we have a new name; we can't be the old project [20:13] Maybe this would be a topic to shelve to wiki page discussion? [20:13] we don't get the trademark, so it doesn't matter. [20:13] CDot, +1 [20:13] ( 70 minutes in and we're almost halfway ) [20:13] whereas using y.m.p we sidestep the entire game [20:13] ok.. [20:13] SvenDowideit: +1 [20:13] I do not like the y.m.p [20:13] Lavr_: rationale? [20:13] if a release gets delayed the whole system is fucked up [20:13] Lavr_, its just a set of numbers - but explain why [20:13] Sven: +1 [20:13] not really [20:13] I like that the next release number is known and stable [20:14] y.m would be fun as it is the ubuntu naming scheme, given the priase of ubuntu by t.n [20:14] Lavr: agree [20:14] we don't need to call the branch until the day [20:14] ok we have three proposals: A continue twiki version numbering, B use Y.M.p, C use 1.0 or 1.0.1 etc.. [20:14] Lavr_: agree on that point [20:14] so there is not scope for fuckage [20:14] SvenDowideit: what about roadmap planning? [20:14] use a symbolic name ubntil the numebr is known [20:14] 09.03.01 can easily become 09.04.1 [20:14] e.g. "Georgetown" [20:14] symbolic names suck imho [20:14] sayotte, freetown? [20:14] ok [20:14] sorry, release management [20:14] Then we are back at the Peter Thoeny name horror [20:14] another point [20:14] using y.m [20:15] sends a clear message [20:15] "we will incorporate that feature into release +months?" [20:15] that we are commited to doing our best to release _then_ [20:15] not like twiki [20:15] We use humor-based code names - working great. ProjectBanana ftw [20:15] where a release gets delayed by 6+months [20:15] * CDot hates that; release when ready, I say [20:15] We NEVER released on the date we wanted. 4.2.1 was 6 months delayed [20:15] release when ready - yes [20:15] ok we have three proposals: A continue twiki version numbering, B use Y.M.p, C use 1.0 or 1.0.1 etc.. [20:16] any other proposals? [20:16] I prefer good old well proven easy to understand and predict x.y.z [20:16] any other discussion items? [20:16] Yes to: release when ready. [20:16] we need to move on ppl, lets vote [20:16] I suspect this could be a larger topic - are we ready to commit to it already with no reservations? [20:16] I see TWO votes [20:16] at work, after a release that took too long we now are commited to fixed dates (every 7 weeks). Stressful, but beneficial. we drop ~ 50% of the feartures at each release (internal service) [20:16] ok we have three proposals: A continue twiki version numbering, B use Y.M.p, C use 1.0 or 1.0.1 etc.. [20:16] VOTE: A or B or C [20:16] I am for C or B. [20:16] NO!!!!! [20:16] B or C [20:16] SvenDowideit: I agree there, but that requires a really dedicated release team capable of bumping features back to the next release when necessary (since we can't force people to work long hours to produce them on time) [20:16] no vote here [20:17] sayotte, y, and i recon we can do that [20:17] Never vote for multiple choices dammit. [20:17] Lavr: A +1 [20:17] Lavr_, this is not binding [20:17] A -3 [20:17] B +1 [20:17] Please keep marketing in mind! [20:17] ok, no vote [20:17] A -3 is not a valid vote [20:17] I will not vote this stupid way [20:18] ok if you're going to call people stupid i suggest i leave now and go have dinner [20:18] heh [20:18] Suggest: Shelve topic to wiki discussion, move on [20:18] gmc please stay [20:18] what's a better way to vote for versioning? [20:18] You always have to vote for or against something. [20:18] All I can say is that A is not a good solution in my opinion: A -1 [20:18] post example vote format, please [20:18] VOTE: discuss on the wiki [20:18] +1 [20:18] +1 [20:18] +1 [20:18] +1 [20:18] +1 [20:18] +1 [20:18] +1 [20:18] +1 [20:18] +1 [20:18] +1 [20:18] +1 [20:18] +1 [20:19] action lavr to lead the discussion? [20:19] Sure [20:19] sure [20:19] +1 [20:19] no vote on that, lavr leads discussion [20:19] Next topic, please. [20:19] ----------------------> 4.2.1 [20:19] ----------------------> 4.2.1 what are we releasing [20:19] ACTION: Lavr to lead discussion on release numbering on wiki to a rapid conclusion [20:20] my suggestion would be to do a release fast, where the major thing is the renumbering and bugfixes.. nothing fancy [20:20] we have 2 dev thread ATM [20:20] s/renumbering/renaming/ [20:20] we have Release 04x02 and trunnk [20:20] i agree with gmc [20:20] sorry for being late, hi * [20:20] trunk is dangerous; it has the stand-alone code and other untestednesses [20:20] We need a release FAST. We need to be a project with a release people can download [20:20] trunk will need quite a few more months to iron out [20:20] Babar: welcome, we're at 4.2.1 of http://www.twikifork.org/bin/view/Community/CommunityMeeting2008x11x03#foo_42 [20:20] release04x02 *already* has more bugfixes than TWiki [20:21] and will get more [20:21] First release should be the 4.2.4 that TWiki would have released if we were there. But rebranded! [20:21] Lavr: agree, but should be just a bugfix [20:21] i'm going out on a limb here: [20:21] Rebrand + existing already committed bugfixes. [20:21] VOTE: we release 4.2.x asap, with s/TWiki/OurNewName/ [20:21] Koen: there is no 4.2.1 :) [20:22] -1 [20:22] We have to release ASAP. [20:22] +1 asap, but note that compatibility code and stuff needs development [20:22] +1, but we have to connect to TWiki somehow to draw attention [20:22] VOTE cancelled [20:22] Rebranding means including compatibility code [20:23] * ktwilight is waiting to hear from CDot [20:23] y, its not a simple patch like release [20:23] which is one reason the 4.2.4 number isn't really right [20:23] * CDot is waiting for prmission to address the chair [20:23] CDot: go ahead [20:23] * ktwilight is glancing over at gmc [20:23] (i dont even have ops) [20:23] * SvenDowideit sets mode: +o gmc [20:23] as sven said, ASAP is too soon; we need compatibiluity code and "stuff" that differentiates [20:23] otherwise it's a "me too" [20:24] and the next TWiki release blows us away [20:24] we have a brweathing space; no-one expects us to rush out a release [20:24] Compatibility - yes. Other stuff NO WAY! We need a download available and it cannot happen fast enough. [20:24] ASAP is never too soon, if you define the P properly [20:24] _I_ expect a rush release. [20:24] How about a bugfix asap and a well planned new relöease commencing next year? [20:24] If we do not have a download we are just a vaporware bullshit project [20:25] Lavr_: we cannot release something that still has TWiki::Foo::Bar.. that would be silly at the least [20:25] basically, i think the rename, and compatibility code is enough work [20:25] Lavr: agree we need download [20:25] that getting it done 8.12 will be hard work already [20:25] and we have to do the rebranding properly, without breakage [20:25] Rebranding includes TWiki::Foo::Bar. [20:25] SvenDowideit: +1 [20:25] but for me, that is the goal [20:25] Lavr +1 [20:25] I gree with Sven [20:25] I also think we need a release fast, so that users do not need to download from twiki.org [20:25] Rebranding means getting rid of TWiki everywhere [20:25] that way be have a checkpoint for the next releases to work from [20:25] I'm with Sven's last statement [20:25] AndreU EXACTLY [20:25] * OliverKrueger has to leave now. :( (For the records: +1 for geo-loc. servers) :) [20:26] FWIW, it took Joomla months to release their first version. [20:26] VOTE; the next release will be rebranded and compatibility layer, and bugfixes we may have lying around [20:26] +1 [20:26] Sven: I understand you but we need a release 4.2.4 for markting reasons [20:26] +1 [20:26] If we release soon, it means using the TWikiname. Very dangerous seeing t.n state of mind [20:26] +1 [20:26] +1 [20:26] +1 [20:26] +1 [20:26] +1 [20:26] No TWIki name Colas. [20:26] +1 [20:26] +1 (yup) [20:26] -1 [20:26] -1 for the reasons I gave [20:26] What we are voting fpr? [20:26] -1 [20:27] democracy rules! [20:27] VOTE; the next release will be rebranded and compatibility layer, and bugfixes we may have lying around [20:27] If we let twiki.org release the next release before us we are DEAD [20:27] Wolf_Marbach: VOTE; the next release will be rebranded and compatibility layer, and bugfixes we may have lying around [20:27] Wolf_Marbach, ^ [20:27] ok, i see more +1 than -1 [20:27] one caveat: if t.n. comes out with new release with new features, we should reconsider so as to at least match feature set. [20:27] +1 if we have bugfix for download [20:27] 10:2, motion carried I believe [20:27] i think we have a decision, and of course we'll change that if we need to [20:27] are we going to get all shaky because t.o released first? do we lack so much confidence?? [20:27] revise ones insights and all [20:27] +1 if new name and new version scheme is used. [20:28] I will swim with the rest. But I think we have time for really good work. [20:28] we move on unless i get a HALT! HAMMERZEIT! [20:28] ACTION: Lavr to drive release team to an ASAP compatibilty layer + bugfix release [20:28] ----------------------------> 4.2.2 when do we release [20:28] That is what I wanted to do as RM [20:28] i dont think we're going to decide on a release date now, i leave that to lavr's discretion myself [20:28] when we are ready? [20:28] Lavr decides [20:28] when we are ready! [20:29] (ah a plate of food is shoved in front of me, nice!) [20:29] The important part is the scope! [20:29] VOTE: we release when we are ready :) [20:29] +1 [20:29] +1 [20:29] Which I put in the release plan I suggested. [20:29] gmc (pass that on, plz) [20:29] 1hour 30 minutes in [20:29] +1 [20:29] +1 [20:29] +1 [20:29] +1 [20:29] +1 [20:29] +1 [20:29] +1 [20:29] +1 (we cannot releas if we are not ready anyways :-) [20:29] +1 (of course...) [20:29] +1 [20:29] (hope we are READY before t.o) [20:29] ------------------_> 5 resources and resource management [20:29] +1 [20:30] i'm actually not sure we need t odiscuss 5.1 and 5.2 plenary [20:30] 5.1 would be nice 5.2 not me [20:30] VOTE: let the infrastructure team handle 5.1 and 5.2 [20:30] I just wanted to be sure a task team had it in their remit to do 5.1 and 5.2 [20:30] +1 [20:30] +1 [20:30] so +1 [20:30] +1 [20:30] +1 [20:31] +1 5.1 & 5.2 to task team [20:31] CDot, +1 :) [20:31] +1 [20:31] +1 [20:31] ACTION: infrastructureTaskTeam take control of 5.1 nd 5.2 [20:31] machine donations, yes. money, let's wait for the association [20:31] +1 [20:31] ---------------> 5.3 [20:31] Mirrors - not urgent. Let the team run +1 [20:31] does anyone no what 5.3's about? [20:31] "other possiblities like techwriter to guide us in re-writing clearer documentation (that we can license differently even) " [20:31] what'd 5.3? [20:31] sorry [20:31] 5.3 was propoed by Martin, i think [20:32] i tossed that in the wrong spot really [20:32] TechWriterTaskTeam or ResourcesTaskforce [20:32] ah, ok. Ignore it? [20:32] and its irrelevant til we have an assoc [20:32] ya [20:32] ok, lets move on then [20:32] ignore for now: +1 [20:32] ------------------> 6. license [20:32] CDot: no. Not my idea. [20:32] ---------------> 6.1 gplv2 vs gplv3, affero ? [20:32] ok [20:33] the licence for twiki is [20:33] SvenDowideit: please could you elaborate (everyone else be quiet) [20:33] GPL2 _OR_ later [20:33] * GilmarSantosJr is not prepared to vote on this today [20:33] the intent of that [20:33] is that anyone can choose to pick later [20:33] * Babar neither [20:33] i recon we should consider doing so [20:33] SvenDowideit: the receiver of the code can choose to do so.. [20:33] to reaffirm our desire to be free [20:33] I have no opinion on GPL2 or 3. As long as it is GPL and we are OK to do what we choose [20:34] gmc, exactly, as we're the receiver [20:34] i dont think you can actually re-license 'gplv2 or later' into 'gplv3' [20:34] I need to ask my lawyer. [20:34] +1 for Sven [20:34] SvenDowideit: what is the pros of doing so ourselves rather than letting end user decide? [20:34] gmc i think you can [20:34] from what i read [20:34] I really don´t know if we could decide this with this state of knowledge [20:34] i remember difficulties with linux [20:34] I don't know what would change for our system ??? [20:34] the linux kernel [20:34] no [20:34] we should ask the experts (FSF etc) [20:34] linux k has not problem [20:34] as far as i know, its just a personal choice [20:35] I am also unsure about GPL2 can just be upgraded to GPL3 without 100% concent. I do not thing we can. [20:35] TravisBarker: con: we do not have the time to ponder all the pro/cons of v3 in a short time [20:35] gmc: taht's wahy linux is/was "GPLv2" and not "GPLv2 or later" [20:35] and linus chooses not to do so for his release [20:35] but i think it is clear, this topic needsd some more lengthy discussion, that we're not going to do here and now [20:35] ok, idea mooted, and tossed for next meeting :) [20:35] We need legal advice before we change at least. [20:35] i vote to table issue [20:35] SvenDowideit: may we ask you to head this discussion on the wiki/ml? [20:35] I would like to explore the possibility of a mechanism that allows extension developers to license under different terms. [20:35] CDot, it'll be very difficult i fear [20:35] not here; in a topic. [20:35] yup [20:36] ACTION: sven to make topic and discuss [20:36] so i think that's 6. license for now [20:36] Seems to be an association thing to decide? [20:36] +1 [20:36] Someone should take the task to seek advice on the GPL3 question [20:36] +1 [20:36] ACTION: SvenDowideit to lead discussion on product + extensions license [20:36] +1 [20:36] +1 [20:36] lets move on [20:36] +1 [20:36] +1 [20:36] +1 [20:36] +1 [20:36] ---------------------------> 7 advertising on our project site [20:36] +1 (move on) [20:36] +1 [20:36] wtf are you voting on? [20:37] CDot: they're not voting, they're just polluting the channel [20:37] they're voting on the license. [20:37] :-) [20:37] lol [20:37] ---------------------------> 7 advertising on our project site [20:37] must be lags [20:37] If you don't want vote on something, don't put out VOTE: [20:37] Careful. There can be lag on IRC [20:37] or loaning moral support to actions for which there was no vote? [20:37] ah.. lag.. yes.. :( [20:38] * CDot never saw the VOTE:, is all [20:38] (makes mental note, need to come up with and document some proper irc meeting procedures if we keep having full-house like this) [20:38] * MartinSeibert is all for commercial advertising on the site and is willing to pay for it. [20:38] if you're only proposing something, put PROPOSE [20:38] i'm very much against commercial advertising on the project site [20:38] guys I have a very urgent issue here [20:38] restrict VOTE to chair. i.e. gmc [20:38] gmc: parlimentary procedure works rather well [20:38] and I want that we talk about that before it got worse [20:38] i'm very against advertising on the site [20:38] we have to keep our platform clean as possible from commercial interests [20:38] i thought the nextwiki would be commercial neutral [20:38] HALT! HAMMERZEIT! [20:38] Advertising: We need a clear guideline. [20:38] ACTION: GMC creates IRC-rules. [20:38] andreu has the floor! [20:38] Please let Andre have its say! [20:39] actually this is one of the reason why we forked [20:39] Lynnwood: +1 [20:39] the rest silence [20:39] i am also against advertising on the site [20:39] thx [20:39] Jens already worked on: http://www.twikifork.org/Community/ByLaws [20:39] (andreu plz say 'done' if youre ready for discussion) [20:39] we need some kind of commitment, that we want to act neutral [20:39] just saw: http://www.twikifork.org/International/DE/DonationRequestTemplate [20:40] and I must say this is not good [20:40] search on nextwiki: http://nextwiki.org/bin/kinosearch/TWiki/?search=SEIBERT [20:40] We need a strong commercial presense on the site so people know they can get paid support. But it must be restricted to well defined topics. [20:40] how about extensions that gets sponsored? are they allowed to be mentioned? [20:40] sorry Martin, but our community platform is not meant be a link-farm for your company [20:40] Lavr, this is a an absolute no go [20:40] Lavr_: ktwilight you're out of order [20:40] Propose: The website will have an area each to advertise free and paid [20:40] -1 [20:40] AndreU - I do not understand what is a nogo. [20:40] seperate site [20:41] i'm all for a seperate site, http://commercial.nextwiki.org/ (or whatever) where corps can go wild advertising themselves [20:41] a go would be specific pages, no go: spreading your company name all over the platform [20:41] ready [20:41] I think the guideline we had on t.o where there was ONE topic with the paid support with clear guide line how you are listed is a GOOD THING [20:41] seperate web and pages like aother OSS projects [20:41] Lavr_, most do not [20:42] And the strong presense is then to link to this page only. [20:42] i would prefer the name to allow us to use .com for the companies to found together [20:42] and the .org and .net for the OSS [20:42] VOTE: we are not advertising companies on the nextwiki.org site for now, and discuss further on/around http://www.twikifork.org/Community/ByLaws [20:42] gmc: commercial.nextwiki.org: +1 [20:42] I do not want to see another twiki.net be built up [20:42] use .net to be free nextwiki hosting for eg [20:42] Sven: I do not see the sense why? [20:42] gmc: +1 [20:42] gmc: +1 [20:42] so there is a clear and obvious difference [20:42] gmc: +1 [20:43] gmc, +1 [20:43] +1 [20:43] +1 [20:43] Right - will splitting off a separate site for commercial make us look like t.o / t.n? Vs. a single page. Also +1 [20:43] Propose: Have a detailed discussion on the wensite [20:43] +1 but we have to define what on that web [20:43] Andre: I remember one instance where somebody wiped out //SEIBERT/MEDIA, which is okay. If you have problems with my contributions. Point at them or just change them. I am not using NextWiki as a link farm. That is only your perception. [20:43] gmc +1 excert on the consultant for hire page. [20:43] excapt [20:43] except dammit [20:43] lavr good point [20:43] sorry guys, we redo [20:43] VOTE: we are not advertising companies on the nextwiki.org site for now, and discuss further on/around http://www.twikifork.org/Community/ByLaws except on the WikiConsultants page [20:43] Martin, everyone else is acting as individual here [20:43] +1 [20:43] except you [20:43] gmc pleas clarify the vote! [20:44] +1 [20:44] allright, full stop [20:44] VOTE cancelled [20:44] i'm making a mess now :) [20:44] good. [20:44] +1 [20:44] :) [20:44] because i thought we just settled the issue [20:44] I suggest you go back to your first vote [20:44] i second [20:45] which I +1'ed [20:45] which one was that? [20:45] VOTE: we are not advertising companies on the nextwiki.org site for now, and discuss further on/around http://www.twikifork.org/Community/ByLaws [20:45] VOTE: we are not advertising companies on the nextwiki.org site for now, and discuss further on/around http://www.twikifork.org/Community/ByLaws [20:45] It is essential to our project that people that cross over can find how to get paid support. [20:45] +1 [20:45] +1 [20:45] we'll vote on WikiConsultants next, please now only +1 or -1 [20:45] +1 [20:45] Having ONE page with the consultant is not a big issue [20:45] +1 [20:45] +1 [20:45] +1 [20:45] +1 [20:45] +1 [20:45] Lavr: true, but need some time to agree on!? [20:45] +1 [20:45] +1 [20:46] -1 I want the consultants page now [20:46] ACTION: we are not advertising companies on the nextwiki.org site for now, and discuss further on/around http://www.twikifork.org/Community/ByLaws [20:46] ok, motion accepted [20:46] VOTE: we make an exception to the last vote for the WikiConsultants page [20:46] +1 [20:46] +1 [20:46] +1 [20:46] +1 [20:46] +1 [20:46] +1 [20:46] +1 [20:46] +1 [20:47] +1 [20:47] For minutes: in which web is the consultants page= [20:47] ? [20:47] Action item for MartinSeibert: Clean the community platform from //SEIBERT/MEDIA and its links to seibert-media [20:47] Lavr_: Community.WikiConsultants [20:47] i sense no strong opposition and declare Community.WikiConsultants as the exception to the 'no company adversitements' [20:47] thanks [20:47] (and Extensions web??) [20:47] and that concludes point 2 of the agenda, at 1h45m ! [20:47] oh [20:47] sorry to re-open [20:47] i take my last sentence back [20:48] SvenDowideit: no problem, good point [20:48] can we agree on going with the tdo guidelines we had for that now [20:48] and include those in the discussion on Bylaws ? [20:48] vote? [20:48] +1 [20:48] :) [20:48] sure [20:48] For extensions the tdo guideline is a good rule to avoid extra work on plugins now [20:48] MOTION to take a 3-5 minute break [20:48] VOTE: for the Extension web we apply the tdo Plugins web guidelines for hte time being, and include this in the ByLaws discussion [20:49] +1 [20:49] +1 [20:49] +1 [20:49] TravisBarker: lets discuss after this vote [20:49] +1 [20:49] +1 [20:49] +1 [20:49] +1 [20:49] someone needs to copy the guidelines over [20:49] ACTION: migration task team copies Plugins web guidelines [20:49] no vote [20:49] Volunteer to copy the guide line? [20:49] ACTION: Lavr_ copies Plugins web guidelines [20:50] haha OK [20:50] oh, did i misread that? :) [20:50] point of order! [20:50] OK [20:50] a motion for a break has been tabled.. [20:50] i see we are done with our short-term agenda points [20:50] +1 [20:50] I would love to fetch a drink [20:50] so do we break, and go into 3. longer term [20:50] or do we just end here? [20:50] Would like to have chat about the PM work [20:51] afterwards [20:51] +1 break & come back [20:51] ehrm.. [20:51] end here; we've donee enough [20:51] VOTE: this meeting will adjourn [20:51] 2hrs enough, too much text. [20:51] +1 [20:51] think so too [20:51] +1 [20:51] +1 [20:51] +1 [20:51] +1 [20:51] need time to get ready for twiki_marketing of course! [20:51] +1 [20:51] -1 /me wants to finish after break [20:51] Sven. You kill me :-)))) [20:51] +1 [20:52] +! [20:52] :-D [20:52] +1 end [20:52] Lavr_, i support all forks [20:52] TravisBarker: sorry, you're overruled it seems .. [20:52] PROPOSE: Some guys a few minutes to discuss some PM stuff 10 min? [20:52] like i always do [20:52] Wolf_Marbach: i think that can be arranged [20:52] Wolf_Marbach, i'm awake, but not quite sane [20:52] gmc: are we adjourned? [20:52] I can discuss PM. But need to fill my glass [20:52] Wolf_Marbach: agreed [20:52] so any last chance to table something for this meeting before i adjourn [20:52] brilliant meeting, guys, once we worked out how to do it! [20:52] for the logs: they are at http://colas.nahaboo.net/twikiirc/bin/irclogger_logs/ [20:52] :) [20:52] yes, I have an AOB [20:52] A glass would be too early its 9 am [20:52] ok, no last items? [20:52] I have set the password to... [20:52] diane [20:53] counting 3 [20:53] I would like to ask all task team leaders to shout about what they are doing [20:53] 2.... [20:53] BUT I have a bug now so you cannot access, will fix it asap [20:53] CDot: now? [20:53] 1.... [20:53] gmc: not now, silly. Blog, mail to discuss, whateber [20:53] allright [20:53] meeting adjourned! [20:53] but report on status, let us all know what is going on [20:53] thanks guys, for cooperating and being so well behaved :)))))) [20:54] We need a page to document irc meeting process/rules [20:54] Please let the PM know what the actual status is [20:54] * CDot isn't sure if he got his point across there [20:54] Association Team: We are 99% done with articles. Next step. Invitation for general assembly [20:54] ok, short reopening: [20:54] thanks Koen for the good coordination of the meeting! [20:54] ACTION: task teams report on their progress by blog or other means [20:54] meeting re-adjourned [20:54] yes: thanks gmc for leading meeting! [20:55] it's TOUGH [20:55] how about a web including Pm tasks and task teams? [20:55] (cdot i assume a mail to the discuss mailing list for now would do too?) [20:55] I'll organize/summarize status info about ContentMigrationTaskTeam [20:55] at that topic [20:55] hm, still need to get on the MLs :) [20:55] and then those reports can be made into the first newsletter [20:55] Going forward it will be increasingly important to remember the cultural issues that lead to our founding this new community. Let us also remember the level of activity and cooperation that we have seen among colegues during this very volitile and emotional time. Let us do what we may to preserve the best parts of our work here today and keep the spirit of collaboration alive within our project for years to come. [20:55] GilmarSantosJr: I'd love to see some blog posts (when the blog is up) [20:55] good idea really [20:55] ok i suggest everyone moves to #twiki_fork again, apart from Wolf_Marbach and whomever wants to dive into project management [20:56] CDot: ok [20:56] (i'm not the chair anymore so this is just a friendely request :) [20:56] * CDot is staying for a while [20:56] yes, thanks gmc [20:56] * SvenDowideit scarpers off to grab food [20:56] * CDot needs to eat