[os-engineering] FW: [os-infrastructure] Re: Model discussionboiled dry(er)

[Chris Clark]

On 6/26/2008 4:59 PM, Joe Abbate wrote:
> ....
> This is not what I had in mind when I mentioned "use case stories".  
> What I think is needed is perhaps a loose combination of "use case" 
> (http://en.wikipedia.org/wiki/Use_case) and "user story"  
> (http://en.wikipedia.org/wiki/User_story).  The point is to show by 
> example what happens when someone has to interact with the proposed 
> models.
>
> ....Snip excellent use case stories......
> Someone needs to carry this story forward as to what happens in each 
> of the three models to the changes, as they make their way from 
> ingres!main into http://code.ingres.com/ingres/main/src and some 
> tentative Community release codeline.  The stories ought to have 
> explicit Piccolo or svn paths so that they're not ambiguous.

I agree that we need use cases like your example (and they should 
ultimately be either on or linked from 
http://community.ingres.com/wiki/Community_Model ). Explicit piccolo 
paths (and svn) paths should be used.

I'm not sure we are ready for them yet though, more below.


> ...snip....
> Again, the story has to be carried forward to what happens on the 
> Ingres Corp side, in particular, how it gets subsequently integrated 
> into ingres2006r3 or other codelines.  It would also be instructive to 
> have an example that implements something that doesn't end up being 
> shared, e.g., on the community side, some new DMF access method that 
> we don't feel comfortable with integrating into commercial codelines 
> but the community is eager to have out there for experimentation; on 
> the Ingres Corp side, the reintroduction of B1 security, assuming we 
> still want to keep that closed source.

This is why I'm not sure we are ready for the full/detail use case 
examples quite yet. I don't think we know what we want to allow yet. See 
my post on 
http://lists.ingres.com/pipermail/opensource-engineering/2008-June/000141.html 
(if I've read the diagram correctly) it appears that end users can not 
get (scs) access to "Enterprise Release Branches".


Coming back to the hypothetical DMF change, this should be done in a 
public experimental branch, the issue would be if this experiment is 
considered a success and if we cross/merge/integrate it into "Main 
Community Mirror". This would then end up in main and future Enterprise 
Branches, I don't think it would be integrated into existing commercial 
branches (they are supposed to be feature complete, support should only 
be integrating bug fixes into existing commercial branches).

But this is my interpretation, of what I think "Proposal 1" is, I could 
have the wrong end of the stick (which is why I've not updated the 
proposal in the wiki with my bare bones use case). I suspect early/mid 
next week http://community.ingres.com/wiki/Community_Model will have 
much more information and we can start to look at use case.

So I think we need detailed use cases, just not for the next few days. I 
think we need less detailed use cases with some reasonable example 
codeline names rather than branch1, branch2. E.g. ingres2006r2 (legacy) 
and ingres10 (or some future codeline).

Chris