E: The about field was meant to be a quick blurb that would, for example, show and be indexed in search results. I agree a paragraph might be a bit much for this purpose. What do you think about 256 or 128 characters?

G: the only concern here was complexity of UIs and fragmentation of content. When there's less choices, UI is simpler and there's less potential for fragmenting. 639-1 has 184 codes and 639-3 has 7,863. Do we need the distinction immediately? IMO since 639-3 is a superset of 639-1, it will be easy to extend later.

H: Agree that it's useful to have some reasonable cost to create a community. If they were free, UIs would have to contend with tens of thousands of random entries. However, even if the fee were 20 STEEM we will end up with thousands. We'll need some way to roughly, objectively, measure the interestingness and relevance of a community. We could also add some feature where you burn STEEM with the community's name in the memo, and this would raise its default rank on the communities overview page, for example. But for ease of implementation, I recommend we leave it as-is, especially since namespace is not an issue.