Real Time Editing: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
(Created Page + Added Basic Sections/Info)
 
(Added some more links under the "Internal Links" section)
 
(4 intermediate revisions by the same user not shown)
Line 2: Line 2:
*Editing something in "real time", often with others doing so as well
*Editing something in "real time", often with others doing so as well
*More complex than saves etc (similar to batch vs continous flow reactors), but ultimantly "better" / "more "pro" "
*More complex than saves etc (similar to batch vs continous flow reactors), but ultimantly "better" / "more "pro" "
*Prevents most if not all "stepping on toes" :
**edits don't conflict as the computer + software knows this
**You can communicate to clear up uncertainty, thus no confusion/assumptions
*Due to this there is IN THEORY more productive "burning" of the metaphorical "fuel" that is [[Total Available Development Hourse]]
*OSE is About to Get to This Level of Software + [[Best Practices]] policy / workflow, so if developing/intrested '''STAY IN THE LOOP'''
*OSE is About to Get to This Level of Software + [[Best Practices]] policy / workflow, so if developing/intrested '''STAY IN THE LOOP'''


=Internal Links=
=Internal Links=
*
*[[RTE CAD]]
*[[RTE Animation]]
*[[Dev Team Meetings]]
*[[Inter-OSE Communications]]
*[[OSE's Social Media]]
*[[OSE Developer's Social Media]]
*[[OSE Active Users]] / [[OSE Developers]]
*[[True Fans]]
*[[PR]]
*[[Customer Service]]
* -should i make this into a construction set or something lol


=External Links=
=External Links=
*
*
[[Category:Start Here]] [[Category:Best Practices]] [[Category:Business Managment / Group Work Philosophy (is there one for this already?) ]

Latest revision as of 16:20, 30 May 2020

Basics

  • Editing something in "real time", often with others doing so as well
  • More complex than saves etc (similar to batch vs continous flow reactors), but ultimantly "better" / "more "pro" "
  • Prevents most if not all "stepping on toes" :
    • edits don't conflict as the computer + software knows this
    • You can communicate to clear up uncertainty, thus no confusion/assumptions
  • Due to this there is IN THEORY more productive "burning" of the metaphorical "fuel" that is Total Available Development Hourse
  • OSE is About to Get to This Level of Software + Best Practices policy / workflow, so if developing/intrested STAY IN THE LOOP

Internal Links

External Links

  • [[Category:Business Managment / Group Work Philosophy (is there one for this already?) ]