Re: [papyrus-rt-dev] How to? Design notes for Papyrus-RT feature develop

[Ernesto Posse <eposse@xxxxxxxxxxxxx>]

That page location sounds good to me, although "UML-RT-Implementation" sounds a bit too general. What does it cover? The Profile? A façade API? Tooling? Code generation? Runtime? 

Perhaps we should move the codegen docs also under Papyrus-RT/Developer/Design/0.9.

And what do we do with notes that reflect design shared between different versions? Do we put them under Papyrus-RT/Developer/Design/all? or something like that?

--

Ernesto

 

On Wed, Nov 16, 2016 at 10:36 PM Christian Damus <give.a.damus@xxxxxxxxx> wrote:

Hi, Team,

I’ve got a draft of a design note for the UML-RT implementation in UML (subject of recent discussion around demos) ready in MediaWiki format, just looking for a home on the Papyrus-RT wiki.

However, that home doesn’t seem to exist, yet.  Or, at least, I can’t see how to navigate to code-level design information from the main Papyrus-RT page.  How would we like to organize the design notes that we would like to share?  The Papyrus project uses “incoming work” pages per release to collect these notes, but I don’t like that terminology.  I was thinking maybe something like

Papyrus-RT/Developer/Design/0.9/UML-RT-Implementation

for my particular page.  So, a developer corner with a place for design notes, by release, with my feature targeting 0.9.  Re-targeting a feature just means renaming the page so that it ends up with the appropriate new breadcrumb.

Thoughts?  I welcome alternative propositions; my suggestion may be too fussy.

Thanks,

Christian

_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev