From: Ihor Radchenko <yantar92@posteo.net>
To: Joel Reicher <joel.reicher@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: New Emacs features via Google Summer of Code (or other similar stipend schemes)
Date: Mon, 12 Aug 2024 18:59:04 +0000 [thread overview]
Message-ID: <87ed6tin47.fsf@localhost> (raw)
In-Reply-To: <86msliym9t.fsf@gmail.com>
Joel Reicher <joel.reicher@gmail.com> writes:
>>> Eli, have you considered using GSC to get volunteers for
>>> implementing some moderately difficult Emacs features? Since
>>> GSC provides financial incentive, it may be possible to get
>>> student volunteers.
>>
>> I can only say that it would be harder for a casual contributor
>> to do a GSoC-style job for Emacs than for other projects,
>> because Emacs has a lot of specialized needs and requirements
>> that take time to learn. But maybe this is not an obstacle.
>
> Does GSC have an 'avenue' for working on bugfixes rather than
> features?
AFAIK, no. It is based on well-defined projects.
Some nontrivial bugfixes may be worth a whole project, but I doubt that
having a goal like "close N bugs" will qualify.
> I know that's not where this thread started, and it's
> significantly less glamorous, but the requirements for a bugfix
> tend to be more immediately clear than a 'library'.
If we aim for volunteers to fix bugs, it should probably be some other
funding scheme; not GSoC. I am not aware about anything existing.
The only somewhat relevant thing I recall was crowdfunding scheme like
code bounty (proposed in the past on the list), but that is also more
suitable for new features.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-08-12 18:59 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-10 22:48 as for Calc and the math library Emanuel Berg
2024-08-11 4:58 ` Eli Zaretskii
2024-08-11 16:45 ` Ihor Radchenko
2024-08-11 16:55 ` Christopher Dimech
2024-08-11 17:05 ` Emanuel Berg
2024-08-11 17:59 ` Eli Zaretskii
2024-08-11 18:17 ` Christopher Dimech
2024-08-11 18:32 ` Eli Zaretskii
2024-08-11 19:53 ` Christopher Dimech
2024-08-11 18:27 ` Ihor Radchenko
2024-08-11 18:38 ` Emanuel Berg
2024-08-12 6:28 ` New Emacs features via Google Summer of Code (or other similar stipend schemes) (was: as for Calc and the math library) Ihor Radchenko
2024-08-12 11:09 ` Eli Zaretskii
2024-08-12 12:10 ` New Emacs features via Google Summer of Code (or other similar stipend schemes) Joel Reicher
2024-08-12 18:59 ` Ihor Radchenko [this message]
2024-08-12 22:28 ` Pedro
2024-08-14 10:07 ` Ihor Radchenko
2024-08-15 11:44 ` Ihor Radchenko
2024-08-12 19:17 ` New Emacs features via Google Summer of Code (or other similar stipend schemes) (was: as for Calc and the math library) Ihor Radchenko
2024-08-13 8:12 ` New Emacs features via Google Summer of Code (or other similar stipend schemes) Andrea Corallo
2024-08-18 11:48 ` Ihor Radchenko
2024-08-18 12:35 ` Eli Zaretskii
2024-08-18 12:52 ` Ihor Radchenko
2024-08-18 13:39 ` Eli Zaretskii
2024-08-18 13:56 ` RTF import/export emacs (was: New Emacs features via Google Summer of Code (or other similar stipend schemes)) Ihor Radchenko
2024-08-18 14:14 ` Eli Zaretskii
2024-08-18 14:35 ` Ihor Radchenko
2024-08-18 14:38 ` Eli Zaretskii
2024-08-18 17:37 ` Jim Porter
2024-08-18 18:16 ` Eli Zaretskii
2024-08-18 18:38 ` Jim Porter
2024-08-18 19:05 ` tomas
2024-08-13 11:02 ` New Emacs features via Google Summer of Code (or other similar stipend schemes) (was: as for Calc and the math library) Eli Zaretskii
2024-08-18 11:09 ` Ihor Radchenko
2024-08-18 11:25 ` Eli Zaretskii
2024-08-18 11:33 ` Stefan Kangas
2024-08-18 12:47 ` Ihor Radchenko
2024-08-11 18:52 ` as for Calc and the math library Eli Zaretskii
2024-08-11 19:13 ` Ihor Radchenko
2024-08-12 2:24 ` Eli Zaretskii
2024-08-11 21:50 ` Christopher Dimech
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=87ed6tin47.fsf@localhost \
--to=yantar92@posteo.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joel.reicher@gmail.com \
/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).