forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Crossley (JIRA)" <j...@apache.org>
Subject [jira] Closed: (FOR-603) How to become a Forrest Committer
Date Sun, 07 Aug 2005 02:18:37 GMT
     [ http://issues.apache.org/jira/browse/FOR-603?page=all ]
     
David Crossley closed FOR-603:
------------------------------

    Fix Version: 0.8-dev
     Resolution: Fixed

Wow, Addi, you are a champ. This is one of the most important documents that we could have
on our website. Thanks for doing such a nice job of converting that mail list discussion.
We need more of that type of effort.

I left this issue open for a while because there sure to be more changes. There is another
discussion happening on a related topic. Anyway

I added your patch as-is, except that i converted tabs to two-space. I also folded long lines
into about 80-characters wide. The reason for this is very important. I am now going to proceed
to make some minor changes and you will see via the commit diffs (see www.mail-archive.com
if you are not subscribed). If each paragraph was one enourmous long line, then it would be
difficult to know the changes. (Yes i am adding stuff like that to a new "how to be a developer"
document.)

I have left this issue open for a while because there are sure to be more changes. The discussions
are not finished.

> How to become a Forrest Committer
> ---------------------------------
>
>          Key: FOR-603
>          URL: http://issues.apache.org/jira/browse/FOR-603
>      Project: Forrest
>         Type: Improvement
>   Components: Documentation and website
>     Reporter: Addison Berry
>     Assignee: David Crossley
>     Priority: Minor
>      Fix For: 0.8-dev
>  Attachments: com.aart, committer.xml
>
> Issue brought up on the mail list at http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=112239074108858&amp;w=2
re: creating documentation on becoming a committer in Forrest.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message