All: These are great! Thank you for your participation. The intent of the project work is to expose the student teams to real work in real software. If a project ends up in a dead-end then it's a dead-end and I would look to the students (working with the mentors) to write up the experiment and what was learned so the students can point to that experience as well as helping the Lucene community. If the student team finishes a project early, then continuing down the path with related work is perfectly acceptable. They have come up the learning curve (language, toolchain, test environments, Lucene itself), so keeping them busy and getting more work done is a Good Thing™. The students are not being graded on pull requests. (That said, it would be weird if most people in a student team have PRs happening and one student doesn't.)
With 5 mentors, it feels like there are two teams worth of projects. I would ask you to pick two or three projects that you collectively believe to be the strongest candidates, and pull them up to the top of the List and I will present those on Tuesday. I would ask that they aren't the two LLM project proposals. That said, one of the co-instructors this summer is building out an AI-augmented Software Engineering undergrad course for the Fall semester. I'm also working on the edge with him on ideas. I would love to dig into these ideas with him and the Lucene project more deeply. Does this make sense? Hope so. kind regards, stephe On Fri, May 9, 2025 at 1:53 PM Michael McCandless <luc...@mikemccandless.com> wrote: > [Adding Stephen back on the "To:" line (not sure if he's sub'd to Lucene > dev list).] > > Stephen, it looks like we have a nice collection of possible projects in > the Google Doc ( > > https://docs.google.com/document/d/10luAXYfHDe3j_pF9dslPdDzDMHaUqMTmnPI6QEgUP4w/edit?usp=drivesdk) > and a number of mentors volunteering on this thread (Vigya Sharma, Marcus > Eagan, Rahul Goswami, Marcus Eagan, and myself). > > I think we have a good starting point to kick off initial discussions to > hone down to more specific / better scoped projects + teams + mentors? > What are the next steps? Should we set up a shared Slack/Discord/Signal > group chat somewhere? > > Mike McCandless > > http://blog.mikemccandless.com > > > On Thu, May 8, 2025 at 9:47 AM Vigya Sharma <vigya.w...@gmail.com> wrote: > >> Hi Stephen, >> >> Project ideas are quite high level at this stage and will likely hit >> roadblocks as we progress. Some of them may even get abandoned due to good >> technical reasons, like performance overhead. Are students required to have >> their projects completed and merged into the repo? Also, what happens if >> they complete the project too soon? Do theysimply pick another one? >> >> I'm planning to create a new label for "mentored project candidates" and >> tagging GitHub issues for programs like this one. Wanted to get a sense of >> the scope of projects we should consider here. >> >> Vigya >> >> On Mon, May 5, 2025 at 7:21 PM Stephen Walli <stephen.wa...@gmail.com> >> wrote: >> >>> All: Thank you for your interest. >>> Here is the course description: 99-520 Applied Software Engineering for >>> the Real World with Distributed Teams >>> <https://www.cmu.edu/education-office/resources/99-520-course-listings.html> >>> . >>> You're looking under the "Remote Options" courses. >>> >>> Often the project description is covered by a project GitHub Issue. >>> Students have done a lot of work on real plumbing within the projects over >>> the past couple of years. Current projects from a couple of different >>> Eclipse projects include: >>> Add support for shared-memory >>> <https://github.com/eclipse-uprotocol/up-spec/issues/273> >>> Add support for WebAssembly / WebAssembly Interface Types >>> <https://github.com/eclipse-uprotocol/up-spec/issues/278> >>> >>> https://github.com/eclipse-ee4j/starter/issues/185 >>> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Feclipse-ee4j%2Fstarter%2Fissues%2F185&data=05%7C02%7CStephen.Walli%40microsoft.com%7Cb19d92e662df4e90338208dd829742e1%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638810308369574998%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Wxr%2FF4%2FdacvcJNFruIXPB%2BSUINzx2D3kTGD7%2Fbu2R8g%3D&reserved=0> >>> https://github.com/eclipse-ee4j/cargotracker/issues/17 >>> >>> I would love to see a couple of projects with mentors from the Lucene >>> community. >>> kind regards, stephe >>> >>> >>> On Sun, May 4, 2025 at 10:12 PM Rahul Goswami <rahul196...@gmail.com> >>> wrote: >>> >>>> Stephen, >>>> I am not a Lucene committer (yet), but have a good understanding of >>>> certain parts of the codebase. I am also a contributor for the Apache >>>> Solr project (built on top of Lucene) so that too helps with the >>>> understanding. >>>> I am happy to team up with one of the committers and help out as a >>>> mentor. Already a list of exciting projects in the Word doc, so that's >>>> nice to see! >>>> >>>> Do you mind sharing the link to the course please (or the name/code)? >>>> This is to get a general sense of what the course entails and what the >>>> target audience is looking for. Also, as Vigya already requested, >>>> links to past projects would be nice too. Thanks. >>>> >>>> - Rahul >>>> >>>> On Sun, May 4, 2025 at 7:17 PM Vigya Sharma <vigya.w...@gmail.com> >>>> wrote: >>>> > >>>> > What a great way to get some new contributors onboarded to Lucene! >>>> Thanks for connecting here Stephen. I'm a committer on Apache Lucene and >>>> would be happy to help as a mentor. >>>> > >>>> > Since you requested questions, here's one to get us started ;) – >>>> Could you share links to past projects students have done as part of this >>>> course? >>>> > I added some projects to the shared doc, but also wanted to get a >>>> better sense of the typical scope of problems that students are able to >>>> successfully tackle in this timeframe, as well as how well defined the >>>> problems need to be. >>>> > >>>> > Best, >>>> > Vigya >>>> > >>>> > >>>> > On Sun, May 4, 2025 at 8:18 AM Marcus Eagan <marcusea...@gmail.com> >>>> wrote: >>>> >> >>>> >> I wouldn't exactly call us a Lucene company but the CEO and CTO (Tim >>>> Potter) at my company are both Lucene contributors in the past. Tim is a >>>> committer. I don't think the CTO has the bandwidth to mentor too much for a >>>> couple months, but I certainly can make time. He will also be able to help >>>> more in the latter half of the class. I think 4-5 students could certainly >>>> work on a project that uses Lucene and our system for a project. >>>> >> >>>> >> A few of the ideas from the project list stood out to me so I think >>>> there could be a fit. >>>> >> >>>> >> Marcus Eagan (LinkedIn) >>>> >> >>>> >> On Sat, May 3, 2025 at 9:29 PM Stephen Walli < >>>> stephen.wa...@gmail.com> wrote: >>>> >>> >>>> >>> All: Mike McCandless pointed me to the dev list and he kindly >>>> started a google doc with project ideas. >>>> >>> I've been co-teaching a summer internship course this past couple >>>> of summers at CMU. The core of the course is the work experience. Students >>>> in teams of 5 work together for 11 weeks for 40 hours/week on a large >>>> project in a real code base, meeting with two mentors once a week to guide >>>> the work. The instructors also meet with the students once a week beyond >>>> the classes to coach students to ensure they're staying on top of the work >>>> and engaging well with mentors. The classes are ~3 hours a week on topics >>>> in software engineering to which every developer should be exposed. . >>>> >>> >>>> >>> I have worked with OpenStack projects and Eclipse Adoptium projects >>>> this past couple of summers and they are participating again. I would love >>>> to engage students with Apache projects, and I think Lucene is a great >>>> community in which they can learn. My apologies, but I have had a late >>>> start this year and classes start on 13 May, so I would need mentor >>>> commitments and project ideas over this next week. The rest of the email is >>>> a broader description of the course. Do please ask questions. Over the time >>>> this course has been evolving, the student outcomes get better and better, >>>> and watching the students gain confidence this past couple of summers has >>>> been brilliant. >>>> >>> >>>> >>> I hope Apache Lucene can contribute projects and mentors this >>>> summer, and thank you for the consideration. >>>> >>> kind regards, always stephe >>>> >>> >>>> >>> --- cut >>>> >>> >>>> >>> We are building out the CMU internship course for open source >>>> software engineering again. >>>> >>> >>>> >>> >>>> >>> >>>> >>> The ask from last year (and call out differences for this year in >>>> bold): >>>> >>> >>>> >>> We are looking for projects that a team of 4-5 students could >>>> tackle together with at least two mentors for each project. (Life happens >>>> and having the built-in mentor redundancy helps. I’ve had mentors get laid >>>> off, change jobs, and take summer vacation.) As we saw last year, mentors >>>> can certainly overlap more than one student team project if appropriate and >>>> they have the time. >>>> >>> Mentors are expected to meet student teams once a week for an hour >>>> (via any video conference setup folks want to use), and to be available by >>>> email during the rest of the week to answer any urgent questions. >>>> >>> This summer we are running the class from 13 May to 31 July (11 >>>> weeks). >>>> >>> We want to try teaching concurrently in both campuses Doha, Qatar >>>> (GMT+3) and Pittsburgh (GMT-5), USA. The entire course will be taught >>>> virtually this year, without a classroom. I certainly did something similar >>>> a few years ago when I was teaching at Johns Hopkins (20 students) with >>>> another group in Galway (16 students). The morning class in Pittsburgh will >>>> be the afternoon in Doha. >>>> >>> We likely have 15-20 students in each location, so if you had on >>>> the order of 2-4 team projects with mentors that fit the format that would >>>> be fantastic. >>>> >>> We are considering going so far as to choose the teams across time >>>> zones to get them working remotely from the start. Last year, after six >>>> weeks together in class and daily stand-ups, the students scattered home >>>> away from Doha, and all of them worked remotely the last four weeks. They >>>> proved they could work remotely together. Of course, the relationships with >>>> mentors have always been remote. The profs in Doha and Pitt want to try >>>> remote from the beginning. (I have a few concerns but I’m also always up to >>>> experiment on students.) >>>> >>> We post the projects on the first day of class and will organize >>>> the teams in that first couple of days, so student teams are introduced to >>>> their mentors in the first week of class and expected to organize that >>>> first meeting to begin the project learning curve. That’s when mentors >>>> point students at any tutorials and bootstrap materials, recommended >>>> getting started materials, etc. >>>> >>> We have set the expectations with the students that they will be >>>> spending 20-40 hours of time per week on the project. It is an >>>> internship-like experience. >>>> >>> >>>> >>> · Two co-teachers run classes on three days a week for 80 >>>> minutes, and I will guest lecture a collection of classes. (Last year, >>>> there was just the real professor and I.) >>>> >>> >>>> >>> · The three of us will provide a coaching session with each team >>>> to ensure they are working with the mentors well. >>>> >>> >>>> >>> · Students generally have Windows or Mac laptops, but we have >>>> teaching assistants on each site that we can start to prep any other access >>>> to resources they might need. >>>> >>> >>>> >>> · As with last year, mentors have a lot of freedom to >>>> experiment. Some have run joint sessions if they are mentoring more >>>> students for learning curves. Some have run Slack or Discord channels. >>>> >>> >>>> >>> >>>> >>> What have I forgotten to mention? What new questions have occurred >>>> since last time we talked? >>>> >>> >>>> >>> I’m really hoping the ASF can participate this year. >>>> >>> >>>> >>> >>>> >>> -- >>>> >>> Stephen R. Walli >>>> >>> +1 425 785 6102 >>>> >>> @stephenrwalli (LinkedIn, Twitter, etc.) >>>> >>> Public Presentations on Open Source Software and Standards >>>> >> >>>> >> >>>> >> >>>> >> -- >>>> >> Marcus Eagan >>>> >> >>>> > >>>> > >>>> > -- >>>> > - Vigya >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >>>> For additional commands, e-mail: dev-h...@lucene.apache.org >>>> >>>> >>> >>> -- >>> Stephen R. Walli >>> +1 425 785 6102 >>> @stephenrwalli (LinkedIn <https://www.linkedin.com/in/stephenrwalli/>, >>> Twitter, etc.) >>> Public Presentations on Open Source Software and Standards >>> <https://www.youtube.com/playlist?list=PLdtp42LZvQ1aBykIT1Ksza1JOrOXtJ6-h> >>> >> -- Stephen R. Walli +1 425 785 6102 @stephenrwalli (LinkedIn <https://www.linkedin.com/in/stephenrwalli/>, Twitter, etc.) Public Presentations on Open Source Software and Standards <https://www.youtube.com/playlist?list=PLdtp42LZvQ1aBykIT1Ksza1JOrOXtJ6-h>
