[FM Discuss] FM upstream to Sugar Labs

[David Farning]

I spent a good part of today thinking about how FM and SL could
collaborate in a way that was beneficial to both of us.

I keep coming back to the upstream/downstream relationship between
software packages.  When I write a program in c, I don't rewrite the
compiler.  I use gcc.  It makes no sense spending the time required to
learn compiler theory and hack away on my own.  The gcc project has
already assembled the expertise and processes to do a better job than I
ever could.

I am thinking about using FM documentation in the same manner.  Sugar
Labs has nowhere near the time or manpower to create documentation as
effectively as FM.

I hope that I did not appear as if I had a laundry list of things I
would like FM to do for me.  Rather, I would like to:

1.  Ask your permission to use your documentation as our primary user
documentation.

2.  Request that we work together to create the 'canonical' Sugar and
Activities documentation.

3.  Express that we are not expecting you to write our manual.  Instead,
we are using your manual about our product.

In return we will:

1. Always keep the documentation open.

2.  Send patches back upstream if we find bugs or ways to improve the
manual.  (Sending patches and finding bugs is not the right terminology,
but you get the idea.) 

3.  Direct potential documentation writers to you to help build your
community.

Thanks
Dfarning