From: Fermin <fmfs@posteo.net>
To: emacs-devel@gnu.org
Subject: CEDET maintainer
Date: Sat, 27 Mar 2021 22:06:26 +0100 [thread overview]
Message-ID: <ebdd0600-f1f8-b12b-dd86-125f65e862e3@posteo.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1952 bytes --]
Hello Emacs developers,
My name is Fermin, I'm the maintainer of several Emacs external packages
(some of them are maxima.el <https://gitlab.com/sasanidas/maxima>
,realgud-xdebug <https://github.com/realgud/realgud-xdebug> and
lsp-sonarlint <https://github.com/emacs-lsp/lsp-sonarlint>) aside from this,
I've been messing around with CEDET these past year or so, and I really
like it overall, I can understand his faults and how/why the Emacs
community
is not taking CEDET into account too much these days, but I also think
that this can change.
I'm proposing myself as a CEDET maintainer, I want to contribute to it
in a more direct way, I have some degree of familiarity with the source
code now
and I think I can help in the future development of it, recently there
were a talk about a xref background integration and I think this can be
a great initial
addition. I'm also working on in a more in depth analysis of CEDET so
other people can jump and point out new improvements.
I talked with the original creator/maintainer (Eric) privately and he
kindly gave me the source code of the current CEDET webpage
<http://cedet.sourceforge.net/>, so the first thing
I did was to update it, keeping the old aesthetic but making it HTML5
compatible, it is still a work in progress and the information need to be
also updated, but I think a nice informative webpage can help for new
people to know and use CEDET.
This is the repository of the webpage
https://gitlab.com/sasanidas/cedet-webpage and this is the current URL
https://sasanidas.gitlab.io/cedet-webpage/ ,
I'm using plain HTML5 with a simple script to translate "templates".
If the Emacs maintainers, decide that I'm worthy of it, my initial idea
is to develop CEDET in a separate branch for now, even tho I think the
send patch workflow is valid,
for a package like CEDET that needs a lot of changes, this can really
slow down the process.
Thank you.
Regards,
Fermin
[-- Attachment #2: Type: text/html, Size: 2765 bytes --]
next reply other threads:[~2021-03-27 21:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-27 21:06 Fermin [this message]
2021-03-27 21:22 ` CEDET maintainer Stefan Monnier
2021-03-27 21:54 ` Fermin
2021-03-27 22:40 ` Stefan Monnier
2021-03-27 23:25 ` Fermin
2021-04-24 20:20 ` Eric Ludlam
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=ebdd0600-f1f8-b12b-dd86-125f65e862e3@posteo.net \
--to=fmfs@posteo.net \
--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).