This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Describing commercial support on our website
- From: "Richard Guenther" <richard dot guenther at gmail dot com>
- To: "Joe Buck" <Joe dot Buck at synopsys dot com>
- Cc: "Manuel López-Ibáñez" <lopezibanez at gmail dot com>, "Ben Elliston" <bje at au1 dot ibm dot com>, "Ankur Gupta" <ankur17 at gmail dot com>, gcc at gcc dot gnu dot org, "Ankur Gupta" <ankurgupta at acmet dot com>
- Date: Thu, 29 Nov 2007 23:33:33 +0100
- Subject: Re: Describing commercial support on our website
- References: <6c33472e0711281608t37d0f9b6m71d5820d1765c766@mail.gmail.com> <20071129221317.GB20723@synopsys.com>
On Nov 29, 2007 11:13 PM, Joe Buck <Joe.Buck@synopsys.com> wrote:
>
> On Thu, Nov 29, 2007 at 01:08:26AM +0100, Manuel López-Ibáñez wrote:
> > On 29/11/2007, Ben Elliston <bje@au1.ibm.com> wrote:
> > > > Actually, I wanted to provide some examples, but I couldn't easily
> > > > find a list of companies providing commercial support for GCC.
> > > > Shouldn't we have such a list in the website in a prominent place?
> > >
> > > This is explained in the gcc/SERVICE file.
> > >
> >
> > Perhaps we should have that link in our website + a list specific to GCC.
> >
> > By the way, the link is broken. The correct link seems to be
> > http://www.fsf.org/resources/service
> >
> > I can send a patch, but I think it would be better if we linked to our
> > own http://gcc.gnu.org/support page and from there to wherever the FSF
> > wants us to link. That way we could include and update ourselves the
> > information specific to gcc.
>
> Unfortunately, that's an area that the FSF wants tight control over;
> they would be especially cheesed off if we linked to a consultant's page
> and the consultant also advertised his/her ability to support proprietary
> compiler development.
>
> But the page on fsf.org is outdated and mostly-useless; people are
> unlikely to find it. It should be possible to do something better and
> still meet the FSF's requirements (which mainly are that FSF sites don't
> promote proprietary software or link to pages that do).
So maybe we should instead drop the SERVICE file completely.
Richard.