thedemocracyfoundation / epitome-django Goto Github PK

Currently there is no prompt to display the message that a user has voted once they do in a poll. That causes those confirmation messages to appear in the page of django admin. There needs to be a field to display those messages in the poll voting page.

https://github.com/TheDemocracyFoundation/epitome/blob/f34b58954c0ca6b9b138e3b6b64f7c4720da7720/Agora/forms.py#L6

The total votes need to be tallied correctly and also the graphs need to show correct information

Make possible for users to create polls.

https://github.com/TheDemocracyFoundation/epitome/blob/baaf073f8a0bf89451044f18c03594db7134e75d/templates/error.html#L7

https://github.com/TheDemocracyFoundation/epitome/blob/baaf073f8a0bf89451044f18c03594db7134e75d/Propylaea/tests.py#L3

The template in Eisegesis required partials which will be phased out in favor of external build tools. The location and structure of scripts and styles have also been modified. The poll view needs to be recreated.

Thing have got a bit newspeak with @MavropaliasG.

Apparently epitome doesn't have representatives.

@MavropaliasG seems quite happy to have people appointed to make decisions on behalf of the group where time is a pressing factor. These de facto representatives wouldn't actually be representatives because .

Another situation where having representatives is useful is in ratifying formal agreements. Where a group has a formal representative, that representative can sign a document on behalf of the group. Without such a representative, every member of the group must sign the document for the group to have signed the document. Why send one man to sign a piece of paper when you can send hundreds?

In recourse to court or arbitration, whether as plaintiff or defendant, the group will have to appoint a representative to make an argument or cede without argument.

Representatives aren't inexorably a problem. Failure to hold representatives to account for their actions is a problem.

Does not work with django 2 when trying to make migrations in a new install.

@MavropaliasG says epitome should be both for those who want to use a collective decision making tool as a method to make legally enforceable decisions the collective has agreed to abide by in advance, and legally unenforceable decisions the collective has not agreed to abide by.

At the beginning of a football game, the referee tosses a coin to decide which team kicks off the first half. The decision made by coin is legally enforceable, and both teams agree in advance to abide by the decision.

If the teams did not agree to abide by the decision of the coin flip, what would be the point in flipping the coin?

Exactly the same as the point in using epitome to make a decision that nobody has agreed in advance to abide by.

What is the point in expending effort to make a decision if you have no intention for anyone to abide by that decision?

For what can a group use epitome (a decision-making tool), if they have exercised the option not to use it to make decisions?

I think it's better if we have this field empty.

https://github.com/TheDemocracyFoundation/epitome/blob/baaf073f8a0bf89451044f18c03594db7134e75d/Epitome/settings.py#L25

What is related to the code if the design specification is not related to the code?

I could work with your design spec, because I learned about what agreements are by studying accountancy. If it were my primary project I could get to alpha in 5-8 weeks, mostly by dumping the unproven deliberation system and using something simpler.

The reason I'd dump the democracy.foundation deliberation system are

• I don't understand it, and
• I don't want to understand it, because
• I've not been shown a single example of a good decision made using it, and
• a design specification for decision making system that lacks a definition of a decision is literally a bad decision.

If you had a credible design specification, I'd be interested in turning into code.

If you were interested in salvaging the credible and possible from your design specification, I'd be interested in helping.

As it is, I have tried to explain what a decision actually is, and how this previously unconsidered truth impacts your design.

If you don't care to listen, I don't rate the chances of finding someone with the wit to listen on your forum, since you've collectively managed to produce a white paper on communal decision making without managing to consider or include what communal decisions actually are.

Nobody writes good code from a bad design spec. When you have a good design spec, writing good code is easy. The unit tests are directly translated from the design spec, and when they all pass, the job is done. When you've a bad design spec, you've no clear idea what to code, or when you might be finished.

You've got yet another polling system working because (like everyone else) you've a clear definition of what a polling system should do, and therefore the coders can identify task completion.

You say you see the project going on for 5-8 years. How do you see the software improving in that time? How will this occur if you've no intention to improve the design specification?

Not my circus, not my monkeys. I am sure you'll now fantasise that, despite mentioning nothing but the coding process, I'm somehow not discussing code.

Creating the front-end using the current format is difficult to manage as the result is not directly viewable. Currently, the front-end is created using handlebars, sass and gulp, producing static html pages which must be converted into django templates manually.
Task: Create a gulp task to produce django templates directly.

When creating a new poll and I press "Now" as the time of creation, the time is in GMT not local.

The user shouldn't have to set the code (what is this used for??) and also the time and date for creation and end of a poll.

• The code should be automatically set incrementally (make sure we don't have a problem with races)
• Creation time and date should be automatically set as soon as the user presses submit
• Ending time and date should be automatically set to 7 days from the creation date by default

Evaluating chart.js as a visualization tool for user information.

Users should be able to add styling to the text of their posts. Quill.js will be added to the template to provide additional text editing options.

https://github.com/TheDemocracyFoundation/epitome/blob/2fdc0cc35761e7ec52cfbf28432b856790d9bf76/Propylaea/templates/Propylaea/login.html#L32

ttest

Should those comments be removed now that we have transitioned to python 3 ?

https://github.com/TheDemocracyFoundation/epitome/blob/development/Agora/models.py

The cards in the polls template must be modified to remove voting from the card itself. Additionally, the card does not resize properly on smaller screens and may overflow.

Preferably with this https://kyusuf.com/post/password-visibility-toggles

i want a help to make an online voting system

Create custom test templates for poll creation.
The user has to supply the issues and create the poll.

I saw the CONTRACTS.md file.

I suggest that you keep this system, except use a platform specifically designed for this purpose. The best one I know of is BountySource: https://www.bountysource.com/

Here is their FAQ: https://github.com/bountysource/core/wiki/Frequently-Asked-Questions

Material Design Icons amount to nearly 25%-35% of the overall size of the final styles file.
Removing all unused icons would improve loading speed for the styles.

After a logged in user with administrative rights logs out, he can re-enter without logging in just by entering the home url. This does not apply to regular users.

https://github.com/TheDemocracyFoundation/epitome/blob/f34b58954c0ca6b9b138e3b6b64f7c4720da7720/Agora/tests.py#L1

Can we use this ? https://stackoverflow.com/questions/12468915/django-post-time-to-database

http://legacy.earlham.edu/~peters/writing/nomic.htm

Nomic forms a unit test for your proposal. If the project can run a game of Nomic, it can run an arbitrary legislature.

git forms a storage mechanism for a body of legislature arbitrarily modified by amendments.

tinder manages to crowdsource a large number of proposals into a large number of reviews.

After creating the first poll and voting on it, if an additional poll is created and an attempt to vote on it is made, the following error is produced:

IntegrityError at /eisegesis/2/vote/
UNIQUE constraint failed: Eisegesis_voter.user_id

Should the polls be in a separate app as @pbout mentioned?

What do you propose as a name ?

Are "Demoscopisis", or "Demoscopy"/"Demoscope", good names?

Use the symbol as favicon

epitome/static/img/logo.svg

https://github.com/TheDemocracyFoundation/epitome/blob/baaf073f8a0bf89451044f18c03594db7134e75d/Propylaea/admin.py#L1

https://github.com/TheDemocracyFoundation/epitome/blob/763ced1b44114bb8ceaf94091f773980af6949fa/Eisegesis/templates/Eisegesis/index.html#L70

I have noticed that in commit c6b1c36 the database names changed, for example P_TITLE -> PL_TITLE.

Could there be problems in the views of the static files that call them, for example in Eisegesis/templates/Eisegesis/index.html as mentioned in this issue ?

Why do you think there is a discussion to be had?

Either:

• you want to give your users all the options, including the option to have representatives,

or

• you wish to forbid users from having representatives and don't wish to give them all the options.

You need to dump one of these design specs since they're fundamentally incompatible.

Discussion, in any quantity, won't change this.

Could this help? https://stackoverflow.com/questions/13190758/django-case-insensitive-matching-of-username-from-auth-user

The current workaround is to run the commands below manually:
'python manage.py makemigrations Eisegesis'
'python manage.py makemigrations Agora'
'python manage.py makemigrations Propylaea'