I feel the same. Eagle project today needs more discussion in Eagle dev DL. I do see many discussions and code reviews within individual emails instead of going through Eagle dev DL. And some users also ask questions to individual email directly :-)
Could I suggest Eagle committers and community please discuss important plans and issues in Eagle dev DL to have public record for people to review at any time? Thanks Edward On Fri, Jul 15, 2016 at 10:07 AM, Julian Hyde <[email protected]> wrote: > I am seeing a few JIRA cases which are basically just check-in comments. > They are created just before the commit, they explain what was done in the > commit, do not explain why, do not link to any previous or future work. > > An example of this is EAGLE-378. It arrives a couple of days after I had a > conversation with Michael [1] about cleaning up included jars, yet it seems > to be doing exactly the opposite. > > Is the Eagle project operating commit-then-review or review-then-commit? > It seems to be operating commit-then-review, but if so, there’s not enough > information in the public record for people to review what is happening. > > As my math teacher used to say: don’t just write down the answer, you need > to show your working! > > Julian > > [1] https://issues.apache.org/jira/browse/EAGLE-378 < > https://issues.apache.org/jira/browse/EAGLE-378> > > [2] https://issues.apache.org/jira/browse/EAGLE-377 < > https://issues.apache.org/jira/browse/EAGLE-377>
