Please do NOT use Google Groups - that interface is virtually impossible to work with - PINTA - please use a real listserver. If moving to Github, try Octopress +1
Thx - Ed On Fri, Nov 29, 2013 at 7:35 PM, Joseph Gentle <jose...@gmail.com> wrote: > We should keep a mailing list (on incubator.apache.org or on google > groups) until we can host these discussions in wave itself. We can > arrange google hangouts just as easily. > > -J > > On Fri, Nov 29, 2013 at 5:56 PM, Evan Hughes <ehu...@gmail.com> wrote: >> By moving to github will the community there be able to communicate as >> easily as we do here. I have no experience working on any long term gothic >> projects but in asf we can easily arrange for hangout debates which would >> need to be recorded for public view. Tbh I agree with deadlines and emails >> like these need to be frequent for us to band together. So either way after >> the review submission date we should start another email for prep to move >> to github or we should discuss the New timeline of the project and what we >> need to build this into a stable community. >> On 30/11/2013 8:59 AM, "Fleeky Flanco" <fle...@gmail.com> wrote: >> >>> very simple workaround, have everyone reply to everything in one blip, but >>> to append there name to things they say. this way you keep blip count low. >>> >>> the state of wave imo is that its a blank slate, you have to impose your >>> own organizational structure onto each wave, and how you do that dictates >>> how things work in that particular wave. that is the beauty and also the >>> problem of it. >>> >>> >>> On Fri, Nov 29, 2013 at 11:55 PM, Fleeky Flanco <fle...@gmail.com> wrote: >>> >>> > thomas, >>> > >>> > i dont think there has even been enough testing of wave to prove this one >>> > way or the other but the main point is that if we are all using wave for >>> > something that matters, it will piss someone off enough to actually start >>> > to fix things. >>> > >>> > >>> > >>> > On Fri, Nov 29, 2013 at 11:53 PM, Thomas Wrobel <darkfl...@gmail.com >>> >wrote: >>> > >>> >> So are you confirming then that Wave as it stands can (stably) take very >>> >> long discussion threads with lots of comments? >>> >> >>> >> I wasn't even aware the storage format of the current Wave builds was >>> >> final. >>> >> Maybe more has progressed in the last year then I was aware of. >>> >> >>> >> >>> >> ~~~ >>> >> Thomas & Bertines online review show: >>> >> http://randomreviewshow.com/index.html >>> >> Try it! You might even feel ambivalent about it :) >>> >> >>> >> >>> >> On 29 November 2013 23:44, Fleeky Flanco <fle...@gmail.com> wrote: >>> >> >>> >> > christian, from my observations of the project i would have to answer >>> >> no, >>> >> > its not working out ? >>> >> > >>> >> > pardon my passion on this subject (@mailing list) but ive kept quiet >>> for >>> >> > too long. id rather get an argument started on this rather then let >>> wave >>> >> > die the slow death that it is currently facing. passion is what wave >>> >> needs >>> >> > right now, not patience. >>> >> > >>> >> > i dont think moving wave to github or getting everyone to actually use >>> >> wave >>> >> > will magically make everything better, but i think that is a step in >>> the >>> >> > right direction that Should have been taken a long time ago. >>> >> > >>> >> > theres no reason that moving discussion to a wave server reduces the >>> >> open >>> >> > nature of the discussion, as stated previously, its trivial to make an >>> >> > anonymous account to grant anyone access to this discussion if it was >>> >> on a >>> >> > wave server. also anyone can register on a wave server and participate >>> >> in >>> >> > the discussion if the wave has been setup properly, theres even a >>> patch >>> >> > somewhere for rendering wave files as html files which would make it >>> >> > searchable by google and everyone esle. federation should make >>> >> propogating >>> >> > this data to multiple servers possible, using wave as the main >>> >> discussion >>> >> > area maintains the openness , searchability, and also longevity of the >>> >> > discussion. >>> >> > >>> >> > On Fri, Nov 29, 2013 at 9:41 PM, Christian Grobmeier < >>> >> grobme...@gmail.com >>> >> > >wrote: >>> >> > >>> >> > > On 29 Nov 2013, at 16:40, Fleeky Flanco wrote: >>> >> > > >>> >> > > i really dont understand why i have to be explaining the >>> usefullness >>> >> of >>> >> > >> using wave to communicate with the people on this list. its kindof >>> >> > >> amazing. >>> >> > >> >>> >> > > >>> >> > > If you don't understand why we operate on a mailing list then you >>> >> > probably >>> >> > > have >>> >> > > not understood that the ASF tries to develop in an open way. All >>> >> > > discussions must held >>> >> > > public and must be archived for a long time. The only solution so >>> far >>> >> is >>> >> > > mailing lists. >>> >> > > Wave is simply not that far to provide that at the moment. >>> >> > > >>> >> > > Of course there is an opportunity to bring Wave to the ASF. But >>> there >>> >> are >>> >> > > a lot of requirements >>> >> > > to meet. If you want to develop here, you need to fulfill these >>> >> > > requirements. >>> >> > > >>> >> > > We have discussed that several times. Every of the committers >>> >> understood >>> >> > > these requirements >>> >> > > and were working against them. However Wave is not there yet. >>> >> > > >>> >> > > This doesn't answer the question which was initially asked: is the >>> ASF >>> >> > the >>> >> > > right place? >>> >> > > Or more precise: can we as a project ever succeed the incubator and >>> >> > become >>> >> > > an ASF project? >>> >> > > >>> >> > > This has nothing to do with the great technology behind Wave nor the >>> >> > > willingness of people. >>> >> > > It is: is there enough manpower to live the ASF way or not. >>> >> > > >>> >> > > Christian >>> >> > > >>> >> > > >>> >> > > >>> >> > >> fleeky >>> >> > >> >>> >> > >> >>> >> > >> On Fri, Nov 29, 2013 at 4:19 PM, Robert Brumbelow < >>> >> > rkbrumbe...@gmail.com >>> >> > >> >wrote: >>> >> > >> >>> >> > >> Fleeky, those are fine for us, they will do little for outside >>> >> > >>> exposure. I would suspect having to use wave in order to learn to >>> >> use >>> >> > >>> wave might be self defeating. >>> >> > >>> >>> >> > >>> On Fri, Nov 29, 2013 at 10:05 AM, Fleeky Flanco <fle...@gmail.com >>> > >>> >> > >>> wrote: >>> >> > >>> >>> >> > >>>> >>> >> > >>> https://cwiki.apache.org/confluence/display/WAVE/Building+Wave+in+a+Box >>> >> > >>>> >>> >> > >>>> https://cwiki.apache.org/confluence/display/WAVE/Home >>> >> > >>>> >>> >> > >>>> also there is #wiab on irc.freenode.net >>> >> > >>>> >>> >> > >>>> also Ali just a few emails up mentioned that you could start a >>> >> > >>>> discussion >>> >> > >>>> on his wave server , why not try those things first? and if >>> there >>> >> is >>> >> > a >>> >> > >>>> problem, go to Ali's wave server and simply start a problems wave >>> >> add >>> >> > >>>> the >>> >> > >>>> participant @domain to the wave and everyone inclduing Ali on >>> that >>> >> > >>>> server >>> >> > >>>> should be able to see your problem wave, and maybe attempt to >>> >> answer >>> >> > >>>> your >>> >> > >>>> problem. >>> >> > >>>> >>> >> > >>>> -fleeky >>> >> > >>>> >>> >> > >>>> >>> >> > >>>> On Fri, Nov 29, 2013 at 4:01 PM, Robert Brumbelow < >>> >> > >>>> rkbrumbe...@gmail.com >>> >> > >>>> wrote: >>> >> > >>>> >>> >> > >>>> Thomas, >>> >> > >>>>> Hangouts on air are the recorded versions of Google Hangouts, >>> >> > >>>>> they are streamed and recorded via Youtube. Screencasts, I >>> >> thought, >>> >> > >>>>> also defaulted to being recorded. >>> >> > >>>>> >>> >> > >>>>> I know during my years of teaching, video was often preferred by >>> >> > >>>>> students simply because even in step by step instruction, aka >>> hand >>> >> > >>>>> holding, there would be something glossed over, ignored or >>> assumed >>> >> > >>>>> known by students or the teacher. Video shows every keystroke, >>> >> > command >>> >> > >>>>> and mouse movement >>> >> > >>>>> >>> >> > >>>>> >>> >> > >>> >>> >> > >>> >>> >> > >>> -- >>> >> > >>> Kelly Brumbelow >>> >> > >>> >>> >> > >>> >>> >> > > >>> >> > > --- >>> >> > > http://www.grobmeier.de >>> >> > > @grobmeier >>> >> > > GPG: 0xA5CC90DB >>> >> > > >>> >> > >>> >> >>> > >>> > >>>
