unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "chen.mingzheng" <chen.mingzheng@outlook.com>
Cc: emacs-devel@gnu.org
Subject: Re: Where is sr-speedbar.el upstream repo?
Date: Tue, 05 Jul 2022 11:55:14 -0400	[thread overview]
Message-ID: <jwv1quzk15q.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <TYCPR01MB5743082824CF07D0F62F5A2F81819@TYCPR01MB5743.jpnprd01.prod.outlook.com> (chen mingzheng's message of "Tue, 5 Jul 2022 23:49:40 +0800")

> I'm curious why is that happens. What are the responsibilities for
> a maintainer

Nobody can sue the maintainer for not doing its job, so in terms of real
responsibilities there aren't any, but in terms of what's expected, it's
mostly to be responsive and to care about the package.

> and what gonna happens if someone want to be a maintainer for it.

The world will rejoice and there will be much celebration.

> managing PRs, fixing bug for some PR and so on?

That's right.


        Stefan




  reply	other threads:[~2022-07-05 15:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-04 23:21 Where is sr-speedbar.el upstream repo? chen.mingzheng
2022-07-05  0:38 ` Stefan Kangas
2022-07-05  0:51   ` chen.mingzheng
2022-07-05  1:26     ` Stefan Kangas
2022-07-05  1:59       ` chen.mingzheng
2022-07-05  6:56       ` Sebastian Rose
2022-07-05  9:34         ` chen.mingzheng
2022-07-05 12:03           ` Stefan Monnier
     [not found]             ` <TYCPR01MB5743F6F10A0573375954655681819@TYCPR01MB5743.jpnprd01.prod.outlook.com>
     [not found]               ` <jwv7d4rk5by.fsf-monnier+emacs@gnu.org>
2022-07-05 15:49                 ` chen.mingzheng
2022-07-05 15:55                   ` Stefan Monnier [this message]
2022-07-05 16:56                     ` Lynn Winebarger
2022-07-05 18:39                       ` Akib Azmain Turja
2022-07-05 18:40                       ` Stefan Monnier

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=jwv1quzk15q.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=chen.mingzheng@outlook.com \
    --cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).