Received.
-Original Message-
From: Avinash Lakshman [mailto:avinash.laksh...@gmail.com]
Sent: Wednesday, 11 March 2009 5:33 AM
To: cassandra-dev@incubator.apache.org
Subject: Test
This is a test.
Hi guys,
I've just created a new Confluence space for Cassandra, Avinash's planning
to use it and most projects find it handy anyway. If other committers want
edit access to it, please send me your Confluence user name. If you don't
have one yet, just register there:
http://cwiki.apache.org/confl
Out of curiosity is there a reason to use a wiki without public edit
access? Apache Hadoop, for example, have had one that is editable by
anyone and they have not had any problems afaik. On the contrary I
believe a lot of useful updates wouldn't happen with a wiki restricted
to committers only.
/J
On Wed, Mar 11, 2009 at 10:59 AM, Johan Oskarsson wrote:
> Out of curiosity is there a reason to use a wiki without public edit
> access? Apache Hadoop, for example, have had one that is editable by
> anyone and they have not had any problems afaik. On the contrary I
> believe a lot of useful upda
Ok, I understand.
On the topic of website I have suggested and created a basic Forrest
generated site here:
https://issues.apache.org/jira/browse/CASSANDRA-2
No response from any of the committers on the jira or on the lists yet
though.
/Johan
Matthieu Riou wrote:
> On Wed, Mar 11, 2009 at 10:5
On Wed, Mar 11, 2009 at 11:08 AM, Johan Oskarsson wrote:
> Ok, I understand.
>
> On the topic of website I have suggested and created a basic Forrest
> generated site here:
> https://issues.apache.org/jira/browse/CASSANDRA-2
>
Nice!
> No response from any of the committers on the jira or on the
I would suggest setting it up so that any changes to jira issues are
also sent to the dev mailinglist.
This way a lot more eyes will see the progress of the development work
that would otherwise be hidden in jira. It would create a positive
feedback loop of more comments on issues etc.
Thoughts o
+1
On Wed, Mar 11, 2009 at 19:19, Johan Oskarsson wrote:
> I would suggest setting it up so that any changes to jira issues are
> also sent to the dev mailinglist.
>
> This way a lot more eyes will see the progress of the development work
> that would otherwise be hidden in jira. It would create
I agree.
On Wed, Mar 11, 2009 at 3:11 PM, Torsten Curdt wrote:
> +1
>
> On Wed, Mar 11, 2009 at 19:19, Johan Oskarsson wrote:
>> I would suggest setting it up so that any changes to jira issues are
>> also sent to the dev mailinglist.
>>
>> This way a lot more eyes will see the progress of the d
Hi guys,
Next week is the board meeting and Cassandra has to report as part of the
incubator. We have to submit this report before Sunday. If somebody could
give a shot at writing it, that would be really swell as I'll have very
limited time until next week.
Thanks,
Matthieu
Is there a report template somewhere?
On Wed, Mar 11, 2009 at 7:22 PM, Matthieu Riou wrote:
> Hi guys,
>
> Next week is the board meeting and Cassandra has to report as part of the
> incubator. We have to submit this report before Sunday. If somebody could
> give a shot at writing it, that would
I will do it. But is there a template some place I can use.
On 3/11/09, Matthieu Riou wrote:
> Hi guys,
>
> Next week is the board meeting and Cassandra has to report as part of the
> incubator. We have to submit this report before Sunday. If somebody could
> give a shot at writing it, that would
There's no template but there are guidelines here:
http://incubator.apache.org/guides/ppmc.html
For examples check the last minutes, under attachment N, for the reports
submitted by Incubator podlings:
http://www.apache.org/foundation/records/minutes/2009/board_minutes_2009_01_21.txt
This shoul
13 matches
Mail list logo
