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 (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
