The future of how to debug pages

["Jóhann B. Guðmundsson"]

On 09/25/2012 10:59 PM, Adam Williamson wrote:
> On Tue, 2012-09-25 at 22:37 +0000, "Jóhann B. Guðmundsson" wrote:
>> On 09/25/2012 07:54 PM, Adam Williamson wrote:
>>
>>> I don't see that that follows logically at *all*. The two just seem like
>>> totally different things. Instructions for debugging a given component
>>> are going to be the same whether you're running Fedora, Ubuntu, SUSE or
>>> whatever: debugging systemd is debugging systemd. There may be cases
>>> where there are local variations, in which case it makes sense to have a
>>> local wiki page, but in cases where there aren't, it seems perfectly
>>> sensible if the instructions are provided upstream. I don't see any way
>>> in which that means bugs reports should always be upstream.
>> Upstream is also upstream for all those distribution and your point
>> being?
>>
>> Mine point is pretty obvious if we are going to be redirect reporters
>> upstream in the first place why not then just go the whole way.
> I may be being dim, but it just isn't obvious to me at all. The internet
> is a set of linked documents. If there is a document somewhere on the
> internet which already specifies the correct steps to take to debug
> something, it seems to make sense just to point to that instead of
> rewriting the whole thing just because we want to have an orderly set of
> documents in our wiki.
>
>> In fact a lot of maintainers withing the distribution would like us to
>> do just that and while we dont have our own bugzilla instance where
>> reporters wont be hitting "Your not authorized to view this bug" or
>> other RHEL related bugzilla policies that nobody knows who are ( or
>> those that do cant disclose it ).
>>
>> To me we should either try to keep everything locally within the QA
>> community and withing the distribution by building our own knowledge
>> base or we should simply do it the other way around.
> I still don't think you've actually demonstrated any causal linkage
> between these two things. Debugging instructions are debugging
> instructions. Bug reports are bug reports. They are separate things. I
> don't see how sourcing one of those things upstream inevitably means we
> should send the other one of them upstream. There is no obvious causal
> linkage there.

If we send reporters upstream to read documents we can just as well send 
them by the same method to upstream bugzilla's to file reports.

That's the linkage

JBG