public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Luis Machado <luis.machado@arm.com>
To: joel@rtems.org, Mike Frysinger <vapier@gentoo.org>,
	Nick Clifton <nickc@redhat.com>,
	Joel Brobecker <brobecker@adacore.com>,
	Nick Clifton via Binutils <binutils@sourceware.org>
Subject: Re: A GNU Binutils wiki
Date: Wed, 2 Nov 2022 15:28:19 +0000	[thread overview]
Message-ID: <5e1fa34f-781c-21d6-2459-263d818e938f@arm.com> (raw)
In-Reply-To: <CAF9ehCW9jCsU=_OGCGsnUVkwXYvYjoOM0NiHx9++xdXQMVMG_Q@mail.gmail.com>

On 11/2/22 13:41, Joel Sherrill wrote:
> Not to be negative but what type of content is going to go in the Wiki?
> 
> Over at RTEMS, I've become quite disillusioned with Wikis for most
> content. Not being integrated with the source processes, version
> control, and releases, it can become out of sync and out of date.
> It's usually much easier to keep documents in any markup system
> up to date than a wiki.

I feel the same way about wiki's and confluence in general. If there isn't a team on top of it,
pages do go out of sync and go stale over time. Having something in-tree that can get exported to "wiki format"
would be nice.

That would sort out the permissions issue and the vandalization.

> 
> This ignores that Wikis get vandalized and have spam account attempts
> which doesn't seem to happen with source code in git (or cvs).
> 
> What's the process for ensuring any links in the wiki don't break?
> 
> What review processes are going to be used for content?
> 
> What's the driving content need for a wiki?
> 
> Sorry to be negative. I like the "control" in source code control
> and a wiki is lacking there.
> 
> --joel
> 
> On Wed, Nov 2, 2022 at 6:49 AM Mike Frysinger via Binutils <
> binutils@sourceware.org> wrote:
> 
>> On 01 Nov 2022 16:47, Nick Clifton via Binutils wrote:
>>> Hi Mike,
>>>
>>>>> https://sourceware.org/gdb/wiki/EditorGroup
>>>> seems like it's already configured the same
>>>
>>> It is.
>>>
>>>> can someone copy & paste the list from gdb to binutils ?
>>>
>>> Now done.  Mike - could you check that I did it correctly please ?
>>> (This is my first time administering a wiki...)
>>
>> i was able to edit the homepage, so lgtm
>> -mike
>>


  parent reply	other threads:[~2022-11-02 15:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01 13:34 Nick Clifton
2022-11-01 13:44 ` Joel Brobecker
2022-11-01 15:17   ` Mike Frysinger
2022-11-01 16:47     ` Nick Clifton
2022-11-02 10:34       ` Mike Frysinger
2022-11-02 13:41         ` Joel Sherrill
2022-11-02 14:49           ` Nick Clifton
2022-11-02 15:04             ` Joel Brobecker
2022-11-02 15:12             ` Joel Sherrill
2022-11-27 23:44             ` Mark Wielaard
2022-11-30 11:03               ` Nick Clifton
2022-12-31 22:19                 ` Mark Wielaard
2023-01-03 10:08                   ` Nick Clifton
2022-11-02 15:28           ` Luis Machado [this message]
2022-11-09 17:00             ` Mike Frysinger

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=5e1fa34f-781c-21d6-2459-263d818e938f@arm.com \
    --to=luis.machado@arm.com \
    --cc=binutils@sourceware.org \
    --cc=brobecker@adacore.com \
    --cc=joel@rtems.org \
    --cc=nickc@redhat.com \
    --cc=vapier@gentoo.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).