* Help maintain bzr on Savannah?
@ 2010-01-28 15:30 Richard Stallman
2010-01-28 17:03 ` Karl Fogel
0 siblings, 1 reply; 4+ messages in thread
From: Richard Stallman @ 2010-01-28 15:30 UTC (permalink / raw)
To: emacs-devel
Is there someone here who would like to help maintain bzr on savannah?
It requires knowledge of system administration for a Debian-like
variant of GNU/Linux, and security, as well as knowledge of (or
willingness to learn) Bzr.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Help maintain bzr on Savannah?
2010-01-28 15:30 Help maintain bzr on Savannah? Richard Stallman
@ 2010-01-28 17:03 ` Karl Fogel
2010-01-29 20:50 ` Richard Stallman
0 siblings, 1 reply; 4+ messages in thread
From: Karl Fogel @ 2010-01-28 17:03 UTC (permalink / raw)
To: rms; +Cc: emacs-devel
Richard Stallman <rms@gnu.org> writes:
>Is there someone here who would like to help maintain bzr on savannah?
>It requires knowledge of system administration for a Debian-like
>variant of GNU/Linux, and security, as well as knowledge of (or
>willingness to learn) Bzr.
How much overhead is involved in this? Are there any documents that
describe the process?
I have the requisite knowledge, and am interested. However, when I last
looked at volunteering to do this on Savannah, I recall being put off by
various bits of overhead that made it expensive to volunteer. I wish I
could be more specific, and it's quite possible that I was simply
mistaken -- if you can point to some documentation on what is involved,
that would help.
-Karl
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Help maintain bzr on Savannah?
2010-01-28 17:03 ` Karl Fogel
@ 2010-01-29 20:50 ` Richard Stallman
2010-01-31 2:44 ` Karl Fogel
0 siblings, 1 reply; 4+ messages in thread
From: Richard Stallman @ 2010-01-29 20:50 UTC (permalink / raw)
To: Karl Fogel; +Cc: emacs-devel
How much overhead is involved in this? Are there any documents that
describe the process?
I have the requisite knowledge, and am interested. However, when I last
looked at volunteering to do this on Savannah, I recall being put off by
various bits of overhead that made it expensive to volunteer.
I don't know the answer; I am not sure I even understand the question.
What does "overhead" mean in this context?
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Help maintain bzr on Savannah?
2010-01-29 20:50 ` Richard Stallman
@ 2010-01-31 2:44 ` Karl Fogel
0 siblings, 0 replies; 4+ messages in thread
From: Karl Fogel @ 2010-01-31 2:44 UTC (permalink / raw)
To: rms; +Cc: emacs-devel
Richard Stallman <rms@gnu.org> writes:
> How much overhead is involved in this? Are there any documents that
> describe the process?
>
> I have the requisite knowledge, and am interested. However, when I last
> looked at volunteering to do this on Savannah, I recall being put off by
> various bits of overhead that made it expensive to volunteer.
>
>I don't know the answer; I am not sure I even understand the question.
>What does "overhead" mean in this context?
It's okay to ignore that part of the question. I just want to see the
documents that tell the process of becoming a Savannah admin. I read
them once, but the pages were rather hard to find and I haven't been
able to find them again, even though I looked quite a bit. Before
volunteering for this, I want to read them more carefully again.
("Overhead" means things like new mailing lists to join, etc.)
-Karl
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2010-01-31 2:44 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-01-28 15:30 Help maintain bzr on Savannah? Richard Stallman
2010-01-28 17:03 ` Karl Fogel
2010-01-29 20:50 ` Richard Stallman
2010-01-31 2:44 ` Karl Fogel
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.