Mailinglist Archive: opensuse-buildservice (339 mails)

< Previous Next >
[opensuse-buildservice] Proper etiquette?
  • From: "John Calcote" <john.calcote@xxxxxxxxx>
  • Date: Mon, 24 Mar 2008 09:19:13 -0600
  • Message-id: <3ee91eb90803240819y21296897n4e6191ecda73a9f1@xxxxxxxxxxxxxx>
Hi list.

I've read the online wiki docs, and they're great--as far as they go.
Unfortunately, they don't go very far. Don't get me wrong--I love the
opensuse build service! I can't believe we got along all these years
without it.

The trouble is, there's no proper use-case description. I don't mean a
formal design document. I mean a true user scenario document,
answering questions like:

"Why would I want to use this tool?"
"How do I properly use it?"
"What's the proper workflow?"
"When do I build locally?"
"What philosophy do I use to decide when to commit?"
"When do I publish?"
"Which repos do I choose?"
"Should I disable publish during testing?"
"What do I tell my package users about my use of the OBS?"
etc, etc.

Before you send me off to, or any
of it's sub-links (Tutorial, WorkFlow, etc), just know that I've
already read these documents--committed them to memory, in fact.
They're not that helpful. Oh, sure, they provide the basic "HowTo"
information. What's missing is the "Why" information.

There's still some vision in the designers' heads that hasn't made it
onto the table yet. Can we get a brain dump on some of this stuff? It
will explain to me (and others) what the original intent of the
project is--and in a way that will make it simpler to get started
using the OBS properly--the way it was originally intended to be used.
Too much of this really cool sort of stuff takes decades for people to
start using properly because "proper" use of it has to become folklore
passed down from generation to generation by the bards...

To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups