[
http://mifosforge.jira.com/browse/MIFOS-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarah Farrier updated MIFOS-5551:
---------------------------------
Description:
I don't think this has been explicitly mentioned under any existing sub-tasks
for the Documentation Sprint - I wanted to add something regarding the slightly
inconsistent set-ups advised in the various developer guides, depending on
which O/S guide you're using.
Three examples, off the top of my head:
1) Different install locations for Jetty ($HOME/jetty7/... vs.
c:/jetty7/7.3.1.v20110307/...)
2) Different example git clone locations (/head vs. /mifostrunk)
3) Some really helpful tips missing on some developer set-up guides, whilst
they are prominent on other O/S guides (Ubuntu guide missing the tip for 'mvn
clean install -Dmaven.test.skip=true' to skip tests, whilst this is nicely
highlighted in Andrew's Windows screencasts)
It may seem trivial at first, but I definitely think that consistency in demo
set-ups would help new developers out more (hopefully for fairly low effort).
Often, if example setups are as similar as possible between O/Ss, then new
developers can extract existing knowledge and quickly see how to adapt it to
their current difficulty. A great example in my own case was knowing how to set
up environmental variables in Windows but not knowing how to do the same task
in Ubuntu before I started with Mifos.
was:
I don't think this has been explicitly mentioned under any existing sub-tasks
for the Documentation Sprint - I wanted to add something regarding the slightly
inconsistent set-ups advised in the various developer guides, depending on
which O/S guide you're using.
Three examples, off the top of my head:
1) Different install locations for Jetty ($HOME/jetty7/... vs.
c:/jetty7/7.3.1.v20110307/...)
2) Different example git clone locations (/head vs. /mifostrunk)
3) Helpful tips included or missing on developer set-up guides (the Ubuntu
guide missing the tip for 'mvn clean install -Dmaven.test.skip=true' to skip
tests, whilst this is nicely highlighted in Andrew's Windows screencasts).
It may seem trivial at first, but I definitely think that consistency in demo
set-ups would help new developers out more (hopefully for fairly low effort).
Often, if example setups are as similar as possible between O/Ss, then new
developers can extract existing knowledge and quickly see how to adapt it to
their current difficulty. A great example in my own case was knowing how to set
up environmental variables in Windows but not knowing how to do the same task
in Ubuntu before I started with Mifos.
> Harmonise Example Installs on the Various O/S Developer Setup Guides
> --------------------------------------------------------------------
>
> Key: MIFOS-5551
> URL: http://mifosforge.jira.com/browse/MIFOS-5551
> Project: mifos
> Issue Type: Dev Task
> Components: Documentation
> Reporter: Sarah Farrier
>
> I don't think this has been explicitly mentioned under any existing sub-tasks
> for the Documentation Sprint - I wanted to add something regarding the
> slightly inconsistent set-ups advised in the various developer guides,
> depending on which O/S guide you're using.
> Three examples, off the top of my head:
> 1) Different install locations for Jetty ($HOME/jetty7/... vs.
> c:/jetty7/7.3.1.v20110307/...)
> 2) Different example git clone locations (/head vs. /mifostrunk)
> 3) Some really helpful tips missing on some developer set-up guides, whilst
> they are prominent on other O/S guides (Ubuntu guide missing the tip for 'mvn
> clean install -Dmaven.test.skip=true' to skip tests, whilst this is nicely
> highlighted in Andrew's Windows screencasts)
> It may seem trivial at first, but I definitely think that consistency in demo
> set-ups would help new developers out more (hopefully for fairly low effort).
> Often, if example setups are as similar as possible between O/Ss, then new
> developers can extract existing knowledge and quickly see how to adapt it to
> their current difficulty. A great example in my own case was knowing how to
> set up environmental variables in Windows but not knowing how to do the same
> task in Ubuntu before I started with Mifos.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://mifosforge.jira.com/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
