On 2 Dec 2013, at 18:35, Joseph Gentle wrote:
On Sun, Dec 1, 2013 at 10:35 AM, Christian Grobmeier
<grobme...@gmail.com> wrote:
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.
Both can work just not for all people.
- 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.
This not the case here. How many active committers does Wave have?
You just need to make sure to have consensus with them which is not 1000
people.
- 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.
GitHub is just a tool. Not a community or a foundation. Google
has the benefits of a foundation because it's Google. You need to take
care on a few things on your own. Which of course can work out fine.
Just saying.
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.
Or like Apache Cordova which is Phonegap and got a great website:
http://cordova.apache.org
...and is super agile.
Besides, having an enterprise ready Wave is not a bad thing.
A side note on my comments above: I don't want to convince anybody to
stay
or leave. It's up to you folks. However I put some more salt in the
discussion
to make a good decision.
There are a lot of pros/cons for foundations/scm hosting.
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).
I am not speaking of patents.
Please make sure that any contributions you might get are covered by an
ICLA.
This is important to flee under the apache umbrella if necessary. You
can use the ICLAs used at the ASF and so on
for your own project.
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.
Sure.
However you folks better make sure you are all in one boat. If you start
with Kickstarter
you should have decided who is participating and where.
Cheers,
Christian
-J
Cheers
Christian
-J
---
http://www.grobmeier.de
@grobmeier
GPG: 0xA5CC90DB
---
http://www.grobmeier.de
@grobmeier
GPG: 0xA5CC90DB
