Greetings!

On Fri, 5 Jan 2001 [EMAIL PROTECTED] wrote:
> IMO: Bad information detracts from good information. We need to delete
> everything that's dated. We've got Marius' rewrite of Azman's installation
> from source. Why is Azman's original article still on the site? Probably
> because there hasn't been time to move the document into an archive, if such 
> an archive is even needed, I'm doubtful.

I'd like to have an archive here. Maybe so that outdated content
is not included in the regular site hierarchies, and doesn't show
up on searches, but can still be found by content producers, etc.

> The graphic tour needs to be redone with Asgard
> graphics, perhaps even rethink it's content. It's almost a decent little
> tutorial.

It could work as one, as people tend to learn more easily
when they have screenshots showing the action being
performed, and not just textual explanation.

> A list isn't a good solution, nobody is going to read a list and the
> people that are doing the work aren't going to recieve their due credit.
> View the following page and click on the colored things, replace the build
> information with reports on snippets, features, who is writing them, state
> of development, anticipated completion dates, etc. 
> http://community.roxen.com/developers/autobuild/pike71.html

I'm not sure about this. However, the interface you
described could fit well the nightltbuilds system.

But yes, the Who's Who should link closely to our
bugtracking and task management system. As they all
will be done natively in Midgard, this shouldn't be
too difficult to handle.

> I think we should consider Commentext as the solution for documentation.
> In my opinion, there are barriers which prevent participation and
> contributions; cvs, sgml, etc. Time and energy to write documentation
> are a serious problem.

Yes, CommenText is a very nice application. It would be
a good choice for managing our documentation.

However, if we are to use CommenText for our documentation
needs, we will need to integrate it with the Midgard site
so that they can share authentication information, and we
can interface with the CommenText system more easily.

At some point we need to be able to produce documentation
in other formats than just HTML, so we'll need some
conversion utilities here.

Also, I think that we will still need the annotations system.
CommenText is still a bit too difficult to use for a casual
user who happens to get an addition idea while browsing the 
documentation. How to link this with the CommenText system
is left to be decided.

Paul, what do you think, is this feasible?

> In general: the site should be thought of as a tool, not a site. In it's
> current state, we always see the same information, nothing changes but
> many things are undergoing updates within the effort. I'd suggest studying
> publishers like The New York Times, Salon, Fresh Meat, slashdot,
> Roxen, blah blah.

We need to link the whole Midgard development and community process more
closely with the site.
Things like mailing list archives and task management systems brought to
the site will help here, but we will also make producing content like
announcements and downloadable files to the site easier.
Also, I would like to add user comment options similar to the
annotations system to also other parts of the site.

> I don't imagine it's feasible to use Repligard in a qausi CVS
> strategy, allowing many people to work locally, commit updates, update
> local instance.

...but hopefully it will be the future. Before that,
we will need to work in centralized fashion.

Alexander, what is your view on using Repligard in
the quasi-CVS way mentioned above? I'm working on
some projects where that would be extremely useful.

> Speaking of instructions, how about instructions for the people that are
> going to maintain the site one or two years from now? I hope the new
> site will be friendly and flexible.

Yes, this was to be part of my previous email, but
I seem to have forgotted to add it. Documentation is
vital here.

> If enough of us are on the same page with the need to prune dated
> content and replace it with current material or simply remove it, I'll
> inventory the site and write a report.

Please do that.

> Ron

/Bergie

-- 
-- Henri Bergius -- +358 40 525 1334 -- [EMAIL PROTECTED] --
               http://www.iki.fi/Henri.Bergius


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to