Quantcast

Documentation updates for GitHub and Trac

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

Documentation updates for GitHub and Trac

Eli Adam
Hi all,

I've been drafting changes to outdated details like
http://docs.geomoose.org/master/howto/testing_reporting_ticketing.html
and http://docs.geomoose.org/master/howto/run_trunk.html

Instead of updating this information here, should I remove it from
version specific documentation, geomoose/geomoose-docs, and add it to
project documentation, geomoose/geomoose-website?  This does not
appear to be version specific documentation.

Something nice about our project website is that it is a very clean
overview and not overwhelmed with highly specific details.

Another option is to just remove it and not have it any longer.

Update in place in version specific documentation, move to project
documentation, or remove entirely?  Thoughts?  Suggestions?

Thanks, Eli
_______________________________________________
geomoose-psc mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/geomoose-psc
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Documentation updates for GitHub and Trac

James Klassen-2

How to run/build is version specific, although that page is horribly outdated.  There are github wiki pages that are more up to date and there is also the OSGeo Live installer and Duck's Docker image.

Testing/Reporting seems project related and IMHO should be moved.

On Apr 11, 2016 12:10 PM, "Eli Adam" <[hidden email]> wrote:
Hi all,

I've been drafting changes to outdated details like
http://docs.geomoose.org/master/howto/testing_reporting_ticketing.html
and http://docs.geomoose.org/master/howto/run_trunk.html

Instead of updating this information here, should I remove it from
version specific documentation, geomoose/geomoose-docs, and add it to
project documentation, geomoose/geomoose-website?  This does not
appear to be version specific documentation.

Something nice about our project website is that it is a very clean
overview and not overwhelmed with highly specific details.

Another option is to just remove it and not have it any longer.

Update in place in version specific documentation, move to project
documentation, or remove entirely?  Thoughts?  Suggestions?

Thanks, Eli
_______________________________________________
geomoose-psc mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/geomoose-psc

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

Re: Documentation updates for GitHub and Trac

Brian Fischer

Eli,

I’m just getting into testing on my Windows 7 machine now and starting from the beginning.  I don’t have time to get into learning how to update the docs directly in the code repository but here are some notes if you plan to update any of this documentation.  This was all the further I got on testing this week but in general seems solid to release.  The only thing that might be considered a bug would be the popups but maybe that is supposed to be how it works.  Great work all!

 

Installation and Documentation Comments:

-          I noticed the Getting Started Guide and How to Run Trunk both reference older versions of MS4W and GeoMoose.  It should be updated to say MS4W 3.1.3.  Should we drop the documentation for older versions and IIS?  Not sure anyone has the resources to go back and re-write those instructions.

-          When you go to the MS4W website it is unclear if a user should download the .zip file or run the installer.  Should we be making a recommendation?  I choose the installer to give it a try.  After I ran the installer it installed the Apache web service but would not start the service.  After figuring out there was other software running on port 80 I was able to switch it to another port.  You also have to go back and run as an Administrator.  For this reason I think we should instruct users not to use the installer and use the zip.  Make sure they don’t have something running on port 80 and run as administrator.

-          I also noticed the MS4W website has a GeoMoose package for 2.8.1 that you can optionally install.  This might get confusing if Jeff doesn’t update this each time a new GeoMoose version gets released.  Documentation should probably make a recommendation on whether to install the package.

-          I then downloaded GeoMoose for MS4W nightly.  I noticed the package still says 2.8 on the MS4W launch web page.  Should this be changed to say nightly so it is clear which version you are running?

From here I had a working Demo from nightly.

 

Demo Comments (mostly subjective):

-          Would there be an easy way to update the footer to say nightly instead of the previous version release?

-          When I did a Search Parcels and used the value of Chambers.  It returned 3 records but the parcel features did not highlight on the map.  Is this supposed to work that way?

-          When I used the Print to PDF tool the layout generated but the Map was blank.  Seems to work fine on the website demo URL though.  Must be a local configuration issue.

-          The circle icon with the checkbox in it is confusing to me as a user.  It says Activate but when you click on it there is not action.  Seems like this could be removed unless it is meant to change the state of the tools.

-          Popups seem to stick every time you move your mouse instead of going away.  See screen capture.  It happens for me on both IE11 and Chrome.  The popup seems to stick even without a click if you pause your mouse movement for a couple of seconds. If you move right away then it disappears.

 

Brian Fischer

Vice President, GIS Project Manager

Houston Engineering, Inc.

O 763.493.4522 | D 763.493.6664 | M 763.229.2734

 

From: geomoose-psc [mailto:[hidden email]] On Behalf Of James Klassen
Sent: Monday, April 11, 2016 1:07 PM
To: Eli Adam <[hidden email]>
Cc: [hidden email]
Subject: Re: [geomoose-psc] Documentation updates for GitHub and Trac

 

How to run/build is version specific, although that page is horribly outdated.  There are github wiki pages that are more up to date and there is also the OSGeo Live installer and Duck's Docker image.

Testing/Reporting seems project related and IMHO should be moved.

On Apr 11, 2016 12:10 PM, "Eli Adam" <[hidden email]> wrote:

Hi all,

I've been drafting changes to outdated details like
http://docs.geomoose.org/master/howto/testing_reporting_ticketing.html
and http://docs.geomoose.org/master/howto/run_trunk.html

Instead of updating this information here, should I remove it from
version specific documentation, geomoose/geomoose-docs, and add it to
project documentation, geomoose/geomoose-website?  This does not
appear to be version specific documentation.

Something nice about our project website is that it is a very clean
overview and not overwhelmed with highly specific details.

Another option is to just remove it and not have it any longer.

Update in place in version specific documentation, move to project
documentation, or remove entirely?  Thoughts?  Suggestions?

Thanks, Eli
_______________________________________________
geomoose-psc mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/geomoose-psc


_______________________________________________
geomoose-psc mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/geomoose-psc
Loading...