search

dcorking / wave-robot-java-client

Automatically exported from code.google.com/p/wave-robot-java-client
0 stars 0 forks source link

Test suite for API and participation rules should be released as APL 2.0 as well #7

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
If Google Wave team really wants community participation then rules of such
participation and test suite for API should be published.

I guess community also expect that design decisions, API changes and other
related things should happen in normal OSS manner and not privately inside
Google. GWT community is great example how it work on practice.

Original issue reported on code.google.com by alex.tka...@gmail.com on 20 Jul 2009 at 9:40

GoogleCodeExporter commented 9 years ago 
I think it is ok to think in terms of an eventual establishment of rules of
engagement and open source participation, but it seems that it's way too early 
to
make such a demand on Google; Waves are far too complex, far too non-trivial in
internals, and it seems clear, at least to me, that the product is not yet 
ready to
be unleashed on the grand design committee that is the public. I have no reason 
to
believe the product will not eventually (if not sooner) be released to the full
community. I see this as a "non issue". It is written as if the writer Alex 
Tkachman
assumes Google does not really want community participation. I certainly do not 
see
it that way.

Original comment by jackpark on 20 Jul 2009 at 2:34

GoogleCodeExporter commented 9 years ago 
Jack, I do assume that Google wants community participation (maybe problem is 
that
English is not my native language) I just think that as soon as part of the 
code is
open-sourced you have to define rules and open development process.

Original comment by alex.tka...@gmail.com on 20 Jul 2009 at 10:29

GoogleCodeExporter commented 9 years ago 
Hi Alex -

You can check out the source and submit patches to us using this issue tracker. 
We 
would review any patches that came in.

Do you want a wiki with more details on how to contribute, a forum for Java 
Client 
Library developers, or just more explicit encouragement of patch submission?

Original comment by pamela.fox on 21 Jul 2009 at 12:35

GoogleCodeExporter commented 9 years ago 
Hi Pamela! 
I am OK to submit patches and did some already. 
But don't you need contributor agreement from third parties? :) I am almost 
sure you do.

A forum for Java Client Library developers would be lovely as soon as your team 
will
participate in the forum as active as all the rest. I want to refer here again 
for
experience of GWT team, who do amazing job in that respect. My favorite part is 
that
all code reviews go publicly, which helps a lot to improve quality.

Another important topic is that issue tracker is not most convenient place for
discussions.

One more thing where I would love to see more transparency is progress of 
submitted
issues. For example, I see that Java code comes from Seth and Marcel but don't 
see
any issue assigned to them.

Pleease understand me correctly. I am not trying to say that Wave team does bad 
job.
In fact, you do very good one. I am just trying to translate my experience in 
OSS (I
was involved in GWT, Groovy and Grails mostly) to expectations of what would be 
good
for community to help developing high-quality API for Wave.

Original comment by alex.tka...@gmail.com on 21 Jul 2009 at 9:15