[personal profile] alexbayleaf

Originally published at Growstuff Blog. You can comment here or there.

Since this project started we’ve used mailing lists such as our Discuss list to talk about Growstuff-the-project. Discuss is a place for developers, testers, and volunteer contributors of all stripes to chat to each other and keep the project moving forward.

Unfortunately, mailing lists have a lot of problems. For instance, you have to commit to being a member — going through a multi-step signup process, which isn’t the most user-friendly — to be part of it at all. For another, members sometimes find the flow of email too much and switch to “digest” mode, but then have trouble replying to particular threads they’re interested in. And the archives are far from friendly, and it’s hard to link to a thread and ask someone to contribute.

On the plus side, everyone has email, it works on everything from desktops to phones, and there are lots of tools to manage your email (for instance by filing messages into folders automatically) if you know how to use them. Email lists have a long history in the open source community, and many open source developers prefer them.

Growstuff wants to encourage everyone to get involved in how the site is built. We want you all to be able to suggest features, report bugs, improve our data, use our API, help with testing, and have a say in how our community is run. Some of us feel like mailing lists are hindering this goal.

Around the time we started, there was a brand new project also starting, called Discourse which aimed to replace antiquated web forums and mailing lists with something more modern and engaging. One of our community suggested we use it for discussing Growstuff, or even integrate Discourse into Growstuff itself, but the time wasn’t right for that, as it was too new and untried. Now Discourse has released Discourse 1.0 and it’s stable and full-featured enough for us to revisit it.

I’ve set up a trial Discourse installation called Growstuff Talk. You’re invited to come and look and see if this is a platform you’d like to use to participate in the Growstuff volunteer community.

screenshot of Growstuff Talk, showing threads categorised as Development, Testing, and Meta

A screenshot of our nascent Discourse discussions.

Here are some of the features of Growstuff Talk:

  • New and active conversations are right on the front page.
  • Anyone can browse and read topics, and see what the Growstuff community is doing to build our site, our data, and our community.
  • To participate, you can sign in with Twitter, Facebook, or various other options.
  • It’s easy to link to individual conversations, or to categories of conversations, and share them with others who might be interested.
  • If you like email, you can choose to get email notifications of new topics, and reply to topics by email as well — you can do almost anything from within your existing email client.
  • For our coders, there’s syntax highlighting, which makes pasted source code easier to read.
  • It works great on your phone or or other mobile device, too.

Read more about Discourse’s features on the Discourse website.

We have a one week free trial, so we’ll be playing with Discourse until next Thursday, September 4th. After that we’ll decide whether to continue to pay for a hosted Discourse server (it’s not much, but it’s silly to pay for it if we don’t like it.)

Please join us over the next week, try out Growstuff Talk, and let us know what you think!

[personal profile] alexbayleaf
My main task for this iteration (other than coaching) is to come up with a community guidelines document. I've just posted the draft to the mailing list so I'll just copy what I wrote there:

So, I drafted a proposed set of community guidelines. These aren't a full TOS or anything like that, but a short statement of values and then setting out a few specific interpersonal behaviours that aren't welcome, and what we'll do if they happen. I figure that when we get around to having a TOS, we include it by reference, i.e. the TOS will say something like "you agree to abide by our community guidelines".

I've put the document in github and I figure the TOS and any other policies (eg. privacy policy, copyright policy) can go there too. The good thing about having this stuff in github is that if/when we change any of our policies the change history will be visible, and people can see what's different from one version to the next.

Anyway! My draft is at https://github.com/Growstuff/policy/blob/master/community-guidelines.md and I would appreciate people reading it and letting me know what you think. I'm interested in anything ranging from high level conceptual feedback to smaller wording tweaks.

Profile

The Growstuff Project

June 2016

S M T W T F S
   1234
567891011
12131415161718
192021 22232425
2627282930  

Syndicate

RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Jun. 24th, 2017 08:38 pm
Powered by Dreamwidth Studios