| Re: [lsat-dev] [technology-pmc] Committer Election for Alvaro Piedrafita on Eclipse LSAT has started |
|
Hi Wayne, all, What was meant with “behind the scenes” was “outside of the software development domain”, not “hidden from public view”. Most of the contributors to the LSAT project work for TNO, a member of the Eclipse foundation
(https://www.eclipse.org/membership/show-member/?member_id=1489). At TNO we perform applied scientific research (TRL 4-6) in which we aim to bring scientific research (TRL 1-3) closer
to industry adoption. One part of our work is research into e.g., algorithms which scale to the size of problems in industry. Another part is to convert ideas and concepts into applications. Both parts are applicable for LSAT; Alvaro has been working on a
scheduling algorithm which supports just-in-time scheduling (https://gitlab.eclipse.org/eclipse/lsat/lsat/-/issues/81), while e.g., Paul and Gert-Jan have been more involved on the implementation
side. This year we picked up LSAT development with a larger team, and established contact with beta testers in industry. For 2026 we’d like to use the Eclipse Gitlab issue tracker more, not only for problems and
implementation bugs, but also for discussing algorithms, design decisions, which corner cases the algorithms must support, etc. That way we can have these kinds of discussions in one place across organizations, and it should be clearer why certain features
have been implemented a certain way and not only how. To give all team members the option to e.g., assign, label, prioritize, or add attachments to issues, we’d like them to have the developer role in the LSAT project. Hopefully this clarifies our request why we’d like team members like Alvaro to become committers, and he can get the developer role in the LSAT project soon. Kind regards, Bram From: lsat-dev <lsat-dev-bounces@xxxxxxxxxxx>
On Behalf Of Wayne Beaton via lsat-dev It doesn't work like this. "Behind the scenes" isn't a thing in open source. The candidate must demonstrate their contributions publicly. Are there any pull requests that you can cite? Discussion on public issues or mailing lists? Without public evidence, we have no reason to believe that the candidate understands the process. Indeed, not working publicly is an indication that they do not understand how open collaboration works. If the candidate is ready to be a committer, perhaps they can make a few pull requests to demonstrate that they're ready. Wayne (in my combined capacities as a member of the Eclipse Technology PMC and representative of the EMO). On Tue, 25 Nov 2025 at 06:41, Eclipse Foundation via technology-pmc <technology-pmc@xxxxxxxxxxx> wrote:
Wayne Beaton (he/him) Director, Open Source Projects |
Eclipse Foundation |