Hi All,
Well, I've done it again. I've made major revisions to the MultiSite
functional spec. You'll find the latest here:
http://bricolage.cc/docs/design/MultiSite/FunctionalSpec.html
I've completely changed my approach to managing stories and media in
sites. They now can be associated with only one site, but now users can
create new "alias stories" (or "alias media") that simply point to an
asset to which they have READ permission. I think that this was
originally Joao Pedro's idea, and on reflection, I thought it might be
the best way to eliminate the permissions problems.
Anyway, please read it when you have a chance. I'm going to start work
on the technical spec tomorrow, but need to know from everyone:
* What's wrong with this proposal.
* What do you like?
* What don't you like?
* What's your response to the remaining question about related
assets?
* What am I missing?
This last question is most important, as I'm sure that I must be
forgetting things what with the size of the revision I'm proposing.
Thanks!
David
--
David Wheeler AIM: dwTheory
david@kineticode.com ICQ: 15726394
Yahoo!: dew7e
Jabber: Theory@jabber.org
Kineticode. Setting knowledge in motion.[sm]
-------------------------------------------------------
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
_______________________________________________
Bricolage-General mailing list
Bricolage-General@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bricolage-general
Well, I've done it again. I've made major revisions to the MultiSite
functional spec. You'll find the latest here:
http://bricolage.cc/docs/design/MultiSite/FunctionalSpec.html
I've completely changed my approach to managing stories and media in
sites. They now can be associated with only one site, but now users can
create new "alias stories" (or "alias media") that simply point to an
asset to which they have READ permission. I think that this was
originally Joao Pedro's idea, and on reflection, I thought it might be
the best way to eliminate the permissions problems.
Anyway, please read it when you have a chance. I'm going to start work
on the technical spec tomorrow, but need to know from everyone:
* What's wrong with this proposal.
* What do you like?
* What don't you like?
* What's your response to the remaining question about related
assets?
* What am I missing?
This last question is most important, as I'm sure that I must be
forgetting things what with the size of the revision I'm proposing.
Thanks!
David
--
David Wheeler AIM: dwTheory
david@kineticode.com ICQ: 15726394
Yahoo!: dew7e
Jabber: Theory@jabber.org
Kineticode. Setting knowledge in motion.[sm]
-------------------------------------------------------
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
_______________________________________________
Bricolage-General mailing list
Bricolage-General@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bricolage-general