chitectural implementation and less to do with how the information is
actually presented in the UI (although please don't interpret this to mean
that I feel you should disregard my opinion on the matter). Its important to
have clear division of responsibility, loose coupling, and high functio
became stalled? What can we do to get this moving
again?
Cheers,
--
Cody A.W. Somerville
Release Engineer
Foundations Team
Custom Engineering Solutions Group
Canonical OEM Services
Phone: +1 781 850 2087
Cell: +1 613 401 5141
Fax: +1 613 687 7368
Email: cody.some
for the launchpad team. For most, this mailing list will just be a much
appreciated blackhole for notifications. For those interested in *all*
notifications, they can of course subscribe. For those who are only
interested in a subset of the notifications (ex. vcs imports), one can
instead join
is is important so that we can present the list in
> the same order it was when last changed.
>
> How do you guys feel about it? Maybe you have other ideas about how we
> can implement this?
>
What about a linked list via self-referencing foreign key?
Cheers,
--
Cody A.
Anyhow, I can see how ReST is good for somethings (like when you place high
value on the readability of the markup, ex. doctests) but I can't see it
working for a high traffic wiki. With ReST being so technical and elaborate,
you'd be going around all day fixing the f
5 matches
Mail list logo
