guidelines
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
guidelines [2019/02/08 23:31] – puffinux | guidelines [2019/02/15 18:34] – puffinux | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Guidelines ====== | ====== Guidelines ====== | ||
- | Here are listed our guidelines for the use of our services. | + | Here are listed our guidelines for our services. |
---- | ---- | ||
Line 9: | Line 9: | ||
==== Creating Proposals ==== | ==== Creating Proposals ==== | ||
- | Cos 🦉 changed their profile picture. | + | Note that there are also hard rules regarding the creation of proposals. It is recommended to read the [[governance_policy|Governance Policy]] under **Voting**. |
- | kawaiipunk | + | === Proposal Structure === |
- | @CoroCocoron | + | |
- | My objection | + | When creating new proposals, it is recommended |
- | The first is that no matter how you cut it, form is content and enforcing | + | - **Background**: |
+ | - **Proposal**: | ||
+ | - **Budget or labour cost**: A paragraph outlining | ||
+ | - **Rationale**: | ||
+ | - **Timeframe**: | ||
- | Enforcing templates and forms to be filled out will only make more work for those involved. You can simply say that it won't, but coming from someone who has been doing that work, I know that it will. If I have to get other instance admins to fill out a form and then fill out a second form myself to initiate the proposal to let them use out Loomio, I know I won't. Asking us to fill out two forms for one proposal is absurdly excessive. | + | A summary paragraph might also be useful, to briefly sum up what members are voting |
- | Would you feel ok with that proposal if it was an entirely optional thing? | + | ---- |
+ | ===== Wiki Contribution Guidelines ===== | ||
- | I.e. just a style guide | + | These are guidelines for how to contribute to the wiki in a way that is most efficient and effective. I get that we're all anarchists and whatnot, but it makes sense to have a method to adding content |
- | I would be fine with that | + | |
- | I'm a bit confused what to do because I proposed | + | |
- | Chupacabra | + | |
- | I also like both, I think they can work together | + | |
- | kawaiipunk | + | Please see the [[wiki: |
- | I'm happy for the template to just be a page on the wiki tbh | + | |
- | It could even be more of a inspo thing to help people write proposals | + | ==== Creating Pages ==== |
- | Puffinux | + | |
- | I've added it to our Governance Policy. I'm hoping it's that right place to put it, as it contains details of the 7-day duration policy already. I've worded it as though it was not a hard enforced rule, though this can be changed. | + | |
- | Cocoron | + | If a page doesn' |
- | It should not be in the GP | + | |
- | The governance policy is a set of rules that require a high threshold to change | + | ==== Content in pages ==== |
- | Amendments | + | |
- | Any changes to this Governance Document must be subject | + | Pages start with their name in a header--- |
- | Any changes | + | When changing topics in pages (using H2 level headers and changing focus / subject), place a horizontal rule above the header, except above the first H2 header in the page, when there is no text between |
- | I've removed it | + | |
- | Cocoron | + | |
- | I've also closed | + | |
- | 10 days* | + | Try to keep things tidy, and, if you see a method |
- | Puffinux | + | |
- | Okay. Apologies. It sounds like the 7 day rule shouldn' | + | |
- | I think it passed with four times as many votes anyway? | + | ---- |
- | Cocoron | + | |
- | The 7 day rule was there from the creation of the GP and was agreed upon when the GP was ratified | + | |
- | It needed 15 | + | ===== Tech Action Squad ===== |
- | Puffinux | + | |
- | That makes sense. | + | |
- | Should I create another page with other documents in it then, for things like the proposal structure guidance? | + | ==== Defederation policy ==== |
- | Cocoron | + | |
- | You have a bit of a carter blanche since the proposal didn't specifying, so it's up to you on how to do it, although I can help you if you like | + | |
- | Specify anything* | + | We can't go scouring the fediverse and defederating from all instances that are problematic, |
- | Puffinux | + | |
- | Puffinux | + | *This is intended as the first step in defining our federation policy, not the last. It does not aim to be exhaustive, but to cover the basics. Further proposals on Loomio may amend and extend |
- | Should I create another page with other documents | + | |
- | And if so, perhaps | + | |
+ | This is what we expect from an instance we federate with: | ||
- | Cocoron | + | - The instance must have a code of conduct. |
- | You have a bit of a carter blanche since the proposal didn't specifying, so it' | + | - The instance' |
- | You already do a lot so I'm happy to take this on, unless you actively wish to take part. Otherwise, I can speak to people if I need guidance but otherwise handle things. | + | - The instance's code of conduct, and its stated and actual purpose, should be compatible with that of our instance, that is: |
+ | * Hate speech and harassment are disallowed. | ||
+ | * Content illegal in France shall not be allowed. | ||
+ | * Fascist and Nazi advocacy is disallowed. | ||
guidelines.txt · Last modified: 2022/03/06 18:54 by squeakypancakes