incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave Brondsema <dbronds...@geek.net>
Subject Re: svn commit: r1354707 - /incubator/public/trunk/content/projects/allura.xml
Date Tue, 03 Jul 2012 16:04:01 GMT
On Mon, Jul 2, 2012 at 10:21 AM, Sam Ruby <rubys@intertwingly.net> wrote:

> On Thu, Jun 28, 2012 at 8:51 PM, Greg Stein <gstein@gmail.com> wrote:
> > On Jun 28, 2012 3:26 AM, "David Crossley" <crossley@apache.org> wrote:
> >>
> >> David Crossley wrote:
> >> > Sorry Rich, that extra information in the "mailing lists" section
> >> > cannot be parsed by Clutch. Perhaps move it to the "News" section.
> >>
> >> Also, the "tracker" is the eventual ASF tracker that is intended.
> >
> > There is no requirement to run the issue tracker on ASF hardware, so the
> > link to SF.net is just fine.
>
> The requirement derives from the Apache License which states:
>
> > issue tracking systems that are managed by, or on behalf of,
> > the Licensor for the purpose of discussing and improving the
> > Work
>
> My hope is that we find a way to host the Allura issue tracker here,
> but failing that we will need to ensure that it is unambiguously clear
> to anybody that finds their way to that page that the issue tracker is
> managed on behalf of the Apache Allura (incubating) project.
>
> I don't believe that the following page currently does that:
>
> http://sourceforge.net/p/allura/tickets/


I've added text on that page to clearly state that now.  We (SourceForge)
also have tickets in there regarding non-Allura work that our team works
on.  When we move the tickets to an apache-hosted allura instance, we'll
need to separate them.


-- 
Dave Brondsema
Principal Software Engineer - sf.net
Geeknet

-- 
====
This e- mail message is intended only for the named recipient(s) above. It 
may contain confidential and privileged information. If you are not the 
intended recipient you are hereby notified that any dissemination, 
distribution or copying of this e-mail and any attachment(s) is strictly 
prohibited. If you have received this e-mail in error, please immediately 
notify the sender by replying to this e-mail and delete the message and any 
attachment(s) from your system. Thank you.


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message