:D I meant your fix doesn't look into the source of the bug, so it could cause collateral effects. Anyway, it opens a debate about which logic from editor could be removed as far as modern browsers have changed a lot.
About GWT tests, we have avoided them because we avoid GWT specific code in most of the code. But I am very interested on knowing more about it. 2016-12-06 15:00 GMT+01:00 Evan Hughes <ehu...@gmail.com>: > Ill review the pull requests in the morn, technically i see nothing wrong > with my fix :P the code shared between the webkit and firefox are very > similar :P. Much appreciated specially with the dev server. Has swellrt > been doing many tests with GWt, we did manage to get ours working, just a > few compilation issues left, just wondering. > > On Tue, 6 Dec 2016 at 22:10 Pablo Ojanguren <pablo...@gmail.com> wrote: > > > Finally I've written down a shorter version of Adam's text following > > Upayavira suggestion. > > > > https://wiki.apache.org/incubator/December2016 > > > > Also I pointed out some items I am not sure how to fill, I guess > @upayavira > > you should double check! > > > > > > > > 2016-12-06 12:49 GMT+01:00 Pablo Ojanguren <pablo...@gmail.com>: > > > > > Evan, I checked out your hot fix, so hot indeed :D I sent a pull PR > with > > > my version. > > > > > > 2016-12-06 10:23 GMT+01:00 Evan Hughes <ehu...@gmail.com>: > > > > > >> my own fix is in the dependencies fix branch if you wanna cross check > > >> them, > > >> though mine is more of a hot fix. > > >> > > >> On Tue, 6 Dec 2016 at 19:05 <pablo...@gmail.com> wrote: > > >> > > >> > Thanks Adam, lets include your text in the report. > > >> > > > >> > One thing, regarding the editor the issue caused by chrome 54 has > been > > >> > fixed in swellrt... I will send a PR ;) > > >> > > > >> > El 5 dic. 2016 16:48, Adam John <a...@sterlingsolved.com> escribió: > > >> > > > >> > Excellent work, Pablo & folks. I took what both of you wrote and > > >> combined > > >> > / formatted... with some tweaks I hope help to improve... > > >> > > > >> > * * How has the community developed since the last report?* > > >> > > > >> > The community has several new/re-activated contributors and > > participants > > >> > across different disciplines since last report. The most > significant > > >> > developments for our community have come about since September. > > >> > > > >> > After an open community conference call on Sept 28th, a joint effort > > >> > between Wave and SwellRT development was initiated. This was > started > > in > > >> > order to align community development efforts and has had some very > > >> positive > > >> > results. > > >> > > > >> > An effort has started to reduce the dependencies in the source of > the > > >> main > > >> > project, with help from the SwellRT team. Mostly transitive > > >> dependencies > > >> > were updated, and work is still proceeding. > > >> > > > >> > A focus area next cycle is the removal of core dependencies which > were > > >> long > > >> > ago depreciated, this currently revolves around the UI design of the > > >> static > > >> > content of wave. In the next report it is expected that some > reworking > > >> of > > >> > the UI design will be done and integrated. > > >> > > > >> > > > >> > SwellRT API has been tried out by some members of the community and > a > > >> > branch containing the SwellRT code is now in the repository. > > >> Discussions > > >> > are > > >> > still taking place to determine the full extent of the integration > as > > >> the > > >> > projects share a common goal but have side plans as well. > > >> > > > >> > One notable consideration in ongoing development originates from a > > >> sister > > >> > project that provides a real time editor (gpl type license). Apache > > >> Wave > > >> > already contains an editor but has experienced some bugs this past > > week > > >> > (relating to chrome api changes). > > >> > > > >> > Discussion of a new editor in-house did happen a few reports ago and > > >> will > > >> > need to continue as we refine, remodel and clean house overall. > > >> > > > >> > * * How has the project developed since the last report?* > > >> > > > >> > Some members of Wave community have tried SwellRT API and some > common > > >> > tasks have been performed, such as: > > >> > > > >> > > > >> > 1. Cleaned up some obsolete dependencies. > > >> > 2. New branch created on wave repo containing a mirror of swellrt > > >> code. > > >> > 3. Updated major dependencies and fixed minor bugs. > > >> > > > >> > > > >> > > > >> > Thanks, and talk soon! > > >> > > > >> > AJ > > >> > > > >> > Adam John > > >> > (914) 623-8433 > > >> > Google+ <https://plus.google.com/+AdamJohn1> | LinkedIn > > >> > <https://www.linkedin.com/in/mradamjohn> > > >> > | Twitter <https://twitter.com/mradamjohn> | Facebook > > >> > <https://www.facebook.com/mradamjohn> > > >> > > > >> > On Mon, Dec 5, 2016 at 10:17 AM, Pablo Ojanguren < > pablo...@gmail.com> > > >> > wrote: > > >> > > > >> > > Here is a draft for the report, please suggest (just two major > > >> > > questions)... > > >> > > > > >> > > > > >> > > *How has the community developed since the last report?* > > >> > > > > >> > > After Sept 28th concall, a joint effort between Wave and SwellRT > > >> > > communities has started in order to prove that Wave community is > > >> eager to > > >> > > replace or integrate its code base with SwellRT's one. > > >> > > > > >> > > *How has the project developed since the last report?* > > >> > > > > >> > > Some members of Wave community has been tried SwellRT API and some > > >> common > > >> > > tasks has been performed: > > >> > > > > >> > > Clean up of obsoletes dependencies. > > >> > > New branch on wave repo containing a mirror of swellrt code. > > >> > > Updated major dependencies and fixed minor bugs. > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > 2016-12-05 15:39 GMT+01:00 Pablo Ojanguren <pablo...@gmail.com>: > > >> > > > > >> > > > hehe :D you right Evan > > >> > > > > > >> > > > About Mozilla grant I just filled out the form, and just waiting > > for > > >> > > their > > >> > > > answer. At least, I have been endorsed by Audrey Tang, Digital > > >> Minister > > >> > > of > > >> > > > Taiwan and famous free software developer. ( > > >> https://en.wikipedia.org/ > > >> > > > wiki/Audrey_Tang) > > >> > > > > > >> > > > > > >> > > > > > >> > > > 2016-12-05 14:01 GMT+01:00 Evan Hughes <ehu...@gmail.com>: > > >> > > > > > >> > > >> but were would the mystery be :P > > >> > > >> > > >> > > >> we were just discussing how with recent developments there > needs > > >> to be > > >> > > >> some > > >> > > >> work with our license and notices to be updated. This will > > >> probably be > > >> > > >> something we need to keep on top of while a lot is > transitioning. > > >> > > >> > > >> > > >> On a side note, how did the Mozilla funding for SwellRT go > pablo? > > >> > > >> > > >> > > >> On Mon, 5 Dec 2016 at 22:57 Pablo Ojanguren < > pablo...@gmail.com> > > >> > wrote: > > >> > > >> > > >> > > >> Ops... well, if you don't mind to invite us... ;) > > >> > > >> > > >> > > >> 2016-12-05 13:55 GMT+01:00 Evan Hughes <ehu...@gmail.com>: > > >> > > >> > > >> > > >> > Haha, sorry we were discussing some of the contents in the > > >> private > > >> > > >> channel > > >> > > >> > but it should've been here, my mistake. > > >> > > >> > > > >> > > >> > On Mon, 5 Dec 2016 at 22:28 Pablo Ojanguren < > > pablo...@gmail.com> > > >> > > wrote: > > >> > > >> > > > >> > > >> > > Hey Adam, I am about to start filling the report... > > >> > > >> > > > > >> > > >> > > 2016-12-05 13:22 GMT+01:00 Adam John < > a...@sterlingsolved.com > > >: > > >> > > >> > > > > >> > > >> > > > I realize this was sent to the list... curious who is > > >> completing > > >> > > the > > >> > > >> > > > report? > > >> > > >> > > > > > >> > > >> > > > Also, the "move" referenced... not sure what that might > be? > > >> > > >> > > > > > >> > > >> > > > Report is due Wednesday. > > >> > > >> > > > > > >> > > >> > > > Thanks, all. > > >> > > >> > > > > > >> > > >> > > > Adam John > > >> > > >> > > > (914) 623-8433 > > >> > > >> > > > > > >> > > >> > > > On Dec 4, 2016 9:18 AM, <johndam...@apache.org> wrote: > > >> > > >> > > > > > >> > > >> > > > > Dear podling, > > >> > > >> > > > > > > >> > > >> > > > > This email was sent by an automated system on behalf of > > the > > >> > > Apache > > >> > > >> > > > > Incubator PMC. It is an initial reminder to give you > > >> plenty of > > >> > > >> time > > >> > > >> > to > > >> > > >> > > > > prepare your quarterly board report. > > >> > > >> > > > > > > >> > > >> > > > > The board meeting is scheduled for Wed, 21 December > 2016, > > >> > 10:30 > > >> > > am > > >> > > >> > PDT. > > >> > > >> > > > > The report for your podling will form a part of the > > >> Incubator > > >> > > PMC > > >> > > >> > > > > report. The Incubator PMC requires your report to be > > >> > submitted 2 > > >> > > >> > weeks > > >> > > >> > > > > before the board meeting, to allow sufficient time for > > >> review > > >> > > and > > >> > > >> > > > > submission (Wed, December 07). > > >> > > >> > > > > > > >> > > >> > > > > Please submit your report with sufficient time to allow > > the > > >> > > >> Incubator > > >> > > >> > > > > PMC, and subsequently board members to review and > digest. > > >> > Again, > > >> > > >> the > > >> > > >> > > > > very latest you should submit your report is 2 weeks > > prior > > >> to > > >> > > the > > >> > > >> > board > > >> > > >> > > > > meeting. > > >> > > >> > > > > > > >> > > >> > > > > Thanks, > > >> > > >> > > > > > > >> > > >> > > > > The Apache Incubator PMC > > >> > > >> > > > > > > >> > > >> > > > > Submitting your Report > > >> > > >> > > > > > > >> > > >> > > > > ---------------------- > > >> > > >> > > > > > > >> > > >> > > > > Your report should contain the following: > > >> > > >> > > > > > > >> > > >> > > > > * Your project name > > >> > > >> > > > > * A brief description of your project, which assumes > no > > >> > > >> knowledge > > >> > > >> > of > > >> > > >> > > > > the project or necessarily of its field > > >> > > >> > > > > * A list of the three most important issues to > address > > in > > >> > the > > >> > > >> move > > >> > > >> > > > > towards graduation. > > >> > > >> > > > > * Any issues that the Incubator PMC or ASF Board > might > > >> > > wish/need > > >> > > >> to > > >> > > >> > > be > > >> > > >> > > > > aware of > > >> > > >> > > > > * How has the community developed since the last > report > > >> > > >> > > > > * How has the project developed since the last > report. > > >> > > >> > > > > > > >> > > >> > > > > This should be appended to the Incubator Wiki page at: > > >> > > >> > > > > > > >> > > >> > > > > https://wiki.apache.org/incubator/December2016 > > >> > > >> > > > > > > >> > > >> > > > > Note: This is manually populated. You may need to wait > a > > >> > little > > >> > > >> > before > > >> > > >> > > > > this page is created from a template. > > >> > > >> > > > > > > >> > > >> > > > > Mentors > > >> > > >> > > > > ------- > > >> > > >> > > > > > > >> > > >> > > > > Mentors should review reports for their project(s) and > > sign > > >> > them > > >> > > >> off > > >> > > >> > on > > >> > > >> > > > > the Incubator wiki page. Signing off reports shows that > > you > > >> > are > > >> > > >> > > > > following the project - projects that are not signed > may > > >> raise > > >> > > >> alarms > > >> > > >> > > > > for the Incubator PMC. > > >> > > >> > > > > > > >> > > >> > > > > Incubator PMC > > >> > > >> > > > > > > >> > > >> > > > > > >> > > >> > > > > >> > > >> > > > >> > > >> > > >> > > > > > >> > > > > > >> > > > > >> > > > >> > > > >> > > > > > > > > >
