documenting how to get source code in ubuntu-doc

[Kyle Nitzsche]

Kyle Nitzsche wrote:
> Matthew East wrote:
>   
>> On Tue, Feb 23, 2010 at 4:19 PM, Kyle Nitzsche
>> <kyle.nitzsche at canonical.com> wrote:
>>   
>>     
>>> Kyle Nitzsche wrote:
>>>     
>>>       
>>>> Matthew East wrote:
>>>>
>>>>       
>>>>         
>>>>> Hi,
>>>>>
>>>>> On Thu, Jan 7, 2010 at 7:36 PM, Kyle Nitzsche
>>>>> <kyle.nitzsche at canonical.com> wrote:
>>>>>
>>>>>         
>>>>>           
>>>>>> Matthew East wrote:
>>>>>>
>>>>>>           
>>>>>>             
>>>>>>> On Wed, Dec 16, 2009 at 8:29 PM, Kyle Nitzsche
>>>>>>> <kyle.nitzsche at canonical.com> wrote:
>>>>>>>
>>>>>>>             
>>>>>>>               
>>>>>>>> I am putting together a modification of ubuntu-docs that will explain
>>>>>>>> a
>>>>>>>> bit
>>>>>>>> more about how to get source code.  While not applicable to some/most
>>>>>>>> users,
>>>>>>>> it is probably important to include it as an aspect of Ubuntu's
>>>>>>>> commitment
>>>>>>>> to open source. (At any rate, we in the OEM group would very much like
>>>>>>>> to
>>>>>>>> add it.)
>>>>>>>>
>>>>>>>>
>>>>>>>>               
>>>>>>>>                 
>>>>>>> Sorry for the slow response and thanks for reminding me about the
>>>>>>> thread. I don't have a strong view on this but my instinctive reaction
>>>>>>> is that this information should probably be on the Ubuntu website,
>>>>>>> with a link to it inserted in the About Ubuntu document, rather than
>>>>>>> the material being included in the ubuntu-docs package.
>>>>>>>
>>>>>>> How do you feel about that? Do you have strong reasons to include the
>>>>>>> information on-disk?
>>>>>>>
>>>>>>>
>>>>>>>             
>>>>>>>               
>>>>>> The open-source, community-developed nature of ubuntu is supported and
>>>>>> even
>>>>>> proved by providing simple instructions within ubuntu for getting source
>>>>>> for
>>>>>> particular packages and for the whole image.
>>>>>>
>>>>>> Whereas pointing users to an external website is a level of indirection
>>>>>> that
>>>>>> seems inappropriate (to me) for such a core aspect of the project and
>>>>>> its
>>>>>> culture.
>>>>>>
>>>>>> So why not, as long as it is 1) brief and 2) unobtrusive?
>>>>>>
>>>>>>           
>>>>>>             
>>>>> Sorry for the delay in responding and thanks for reminding me about this
>>>>> thread.
>>>>>
>>>>> I don't really agree with you. I think the website is the perfect
>>>>> place for this type of information.
>>>>>         
>>>>>           
>>>> Is the website localized?
>>>>       
>>>>         
>>> Hello Matthew. Can you please address the question ^^^?
>>>     
>>>       
>> The website isn't localised on site, but instead we encourage local
>> teams to create their own Ubuntu websites in their own language.
>>
>> I don't think whether the material is localised is particularly
>> relevant, myself, because if it were, then that would be a reason not
>> to put information there about our philosophy, licensing and all the
>> other things that are on the website. I'd rather look at the nature of
>> the material, as I did in my previous post.
>>
>>   
>>     
> Matthew:
>
> We (canonical oem) are providing localized images to people all around 
> the world. We would like to be sure they have in their language 
> instructions on how to get source code. It can be very brief. Please say 
> definitively whether you will allow this or not.
>   
And I'll still respect you in the morning even if you say "No". ;)
> Thank you,
> Kyle
>
>