Community Call 5/30/21 | Unstructured

[tangjeff0]

I can't speak above a whisper today because of a sore throat, and there aren't any glaring topics topics to cover for the community call today, so I am creating this discussion for general Q&A. More of an async "Town Hall" perhaps.

Copying some questions below to get the ball rolling.

[tangjeff0]

@seekanddefine

Brainstorm: -details on the update/highlights from folks involved
-thoughts on Fluree since last call
-goals for the next update/June and possible 60/90, status on current P1s
-open positions, reminder to have folks share in their networks
-website/handbook updates

[tangjeff0]

Some of these questions should be answered by new post: #1099

-thoughts on Fluree since last call

Won't be able to make decision until we have v1 self-hosted RTC up. Still have open questions about license, implementation, and business model (for Athens).

-goals for the next update/June and possible 60/90, status on current P1s

Not planning ahead of the month.

-open positions, reminder to have folks share in their networks

• Right now just Head of Community, see June priorities. Resuming engineering recruiting at the end of June.

-website/handbook updates

• website: updating self-hosted RTC survey form - https://docs.google.com/forms/u/4/d/e/1FAIpQLSfuWgzGZ2ocB-SweDizMAINYyRZ-3KYwkaf3xIdb4pOs1I-4A/viewform
• handbook: not sure where this is right now actually. Would be helpful if you could write the current state of the Handbook and open questions @seekanddefine.

[tangjeff0]

@joelhans

I can't be there this weekend sadly, but maybe a brainstorm about onboarding would be useful: https://discord.com/channels/708122962422792194/800439780910563358/847093820395094067

Could tie in with the conversation in #website about example DBs: https://discord.com/channels/708122962422792194/836501172214431804/846465953239924826

[tangjeff0]

@sid597

In addition to what Linnea mentioned we can also discuss priorities regarding open issues, from my perspective currently, P1 issues are up for bounty but most of them are done or are getting worked on, apart from bounty issues I don't think there is some way of knowing what issue is what priority contributor has to decide that by themselves. So we can discuss a process through which issues can be divided up into the tiers mentioned in this discussion #1071 , the tiers can be a way for the contributor to get a sense of priority of an issue and its complexity.

[tangjeff0]

@sid597 still a challenge prioritizing a lot of bugs/bounties because there are so many and they aren't organized in a clear way yet. Your links to operating a large-scale GitHub will come in handy here.

Plan right now is to highlight some of the high priority issues and encourage others to help via research or code (such as with new textarea or dropdown).