Search results

[[Category:Documentation]] [[Category:User documentation]]

[[Category:Documentation]] [[Category:User documentation]]

* Adoption of IFRS as the standard for Adempiere (with documentation of local variations) * Review of IFRS and it's implementation and documentation in Adempiere

# Present documentation to System Auditor == Technical Scope ==

!style="background:#efefef;" width="80"|<small>Technical Data</small> <p>Product mapping (for details see documentation):

!style="background:#efefef;" width="80"|<small>Technical Data</small> ||Used for internal documentation

!style="background:#efefef;" width="80"|<small>Technical Data</small> ||Used for internal documentation

!style="background:#efefef;" width="80"|<small>Technical Data</small> <p>Product mapping (for details see documentation):

!style="background:#efefef;" width="80"|<small>Technical Data</small> ||Used for internal documentation

!style="background:#efefef;" width="80"|<small>Technical Data</small> ||Used for internal documentation

!style="background:#efefef;" width="80"|<small>Technical Data</small> ...roduct table column explanations (for details see [[ManPageW_ImportProduct|documentation]]):

!style="background:#efefef;" width="80"|<small>Technical Data</small> ||Used for internal documentation

=TECHNICAL FUNCTIONALITY= **documentation

==Documentation== <li>The level of documentation should be in proportion to the degree the proposed change will impact on th

...further enhancements to be comitted to trunk after we have translated the documentation and when community accepts them ==Documentation==

*[[ADempiere technical specifications]] *[[Technical FAQ about ADempiere ]]

== Technical documentation and howto ==

=Technical documentation and howto =

...pes, Appliances, user documentation, administrator documentation developer documentation, training programmes. ...and technical infrastructure development, tool development and management, documentation updating

[[Category:Developer documentation]] Before proceeding, please refer to the [http://git-scm.com/doc Git SCM Documentation].

[[Category:Technical documentation]]

* Take features + results into Technical and Functional Teams * Focus on automatic testing -> Integrate Build-Process -> Create documentation

...> <span class="irc-black">&lt;Michael_Judd&gt; So far, we have very little documentation of the kernel</span><br /> ...<span class="irc-black">&lt;Michael_Judd&gt; So we need to have a lot more documentation - to ensure that we understand the accounting kernel and what it is trying

...ngtree for their contributions as well as all the members of the ADempiere Technical and Functional teams. Of special note, thanks to Victor Perez of e-Evolutio * Updates to the wiki and documentation

.../technical team to review, discuss and vote for functional specifications, technical discussions and architectural movements. == Contributing sponsorship for approved functional specifications or technical/architectural improvements ==

'''''croo_''''' unless it's a technical issue <br> ...in''''' carlos, for "ease people to contribute", we are a bit short on the documentation part.<br>

#* Norbert will ask the technical team for maintainer of central id server o Documentation:

==OBSOLETE DOCUMENT - PRESERVED FOR DOCUMENTATION PURPOSES== == Technical Discussion ==

...users, system integrators, students, technology enthusiasts, industry and technical experts. In order to improve the decision making process we felt it was im ** created or maintained some documentation

Today we have an entity for controlling technical aspects of the project which is PMC. # On technical matters, the PMC can make a final decision.

...ain goal of Compilo is to join forces to develop and publish a developer's documentation for Compiere ERP + CRM. ** Compilo Developer Guide to give a technical map for developers to learn from

[[Category:Developer documentation]] ...ine the minimum and maximum RAM allocation for the Java VM. Check the Java documentation for more information.}}

[[Category:Technical documentation]]

...inted manual done by Mario Calderon committed to the SourceForge Downloads/Documentation section - [[User:Red1|Red1]] 22:03, 26 October 2008 (EDT) You will need to Checkout Documentation and Posterita projects.

...View|Developers Guide|The [http://sourceforge.net/projects/adempiere/files/Documentation/All%20Documents/DeveloperGuide.pdf/download Developers Guide] explains in v This information [[Manual|here]] is a good technical help, i.e. if you want to know which window is used to maintain a table, yo

...h="60%">&nbsp;</th><td align="right" width="20%">&nbsp;[[DocBook - Writing Documentation|Next]]</td></tr></table><hr></div> ==<span id="N1006E">Documentation Headaches</span>==

...to give "real world" examples that could really benefit the readers of the documentation. [[User:Joseph.brower|Joseph.brower]] 22:08, 18 January 2008 (EST) *We think that the ideal audience for this manual is non-technical managers of organizations and companies. - [[User:Npsglobal|Npsglobal]]

[[Category:User documentation]] [[Category:Documentation]]

Two technical approaches are feasible: = Technical documentation =

*technical discussions ...hop led by [[User:Kthiemann|Karsten Thiemann]] (Germany) to create missing documentation. We will discuss and create wiki pages like [[NewWindow|New Window]] here.

=== Technical Breaktrough === **Technical

[[Category:User documentation]] [[Category:Documentation]]

[[Category:User documentation]] [[Category:Documentation]]

=== Technical === {{FAQ|question=Where can I find documentation to help me understand Adempiere's code?|answer=See [http://downloads.source

==Documentation== ==Technical Specifications==

=== Technical Requirements === ...maybe a module to manage approval amounts - bringing here the comment for documentation purposes for future improvements:

...gs are prefered but we will switch to IRC if we have to many participants (technical problems) #*The teams will define the details like documentation templates, how acceptance criteria and testcases should be documented etc.

#* Which elements do we use? (scenarios, documentation, tests)''' #*The Technical Team can stick to Jira.

#*Technical team reviews #'''Technical team reviews'''

[22.02.2012 17:36:25] Perez Juarez, Victor: 2.-create the wiki page documentation for the contribution [22.02.2012 17:36:55] Perez Juarez, Victor: 3.- request the peer review to technical team and define a deadline