I think its possible to add a video link.
On Dec 31, 12:18 pm, harrisb <[email protected]> wrote:
> Good question about the screen casts - I don't know the answer. I
> just grabbed the WikkaWiki software as a free wiki platform for
> hosting the project. I don't really know the full capabilities of
> this software. If you discover how to do this, that would make a
> great addition to the DocumentationDiscussion page. If nothing else,
> the screen casts could be stored elsewhere, and then linked to via raw
> html from a project page. Ideally, though, we would want the screen
> casts posted to the site so that pages don't fail due to broken
> external links.
>
> Can't wait to see your notes!
>
> On Dec 31, 1:55 am, "Kevin Baker" <[email protected]> wrote:
>
> > This is great! I've been collecting a bunch of notes on our configuration.
> > I'll pull them together in a format that will work for the documentation
> > project.
>
> > I've also been thinking of doing a couple screen casts. Is this something I
> > could post to this site too?
>
> > On Tue, Dec 30, 2008 at 9:10 PM, Groovetap Gmail <[email protected]>wrote:
>
> > > Excellent! This will help out a lot!
> > > On Dec 30, 2008, at 11:57 PM, harrisb wrote:
>
> > > > SCALR supplies a critical part of a modern application infrastructure
> > > > - kudos to the design team for such a great and improving product!
>
> > > > A ambitious project like SCALR needs an equally ambitious
> > > > documentation effort. Frankly, I'd rather the current design team
> > > > keep working on adding features - the rest of us can help with the
> > > > documentation. To that end, I am announcing a new documentation wiki,
> > > > the SCALR Documentation Project, hosted at scalr-wiki.org. At this
> > > > point, it's beginnings are more than humble, but I wanted to open it
> > > > up for your contributions as soon as I could. Currently, the pages
> > > > are fully editable by registered users.
>
> > > > The plan is to document the public releases as completely as possible.
>
> > > > I have shamelessly "borrowed" the SCALR logo and the Google scalr/
> > > > wiki/
> > > > Installation page - Alex, please feel free to let me know I've
> > > > overstepped my bounds in using the logo. I've also thrown some other
> > > > text out there, just for starters.
>
> > > > In these very early days, you can add value very quickly in one of two
> > > > ways:
> > > > 1) Edit the HomePage, expanding/modifying the outline of the
> > > > documentation the project needs. Just supply bullet points - others
> > > > will fill them in. Treat nothing you find there as sacred - I just
> > > > put some suggested topics on the page as a starter.
> > > > 2) Take one experience you've had with SCALR and document it. Don't
> > > > worry too much about form. Just describe the steps you took to get
> > > > some particular task done. Give it a title, and create a link to it
> > > > from the HomePage under some appropriate bullet point. As the list
> > > > grows, others will clean up the form, move/group topics into a more
> > > > logical framework, etc.
>
> > > > The users of this list have shown a remarkable depth of knowledge and
> > > > experience. I believe that SCALR can become as important to the
> > > > internet community as Apache. With your help, we can create
> > > > documentation to match.
>
> > > > With many thanks.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"scalr-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/scalr-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
