incubator-wave-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Upayavira>
Subject Re: Wave Kickstarter
Date Tue, 03 Dec 2013 10:04:00 GMT

On Mon, Dec 2, 2013, at 05:35 PM, Joseph Gentle wrote:
> On Sun, Dec 1, 2013 at 10:35 AM, Christian Grobmeier
> <> wrote:
> > Hi,
> >
> > On 1 Dec 2013, at 19:24, Joseph Gentle wrote:
> >> On Sun, Dec 1, 2013 at 9:22 AM, Ali Lown <> wrote:
> >>> My only worry with a KS is how do we market it? As beyond putting it
> >>> on Hacker News, explaining an P2P OT-backend communication system is
> >>> likely to confuse (if not discourage) potential backers.
> >>> (It also sounds more like the abstract for some academic research,
> >>> than a commercial project [the issue with being on the edge of
> >>> research for this technology]).
> >>
> >> Aside from hackernews, we should talk to techcrunch and all the other
> >> little tech news places. We should do a meetup on the topic here in SF
> >> to gather support, and we should try to sell the story to our local
> >> newspapers in our hometowns. I have friends who are good at this stuff
> >> that I can call on.
> >>
> >> I agree though - the hardest part is (as you say) figuring out how we
> >> distill down the idea to make it easy to explain.
> >
> > I can help a little with marketing. I have a well visited blog meanwhile
> > and the right story might draw some good attention to a kickstarter campaign.
> Oh sweet, thanks! We'll also want to do a media blitz, telling
> techcrunch and all those guys.
> > As I have some interest in making Wave happen and so I would even support
> > the Kickstarter myself with $.
> >
> > That all being said, with all the new ideas and hope I would say we should
> > postpone the "go to github discussion" a little more. I think ppl will
> > support some ASF Wave more than a "random github Wave". And be it only
> > because of the safety for a clean IP.
> Actually, I don't want to run this project through the ASF:
> - I'd prefer to use the benevolent dictator model, at least for the
> initial development period. I don't think the ASF is the right place
> for brand new projects, and this will be entirely new code.
> - I don't want to have to convince a peanut gallery of backers before
> I make decisions about the project. I'm happy for the input, but
> building consensus amongst 1000 people for every decision will kill
> any project.
> - Politically, I will also need to develop out of github for the
> hip-new-project feel. Even google has started putting their projects
> on github.
> I'm don't actually think people will support an ASF wave more - I
> doubt most developers know who the ASF are or what they do, let alone
> regular people. The developers who have heard of the ASF probably
> associate it more with old, mature XML libraries, Java build tools
> with bad websites & enterprise tools like hadoop rather than young
> agile projects. The ASF might make sense after a year or two, but I
> want the project to mature outside of the ASF first.
> The IP will be clean anyway - it'll be entirely new code, and I'll
> probably keep the apache2 license for patent protection (that won't do
> much for a standalone project, but I might be able to flee under the
> apache umbrella if any patent trolls actually come knocking).
> > Please let me know if I can do more to support this effort (speaking with
> > my entrepreneur hat on, not my ASF hat)
> Thanks - I may well take you up on that :)
> I think the biggest way people will be able to help is to help get the
> word out if/when we launch a kickstarter. For this sort of thing we'll
> want a media blitz in the first few days of launching the kickstarter
> to build momentum and get people talking about it.


Just to say that what you are proposing is eminently possible within an
ASF framework. You can create an SVN or git branch, and work there to
your heart's content. The wider community need only kick in at the point
at which you want to release something.

I'm not saying you should do it in the ASF. As has been suggests here,
you'll need to assess a set of intangibles to make your decision - which
location would get you more traction? Which would better facilitate
exploration? Which would appeal most to potential funders?

And then, when you've made your decision, the rest of hue he wave
community needs ego make their own decision as to whether to stay or go.
All I'd like is that a decision is made, one way or the other.


View raw message