[gobolinux-users] Upstream Contact Project

[Isaac Dupree]

MJ Ray wrote:
> Isaac Dupree <isaacdupree at charter.net> wrote:
>> [...] We have a philosophy to try to get patches 
>> integrated upstream, but no coordination or concerted effort on this 
>> that I can see.  I think perhaps, we should make a wiki page for this, 
>> at least an "Upstream contact log" where anyone who contacts upstream 
>> regarding a certain patch in Gobo is encouraged to make a note [...]
> 
> How will we encourage it?
> 
> I think this looks like making it more effort to contact upstream,
> which would *dis*courage trying to get patches integrated there.

Hmm, good point.  Well, I notice recipe patches that I want to contact 
upstream about, but not right then, I just want to record it somewhere 
so I can get to it later.  This way those notes can be shared.

Maybe OTOH it's good if upstream is bothered by more of us, 
uncoordinated, if they need convincing that it's a problem.  But this 
might help a systematic contacting, if anyone felt like doing so 
(avoiding bothering the same developers a lot before they've had a 
chance to make another release)...

Maybe we just need a Gobo script to search for patches in recipes. Maybe 
just a way to annotate patches as to whether they should or shouldn't 
try to get into upstream (then there are things like Linux-kernel 
squashfs and unionfs that are not up to us to get into Linux, but up to 
their developers. (Is there a reason they can't be put in separate 
/Programs as modules - is it that they're not designed that way?)).  The 
comments in a patch can't be updated without issuing a new revision of 
the recipe...

Isaac