[EMAIL PROTECTED] wrote:
BTW, I think it is too early for this to go to a vote. Right now, all
of the binding votes would be cast by people who haven't written any
code on the project. I would favor addressing this issue once there are
some active committers. For now laissez-faire should rul
On Oct 3, 2005, at 3:05 PM, [EMAIL PROTECTED] wrote:
Geir Magnusson Jr. wrote:
I was just discussing it to find out what people thought about
the general subject. I didn't call for a vote.
Right and I was stating that I don't think anyone should.
That said, this is an Apache project
Geir Magnusson Jr. wrote:
I was just discussing it to find out what people thought about the
general subject. I didn't call for a vote.
Right and I was stating that I don't think anyone should.
That said, this is an Apache project in the Incubator, and one of the
objectives is to crea
On Oct 3, 2005, at 2:38 PM, [EMAIL PROTECTED] wrote:
Initially the discussion had a component of author tags. It will
be easy to change the policy of author tags to not than vice
versa. Even easier to allow all to do as they feel initially and
set a uniform policy later when the binding
Initially the discussion had a component of author tags. It will be
easy to change the policy of author tags to not than vice versa. Even
easier to allow all to do as they feel initially and set a uniform
policy later when the binding votes can be cast by a basic quorum of
those whom it will
What? I was talking about having a contributor page *and* an AUTHORS
file, independent of the in-file author tag issue, and quite frankly,
I think we should do it now as people are contributing. If anyone
has a real problem with the httpd-style committers page and tracking
AUTHORS in a fi
BTW, I think it is too early for this to go to a vote. Right now, all
of the binding votes would be cast by people who haven't written any
code on the project. I would favor addressing this issue once there are
some active committers. For now laissez-faire should rule.
-Andy
Geir Magnusson
On Oct 3, 2005, at 11:48 AM, Dan Lydick wrote:
I have looked at the HTTPD contributors page and I like it.
I have also looked at the AUTHORS file in Archie Cobbs' code
and I like it as well.
If I had to choose between the two, I'd choose both.
That was my intention. On the website where i
> [Original Message]
> From: Geir Magnusson Jr. <[EMAIL PROTECTED]>
> To:
> Date: 10/1/05 11:10:55 PM
> Subject: [project policy] Author credit and attribution
>
...snip...
>
> I've worked in projects that did it, and some that didn't. When tags
>
Leo Simons wrote:
I'm against author tags. I've had too many discussion about it in
the past that I don't want to repeat though, so I won't bother ;)
Same here.
SVN + a detailed credits.txt file is a much better way to deal with this
issue and it scales for years, not just for the little ego
On Oct 2, 2005, at 6:49 PM, Leo Simons wrote:
On Sun, Oct 02, 2005 at 12:04:55PM +0200, Mark Wielaard wrote:
[SNIP]
Cool!
I also like
http://subversion.tigris.org/hacking.html
which is basically the same kind of guide, only a little different
in some
corners. At apache, lots of proje
On Sun, Oct 02, 2005 at 12:04:55PM +0200, Mark Wielaard wrote:
> If you are looking for some guidelines for working together on code and
> how to keep track of who wrote what when then I would recommend starting
> out with our GNU Classpath Hacker Guide. Specifically chapter 7.
> "Working on the co
I'm against author tags. I've had too many discussion about it in
the past that I don't want to repeat though, so I won't bother ;)
- LSD
Geir Magnusson Jr. wrote:
The Apache Board has recommended that projects not employ author tags
in their source code. The main motivation for this recommendation is
to remove "territorial ownership" from code.
My vote is to not have @author tags. The SVN log should be the definitive
source
Thanks mark for this link. This captures a lot about how I like to
work. Some key things :
"The main thing is to always discuss what you are up to on the
mailinglist. Making sure that everybody knows who is working on what
is the most important thing to make sure we cooperate most
effec
Hi,
If you are looking for some guidelines for working together on code and
how to keep track of who wrote what when then I would recommend starting
out with our GNU Classpath Hacker Guide. Specifically chapter 7.
"Working on the code, Working with others". It explains that the main
rule is to alw
On Oct 2, 2005, at 12:22 AM, [EMAIL PROTECTED] wrote:
I prefer them. I've never had any of the problems that happened in
Avalon or other projects in any project I've been involved in.
Author tags do not signify ownership, they signify "I wuz here".
They are also a principle reason that
I prefer them. I've never had any of the problems that happened in
Avalon or other projects in any project I've been involved in. Author
tags do not signify ownership, they signify "I wuz here". They are also
a principle reason that a lot of newbies get involved in open source
because they c
Might as well do this, now that we are getting in code by the bucketful.
One of the fundamental notions of an Apache project is the notion of
community ownership - that this is _our_ project, collectively.
However, this collective project is composed of significant
individual contributions
19 matches
Mail list logo
