On Mon, Mar 08, 2010 at 05:07:00PM -0500, [email protected] wrote: > Viktor Griph <[email protected]> writes: > > > 2010/3/7 Thomas Adam <[email protected]>: > >> The poignant things any prospective mentors are going to need to know > >> [3] are covered in question 2 -- which I am happy to fill out, but note > >> that this won't and cannot get off the ground without a *backup* mentor. > >> That's critical, and one of the failings from last year's proposal. > >> > >> So -- anyone from fvwm-workers wanting to step up to that? ?To be clear > >> again -- I am offering to be main point of contact, etc., etc., the role > >> of a backup mentor is to supplement my role should I die, or have no > >> Internet access, etc. ?Hopefully something unlikely! > >> > > > > I could probably serve as a backup mentor, but I will be on vacation > > sometime this summer (I'm not sure of the timeline currently), at > > which point I would not be able to step in as a mentor, should the > > needs appear. > > I'm not ready to volunteer, but the normal way fvwm developers seek > help is through the Fvwm-workers mailing list. > > That doesn't need to change in this case.
Perhaps, but on larger projects (as I have seen working on Git, for instance) some applicants prefer the one-to-one approach when developing a given feature for GSOC. I see no reason to discourage that approach if it's more appropriate for *them* -- and my role is to always keep fvwm-workers@ fully informed, etc., as I am sure most people might have assumed anyway. -- Thomas Adam -- "It was the cruelest game I've ever played and it's played inside my head." -- "Hush The Warmth", Gorky's Zygotic Mynci.
