auctex-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [AUCTeX-devel] Hello and a question about missing AUCTeX features


From: Tassilo Horn
Subject: Re: [AUCTeX-devel] Hello and a question about missing AUCTeX features
Date: Fri, 17 Apr 2015 23:50:50 +0200
User-agent: Gnus/5.130012 (Ma Gnus v0.12) Emacs/25.0.50 (gnu/linux)

Marcin Borkowski <address@hidden> writes:

Hi Marcin,

> I have read carefully all the replies to my ramblings, for which I
> thank all of you who took the time to answer me.  I don't have the
> time to answer them now, but I promise to come back and do it soon.
> For now, I'd like to look at the FSF copyright agreement.  What do I
> do exactly to receive the form from the FSF?

Follow the instructions in this form:

http://git.savannah.gnu.org/cgit/gnulib.git/tree/doc/Copyright/request-assign.future

> Where can I ask question with regards to my particular situation?

I'd just ask whom to ask when emailing the above form to address@hidden
Probably, that's the right recipient, and if not he'll know who is.

> I guess that if I want to contribute to AUCTeX, I should write here;

Yes.  We have chosen the name auctex-devel very wisely to make people
guess that.  And it seems to work. :-)

> what if I want to contribute to Emacs in general?

If you want to contribute to Emacs (and/or the packages that ship with
it or are in GNU ELPA), then write "Emacs" as program when requesting
the CA forms.  Emacs also covers AUCTeX but the reverse is not true.

> Should I subscribe to emacs-devel and/or write there?  (I'm a tiny bit
> afraid to subscribe to yet another, very active ML...)

Not necessarily.  You can also contribute to Emacs just by looking at
its bug reports and submitting patches on the issues.  Or implement an
entry in etc/TODO or some other new feature and submit the patches as
bug report.  Then you can keep focus on the task you are trying to
accomplish without getting 50 mails a day.

However, especially with new features I'd ask on emacs-devel beforehand
if there's a need for it and how to approach it best.

Bye,
Tassilo




reply via email to

[Prev in Thread] Current Thread [Next in Thread]