Thanks for Ross' slides, I look forward to reviewing them. J
On Jun 16, 2013 3:30 AM, "Christian Grobmeier" wrote:
> Ross Gardler was last year on the ASF board and is a well-respected
> community member. He knows a lot about driving open source projects,
> because knowing that is also his day jo
Ross Gardler was last year on the ASF board and is a well-respected
community member. He knows a lot about driving open source projects,
because knowing that is also his day job. On Apache Con EU he held a
great presentation on open source risks:
http://de.slideshare.net/rgardler/managing-project-
Totally agree with all, we need to get better and do more to just became
bigger and better.
2013/6/15 John Blossom
> Christian,
>
> Thanks for clarifying this. One of the factors which I hope that the
> developers new to Apache consider is that just because one calls their
> product open source
Christian,
Thanks for clarifying this. One of the factors which I hope that the
developers new to Apache consider is that just because one calls their
product open source does not mean that you have the resources to manage an
open source program in a way that will lead to successful product
implem
On Fri, Jun 14, 2013 at 9:29 PM, Joseph Gentle wrote:
> On Fri, Jun 14, 2013 at 11:48 AM, Christian Grobmeier
> You mentioned that the code has to be first committed to the apache
> repositories for legal reasons. What exactly are the requirements
> there? Is it bad if I have my own local mirror o
The canonical source of the code should be on Apache hardware. Ideally,
all development and collaboration should happen on Apache hardware,
without dependency on third parties. That's the aim, anyway.
What *you* do, is up to you. That is, if you choose to code on github,
and post pull requests to
On Fri, Jun 14, 2013 at 11:48 AM, Christian Grobmeier
wrote:
> On Fri, Jun 14, 2013 at 4:46 PM, John Blossom wrote:
>> Christian,
>>
>> I leave it up to the developers to make those decisions. Whatever tools
>> help the project to move forward best for both the immediate efforts and
>> the long-t
Christian,
You're preaching to the choir. I understand clearly.
John
On Fri, Jun 14, 2013 at 2:48 PM, Christian Grobmeier wrote:
> On Fri, Jun 14, 2013 at 4:46 PM, John Blossom wrote:
> > Christian,
> >
> > I leave it up to the developers to make those decisions. Whatever tools
> > help the pr
On Fri, Jun 14, 2013 at 4:46 PM, John Blossom wrote:
> Christian,
>
> I leave it up to the developers to make those decisions. Whatever tools
> help the project to move forward best for both the immediate efforts and
> the long-term managing of the brand are the right tools. Knowing that
> GitHub
Christian,
I leave it up to the developers to make those decisions. Whatever tools
help the project to move forward best for both the immediate efforts and
the long-term managing of the brand are the right tools. Knowing that
GitHub is a community that attracts many leading edge developers in its
On Fri, Jun 14, 2013 at 3:27 AM, John Blossom wrote:
> Github+Apache+Wave=awesomeness.
>
> John
Please be aware, that for legal reasons all code must live on ASF
platforms first.
We have a mirror on github: https://github.com/apache
But in first place, we need to deal with code ourselves. We can
Github+Apache+Wave=awesomeness.
John
On Thu, Jun 13, 2013 at 11:56 AM, Scott Wilson <
scott.bradley.wil...@gmail.com> wrote:
>
> On 12 Jun 2013, at 22:08, Upayavira wrote:
>
> > All I can say is, "well said". We need to consider Wave as a young
> > project - one that really doesn't yet have anyt
On 12 Jun 2013, at 22:08, Upayavira wrote:
> All I can say is, "well said". We need to consider Wave as a young
> project - one that really doesn't yet have anything set in stone.
>
> I've heard Apache described as a 'do-ocracy', that is, he who does,
> decides.
>
> If there's an approach you t
On Thu, Jun 13, 2013 at 5:15 AM, Zachary “Gamer_Z.” Yaro
wrote:
> Joseph's parenthetical comment basically sums up the reason I have been
> doing things the way I have. I would love to see some larger wave
> organization take over the Wave Extensions Gallery (
> github.com/zmyaro/wave-extensions-
Joseph's parenthetical comment basically sums up the reason I have been
doing things the way I have. I would love to see some larger wave
organization take over the Wave Extensions Gallery (
github.com/zmyaro/wave-extensions-gallery | waveextensions.org), but I do
not want to make it part of Apach
Michael,
Thanks very much for taking the initiative to make your statement. It is
for developers themselves to decide this, but I see some of the best
talents available beginning to coalesce around the Apache framework, now. I
agree that there are many good ideas on the table, and that there will
I love it. Well said, and I totally agree. (Although I still like
having ShareJS on Github.)
-J
On Wed, Jun 12, 2013 at 12:48 PM, Michael MacFadden
wrote:
> Wavers,
>
> It has become clear that there a MANY more people are interested in Wave
> that we had previously thought. There recent explo
it would be nice to get things like rizzoma to be all the way open source
since they seem to have really attempted to make something useable out of
wave.
i think its a great idea to bring the code together and also the coders
actually working on wave in some form or another, its yet to be seen if
All I can say is, "well said". We need to consider Wave as a young
project - one that really doesn't yet have anything set in stone.
I've heard Apache described as a 'do-ocracy', that is, he who does,
decides.
If there's an approach you think would be good, start coding, show us
your work (stick
Let's not debate the details of the recommendation on this thread. I
would just like to hear from people doing wave type things and see if they
would be willing to join up with us. I feel like people aren't developing
here wave because they don't think their voices will be heard. If people
want
Dear Michael,
Can we start by moving on to Maven? It's a somewhat simple step
considering others this list has discussed lately. This would simplify
further separation of modules like OT, communication/protocol, clients, etc.
Also, IMHO multiple folders/projects on a repository will pollute the
I have been working on a geolocation (/augmented reality) specific Wave project:
arwave.org
I am not sure how suitable this is.
Its effectively a client that I (badly) want to be compatible with any
standard wave server.
As there was no standard client/server protocol for the last few
years, I gave
Wavers,
It has become clear that there a MANY more people are interested in Wave
that we had previously thought. There recent explosion of interest is
fantastic. However, what I am seeing is that the wave community is
splintered and fragmented. There are a lot of people who have been doing
deve
23 matches
Mail list logo
