trustroots / community Goto Github PK

• Get feedback from indigenous artist Gustavo Caboco to see if we can use his artwork.
• Edit and implement photos in the Community stories
• Add photos to newsletter and look over the layout

How to handle this in a good way?

Both https://www.trustroots.org/donate/help and https://www.trustroots.org/donate/policy can be deleted as the relevant information within has been moved to the new main page.

Shopping list:

• potatoes
• tomatoes
• bananas
• rice
• pasta
• toilet paper

please edit and improve this issue description

https://www.trustroots.org/faq

• Add section: How can I help? With at least link to https://www.trustroots.org/volunteering

Need some copywriting for this :)

• Martin A did this.
• check in some time (how long?) if we can edit the logo image

Wiki? P2?

Mostly done, waiting for a couple of updates but can probably be closed soon.

continuation from Trustroots/trustroots#20 (comment)

we have:

• FB page
• FB group
• Newsletter
• Blog
• Twitter
• VKontakte
• Google+ page
• Google+ group
• Instagram

(There are other "non-tech" repos, so perhaps that term would be too all-inclusive.)

short term:

• get open support requests down to 500 (from 956)
• get overview of trustroots stuff: github, website
• find one person to help with this at least 3 times per week
• non trivial commit to code repo

mid term:

• build team(s) of volunteers
• find a way to pay at least 1 salary

use this issue description as a wiki page

pros

• good forum software
• add more

cons

• another account
• 3rd party software, won't integrate
• add more

questions

• is it possible to enforce logging in with trustroots account? is it feasible?
• can we get it for free? only 50% discount with at discourse.com
• would someone want to host and maintain it for us, for free-ish?
• use it for volunteering activity only? or for everything including tribe discussions etc?

Create a new https://www.trustroots.org/support_trustroots or something that sounds better and delete https://www.trustroots.org/donate

https://github.com/Trustroots/community/projects/9

(Do-ocracy, the meaning of life, etc.)

rooting [4:32 PM]
Re: User feedback

How are you replying to emails like that (if at all)?

Is there's a reply template (that you then customise a bit, depending on what was send)? Maybe we can also add in "volunteer opportunities" at the end. If someone writes a lot of feedback, then he might be interested in becoming a tester, in giving more feedback or would do some other volunteering.

We need an anthem, a song that all hitchhikers all over the world can play on their guitar.

Playable with only 4, 5 simple chords.

something like https://www.youtube.com/watch?v=GlDnIPOR8_0

This after agreeing on and sorting other things in the "Hijacking Repo" project, to see whether they need to be updated/restructured.
(For example, the Translation Guide would be better to have together with other reference material. Moving it over would, however, require a change of layout for the Teams and Volunteering pages.)

Hi @maikhoepfel @aschle @nikolaygit @florianwittmann @mschwarzer @maltoe!

You're stargazing https://github.com/Trustroots/trustroots and your location is Berlin (or Germany). We're having a pic nic at Krumme Lanke next Tuesday for which I want to invite you like this.

https://www.facebook.com/events/1446695995658760/1446705102324516/

Let me know if you're not on Facebook and we'll get you the info in another way.

https://www.trustroots.org/#!/profile/guaka
cc @simison

Give @UserStefan access:

• FB
• Twitter
• Blog

rooting: time this right.

Pre-launch

• Have everything well written/presented
• https://www.patreon.com/edit/about
• https://www.patreon.com/edit/tiers
• https://www.patreon.com/edit/goals
• https://www.patreon.com/edit/thanks
• feedback form (google) linked from thank you page?
• Maybe the video artists that are on the road with Dani and joined #collective would also want to create a Trustroots introduction video that could be used there.

Launch

• Post a link on all channels at the same time: blog, facebook, twitter

Post-launch

• it might pick up steam if it shows up in the "trending/new" section. There are a bunch of checklists/tutorials online for it.
• possible that we'd get new users via patreon and people stumble over it that maybe just want to support, because the project sounds good to them. If it's more of a soft launch we'd miss out on that. (edited)

mikael [11:37 PM]
@guaka let’s see if folks at #collective could do some outreach to some hosting FB groups? (edited)

there are several for slackliners, buskers, burners…

• Write the newsletter text
• Implement the newsletter text so it's ready to send
• Shorten community story 1
• Shorten community story 2
• Shorten community story 3
• Write an introduction and ending to the community stories - Martin
• Edit the community stories - Shawn + Martin
• Write the Tribes to Circles blog post
• Edit the TtC blog post
• Polish the Do-ocracy stub on the Wiki and link to it in the newsletter.
• Find and implement photos to both blog posts and newsletter
• Publish everything, party a little, and close issue

1. make guides
2. make videos
3. draft a text to send people explaining we are not a company but a volunteer based organization and therefor would appreciate there help and less their complaints - one way to help would be to just browse around GitHub and add likes to issues or help comment on issues or create issues.
4. using GitHub a place to discuss things more.
5. Add a short overview that some overviews do not have code at all - add this to the website in volunteering section.

Collective stuff we'd like, ideally without buying:

• 1 ethernet cable (length doesn't matter)
• guitar and other musical instruments
• printer and/or a some printed versions of the most recent NDA
• working bikes (we have two bikes in a bad shape, nice to fix these)
• power strips with 5+ holes
• one or more longer power cable
• plastic sheets
• dry rack for clothes

Great if you can bring some of the things that are not checked.

• Decide if we want to split this into separate issues for the project view or keep it like this.
• Going through old issues and updating/moving/deleting as suitable.
• Having a look at the old project and deciding if it is still relevant.
• Moving the ToDo-list from the pad into relevant issues.
• Setting up an issue for walkthrough documentation (how to Codi, Slack, GitHub etc.)
• Setting up an issue for more philosophical documentation (Do-ocracy, the meaning of life, etc.)
• Organising a structure (on the Wiki?) for permanent documentation.
• Having a look at the Teams and Volunteering pages to see if they need updating based on the above-mentioned changes.
• Renaming the repo as "Community" is somewhat vague? (There are other "non-tech" repos, so perhaps that term would be too all-inclusive.

We should be public about what kind of positions now in our volunteering team:

• Community manager(s)
• Developer(s)

mikael: I have a 11.4 K emails in Maitre on “waiting list” and another ~2K in earlier list in MailChimp. What should we do about those?
they’ve all expressed interest to join, many of them have probably joined.

guaka [10:30 AM]

• exclude emails that have already signed up
• send the remaining emails a message they can now sign up without invite, possibly first try a batch of 100 or so

How do we handle these?

clear up these pages

• https://ideas.trustroots.org/volunteering/

• https://www.trustroots.org/volunteering

• https://github.com/Trustroots/trustroots/wiki/Volunteering

• add a link to canonical page from everywhere

what roles do we need?

• Work in progress, v0.1 at https://docs.google.com/document/d/1mP3cwLBZrmUbyWyvVKYOahd3srQfYuL2McthXjVQnE0/edit
• Get folks to sign it
• Get more feedback
• Check https://dochub.com/

What are we doing with this?

https://github.com/Trustroots/trustroots/wiki/Code-of-Conduct

base on

• https://www.contributor-covenant.org/version/1/4/code-of-conduct
• https://www.ubuntu.com/community/code-of-conduct

gdoc: https://docs.google.com/document/d/1PaQs7kKCQnQPWOvaviqMr8_moRYDxta0P3NuHyatvH8/edit

"Contribute" seems to be the best option, as per the discussions here and here.