public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Clara Kowalsky' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com, ibr@radix50.net
Subject: Re: [PATCH] docs: link issue tracker
Date: Wed, 12 Nov 2025 11:43:17 +0100	[thread overview]
Message-ID: <eee3bb73-1c10-4df4-b1c6-4a0df0af2869@siemens.com> (raw)
In-Reply-To: <aRRdGKd8xTkMJJUX@abai.de>



On 11/12/25 11:10, Baurzhan Ismagulov wrote:
> On 2025-11-12 09:15, 'Clara Kowalsky' via isar-users wrote:
>> To make the issue tracker a bit more known, link it in the README.
> 
> Well, we've been actually directing all discussions towards isar-users as the
> single channel of communication and archive. We had checked disabling issues
> and PRs but seems it is not possible on github.
> 
> Issues do have the advantage of focus on the single topic, which mailing lists
> address by archive threading. Are there other reasons why we should want to
> encourage issues?
> 
> With kind regards,
> Baurzhan
> 
I also prefer the mailing list respectively a single communication 
medium. It is just not clear that the issues should not be used.
Are you sure they can't be disabled (Settings - Features - Issues: 
uncheck)? I just tested it on another project.
It looks like pull requests can indeed not be disabled [1].

[1] https://github.com/dear-github/dear-github/issues/84

Best regards,
Clara

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/eee3bb73-1c10-4df4-b1c6-4a0df0af2869%40siemens.com.

      reply	other threads:[~2025-11-12 10:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-12  8:15 'Clara Kowalsky' via isar-users
2025-11-12 10:10 ` Baurzhan Ismagulov
2025-11-12 10:43   ` 'Clara Kowalsky' via isar-users [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=eee3bb73-1c10-4df4-b1c6-4a0df0af2869@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=clara.kowalsky@siemens.com \
    --cc=ibr@radix50.net \
    /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