Hi Justin,
On Tue, May 7, 2013 at 7:05 PM, wrote:
>
> Hi,
>
> > I recently got a request from a PMC member for formal recognition that
> they are an Apache Committer.
>
> I assume that being listed here is not official enough?
> http://people.apache.org/committer-index.html
>
For me, yes (sayi
Nóirín has an ApacheCon poster if someone can arrange to pick it up
ahead of time!
- Shane
Original Message
From: Nóirín Shirley <[EMAIL PROTECTED]>
I've tried to mail community@ a couple of times, but something's
breaking somewhere, so if you could pass on the message below,
On 7/6/07, J Aaron Farr <[EMAIL PROTECTED]> wrote:
My concern is only when such documents become additional rules or
bylaws and individuals start linking to them in their emails as
justification for why someone has or has not done their duty. Maybe
I'm just being picky and overly cautious.
The
Shane Curcuru <[EMAIL PROTECTED]> writes:
> I keep being surprised at the vehemence of feelings against writing
> down any sort of documentation that's non-technical...
I didn't mean to suggest that I oppose any of the work that Ted, you
or anyone else has done to document the fuzzy side of Apac
[EMAIL PROTECTED] wrote:
From: J Aaron Farr <[EMAIL PROTECTED]>
"Henri Yandell" <[EMAIL PROTECTED]> writes:
With "play nice", it's obvious that we're all interpreting things, but
with the attempted code of conduct there's an impression that it is
definitive and that I'm supposed to understand
William A. Rowe, Jr. wrote:
> 4? w.r.t. style of specific authors, doesn't the project aim to have one
>consistent style? If author tags can encourage folks to adopt their own
>style in lieu of following a project-wide style, isn't this an issue?
Well, there is formal code style which may
Thomas Vandahl wrote:
>
> Why is the use of author tags discouraged? I found these to be valuable
> information when trying to understand a piece of code, simply by
> recognizing the style of a certain author.
1. once committed, it isn't your code, it's the project's code. (Not from
a copyrig
Ted Husted wrote:
> Any comments would be very welcome.
Is that document supposed to be published outside the ASF? If so, I'd
suggest to stress the fact (again) that discussions on a public mailing
list are being archived and available for everyone to see. Every once in
a while we still see thes
Ted Husted wrote:
>
> The example project guidelines and cultural principles were added to
> put the draft community guidelines into context. Though, we might not
> want to post all three items together as a block.
Yea - I'm sort of confused. I'm looking to inject two more concepts,
reinforce th
On 6/30/07, William A. Rowe, Jr. <[EMAIL PROTECTED]> wrote:
This isn't a Code of Conduct, it's a top-level description of our ethos.
Yes, that's how it turned out. I started out to research a code of
conduct, and came back with a set of community guidelines that
describe how we expect people to
Henri - I grok what you are saying. This isn't a Code of Conduct,
it's a top-level description of our ethos.
Two more inline...
Henri Yandell wrote:
> On 6/28/07, Ted Husted <[EMAIL PROTECTED]> wrote:
>> Some of the ASF Members have indicated a wish to draft a code of
>> conduct. A working draft
"Henri Yandell" <[EMAIL PROTECTED]> writes:
> With "play nice", it's obvious that we're all interpreting things, but
> with the attempted code of conduct there's an impression that it is
> definitive and that I'm supposed to understand it all.
This is one of my concerns too.
Our culture is not a
"Ted Husted" <[EMAIL PROTECTED]> writes:
> Can someone suggest a patch?
I've changed to it to the following:
Individuals who provide source code and documentation to the ASF
should submit a Contributor's License Agreement. Source code and
documentation must be under the Apache License and
Can someone suggest a patch?
On 6/29/07, Roy T. Fielding <[EMAIL PROTECTED]> wrote:
On Jun 28, 2007, at 8:32 PM, Craig L Russell wrote:
> I have a question about this part of the guidelines:
>
>> Project source code and documentation must be donated to the ASF
>> under a
>>
>> Contributor's L
On 6/28/07, Ted Husted <[EMAIL PROTECTED]> wrote:
Some of the ASF Members have indicated a wish to draft a code of
conduct. A working draft of a set of "Community Guidelines" is
available on the incubator wiki,
* http://wiki.apache.org/incubator/CodeOfConduct
Any comments would be very welcom
On Jun 28, 2007, at 8:32 PM, Craig L Russell wrote:
I have a question about this part of the guidelines:
Project source code and documentation must be donated to the ASF
under a
Contributor's License Agreement. Donated source code and
documentation must carry the ASF copyright and be pla
William A. Rowe, Jr. wrote:
> Craig L Russell wrote:
>
>>> Donated source code and
>>> documentation must carry the ASF copyright and be placed under the
>>> Apache License. Code and documentation donated to the ASF must be
>>> maintained on ASF hardware. Obtaining a non-exclusive ASF copyright on
Craig L Russell wrote:
> I have a question about this part of the guidelines:
>
>> Project source code and documentation must be donated to the ASF under a
>> Contributor's License Agreement.
This just absolutely clarifies the intent of the author, it's the simplest
method of conveying your-code
I have a question about this part of the guidelines:
Project source code and documentation must be donated to the ASF
under a <> Contributor's License Agreement. Donated source code and
documentation must carry the ASF copyright and be placed under the
Apache License. Code and documentation
On 6/28/07, Ted Husted <[EMAIL PROTECTED]> wrote:
Any comments would be very welcome.
At first glance I say Nice Work Ted (or whomever), long overdue and a
mature and considered distillation of What We Think.
No doubt a further reading will reveal nits :-)
I think that leaving this as an evol
Niclas Hedhman <[EMAIL PROTECTED]> wrote
> Question; Should Open Source be Open Participation?
>
> I am sure that the upper-tier of ASF would shiver at the thought that
> hordes
> of people can gain direct access to the repositories. They/we will
> dust of
> the same arguments of why W
On Sun, 21 Dec 2003 17:09:55 -0800
Stefano Mazzocchi wrote:
> What is this "community thanks/sorry" thing? and what does this have to
> do with the brain stucture you describe?
> Excuse my evident stupidity but I don't get it.
Aha. what I wanted to imply is ... that the "local thinking"
and "gl
Tetsuya Kitahata wrote:
Hello!
Now I am exploring about our brains. :-)
left-side cerebral cortex (A) | right-side cerebral cortex (D)
--|---
left-side limbic system (B) | right-side limbic system (C)
(A) can be expressed as "Calculation B
In message <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
g writes:
>I think it's based on the website not any of our projects. =/ -- justin
Somebody else probably beat me to it since I'm subscribed to the digest
(any chance we can change the content type to multipart/digest for easier
reading?), but t
> This list is never going to alter our lives. It does however have the
> potential to improve our lives through building friendships or a
> feeling of
> belonging to something. It's not going to be an easy ride and accepting
> others points of view as valid and as acceptable/correct as your own i
"Daniel F. Savarese" wrote:
>
> I hate to digress, but the community-digest list is unusable.
working on it..
26 matches
Mail list logo
