What shall I do?

[markeaston63]

Hey Carlos, I am back.

I want to get busy on this so will take your lead on what you would like me to work on.

Where I work - we have a nimber of things we need to work on for HugeRTE. At present we are using TinyMCE 6.8.3. I was first going to ask you if you think we should move on to HugeRTE now?

QA is testing all my work and I will be very busy next week fixing issues.

But we have already highlighted a number of areas where we need to improve the functionality in HugeRTE.

I have also implemented a number of features externally to HugeRTE which could be considered. eg Mentions and Attachments.

Looking forward to hearing from you Carlos.

Mark

[carlosmintfan]

Hi @markeaston63,
thank you so much.
First, you can switch to HugeRTE but I have to acknowledge tests are failing since I pulled all commits until the license change from TinyMCE as that was an in-development state. The editor basically works, however. Once or so there was an error...which I didn't investigate further...but mostly, it works.
You should upgrade to new versions as soon as I publish them, however.
Feel free to tell me the areas where you need to improve the functionality if your company agrees that you share them.
For the plugins you've developed, you can send them as zip/tar.gz to me or invite me to a Git repository. However, it's important that I'm legally assured I have full right to use them and license them for everybody to use under the MIT license with the copyright statement being HugeRTE contributors. I would not like having to include a copyright statement of your company in the LICENSE file and headers – that should be kept small with the original TinyMCE copyright statement and one for the HugeRTE contributors.
But, to assure that I have full rights on the plugins, it would be great if your company can send me a copyright disclaimer. That can be either publicly here or an email to [email protected]. IMPORTANT: It should be a full disclaimer of copyrights on the code you contribute without a direct assignment to me (because I don't want to share my full name (if that would be necessary) and another reason that I do not want to explain further), meaning that the code should effectively be public domain. For jurisdictions were public domain doesn't quite work I'd like to have a CC0, Unlicense or BSD Zero Clause from your company. Thank you. I hope that will not be too much expense for your company.
And, if you need to fix many issues next week, maybe consider doing this after it so I have the fixed version 😀.
Many thanks again for your willingness to help.

[markeaston63]

Hey @carlosmintfan,

Ok I am upgrading to HugeRTE today. This feature is the focus of our QAs attention next week - so it will be good to get that in front of them now. And yes I will upgrade as new versions come along.

Understand re Plugins. My plan is that plugins I get approval to work on with HugeRTE will be done as HugeRTE plugins. So work that my company will benefit from. I will effectively do that work in my own time. For example the Attachments plugin we need. I have already on that one suggested that we leave that one to HugeRTE to do. The Attachments work I have done so far (our code - so wont be shared with HugeRTE) is external to HugeRTE but that constrains us plus does not work with functionality such as Full Screen, Drag and Drop, Copy and Paste and dealing with different file types. eg look at Gmail or Outlook to get an idea of what we want there.

One issue that has come up on Friday from our QA team - is the Full Screen mode in HugeRTE. I will investigate. Two issues raised:

1. It is not actually full screen - it only fills the browser window
2. It does not include the full editor. I have added attachments and other things around the editor and so obviously HugeRTE does not know about them

So to be clear I will work on work for HugeRTE via branches and PRs I create directly against HugeRTE in GitHub. ie nothing to do with my company.

I will also assist you with fixing bugs - including bugs that we find and I will raise in GitHub Issues.

So important that I upgrade to HugeRTE today. Doing that now. Then I will raise bugs that we find and feature requests in Issues.

Cheers
Mark

[carlosmintfan]

Thank you for your answer!

In https://github.com/orgs/hugemce/discussions/3#discussioncomment-10686276 you said you were working on a templates plugin. Did you finish it? Would your company be okay with sharing it?

Also, could you review https://github.com/orgs/hugemce/discussions/7#discussioncomment-10784437 and tell me if you implemented the three mentioned plugins and if you are / your company is willing to share them, and what you meant by "versions"?