You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@clerezza.apache.org by "Henry Story (JIRA)" <ji...@apache.org> on 2011/07/09 18:43:59 UTC

[jira] [Created] (CLEREZZA-601) change hjs in @author to bblfish

change hjs in @author to bblfish
--------------------------------

                 Key: CLEREZZA-601
                 URL: https://issues.apache.org/jira/browse/CLEREZZA-601
             Project: Clerezza
          Issue Type: Improvement
            Reporter: Henry Story


That is the handle these issues refer to

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (CLEREZZA-601) change hjs in @author to bblfish

Posted by "Henry Story (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CLEREZZA-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Henry Story resolved CLEREZZA-601.
----------------------------------

    Resolution: Fixed

> change hjs in @author to bblfish
> --------------------------------
>
>                 Key: CLEREZZA-601
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-601
>             Project: Clerezza
>          Issue Type: Improvement
>            Reporter: Henry Story
>
> That is the handle these issues refer to

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Re: [jira] [Commented] (CLEREZZA-601) change hjs in @author to bblfish

Posted by Reto Bachmann-Gmür <me...@farewellutopia.com>.
On Sun, Jul 10, 2011 at 5:59 PM, florent andré
<fl...@4sengines.com> wrote:
> Well, quoted from links :
>>   - author tags are officially discouraged. these create difficulties in
>>     establishing the proper ownership and the protection of our
>>     committers. there are other social issues dealing with collaborative
>>     development, but the Board is concerned about the legal ramifications
>>     around the use of author tags
>
> So remove them all could be a good thing, but it's a project decision IMO,
> let's see what others think.
>
> Create a scala code for this will be a good exercise :) and an easy way to
> get rid of all this tags.
I agree with the reason not to have author tags. But it might be
useful to have a reference to the project and its website (useful when
code gets copied around into other projects and packages), why not
@author Apache Clerezza Community and Contributors:
http://incubator.apache.org/clerezza

Reto

>
> ++
>
> On 07/10/2011 01:44 PM, Henry Story wrote:
>>
>> On 10 Jul 2011, at 13:18, Henry Story wrote:
>>
>>>
>>> On 10 Jul 2011, at 13:00, Florent ANDRE (JIRA) wrote:
>>>
>>>>
>>>>   [
>>>> https://issues.apache.org/jira/browse/CLEREZZA-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13062713#comment-13062713
>>>> ]
>>>>
>>>> Florent ANDRE commented on CLEREZZA-601:
>>>> ----------------------------------------
>>>>
>>>> @author is not a recommended annotation.
>>>
>>> Ah. Ok. Thanks for pointing that out. I just saw a lot of those @author
>>> around, so I thought at least they should be useful.  I don't suppose it's
>>> necessary to rewind that change though, right?
>>
>> I could also write a script to remove them all if you wish, as an exercise
>> in writing scala code.
>>
>> Henry
>>
>>
>>>
>>> Henry
>>>
>>>
>>>> See this mail send by Bertrand Delacretaz on Stanbol ml :
>>>
>>> thanks.
>>>
>>>>
>>>> On Fri, Jul 8, 2011 at 10:32 AM, Alessandro Adamou<ad...@cs.unibo.it>
>>>>  wrote:
>>>>>>
>>>>>> ...what's the ASF way to deal with @author annotations in
>>>>>> single classes? Do we put our Apache IDs there, or full names, or
>>>>>> nothing at
>>>>>> all?...
>>>>
>>>> The recommendation is to avoid @author tags [1] - among other reasons,
>>>> they might cause people to contact developers directly (which we don't
>>>> want - questions should go to our lists) and they quickly become stale
>>>> when people work collectively on code.
>>>>
>>>> The Whole Truth about who committed what is provided by svn annotate
>>>> anyway.
>>>
>>>>
>>>> -Bertrand
>>>>
>>>> [1]
>>>> http://www.apache.org/foundation/records/minutes/2004/board_minutes_2004_02_18.txt
>>>> and
>>>>
>>>> http://mail-archives.apache.org/mod_mbox/www-community/200402.mbox/%3C403A144A.5040602@apache.org%3E
>>>>
>>>>
>>>>> change hjs in @author to bblfish
>>>>> --------------------------------
>>>>>
>>>>>               Key: CLEREZZA-601
>>>>>               URL: https://issues.apache.org/jira/browse/CLEREZZA-601
>>>>>           Project: Clerezza
>>>>>        Issue Type: Improvement
>>>>>          Reporter: Henry Story
>>>>>
>>>>> That is the handle these issues refer to
>>>>
>>>> --
>>>> This message is automatically generated by JIRA.
>>>> For more information on JIRA, see:
>>>> http://www.atlassian.com/software/jira
>>>>
>>>>
>>>
>>> Social Web Architect
>>> http://bblfish.net/
>>>
>>
>> Social Web Architect
>> http://bblfish.net/
>>
>

Re: [jira] [Commented] (CLEREZZA-601) change hjs in @author to bblfish

Posted by florent andré <fl...@4sengines.com>.
Well, quoted from links :
 >   - author tags are officially discouraged. these create difficulties in
 >     establishing the proper ownership and the protection of our
 >     committers. there are other social issues dealing with collaborative
 >     development, but the Board is concerned about the legal ramifications
 >     around the use of author tags

So remove them all could be a good thing, but it's a project decision 
IMO, let's see what others think.

Create a scala code for this will be a good exercise :) and an easy way 
to get rid of all this tags.

++

On 07/10/2011 01:44 PM, Henry Story wrote:
>
> On 10 Jul 2011, at 13:18, Henry Story wrote:
>
>>
>> On 10 Jul 2011, at 13:00, Florent ANDRE (JIRA) wrote:
>>
>>>
>>>    [ https://issues.apache.org/jira/browse/CLEREZZA-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13062713#comment-13062713 ]
>>>
>>> Florent ANDRE commented on CLEREZZA-601:
>>> ----------------------------------------
>>>
>>> @author is not a recommended annotation.
>>
>> Ah. Ok. Thanks for pointing that out. I just saw a lot of those @author around, so I thought at least they should be useful.  I don't suppose it's necessary to rewind that change though, right?
>
> I could also write a script to remove them all if you wish, as an exercise in writing scala code.
>
> Henry
>
>
>>
>> Henry
>>
>>
>>> See this mail send by Bertrand Delacretaz on Stanbol ml :
>>
>> thanks.
>>
>>>
>>> On Fri, Jul 8, 2011 at 10:32 AM, Alessandro Adamou<ad...@cs.unibo.it>  wrote:
>>>>> ...what's the ASF way to deal with @author annotations in
>>>>> single classes? Do we put our Apache IDs there, or full names, or nothing at
>>>>> all?...
>>> The recommendation is to avoid @author tags [1] - among other reasons,
>>> they might cause people to contact developers directly (which we don't
>>> want - questions should go to our lists) and they quickly become stale
>>> when people work collectively on code.
>>>
>>> The Whole Truth about who committed what is provided by svn annotate anyway.
>>
>>>
>>> -Bertrand
>>>
>>> [1] http://www.apache.org/foundation/records/minutes/2004/board_minutes_2004_02_18.txt
>>> and
>>> http://mail-archives.apache.org/mod_mbox/www-community/200402.mbox/%3C403A144A.5040602@apache.org%3E
>>>
>>>
>>>> change hjs in @author to bblfish
>>>> --------------------------------
>>>>
>>>>                Key: CLEREZZA-601
>>>>                URL: https://issues.apache.org/jira/browse/CLEREZZA-601
>>>>            Project: Clerezza
>>>>         Issue Type: Improvement
>>>>           Reporter: Henry Story
>>>>
>>>> That is the handle these issues refer to
>>>
>>> --
>>> This message is automatically generated by JIRA.
>>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>>
>>>
>>
>> Social Web Architect
>> http://bblfish.net/
>>
>
> Social Web Architect
> http://bblfish.net/
>

Re: [jira] [Commented] (CLEREZZA-601) change hjs in @author to bblfish

Posted by Henry Story <he...@bblfish.net>.
On 10 Jul 2011, at 13:18, Henry Story wrote:

> 
> On 10 Jul 2011, at 13:00, Florent ANDRE (JIRA) wrote:
> 
>> 
>>   [ https://issues.apache.org/jira/browse/CLEREZZA-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13062713#comment-13062713 ] 
>> 
>> Florent ANDRE commented on CLEREZZA-601:
>> ----------------------------------------
>> 
>> @author is not a recommended annotation.
> 
> Ah. Ok. Thanks for pointing that out. I just saw a lot of those @author around, so I thought at least they should be useful.  I don't suppose it's necessary to rewind that change though, right?

I could also write a script to remove them all if you wish, as an exercise in writing scala code.

Henry


> 
> Henry
> 
> 
>> See this mail send by Bertrand Delacretaz on Stanbol ml :
> 
> thanks.
> 
>> 
>> On Fri, Jul 8, 2011 at 10:32 AM, Alessandro Adamou <ad...@cs.unibo.it> wrote:
>>>> ...what's the ASF way to deal with @author annotations in
>>>> single classes? Do we put our Apache IDs there, or full names, or nothing at
>>>> all?...
>> The recommendation is to avoid @author tags [1] - among other reasons,
>> they might cause people to contact developers directly (which we don't
>> want - questions should go to our lists) and they quickly become stale
>> when people work collectively on code.
>> 
>> The Whole Truth about who committed what is provided by svn annotate anyway.
> 
>> 
>> -Bertrand
>> 
>> [1] http://www.apache.org/foundation/records/minutes/2004/board_minutes_2004_02_18.txt
>> and
>> http://mail-archives.apache.org/mod_mbox/www-community/200402.mbox/%3C403A144A.5040602@apache.org%3E
>> 
>> 
>>> change hjs in @author to bblfish
>>> --------------------------------
>>> 
>>>               Key: CLEREZZA-601
>>>               URL: https://issues.apache.org/jira/browse/CLEREZZA-601
>>>           Project: Clerezza
>>>        Issue Type: Improvement
>>>          Reporter: Henry Story
>>> 
>>> That is the handle these issues refer to
>> 
>> --
>> This message is automatically generated by JIRA.
>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>> 
>> 
> 
> Social Web Architect
> http://bblfish.net/
> 

Social Web Architect
http://bblfish.net/


Re: [jira] [Commented] (CLEREZZA-601) change hjs in @author to bblfish

Posted by Henry Story <he...@bblfish.net>.
On 10 Jul 2011, at 13:00, Florent ANDRE (JIRA) wrote:

> 
>    [ https://issues.apache.org/jira/browse/CLEREZZA-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13062713#comment-13062713 ] 
> 
> Florent ANDRE commented on CLEREZZA-601:
> ----------------------------------------
> 
> @author is not a recommended annotation.

Ah. Ok. Thanks for pointing that out. I just saw a lot of those @author around, so I thought at least they should be useful.  I don't suppose it's necessary to rewind that change though, right?

Henry


> See this mail send by Bertrand Delacretaz on Stanbol ml :

thanks.

> 
> On Fri, Jul 8, 2011 at 10:32 AM, Alessandro Adamou <ad...@cs.unibo.it> wrote:
>>> ...what's the ASF way to deal with @author annotations in
>>> single classes? Do we put our Apache IDs there, or full names, or nothing at
>>> all?...
> The recommendation is to avoid @author tags [1] - among other reasons,
> they might cause people to contact developers directly (which we don't
> want - questions should go to our lists) and they quickly become stale
> when people work collectively on code.
> 
> The Whole Truth about who committed what is provided by svn annotate anyway.

> 
> -Bertrand
> 
> [1] http://www.apache.org/foundation/records/minutes/2004/board_minutes_2004_02_18.txt
> and
> http://mail-archives.apache.org/mod_mbox/www-community/200402.mbox/%3C403A144A.5040602@apache.org%3E
> 
> 
>> change hjs in @author to bblfish
>> --------------------------------
>> 
>>                Key: CLEREZZA-601
>>                URL: https://issues.apache.org/jira/browse/CLEREZZA-601
>>            Project: Clerezza
>>         Issue Type: Improvement
>>           Reporter: Henry Story
>> 
>> That is the handle these issues refer to
> 
> --
> This message is automatically generated by JIRA.
> For more information on JIRA, see: http://www.atlassian.com/software/jira
> 
> 

Social Web Architect
http://bblfish.net/


[jira] [Commented] (CLEREZZA-601) change hjs in @author to bblfish

Posted by "Florent ANDRE (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CLEREZZA-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13062713#comment-13062713 ] 

Florent ANDRE commented on CLEREZZA-601:
----------------------------------------

@author is not a recommended annotation.

See this mail send by Bertrand Delacretaz on Stanbol ml :

On Fri, Jul 8, 2011 at 10:32 AM, Alessandro Adamou <ad...@cs.unibo.it> wrote:
> > ...what's the ASF way to deal with @author annotations in
> > single classes? Do we put our Apache IDs there, or full names, or nothing at
> > all?...
The recommendation is to avoid @author tags [1] - among other reasons,
they might cause people to contact developers directly (which we don't
want - questions should go to our lists) and they quickly become stale
when people work collectively on code.

The Whole Truth about who committed what is provided by svn annotate anyway.

-Bertrand

[1] http://www.apache.org/foundation/records/minutes/2004/board_minutes_2004_02_18.txt
and
http://mail-archives.apache.org/mod_mbox/www-community/200402.mbox/%3C403A144A.5040602@apache.org%3E


> change hjs in @author to bblfish
> --------------------------------
>
>                 Key: CLEREZZA-601
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-601
>             Project: Clerezza
>          Issue Type: Improvement
>            Reporter: Henry Story
>
> That is the handle these issues refer to

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Closed] (CLEREZZA-601) change hjs in @author to bblfish

Posted by "Henry Story (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CLEREZZA-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Henry Story closed CLEREZZA-601.
--------------------------------


> change hjs in @author to bblfish
> --------------------------------
>
>                 Key: CLEREZZA-601
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-601
>             Project: Clerezza
>          Issue Type: Improvement
>            Reporter: Henry Story
>
> That is the handle these issues refer to

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira