I'll work today to firm this up and see how far I get in executing
against the structure with the feedback incorporated.
I said this in an internal meeting yesterday, and I want to re-assert in
the public domain: I am floored and impressed by what pyogp has become
in the past few weeks, and am grateful for the effort, efficiency and
productivity of those who are contributing. Tao, Locklainn, Infinity,
WOW... thank you so much. I am very much looking forward to watching
this effort mature.
Christian Scholz wrote:
Tess Chu wrote:
What about having a 1-2 line introduction, then 2 links to the
library and the test harness (the details about them can be
explained on these pages). I am also not sure we need the whole
history there and explain AWG and OGP there. These can IMHO be
linked to separate pages in case people do not know about them
(chance is though that they know about it and this is why they came
to those wiki pages).
Yes, an introduction section would be nice, and should include links
to AWG and OGP. There's not really much real "history" but rather
just "background" information that should belong in the
introduction. Of course we'd also have those links under the "Links"
section.
And why not put roadmap and status on separate pages?
I would like to have the status *with* the roadmap. Those who are
interested in status should also know its relation to the roadmap.
It's hard to communicate "where are we" if we don't know "where we
want to be." If anything, you're going to have many statuses in the
roadmap because many people are working on many things. Note that
this is going to be a high-level status and we should really be
linking to Jira for task level status since that will change *all the
time*.
Well, I meant more that Roadmap and Status should not be directly on
the homepage but linked from their. I am ok with both being on one
page and jira links make sense of course, too. It would even be nice
if one could group JIRA tasks into milestones and list these
automatically on that page.
Maybe even separately for the subprojects lib and test harness.
Reason for this: These are more changing pages while I would think
of the start page more or less as a table of contents where you can
quickly find those links which you are looking for.
I like this. We probably need a separate "Library Roadmap" and "Test
Roadmap". Furthermore, I would like the folks doing library changes
to be more careful about merging their changes in because the other
folks doing test changes will want the libraries in a stable state so
that they're not constantly going back to the library folks for bug
fixes. One way to do this is to have a separate branch for each
milestone that merges up periodically.
+1
In the end I would put short overview of ways to participate:
- where to find the repository
- list of meetings
- mailing list, IRC channel
I think this should go in the beginning. Most people looking at this
page wants to get started right away. I think Enus already has it
that way.
Sure, my idea was though to have the homepage that small that it fits
on one screen. Then you would see all information. So I think of it
more being a table of contents with many sublinks in a structured way
so that it's easy to comprehend in one glance.
-- Christian
_______________________________________________
Click here to unsubscribe or manage your list subscription:
https://lists.secondlife.com/cgi-bin/mailman/listinfo/pyogp
