Perhaps a good guideline for projects could be that they build on existing features rather than implement an all new feature.
On 01/17/2017 08:40 AM, Be wrote: > On 01/17/2017 02:28 AM, Daniel Schürmann wrote: >> Produce small merge-able, steps was one of our major goal for the >> time-line the students have to setup for the their project. >> Unfortunately there wasn't not many early merges in the last season, >> because this somehow conflicts with the desired code quality and the >> rule not to merge unfinished PRs or things that introduce a architecture >> changes of an experimental nature. > > Maybe we should not be accepting projects that require such large > architectural changes then. > >> However, I am pretty satisfied with the outcome of last year, we have >> the new library layout on the way to master and we have a new keyboard >> mapping with a solid design, that is waiting for the last polish. >> The same is true for the LV2 branch from an earlier year > > I am glad the library redesign is almost mergeable. I look forward to > using it. However, seeing pull requests like the LV2 support and loop > recorder PRs that have not had any activity in 2+ years and are > accumulating merge conflicts does not make me very optimistic. > >> >> GSoC allows us to start big changes, that are not doable (or not done) >> in small PRs. For example the library layout was a pending project since >> 2012 and the pile of work was so high and probably to fuzzy that no one >> was willing to spend his spare time on it. Similar is true for the >> keyboard mapping branch or the LV2 branch. > > I am not sure we should have GSoC students working on projects like > this. Perhaps we should have GSoC students work on smaller features that > do not require major architectural changes and can be broken into more > discrete, mergeable steps. >> >> The problem of relying on more community feedback, is that it is very >> slow. It does not match with the 40 h working week of the student, who >> does not want just wait. I have softened encouraged the student to ask >> for opinions on mixxx-devel, sometimes it works well, sometimes not. > > You are right. It is normal for PRs that are much smaller than typical > GSoC projects we have had in the past to take several weeks from the > time they are opened to the time they are merged. That is okay for a > project driven by volunteers, but you are right that it is too slow for > GSoC. Instead of requiring community review, if there were smaller PRs > throughout the project, they could be open to community review without > requiring it before merging as long as the mentor reviews it. > >> What can we improve? >> >> We should once more look closely to the student steps and make them >> actually merge-able. >> We may encourage the students to interact even more with the community. >> We should try to decouple each steps that the community has time to >> review the changes without blocking the students progress. > > I agree. What specifically can we do to make these changes? >> >> I do not think we should artificially reduce the GSoC slots, if we have >> N excelent projects and a N mentors with time and fun, we should apply >> for N slots. This gives the best chance to gain a long term contributor >> which is IMHO the major benefit of GSoC. >> >> >> >> 2017-01-16 22:06 GMT+01:00 RJ Ryan <rr...@mixxx.org >> <mailto:rr...@mixxx.org>>: >> >> >> >> On Mon, Jan 16, 2017 at 12:45 PM Thorsten Munsch >> <thorsten.mun...@synthor.de <mailto:thorsten.mun...@synthor.de>> wrote: >> >> Do I understand it right? The students are behind the money they >> may get >> from Google and not after the knowledge they gain solving a specific >> project? >> >> >> The summer stipend of $4500 is a pittance for someone living in an >> urban part of the US or EU, but something like an average >> year's-salary in other countries. Given the economics, it's not >> surprising there is far more interest in GSoC from countries where >> the stipend is more valuable. >> >> >> >> I never studied, but always wanted to. Meanwhile I am in a good >> position >> w/o an exam and having not enough time/mood to contribute. >> >> Really sad to read that. >> >> >> Cheers >> Thorsten >> >> Am 16.01.2017 um 21:17 schrieb Ferran Pujol Camins: >> > >> > 2017-01-16 21:04 GMT+01:00 Be <b...@gmx.com >> <mailto:b...@gmx.com> <mailto:b...@gmx.com <mailto:b...@gmx.com>>>: >> > >> > That is an interesting point that it doesn't matter much if a >> > student is in it for the money if the community gets something >> > positive out of it at the end. Requiring smaller PRs with >> community >> > review would help with that. >> > >> > >> > >> > Also fail a student early. It is highly encouraged by Google. >> Then in >> > future GSOCs we can warn: "Hey, last year we failed a student at >> > mid-term because he did not meet our goals. Make sure you are >> here for >> > the right reasons." >> > >> > >> > >> >> ------------------------------------------------------------------------------ >> > Check out the vibrant tech community on one of the world's most >> > engaging tech sites, SlashDot.org! http://sdm.link/slashdot >> > >> > >> > >> > _______________________________________________ >> > Get Mixxx, the #1 Free MP3 DJ Mixing software Today >> > http://mixxx.org >> > >> > >> > Mixxx-devel mailing list >> > Mixxx-devel@lists.sourceforge.net >> <mailto:Mixxx-devel@lists.sourceforge.net> >> > https://lists.sourceforge.net/lists/listinfo/mixxx-devel >> <https://lists.sourceforge.net/lists/listinfo/mixxx-devel> >> > >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, SlashDot.org! http://sdm.link/slashdot >> _______________________________________________ >> Get Mixxx, the #1 Free MP3 DJ Mixing software Today >> http://mixxx.org >> >> >> Mixxx-devel mailing list >> Mixxx-devel@lists.sourceforge.net >> <mailto:Mixxx-devel@lists.sourceforge.net> >> https://lists.sourceforge.net/lists/listinfo/mixxx-devel >> <https://lists.sourceforge.net/lists/listinfo/mixxx-devel> >> >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, SlashDot.org! http://sdm.link/slashdot >> _______________________________________________ >> Get Mixxx, the #1 Free MP3 DJ Mixing software Today >> http://mixxx.org >> >> >> Mixxx-devel mailing list >> Mixxx-devel@lists.sourceforge.net >> <mailto:Mixxx-devel@lists.sourceforge.net> >> https://lists.sourceforge.net/lists/listinfo/mixxx-devel >> <https://lists.sourceforge.net/lists/listinfo/mixxx-devel> >> >> >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, SlashDot.org! http://sdm.link/slashdot >> >> >> >> _______________________________________________ >> Get Mixxx, the #1 Free MP3 DJ Mixing software Today >> http://mixxx.org >> >> >> Mixxx-devel mailing list >> Mixxx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/mixxx-devel >> > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > Get Mixxx, the #1 Free MP3 DJ Mixing software Today > http://mixxx.org > > > Mixxx-devel mailing list > Mixxx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mixxx-devel > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Get Mixxx, the #1 Free MP3 DJ Mixing software Today http://mixxx.org Mixxx-devel mailing list Mixxx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mixxx-devel
