Hi, your package seems very interesting, and I was wondering if you
would be interested in having the package added to GNU ELPA (or even
core Emacs (or if nothing else then at least NonGNU ELPA))? If so, I
briefly skimmed over the code and could suggest a few changes that I
could suggest.
Philip Kaludercic <philipk@posteo.net> writes:
Hi Philip,
> Hi, your package seems very interesting, and I was wondering if you> would be interested in having the package added to GNU ELPA (or even> core Emacs (or if nothing else then at least NonGNU ELPA))?
Thank you for your kind words. I usually add an MIT license to my
packages, and decided to hold in this case to consider alternatives. And
I had in mind either GNU ELPA or NonGNU ELPA. More on adding to core later.
> If so, I briefly skimmed over the code and could suggest a few changes> that I could suggest.
Regardless of were the package ends up living, all
suggestions/corrections are welcome! Appreciate you taking the time to
read it.
Going back to inclusion in core Emacs; at the very least I know I want to
contribute code to the existing icalendar module (better support for
monthly frequency). I happen to just have accepted an offer at a new
company so I need to look at the copyright assignment process once I
join officially in a few weeks.
Do you think this is functionality we want in the core? I thought it was
a bit niche. Also, since I'm not taking advantage of the existing webdav
module, it does feel like there some overlap to trim.
Have a nice weekend!
Sebastián
Sebastián Monía <code@sebasmonia.com> writes:
> Philip Kaludercic <philipk@posteo.net> writes:>> Hi Philip,>>> Hi, your package seems very interesting, and I was wondering if you>> would be interested in having the package added to GNU ELPA (or even>> core Emacs (or if nothing else then at least NonGNU ELPA))?>> Thank you for your kind words. I usually add an MIT license to my> packages, and decided to hold in this case to consider alternatives. And> I had in mind either GNU ELPA or NonGNU ELPA. More on adding to core later.>>> If so, I briefly skimmed over the code and could suggest a few changes>> that I could suggest.>> Regardless of were the package ends up living, all> suggestions/corrections are welcome! Appreciate you taking the time to> read it.>> Going back to inclusion in core Emacs; at the very least I know I want to> contribute code to the existing icalendar module (better support for> monthly frequency). I happen to just have accepted an offer at a new> company so I need to look at the copyright assignment process once I> join officially in a few weeks.
OK, that is fine, I am looking forward to the patch.
> Do you think this is functionality we want in the core? I thought it was> a bit niche. Also, since I'm not taking advantage of the existing webdav> module, it does feel like there some overlap to trim.
I do think so, after all, M-x calendar is built-in, and having the
ability to synchronise with external sources is something that certainly
sounds useful. If you would prefer to maintain the code out-of-core,
that should be OK as well, but if you are already looking into
contributing code to the core, then adding everything to the core would
be just as doable.
> Have a nice weekend!> Sebastián