You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by David Crossley <cr...@apache.org> on 2007/09/11 04:51:20 UTC
Re: [Proposal] decide the future of forrestdoc
Vincent Siveton wrote:
> David Crossley wrote:
> >> Ross Gardler wrote:
> >> > Gav.... wrote:
> >> > >Ok, so we have given plenty more time.
> >> > >
> >> > >Looking again at the link Vincent gave ,
> >> > >
> >> > >http://www.nabble.com/Forrestdoc-and-Maven-JXR-tf3864888s177.html
> >> > >
> >> > >shows that Maven are in agreement and happy to take the code.
> >> > >
> >> > >What happens now ?
> >> >
> >> > Thanks for waking this up.
> >> >
> >> > I guess we officially invite Maven to take the code into their SVN,
> >> > thank them for taking care of it and remove it from our SVN.
> >> >
> >> > David, is there anything special we need to do?
> >>
> >> Sorry, i have been busy, and still.
> >>
> >> I suggest that one of us composes a list of steps,
> >> then contacts Maven.
> >>
> >> Here are some items that i can quickly think of:
> >>
> >> * A Maven committer does a complete 'svn copy' of
> >> everything in forrestdoc. This retains history (and
> >> can do subsequent moves/deletes from there).
> >
> > Absolutely agree: it is a benefit to be part of ASF community ;)
> >
> >> * Then a Forrest committer does an 'svn delete' from
> >> our SVN forrest/whiteboard/forrestdoc
> >>
> >> * Maven might need to explore what happened with the
> >> import of the Vizant code. We haven't really investigated
> >> the provenance of any of forrestdoc. There are some recent
> >> notes in
> >> forrest/whiteboard/forrestdoc/src/java/org/apache/forrest/forrestdoc/ant/doc/package.htm
> >
> > I am aware :)
> > For others, see FOR-1029
> >
> >> * Need to add comments to the various recent email
> >> threads to provide cross-references for the archives
> >> and mention the issue number.
> >
> > I will also add that Forrest Team needs to remove "Tool: Forrestdoc"
> > component in jira.
Thanks.
Another thing is that Forrest need to remove the "forrestdoc"
entry from our Gump descriptor.
> > So, waiting for the green light to go ahead.
Really sorry that the Forrest PMC has taken so long
to finalise this.
Please Apache Maven PMC, tell us when you have done
the 'svn copy' and we will remove it from ours.
Note for the archives: See https://issues.apache.org/jira/browse/FOR-820
-David
Re: [Proposal] decide the future of forrestdoc
Posted by David Crossley <cr...@apache.org>.
Ross Gardler wrote:
> Vincent Siveton wrote:
> > David Crossley wrote:
> >>
> >>Please Apache Maven PMC, tell us when you have done
> >>the 'svn copy' and we will remove it from ours.
> >
> >Done with r574907
> >http://svn.apache.org/viewvc?rev=574907&view=rev
> >
> >You could delete the forrest/trunk/whiteboard/forrestdoc/ project or
> >add a README.TXT for the log with the new location.
>
> I've deleted the directory, the log message points to Maven.
>
> >Be sure that the Maven Team will take care of the code :)
>
> It's nice to see it finally find a loving home. Thanks for your patience.
Thanks to everyone involved in this, remembering way back to
beyond Nicola Ken saving it after Alexandria. His email signature
rings loud. Those who don't know what i am talking about,
grep the net for him and "the code remains". [*]
The handover to Maven has been a beaut collaboration
and left a solid trail.
> >>Note for the archives: See https://issues.apache.org/jira/browse/FOR-820
> >
> >I moved several Forrest issues on our jira (MSANDBOX-33, 34, 35, 36)
> >and deleted for you some Forrest issues as won't fix (FOR-1033, 1030,
> >1028, 1027, 1024, 1023)
> >You need to delete FOR-820.
>
> Thanks for the cleanup, I closed FOR-820 with a won't fix and removed
> the Tools: Forrestdoc component in JIRA. All issues that were in that
> component are now closed and have been moved to the "other" component.
I removed it from our Apache Gump descriptor at r575120.
---oOo---
Wow, i have just gotta share this with you. I tried that search
above for NKB's email sig, with Google. Now if i had used
"just code remains" (which are his actual words) i get many thousands.
Using my guess above "the code remains" i get just one totally relevant
thread:
http://mail-archives.apache.org/mod_mbox/forrest-dev/200210.mbox/%3C3DBE9969.5060300@apache.org%3E
[RT] Move part of Alexandria code to Forrest?
Coincidence?
-David
Re: [Proposal] decide the future of forrestdoc
Posted by Ross Gardler <rg...@apache.org>.
Vincent Siveton wrote:
> Hi David,
>
> 2007/9/10, David Crossley <cr...@apache.org>:
>> Vincent Siveton wrote:
>>> David Crossley wrote:
>>>>> Ross Gardler wrote:
>>>>>> Gav.... wrote:
>>>>>>> Ok, so we have given plenty more time.
>>>>>>>
>>>>>>> Looking again at the link Vincent gave ,
>>>>>>>
>>>>>>> http://www.nabble.com/Forrestdoc-and-Maven-JXR-tf3864888s177.html
>>>>>>>
>>>>>>> shows that Maven are in agreement and happy to take the code.
>>>>>>>
>>>>>>> What happens now ?
>>>>>> Thanks for waking this up.
>>>>>>
>>>>>> I guess we officially invite Maven to take the code into their SVN,
>>>>>> thank them for taking care of it and remove it from our SVN.
>>>>>>
>>>>>> David, is there anything special we need to do?
>>>>> Sorry, i have been busy, and still.
>>>>>
>>>>> I suggest that one of us composes a list of steps,
>>>>> then contacts Maven.
>>>>>
>>>>> Here are some items that i can quickly think of:
>>>>>
>>>>> * A Maven committer does a complete 'svn copy' of
>>>>> everything in forrestdoc. This retains history (and
>>>>> can do subsequent moves/deletes from there).
>>>> Absolutely agree: it is a benefit to be part of ASF community ;)
>>>>
>>>>> * Then a Forrest committer does an 'svn delete' from
>>>>> our SVN forrest/whiteboard/forrestdoc
>>>>>
>>>>> * Maven might need to explore what happened with the
>>>>> import of the Vizant code. We haven't really investigated
>>>>> the provenance of any of forrestdoc. There are some recent
>>>>> notes in
>>>>> forrest/whiteboard/forrestdoc/src/java/org/apache/forrest/forrestdoc/ant/doc/package.htm
>>>> I am aware :)
>>>> For others, see FOR-1029
>>>>
>>>>> * Need to add comments to the various recent email
>>>>> threads to provide cross-references for the archives
>>>>> and mention the issue number.
>>>> I will also add that Forrest Team needs to remove "Tool: Forrestdoc"
>>>> component in jira.
>> Thanks.
>>
>> Another thing is that Forrest need to remove the "forrestdoc"
>> entry from our Gump descriptor.
>>
>>>> So, waiting for the green light to go ahead.
>> Really sorry that the Forrest PMC has taken so long
>> to finalise this.
>>
>> Please Apache Maven PMC, tell us when you have done
>> the 'svn copy' and we will remove it from ours.
>
> Done with r574907
> http://svn.apache.org/viewvc?rev=574907&view=rev
>
> You could delete the forrest/trunk/whiteboard/forrestdoc/ project or
> add a README.TXT for the log with the new location.
I've deleted the directory, the log message points to Maven.
>
> Be sure that the Maven Team will take care of the code :)
It's nice to see it finally find a loving home. Thanks for your patience.
>> Note for the archives: See https://issues.apache.org/jira/browse/FOR-820
>
> I moved several Forrest issues on our jira (MSANDBOX-33, 34, 35, 36)
> and deleted for you some Forrest issues as won't fix (FOR-1033, 1030,
> 1028, 1027, 1024, 1023)
> You need to delete FOR-820.
Thanks for the cleanup, I closed FOR-820 with a won't fix and removed
the Tools: Forrestdoc component in JIRA. All issues that were in that
component are now closed and have been moved to the "other" component.
Ross
Re: [Proposal] decide the future of forrestdoc
Posted by Vincent Siveton <vi...@gmail.com>.
Hi David,
2007/9/10, David Crossley <cr...@apache.org>:
> Vincent Siveton wrote:
> > David Crossley wrote:
> > >> Ross Gardler wrote:
> > >> > Gav.... wrote:
> > >> > >Ok, so we have given plenty more time.
> > >> > >
> > >> > >Looking again at the link Vincent gave ,
> > >> > >
> > >> > >http://www.nabble.com/Forrestdoc-and-Maven-JXR-tf3864888s177.html
> > >> > >
> > >> > >shows that Maven are in agreement and happy to take the code.
> > >> > >
> > >> > >What happens now ?
> > >> >
> > >> > Thanks for waking this up.
> > >> >
> > >> > I guess we officially invite Maven to take the code into their SVN,
> > >> > thank them for taking care of it and remove it from our SVN.
> > >> >
> > >> > David, is there anything special we need to do?
> > >>
> > >> Sorry, i have been busy, and still.
> > >>
> > >> I suggest that one of us composes a list of steps,
> > >> then contacts Maven.
> > >>
> > >> Here are some items that i can quickly think of:
> > >>
> > >> * A Maven committer does a complete 'svn copy' of
> > >> everything in forrestdoc. This retains history (and
> > >> can do subsequent moves/deletes from there).
> > >
> > > Absolutely agree: it is a benefit to be part of ASF community ;)
> > >
> > >> * Then a Forrest committer does an 'svn delete' from
> > >> our SVN forrest/whiteboard/forrestdoc
> > >>
> > >> * Maven might need to explore what happened with the
> > >> import of the Vizant code. We haven't really investigated
> > >> the provenance of any of forrestdoc. There are some recent
> > >> notes in
> > >> forrest/whiteboard/forrestdoc/src/java/org/apache/forrest/forrestdoc/ant/doc/package.htm
> > >
> > > I am aware :)
> > > For others, see FOR-1029
> > >
> > >> * Need to add comments to the various recent email
> > >> threads to provide cross-references for the archives
> > >> and mention the issue number.
> > >
> > > I will also add that Forrest Team needs to remove "Tool: Forrestdoc"
> > > component in jira.
>
> Thanks.
>
> Another thing is that Forrest need to remove the "forrestdoc"
> entry from our Gump descriptor.
>
> > > So, waiting for the green light to go ahead.
>
> Really sorry that the Forrest PMC has taken so long
> to finalise this.
>
> Please Apache Maven PMC, tell us when you have done
> the 'svn copy' and we will remove it from ours.
Done with r574907
http://svn.apache.org/viewvc?rev=574907&view=rev
You could delete the forrest/trunk/whiteboard/forrestdoc/ project or
add a README.TXT for the log with the new location.
Be sure that the Maven Team will take care of the code :)
> Note for the archives: See https://issues.apache.org/jira/browse/FOR-820
I moved several Forrest issues on our jira (MSANDBOX-33, 34, 35, 36)
and deleted for you some Forrest issues as won't fix (FOR-1033, 1030,
1028, 1027, 1024, 1023)
You need to delete FOR-820.
Cheers,
Vincent
>
> -David
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [Proposal] decide the future of forrestdoc
Posted by Vincent Siveton <vi...@gmail.com>.
Hi David,
2007/9/10, David Crossley <cr...@apache.org>:
> Vincent Siveton wrote:
> > David Crossley wrote:
> > >> Ross Gardler wrote:
> > >> > Gav.... wrote:
> > >> > >Ok, so we have given plenty more time.
> > >> > >
> > >> > >Looking again at the link Vincent gave ,
> > >> > >
> > >> > >http://www.nabble.com/Forrestdoc-and-Maven-JXR-tf3864888s177.html
> > >> > >
> > >> > >shows that Maven are in agreement and happy to take the code.
> > >> > >
> > >> > >What happens now ?
> > >> >
> > >> > Thanks for waking this up.
> > >> >
> > >> > I guess we officially invite Maven to take the code into their SVN,
> > >> > thank them for taking care of it and remove it from our SVN.
> > >> >
> > >> > David, is there anything special we need to do?
> > >>
> > >> Sorry, i have been busy, and still.
> > >>
> > >> I suggest that one of us composes a list of steps,
> > >> then contacts Maven.
> > >>
> > >> Here are some items that i can quickly think of:
> > >>
> > >> * A Maven committer does a complete 'svn copy' of
> > >> everything in forrestdoc. This retains history (and
> > >> can do subsequent moves/deletes from there).
> > >
> > > Absolutely agree: it is a benefit to be part of ASF community ;)
> > >
> > >> * Then a Forrest committer does an 'svn delete' from
> > >> our SVN forrest/whiteboard/forrestdoc
> > >>
> > >> * Maven might need to explore what happened with the
> > >> import of the Vizant code. We haven't really investigated
> > >> the provenance of any of forrestdoc. There are some recent
> > >> notes in
> > >> forrest/whiteboard/forrestdoc/src/java/org/apache/forrest/forrestdoc/ant/doc/package.htm
> > >
> > > I am aware :)
> > > For others, see FOR-1029
> > >
> > >> * Need to add comments to the various recent email
> > >> threads to provide cross-references for the archives
> > >> and mention the issue number.
> > >
> > > I will also add that Forrest Team needs to remove "Tool: Forrestdoc"
> > > component in jira.
>
> Thanks.
>
> Another thing is that Forrest need to remove the "forrestdoc"
> entry from our Gump descriptor.
>
> > > So, waiting for the green light to go ahead.
>
> Really sorry that the Forrest PMC has taken so long
> to finalise this.
>
> Please Apache Maven PMC, tell us when you have done
> the 'svn copy' and we will remove it from ours.
Done with r574907
http://svn.apache.org/viewvc?rev=574907&view=rev
You could delete the forrest/trunk/whiteboard/forrestdoc/ project or
add a README.TXT for the log with the new location.
Be sure that the Maven Team will take care of the code :)
> Note for the archives: See https://issues.apache.org/jira/browse/FOR-820
I moved several Forrest issues on our jira (MSANDBOX-33, 34, 35, 36)
and deleted for you some Forrest issues as won't fix (FOR-1033, 1030,
1028, 1027, 1024, 1023)
You need to delete FOR-820.
Cheers,
Vincent
>
> -David
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>