public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC/RFA] gdb/CONTRIBUTE update (most of the info is now on our wiki)
Date: Tue, 04 Oct 2016 17:18:00 -0000	[thread overview]
Message-ID: <a20e8bf9-4778-7c5c-98dd-8d8a56acf88c@redhat.com> (raw)
In-Reply-To: <20160121101427.GC5146@adacore.com>

Hi Joel,

From the better-late-than-never department...

On 01/21/2016 10:14 AM, Joel Brobecker wrote:
> Hi Pedro,
> 
>> Thanks a bunch for doing this.  It's been on my TODO for a long while
>> after this:
>>
>>  https://sourceware.org/ml/gdb-patches/2014-10/msg00636.html
>>
>> IMO, we'd keep this file even more minimal, and instead of having
>> it point to the wiki page here, it'd point to:
>>
>>   https://sourceware.org/gdb/contribute/
>>
>> (which is also linked from the main page)
>>
>> and that page would be the one that would mention the wiki.
>>
>> My main reason would that the the "contribute" page in the web site
>> would be the canonical entry point, while the wiki page is a fast
>> moving target.  E.g., it's growing past a checklist, so I wouldn't
>> be surprised if we end up splitting it into separate pages at some
>> point (and end up changing the URL).
>>
>> But TBC, I'm definitely already happy with what you propose.
> 
> Sorry for the late reply - busy week! I just wanted to say that
> I tend to agree with your comments. I think we'll just need to
> iron the details out.
> 
> One thing we might want to discuss: Editing the GDB web pages
> (html repository) is not hard per se, but is inconvenient:
> there are 2 CVS repositories to maintain in sync, with distinct
> ACLs for pushing. I personally have the procedure down pat, but
> I wouldn't recommend anyone else but one or two backups spend
> anytime getting setup. So, instead, I am wondering: Why not
> move the https://sourceware.org/gdb/contribute/ page to the Wiki?

If only we'd move the website to git... :-)

> 
> This page could still be the entry point, and be the more stable
> document; and then we could link to the checklist from there
> as you are suggesting.

*nod*

> 
> While discussion, I was trying to find ways to make the checklist
> a little more like a checklist (something you go through quickly
> and repetitively to make sure you haven't forgotten something
> each time). Because of all the comments and annotations, it's
> hard to go through it quickly, or not skip accidently a step.
> I agree everyone is in great shape if only one or two are skipped
> (;-)), but maybe there is a technical way we can only display
> the subject of each item on the checklist, and then have a toggle
> we can use to display/hide the explanations/rationale/examples...
> Not something to discuss right away necessarily, but perhaps
> something interesting.
> 
> I'll get back to this when I can; maybe not this weekend, but
> the next one.
> 

At this point, I'm convinced that the file in the sources serves
no real use, and I'd just remove it entirely.  But, in any case,
I think the next best step would be to tweak
<https://sourceware.org/gdb/contribute/> to point at some gdb/wiki/contribute
page, as discussed above, instead of pointing at gdb/CONTRIBUTE in the sources.
That seems to be the main blocker.

Thanks,
Pedro Alves

      reply	other threads:[~2016-10-04 17:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-17  8:25 Joel Brobecker
2016-01-18 12:00 ` Pedro Alves
2016-01-21 10:14   ` Joel Brobecker
2016-10-04 17:18     ` Pedro Alves [this message]

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=a20e8bf9-4778-7c5c-98dd-8d8a56acf88c@redhat.com \
    --to=palves@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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).