unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Amin Bandali <bandali@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: casual contributing with git
Date: Mon, 20 May 2019 00:23:08 -0400	[thread overview]
Message-ID: <87k1eleour.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <6A7A458B-98F7-4852-8BA1-037BF7343633@gmail.com>

Jean-Christophe Helary <brandelune@gmail.com> writes:

> Thank you very much Amin.
>

You’re very welcome, Jean-Christophe.

>

[...]

>
> There is a discovery issue here because when you go to Savannah
> (https://savannah.gnu.org/projects/emacs/) you don't find that kind of
> information and instead find a link to EmacsWiki.
>
> What is the best way to propose changes to the Savannah top page ?
>

I think only the “project admins” can modify the text on a project’s
page on Savannah.  So, I think asking here on emacs-devel would be the
first thing to try.  If you don’t hear from any of the admins listed on
the Emacs project about your question/suggestion here, feel free to try
emailing one of them directly with your suggestion.

>
> Also, the Savannah page links to https://www.gnu.org/software/emacs/
> which is beautifully designed but has no information about
> "contributing" or "developing" even in "Further information".
>
> What is the best way to propose changes to the gnu/emacs page ?
>

Again, I think the first step would be bringing it up here on this list.
Then, you could have a look Emacs’s web page repository [0] to see if
there’s a person that frequently commits to the web pages repo and takes
care of the project’s site.  Currently, for Emacs that person seems to
be Nicolas Petton.

[0]: http://web.cvs.savannah.gnu.org/viewvc/emacs/emacs/

If all of these fail, you could write to webmasters@gnu.org and request
changes.  However, this should be an absolute last resort, since package
maintainers in charge of their own projects’ pages, and the webmasters
generally don’t modify project pages directly, unless a maintainer asks
for it or approves the change.

>
>> In short, usually you would develop on a local branch created from
>> latest master.  When you’re done and/or when you’d like to show your
>> work to others and get feedback, you create a patch from your changes,
>> e.g. using git-format-patch, and use your mail client to send it to the
>> correct mailing list for the project.  In the case of Emacs, that would
>> be one of emacs-devel@gnu.org (this list) or bug-gnu-emacs@gnu.org,
>> depending on the nature of your patch and e.g. if you’re fixing an
>> existing bug.  I skimmed through the first link in your email, and it
>> does mention format-patch at some point.
>
> That's what I found out eventually. But the EmacsWiki pages don't
> really address people who don't have write access so I was a bit
> confused.
>

Right.  Since it’s a wiki, you could edit the page yourself (by clicking
the “Edit this page” link on the bottom of that page) and try to improve
the instructions and make them clearer :)

[...]

> Thank you.
>
>> Hope this helps.
>
> Very much. Thank you again.
>
> Jean-Christophe Helary

Happy to hear that!

Cheers,
amin



  reply	other threads:[~2019-05-20  4:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-19  1:41 casual contributing with git Jean-Christophe Helary
2019-05-19  2:08 ` Amin Bandali
2019-05-19  2:30   ` Jean-Christophe Helary
2019-05-20  4:23     ` Amin Bandali [this message]
2019-05-19  4:48 ` Marcin Borkowski
2019-05-22  5:31   ` Eli Zaretskii
2019-05-24 17:05     ` Marcin Borkowski

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=87k1eleour.fsf@fencepost.gnu.org \
    --to=bandali@gnu.org \
    --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).