public inbox for gnutools-advocacy@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Carlos O'Donell" <carlos@systemhalted.org>
To: iains.gcc@gmail.com
Cc: gnutools-advocacy@gcc.gnu.org
Subject: Re: GNU toolchain web page
Date: Mon, 01 Jan 2018 00:00:00 -0000	[thread overview]
Message-ID: <CAE2sS1hFuv1dhxuaS8AhoX97bBYA_XVHMM2fSEmg=crqvE3A6A@mail.gmail.com> (raw)
In-Reply-To: <29850D75-B7F9-41FA-8E38-B8B4915D36BC@gmail.com>

On Mon, Oct 1, 2018 at 8:21 AM Iain Sandoe <iains.gcc@gmail.com> wrote:
> Hi Carlos,
> I am interested in contributing to any content / design discussion for the ‘overall toolchain’ web page.
> Do you intend to develop it (pre-initial release) on some collaborative platform?
> .. also test post to the new list.

I have two enablement goals.

(1) A website to unify major toolchain projects and promote an "entire
toolchain" view with "Latest release" type of information.

(2) A website that provides new contributors with a checklist of
things they need to do and walks them through each step.

I'd like to be able to do some deep integration with (2), like
registering for bugzilla accounts (with human vetting, or state of the
art captcha).

With those two goals in mind I need to find a host for this site,
maybe sourceware.org.

Then I need to see what kind of server side tech we can use for this,
like will we be able to use django on sourceware for this new website?

So if I had to take a first step it would be to create a Google doc
with a project plan for (1) and the pages we need to create for that.

Cheers,
Carlos.

  reply	other threads:[~2018-10-02  1:12 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-01  0:00 Iain Sandoe
2018-01-01  0:00 ` Carlos O'Donell [this message]
2018-01-01  0:00   ` David Edelsohn
2018-01-01  0:00     ` David Edelsohn
2018-01-01  0:00       ` Carlos O'Donell
2018-01-01  0:00         ` David Edelsohn
2018-01-01  0:00           ` Carlos O'Donell
2018-01-01  0:00             ` David Edelsohn
2018-01-01  0:00             ` Richard Biener
2018-01-01  0:00               ` David Edelsohn
2018-01-01  0:00   ` David Edelsohn
2018-01-01  0:00     ` Joseph Myers
2018-01-01  0:00   ` Alexandre Oliva
2018-01-01  0:00     ` Carlos O'Donell
2018-01-01  0:00       ` Richard Stallman
2018-01-01  0:00         ` David Edelsohn
2018-01-01  0:00           ` Alexandre Oliva
2018-01-01  0:00             ` Richard Biener
2018-01-01  0:00               ` Alexandre Oliva
2018-01-01  0:00                 ` Richard Biener
2018-01-01  0:00                   ` Alexandre Oliva
2018-01-01  0:00                     ` David Edelsohn
2018-01-01  0:00                       ` Alexandre Oliva
2018-01-01  0:00                         ` David Edelsohn
2018-01-01  0:00                           ` Alexandre Oliva
2018-01-01  0:00                   ` Alexandre Oliva
2018-01-01  0:00                   ` Alexandre Oliva
2018-01-01  0:00               ` Richard Stallman
2018-01-01  0:00           ` Richard Stallman
2018-01-01  0:00       ` Alexandre Oliva

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAE2sS1hFuv1dhxuaS8AhoX97bBYA_XVHMM2fSEmg=crqvE3A6A@mail.gmail.com' \
    --to=carlos@systemhalted.org \
    --cc=gnutools-advocacy@gcc.gnu.org \
    --cc=iains.gcc@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).