On 26/02/2016 19:01, Jet Villegas wrote:
I think our first priority is to establish a clear Module Owner for Editor,
then triage the bugs and draft a project roadmap for that component. We'll
then need to determine the list of contributors who can help put code
behind those plans. Can we add you to that list?
--Jet
Sure.
As you can see from the link in my signature, I have already fixed a few
bugs in these areas, look for the boxes "M-C / Gecko: Editor problems"
and "M-C / Gecko: Spell checker clean-up". Sadly my skills are limited,
so I have to rely on guidance from others.
It would be good to find a module owner and responsive reviewer(s) like
Ehsan and Robert O'Callahan have been in the past (and hopefully still
are during the transition).
On a different issue:
Some of the code in the editor/serialisers/etc. dates back to the
Netscape days, when the program had a browser and integrated e-mail
client. If you're drafting a roadmap, you might consider clearly
identifying the parts only maintained for what has become Thunderbird
and transfer those into the responsibility of the Thunderbird
maintainers, if possible. Just some examples from the top of my head:
grep -i mail editor/libeditor/*.cpp
grep -i mail dom/base/nsIDocumentEncoder.idl
grep -i mail dom/base/nsPlainTextSerializer.cpp
mozTXTToHTMLConv::ScanHTML - OK, different module, but you get the idea.
Jorg K (Mozilla contributor - www.jorgk.com/misc/Mozilla-work.pdf)
_______________________________________________
governance mailing list
[email protected]
https://lists.mozilla.org/listinfo/governance
