Hello Celix community, My name is Prasanna, and I am interested in applying to Google Summer of Code 2026 with Apache Celix.
I am currently exploring the project ideas and wanted to ask whether the project titled "" is expected to be undertaken as part of GSoC this year. I am trying to understand which ideas are actively being considered so that I can focus my efforts on the most relevant areas and start contributing accordingly. Any clarification or guidance would be greatly appreciated. Thank you for your time. Best regards, Prasanna On Fri, Feb 6, 2026 at 5:15 PM moelksasbyahmed (via GitHub) <[email protected]> wrote: > > moelksasbyahmed commented on PR #817: > URL: https://github.com/apache/celix/pull/817#issuecomment-3859979345 > > > In my view, we should either accept a slower build (limiting > parallelism to (.i.e.) -j4) or postpone the analyzer's introduction. I > personally prefer the slower build. We can look into ASF-hosted runners > later to optimize. > well i tried to make it slow by enable -j2 and i ran the workflow on > my forked repo the debug build reached memory limit and has `exit code of > 143` check [forked repo workflow]( > https://github.com/moelksasbyahmed/celix/actions/runs/21686945878/job/62536446202) > so i guess the valid options is making the build so slow by making ninja > -j1 or making a specific Ci pipeline with test disabled but i agree with > you the test should be compatible with test as well so i guess the only > valid option is making the build slow by ninja -j1 and it can be optimized > later i will search for valid solutions > > > > -- > This is an automated message from the Apache Git Service. > To respond to the message, please log on to GitHub and use the > URL above to go to the specific comment. > > To unsubscribe, e-mail: [email protected] > > For queries about this service, please contact Infrastructure at: > [email protected] > >
