Re: [MusicBrainz Bug Tracker] #1281: Porting of static document: download.html

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [MusicBrainz Bug Tracker] #1281: Porting of static document: download.html

DonRedman
On Wed, 14 Jun 2006 21:52:48 +0200, Keschte wrote on Ticket #1281: Porting  
of static document: download.html

>  i hope i don't force a time-table upon you guys, but the menu structure
>  for the next server release relies fully on the now ported documents.
>  therefore, they should be made into wikidocs pages asap.

Hmm, that's a difficult one. WikiDocs is a project that evolves in steps  
of mothns or half-years. But then you cannot wait that long with the  
release.

Here are some thoughts on the matter:

Which pages do you need to be wikidocselt exactly? And most of all *how  
many* I suppose 20 new pages is ok, 50 might not. By new I mean pages  
which were not in the wiki a month ago.

I have worked a bit on some products pages (added the virtual structure  
and modified them a bit). I think those are already better than the static  
html pages. So, from the content point of view, these pages are ready.  
Although the virtual structure should be added to the most important  
product pages.

 From the wiki point of view, these pages are mostly only interwingled  
within themselves. I do not know how much of a problem this is. If the  
pages are good (which most of them are) and prominently shown on the main  
page (which they will), then WikiZens will start to refer to them. Maybe  
one or two of them will die, but then they could be de-wikidocselt.

Then there are pages like the style guidelines which already are alive.  
Here we might need someone checking for typos and wrong information and  
then wikidocsel them all.

And finally, the links will work and the pages will show, whether the  
pages are wikidocselt or not. The presentational pages must be wikidocselt  
for the next server release, but it will not hurt if informational pages  
have the "This is directly taken from our wiki" bit.

Wolfsong, what do you think about this?

   DonRedman



--
Words that are written in CamelCase refer to WikiPages:
Visit http://wiki.musicbrainz.org/ the best MusicBrainz documentation  
around! :-)

_______________________________________________
Musicbrainz-experts mailing list
[hidden email]
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-experts
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Re: [MusicBrainz Bug Tracker] #1281: Porting of static document: download.html

keschte
> Which pages do you need to be wikidocselt exactly? And most of all *how
> many* I suppose 20 new pages is ok, 50 might not. By new I mean pages
> which were not in the wiki a month ago.

The pages:

* Products
* PicardTagger
* PicardTaggerDownload
* ClassicTaggerDownload
* libmusicbrainz
* libmusicbrainzDownload
* libtunepimp
* libtunepimpDownload
* PythonMusicBrainz2
* PythonMusicBrainz2Download
* Server
* ServerDownload
* Database
* DatabaseDownload
* TRMGen
* CdLookupTool


* Development
* DevelopmentOverview
* Subversion
* Projects
* PicardDevelopment
* ServerDevelopment
* DatabaseDevelopment

the leaves of the documentation structure need not be made into
wikidocs pages currently, maybe never. additionally, the existing
physical structure of the old documentation can be used as a hint
which content should be made official:

http://bugs.musicbrainz.org/browser/mb_server/trunk/htdocs/development
http://bugs.musicbrainz.org/browser/mb_server/trunk/htdocs/products

--keschte

_______________________________________________
Musicbrainz-experts mailing list
[hidden email]
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-experts
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Re: [MusicBrainz Bug Tracker] #1281: Porting of static document: download.html

Cristov Russell
In reply to this post by DonRedman
Sounds good. However, I am apprehensive of the Style pages only because they are _very_ interwingled and some of the content linking to it may be dead, misleading or plan confusing primarliy since many of these pages have a lot of old and ongoing discussion items. Wikidocs pages should not include discussions IMO but it's fine if they link to them. The distinction being that newbies should be able to easily discern what is "currently official" and what things are still being discussed; potentially joining the dialog.

We certainly can't avoid doing this on every page but I would like to make sure we have this on wikidocselt Style pages and major items they touch (i.e. AdvancedRelationships).

Also, keep in mind that while the CategoryTerminology pages are very interwingled and they don't need to be wikidocselt; they should be reviewed as we're checking other pages.

A few more comments. Nothing should follow CategoryX at the end of the page; doing so interferes with adding catagories and indexes. Adding a link to the original page on a wikidocs candidate is unnecessary. Part of adding the page to wikidocs implies that the content has been updated and the static page is out of date.

Cristov (wolfsong)

--- [hidden email] wrote:

From: "Don Redman" <[hidden email]>
To: "MusicBrainz Experts" <[hidden email]>
Subject: [mb-experts] Re: [MusicBrainz Bug Tracker] #1281: Porting of static document: download.html
Date: Fri, 16 Jun 2006 00:14:08 +0200

On Wed, 14 Jun 2006 21:52:48 +0200, Keschte wrote on Ticket #1281: Porting  
of static document: download.html

>  i hope i don't force a time-table upon you guys, but the menu structure
>  for the next server release relies fully on the now ported documents.
>  therefore, they should be made into wikidocs pages asap.

Hmm, that's a difficult one. WikiDocs is a project that evolves in steps  
of mothns or half-years. But then you cannot wait that long with the  
release.

Here are some thoughts on the matter:

Which pages do you need to be wikidocselt exactly? And most of all *how  
many* I suppose 20 new pages is ok, 50 might not. By new I mean pages  
which were not in the wiki a month ago.

I have worked a bit on some products pages (added the virtual structure  
and modified them a bit). I think those are already better than the static  
html pages. So, from the content point of view, these pages are ready.  
Although the virtual structure should be added to the most important  
product pages.

 From the wiki point of view, these pages are mostly only interwingled  
within themselves. I do not know how much of a problem this is. If the  
pages are good (which most of them are) and prominently shown on the main  
page (which they will), then WikiZens will start to refer to them. Maybe  
one or two of them will die, but then they could be de-wikidocselt.

Then there are pages like the style guidelines which already are alive.  
Here we might need someone checking for typos and wrong information and  
then wikidocsel them all.

And finally, the links will work and the pages will show, whether the  
pages are wikidocselt or not. The presentational pages must be wikidocselt  
for the next server release, but it will not hurt if informational pages  
have the "This is directly taken from our wiki" bit.

Wolfsong, what do you think about this?

   DonRedman



--
Words that are written in CamelCase refer to WikiPages:
Visit http://wiki.musicbrainz.org/ the best MusicBrainz documentation  
around! :-)

_______________________________________________
Musicbrainz-experts mailing list
[hidden email]
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-experts


_______________________________________________
Musicbrainz-experts mailing list
[hidden email]
http://lists.musicbrainz.org/mailman/listinfo/musicbrainz-experts
Loading...