~~NOCACHE~~ In the course of the recent meetings and discussions the statutes document has already progressed a lot, so that it becomes necessary to facilitate a proper text work environment. The feature set is placed between piratepad and lqfb and was created to serve specific conditions in the context of the statutes development. It may be helpful in other scenarios, too. Piratepad with inline commenting, simple line numbers and coloring of the author does not facilitate textual collaboration in large crowds. It is very well suited for smaller work groups and small texts, but large number of comments or discussions quickly destroy readability and usability of the original document for a new participant. LQFB is a voting environment with little to no textual work support. Although suggestions can be made, the initiator may remain the bottelneck and guard of the document. So the attempt is to provide an environment, in which the * readibility of the original document remains undisturbed even with hundreds of comments * ticket system can assign ownership of parts to different people * unique labels are given to semantic units instead of line numbers * labels do not alter during the course of the document's lifetime * colours are assigne according to text status, and not authors (e.g. new, edited, approved, legal requirement, or other custom states) * parts of the documents can be hidden by the reader (collapse / expand) * list of tickets (which correspond to inline comments in piratepad and suggestions in lqfb) could be displayed for each semantic unit separately. * it is not required to create different documents for unique labelling (although in this particular we chose to do so) Everything could be in one location Todos: * There is a lot of space within the collapsibles, which I would like to reduce. * I want to place the labels on the left of the text. * I need to figure out how to display something meaningful in the report, not only the tickets table * Right now there is less text visible than in piratepad, which is a big no-go, but that can be handled Currently we distinguish the following: * Approved statements are displayed in black on white * new statements are displayed in red on light grey * modified parts are green on light grey * deleted statements have a strike through in grey on white * non negotiables (e.g. for legal reasons) are dark blue on white * statemens borrowed from other organizations are black on light grey {{issuetracker>project=Preamble|display=form}} {{issuetracker>project=Preamble|product=P10,P20,P30,P40,P50,P60,P70,P80,P90,P100,P110,P120,P130,P140,P150|status=all|severity=all|display=issues|view=10}} \\ {{issuetracker>project=General provisions|product=GP10|display=form}} {{issuetracker>project=General provisions|product=GP10,GP20,GP30,GP40,GP50,GP60,GP70|status=all|severity=all|display=issues|view=10}} \\ {{issuetracker>project=Objectives|product=O10|display=form}} {{issuetracker>project=Objectives|product=O10|status=all|severity=all|display=issues|view=10}} \\ {{issuetracker>project=Membership|product=Me10|display=form}} {{issuetracker>project=Membership|product=Me10|status=all|severity=all|display=issues|view=10}} \\ {{issuetracker>project=Organs|product=Cr10|display=form}} {{issuetracker>project=Organs|product=Or10|status=all|severity=all|display=issues|view=10}} \\ {{issuetracker>project=Decision making|product=De10|display=form}} {{issuetracker>project=Decision making|product=all|status=all|severity=all|display=issues|view=10}} \\ {{issuetracker>project=Finances|product=F10|display=form}} {{issuetracker>project=Finances|product=all|status=all|severity=all|display=issues|view=10}} \\ {{issuetracker>project=Modifications|product=Mo10|display=form}} {{issuetracker>project=Modifications|product=all|status=all|severity=all|display=issues|view=10}} \\ {{issuetracker>project=Duration|product=Du10|display=form}} {{issuetracker>project=Duration|product=all|status=all|severity=all|display=issues|view=10}}