Ok, but realize that the sourceforge pages (i.e. “user” documentation) were created directly from the .html files in the /docs directory of the misterhouse source code. Those .html files were created from .pod files in the same directory.
My recommendation is to:
1) correct the .pod files
2) run pod2html
3) check in the changes to Github hollie/misterhouse
4) sftp the .html files to the sourceforge server hosting the web pages
Do you agree, disagree, or have modifications for this process?
BTW the windows install instructions that new users find are not on the wiki, they are on the sourceforge.net pages: http://misterhouse.sourceforge.net/install.html. Those are the pages I intend to correct and I plan to use the process above unless we come up with a better one.
From: Vargster [mailto:email@example.com]
Sent: Tuesday, February 26, 2013 10:31 AM
Cc: The main list for the MisterHouse home automation program
Subject: Re: [mh] Permissions to update sourceforge HTML pages
Right... let me clear this up...
I will be (slowly) updating the info on the misterhouse.sourceforge.net website.
The main drivers for this are 1) the sourceforge page is the no.1 hit on Google, and 2) it looks *REALLY* bad that the last modified date is in 2008...
There is a lot of very interesting info on there describing the depth/breadth of Misterhouse, which I think is good background reading for a newbie.
That said, there are also a lot of dead links which I will try to update or remove.
Where it starts getting into specifics of things like installation, I'm going to just remove them, and point to the wiki.
If Michael can update the Windows Installation Instructions on the wiki that would be great.
I've recently installed Mh on a fresh Ubuntu server box, so I've got notes for that which I'll use to bring the Ubuntu Installation Instructions up to date.
I was also thinking of pressing the need to use the GIT repo, but also have a the GIT .zip download listed on the site? Thoughts?
On Mon, Feb 25, 2013 at 11:13 PM, Michael Stovenour <firstname.lastname@example.org> wrote:
On Feb 25, 2013 1:05 PM Lieven wrote,
> Hi Michael,
> Op 25-feb.-2013, om 02:26 heeft "Michael Stovenour" <email@example.com> het volgende
> > You mentioned support for pod in the wiki; do you know how that works? If the pod is
> > in the source code how do we get it into the wiki?
> You checkout the misterhouse wiki git clone (hollie/misterhouse.wiki.git) and you add
> POD files and you commit them. They are then nicely rendered in the wiki. I just added a
> dummy example file here:
That is a great example. I think this can be easily integrated in the existing "user"
documentation in /docs with just a simple maintenance script and someone with write access
to both repositories (code and wiki). All the maintenance script would need to do is
create the .html files for the "local user" documentation and copy the .pod files across
(not sure where the source .pod files should live yet). For the "developer" documentation
I'm not sure yet how we could pull the pod from the source code over to the wiki just yet;
I assume there are probably existing tools for that. This just leaves the wikispaces
wiki. It sounds like we have some volunteers to copy the stuff over; which meets my
criteria for a rubber stamp.
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365