From: arthur miller <arthur.miller@live.com>
To: "yantar92@posteo.net" <yantar92@posteo.net>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: New Emacs features via Google Summer of Code (or other similar stipend schemes) (was: as for Calc and the math library)
Date: Mon, 19 Aug 2024 13:43:46 +0000 [thread overview]
Message-ID: <DU2PR02MB101094E2DAE8D87D3A3E95239968C2@DU2PR02MB10109.eurprd02.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1835 bytes --]
>Eli Zaretskii <eliz@gnu.org> writes:
>
>>> The interested students will likely also be at least casual Emacs users.
>>> So, some degree of familiarity is expected.
>>
>> User-level familiarity doesn't help in these matters, IME.
>
>>> Other than that, how is Emacs dramatically different from working with
>>> any other large codebase?
>>
>> In a nutshell, Emacs is much larger than most other projects, and its
>> features are much less localized than those of other large projects.
>
>But not every feature, right? Some parts are easier to hack than others.
>I imagine that many Elisp parts are somewhat easier compared to C code.
>
>>> What is needed is a formulation of projects/features that are desired.
>>> Mentors do not have to be maintainers. Experienced Emacs contributors
>>> can be the mentors (also, mentoring a student can be a good addition to
>>> some types of CVs).
>>
>> We have etc/TODO which could be used as a source of ideas.
>
>Are there any specific todo items there that you view as more suitable
>for people with limited experience in Emacs codebase?
I am not sure if this is something, I hope you don't mind me asking, but could a
work to modularize Org, be an appropriate subject?
For example turn displaying pretty text (bold, italics etc), pretty links,
tables, dates, and perhaps some other stuff into, from Org-mode, independent,
minor modes that could be used in other parts of Emacs and more independently of
Org mode. I think both Org-mode and Hyperbole, and perhaps some other libraries
(button.el, help-mode, info), could use some minor mode that works with
links. For us users, it would mean less cruft loaded into Emacs, if those big
players could share some code.
I haven't done much research on this, just something I had in my head for a long
time.
[-- Attachment #2: Type: text/html, Size: 6330 bytes --]
next reply other threads:[~2024-08-19 13:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 13:43 arthur miller [this message]
2024-08-20 17:40 ` Modularizing Org as GSoC project (was: 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-21 2:45 ` Sv: " arthur miller
2024-08-22 12:23 ` Ihor Radchenko
2024-08-23 7:15 ` Sv: " arthur miller
2024-08-31 12:20 ` Ihor Radchenko
2024-09-01 13:54 ` Sv: " arthur miller
2024-09-27 12:21 ` Sv: Modularizing Org as GSoC project Björn Bidar
2024-09-27 12:21 ` Björn Bidar
-- strict thread matches above, loose matches on Subject: below --
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 17:59 ` Eli Zaretskii
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 19:17 ` Ihor Radchenko
2024-08-13 11:02 ` 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
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=DU2PR02MB101094E2DAE8D87D3A3E95239968C2@DU2PR02MB10109.eurprd02.prod.outlook.com \
--to=arthur.miller@live.com \
--cc=emacs-devel@gnu.org \
--cc=yantar92@posteo.net \
/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).