On 5/30/15, 10:28 PM, "Justin Mclean" <jus...@classsoftware.com> wrote:
>> Let’s propose ways to make progress. Please make sure you have clarity >>on >> the pieces involved before speculating on possible blockers, and then >> propose how we can proceed, not why we should stop. > >If it did turn out to be a blocker a lot of effort would be wasted, IMO >it better to look at potential issues up front and resolve them and/or >find another solution. It certainly wasn't clear that these files would >not be bundled and that they are optional. i.e. the majority of users can >use what we release without these files. IMO, it is also wasteful and even more harmful to present issues up front based on faulty assumptions to the point where you scare folks from working on it, and make unsubstantiated accusations about the IP integrity of popular GitHub sites. I did mention before last night that any one of these d.ts files are an optional dependency. I know you are spreading your Apache time across multiple projects these days so I’d say the onus is on you to get clarity before presenting these potential blockers. Maybe ask for a re-cap when you are behind by a lot of posts and have limited time to catch up. I’ll bet plenty of others are struggling to keep up and would love a re-cap as well. And yes, please try presenting solutions for the potential problems you find. It helps create a more collegial tone on the list. Thanks, -Alex
