May I argue that we should aim at being able to use *UN*sophisticated developers (such as, well... myself) ?
There is a *lot* of "maintenance" tasks in Sage that can use (relatively) ignorant people. For example, maintaining Sage ports of well-understood packages (such as Maxima or, in my case, R) does not need extreme level of sophistication ; delegating these tasks to people able to follow some guidelines, read and interpret error messages and propose reasonably clean patches allow people who *are* sophisticated to use their time at more difficult tasks... Therefore, I think that contributing to Sage should not *require* a sophisticated understanding of the finer points of git care and feeding... -- Emmanuelk Charpentier Le mardi 15 mai 2018 15:11:09 UTC+2, Jeroen Demeyer a écrit : > > On 2018-05-15 14:35, Erik Bray wrote: > > I'm not convinced that's a real problem. This is what I meant by "yes > > its contents may change and shift rapidly, but for a sophisticated > > developer who just wants to peek in on the release process this is not > > a problem". > > I agree that it's not a problem for the "sophisticated developer" who > knows what he is doing. But the more you advertise this secret branch, > the larger chance there is of abuse by non-sophisticated developers who > have no clue. I believe that this is the point that Maarten was trying > to make. > -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
