| Re: [eclipse-ide-wg] Eclipse IDE Working Group Minutes - 5th April 2022 |
Thomas,
Getting other people to do even such obviously good
things is just not within anyone's actual control. I can control
what I do myself with my time and I can try to set a good example
to influence others in the direction that I think is best for the
community. Of course each and every one of us can do that...
I've certainly tried to make getting started on the entire set of Eclipse top-level projects as simple as possible:
https://wiki.eclipse.org/Eclipse_Platform_SDK_Provisioning
The recent migration to Github has a been bit overwhelming to track from this regard; now we've started merging repositories so the fun's not over. It's an ongoing moving target.
The goal is to make all this more attractive to contributors familiar with Github's workflows, but initially it has made it more difficult for most of the existing contributors and committers who are not so familiar with that. Even requests for documented guidelines for the new workflows was initially met with resistance because "there's tonnes of documentation on Github already." But, we will adapt and we will move forward.
So yes, we you say makes totally sense, but how do we (you?) get
other people to do this? I'd suggest reading this long and
painful thread to get a full sense of how difficult it is to do
what at a glance seems like obviously the right thing:
https://www.eclipse.org/lists/platform-dev/msg03291.html
Regards,
Ed
Hi Ed,
------ Original Message ------From: "Ed Merks" <ed.merks@xxxxxxxxx>Sent: 20/04/2022 17:33:47Subject: Re: [eclipse-ide-wg] Eclipse IDE Working Group Minutes - 5th April 2022
I think many of the problems are very clear, but the solutions are not. Not only that, even when the solution is very clear, the solution almost always requires people with time, but there are not enough people with enough time...I get the "we don't have time to fix this" argument, but it's kind of circular: we can't attract more contributors, because we can't make the project more attractive to contributors, because we don't have enough contributors.
We can't fix everything in a single go, but we can do two things:
1. If you're in hole, stop digging: when we make changes, we should make sure they don't make things worse for new contributors2. Let's do one thing that helps every release cycle. Review one PR, fix one paragraph of out-of-date documentation.
/Thomas
_______________________________________________ eclipse-ide-wg mailing list eclipse-ide-wg@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse-ide-wg