Goktug, sorry for being a but stubborn here, but we need a tad more
visibility:
{quote}
The main blocker for releasing J2CL for wider audience is even basic
missing functionalities around building it in open-source and seeing at
least some output for your compilations.
{quote}
"even basic missing functionalities" sounds quite worrysome. What is the
ETA for implementing these and releasing a preview? If e.g. two months,
fine. If we are talking Q4/2018 or 2019, then that's a different
proposition altogether. I guess, not just for us. Please don't answer with
the "it's done when it is done" slogan. :) That's one of the major pains
for this community imo.
Final Q: are all the legal issues for releasing in the open resolved by
now? From personal experience, these might take forever to resolve.
On Thursday, March 8, 2018 at 10:51:21 PM UTC+2, Goktug Gokdogan wrote:
>
> > There is still tone of work to do for a polished open source experience
> but at least we can give access to more people who is really interested.
>
> What I meant here; is giving access *after* basic bazel stuff is finished
> so there will be something to play with. We don't want to give access to
> a broader group for something that is dead on arrival.
>
>
> On Thu, Mar 8, 2018 at 5:31 AM Alberto Mancini <ab.ma...@gmail.com
> <javascript:>> wrote:
>
>> Hello,
>> yes, definitely I would like to be in.
>> I am really interested.
>>
>> Cheers,
>> Alberto.
>>
>>
>> On Thu, Mar 8, 2018 at 2:21 PM Nándor Előd Fekete <nandor...@gmail.com
>> <javascript:>> wrote:
>>
>>> I am *really* interested. Can you sign me up?
>>>
>>>
>>> On Thursday, March 8, 2018 at 9:13:01 AM UTC+1, Goktug Gokdogan wrote:
>>>>
>>>> The main blocker for releasing J2CL for wider audience is even basic
>>>> missing functionalities around building it in open-source and seeing at
>>>> least some output for your compilations. That is blocked on missing
>>>> functionalities in bazel. After that we can probably finished in more
>>>> timely manner.
>>>> There is still tone of work to do for a polished open source experience
>>>> but at least we can give access to more people who is really interested.
>>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "GWT Contributors" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com
>>> <javascript:>.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/8de62b64-4bc8-4158-80d4-b15ef688f523%40googlegroups.com
>>>
>>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/8de62b64-4bc8-4158-80d4-b15ef688f523%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "GWT Contributors" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com
>> <javascript:>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAGv30V%3DfWDpwQ45u9mPVuXY%3D62PJZ%2B9uxearZk5Lq_a0j2yjaA%40mail.gmail.com
>>
>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAGv30V%3DfWDpwQ45u9mPVuXY%3D62PJZ%2B9uxearZk5Lq_a0j2yjaA%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
--
You received this message because you are subscribed to the Google Groups "GWT
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/067f44a4-2f87-49f1-9495-3e7a13f1f0ff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
