I welcome the formatting as I find the code to be all over the place stylistically which can mean more confusion for contributions and worsened perception of quality.
Can we also remove the trailing white space too? I find that weirdly annoying. There is a manually "clean-up” check box for it and save action.
Also, I guess Tabs win? :) I don’t mind personally but was expecting more heated debate!
About EPLv2, I don’t know much about that. It doesn’t look like there is any downside? I guess it opens the door to a secondary license of GPL which I don’t foresee anyone to be actively against, especially since the secondary license can be dropped by
adopters.
Cheers,
Marc-André
Hi folks,
A bunch of committers, contributors and adopters are all together at EclipseCon Europe for the
Embedded Summit. We have had many discussions about lots of exciting things and a great roadmap is starting to develop. Watch this space for more on that.
We also discussing some more releng / housekeeping stuff and that is the purpose of this email.
I am planning on updating
CDT to EPLv2 and
normalizing/enforcing the formatting of the code base. The committers
who are here are all in agreement, but I want to notify the larger community and find a time that will interfere as little as possible. These changes will mean all source files are touched so automatic merging will be affected.
I would like to apply these changes the week of the 12th of November (week after 2018-12 M2).
Please speak up if the timing causes you an issue by commenting on the bug report.
Thanks,
Jonah
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________