Re: wiki.debian.org/doc/packagename/readme.debian ?
> > > > I'm not sure what would need to happen process wise to enable
> > > > Developers to use wiki page to collaborate their readme and
> > > > readme.debian.
> > >
> > > Making DD's life easier would unsure quick adoption. May be :
> > > - A set of scripts for the DD to retrieve and update the wiki page.
> > > (that might later be included in debhelper)
> >
> > Making a download script wouldn't be hard. Upload on the other hand
> > would have to somehow be automated triggered by some event. Update
> > script needs access to the wiki files. aka needs to be run from the
> > same server. How would I get access to wiki server if one wanted to
> > implement this?
>
> Erm, the wiki is running on a restricted machine, only a few debian
> developers have access there. And I wonder, why does it need access to
> the wiki files? Directly overwriting is a very bad idea because it's
> working around the version control used by the wiki.
The script is a python script that imports moinmoin module. It reads
the configuration just like a normal moinmoin would and updates the
page just like a moinmoin would do. I am using append_text that moin
has on their website. It needs to read the config file and import
moinmoin therefore it needs to be run on the machine that has moinmoin
files.
>
>
> > How is the package released? If new package has a new release
> > number/version number we could track the new package and know to
> > upload the readme file. If I somehow would be able to tell there is a
> > new version I can overwrite the wiki page.
By overwriting content I meant not the moinmoin file.
As far as uploading the readme file goes, how would I know there is a
new unstable package release ? I can tell the script to download the
new package and update wiki page, how do I know a new package version
is available? Any ideas on how that could be scheduled? Assuming I
would want it to run upon a new version.
>
>
>
> > Good point. In that case I would upload stable/testing with readonly
> > access and ustable would be the one people could modify, allow
> > somekind of suggestions.
>
> How would you put that into the general workflow of package
> maintainers?
I think the work flow would be:
stable/testing readme available on readonly wiki page.
unstable readme is available on wiki and can be edited by users. User
will have to notify the maintainer that there is a new useful content
on a wiki, or maintainer actually checks it.
Upon each new release the content of the 'readme page' on wiki is
updated with a new content from new version.
They are already flooded with various different ressources
> where they are expected to pull informations from, adding to that
> doesn't make the system better but worse because people definitely will
> start to care less.
They don't have to care. It would only work if they care or if user
modifies the wiki page and lets maintainer know about it.
How about now?
http://wiki.debian.org/pkg/README.DebianTemplate
How does the @PACKAGE@ works?
Lucas
Reply to: