Re: WOLips bugfixes and new features planning
Re: WOLips bugfixes and new features planning
- Subject: Re: WOLips bugfixes and new features planning
- From: Michael Kondratov via Webobjects-dev <email@hidden>
- Date: Wed, 1 Jul 2020 18:48:42 -0400
We could just submit features / bugs to the list and vote.
My issue is the null pointer exception in bindings and bogus validation errors.
Michael
> On Jul 1, 2020, at 4:06 PM, Maik Musall via Webobjects-dev
> <email@hidden> wrote:
>
> Hi everyone,
>
> since this came up again yesterday, here’s the current state of it. Developer
> is ready to do some work, but we haven’t yet defined what that should be. We
> haven’t even reached an agreement about how to get to that state. The list of
> people and organizations willing to contribute has 10 entries already, so I
> think we’re good on the funding side. I invited several people on Slack.
>
> Next we need to agree on how to prioritize things that need fixing and
> implementing. Two links as a starting point are below (github issues, wiki
> page). Some people suggested something in the Entity Modeler should be first
> up, while others don’t even use EOF any more and obviously don’t agree. (My
> personal pet bugfix would be to fix the race condition that leads to bogus
> binding errors when loading large components.)
>
> So, how do we go forward with this?
>
> Maik
>
>
>
>> Am 27.05.2020 um 17:08 schrieb Maik Musall via Webobjects-dev
>> <email@hidden>:
>>
>> Hi everyone,
>>
>> we have an offer from an Eclipse plugin developer to work on bugfixes and
>> new features for WOLips. It’ll cost some money, but not too much, and we
>> already had three entities in Slack [1] signaling willingness to provide
>> funding. So, it seems realistic that we can have some progress here.
>>
>> Next step for us would obviously be to identify and prioritize the things we
>> want work to be done on, then decide where to make the cut, get the funding
>> ready for those things, and then have them done. For a start, we already
>> have two places for the first step:
>>
>> 1. The issues list on github: https://github.com/wocommunity/wolips/issues
>> 2. A wiki page created for this:
>> https://wiki.wocommunity.org/pages/viewpage.action?pageId=43155458
>>
>> In the related Slack discussion [2] there were different opions about
>> whether to just bulk-close all old issues and start new, or review them for
>> usefulness and up-to-dateness and keep the ones which are still relevant and
>> update those. At this point, given the limited number of people in Slack, I
>> wanted to move this discussion here.
>>
>> Opinions?
>>
>> Maik
>>
>>
>>
>>
>> [1] https://wocommunity.slack.com/archives/C1LJMP8LW/p1587484179187100
>> [2] https://wocommunity.slack.com/archives/C01402ABXB6/p1589794078001700
>>
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list (email@hidden)
>> Help/Unsubscribe/Update your Subscription:
>>
>> This email sent to email@hidden
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden