Building content associated with the list of 'features'

[aidanbudd]

Ismail and I have updated the list of features of great OS scientific communities, to reflect the GoogleDoc we wrote at the Sep 10th 2015 GoogleHangout.

Looking through the text again, I think a useful way forward could be for different people to take on the content of different features ("Accessibility", "Communicativeness", etc.). Each of these people, could try and write "their" feature up, to include:

• a short explanation of what is meant by it
• an explanation of how this feature is of benefit to a community
• a list of practical tips for achieving this feature
• a list of challenges for establishing this feature

If you think a different focus/summary/structure would work better, please let us know, we can try and choose something together.

If we find this list OK, we may still struggle to use it in each case - but we'll have to try to find out.

Once several people (or groups of people) have had a go at several of the features, we can look at what we've come up with, compare the texts, and see if we can use these to decide on a general style/focus/tone for these texts.

[joncison]

I think this is spot-on. I'd suggest, for ease of comprehension, to bullet the edits under each feature thus:

featureName
explanation - blah blah
benefit - - blah blah
tips - blah blah
challenges - blah blah

That will make subsequent round of revision much easier.

[gedankenstuecke]

👍

[aidanbudd]

Glad you like the plan, Jon, Batien - thanks for the feedback.

Anyone up for taking on one of the topics, to try this out?