Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

November 2015 meeting #168

Open
7 of 36 tasks
waldyrious opened this issue Nov 18, 2015 · 3 comments
Open
7 of 36 tasks

November 2015 meeting #168

waldyrious opened this issue Nov 18, 2015 · 3 comments

Comments

@waldyrious
Copy link
Member

I'm starting a new issue (branching off #167) to track the decisions of this month's meeting and what needs to be done (video recording / raw meeting notes). If we agree this is a good model, we can then have one such issue for each monthly meeting. Or perhaps a wiki page would work better so we can all edit in the same place.

Here are the main topics and decisions, mostly actionable items (unchecked items have open questions to resolve or actions to take):

  • Complete domain transfer (was already in progress at the time of the meeting, so nothing needed to be done, just wait for the transfer to conclude)
  • Create canonical list of all OCI “holdings” and who handles what:
  • Continue Summits, but not use OCI funds to attend or setup until we have a larger number of supporters and we can hold them somewhere that supporters can easily attend
    • Have Summits online
    • Have OCI members attend larger events/conferences and represent the OCI there
      • Create materials for would-be official/unofficial representatives
  • To do: Create a guide for OCI supporters that want to contribute
    • Possibly through a CONTRIBUTING file
    • Be mindful that not everyone is familiar with Github
  • To do: Create separate lists of companies: those that have pledged and those that have not but reflect the OCI principles (with the latter being akin to @waldyrious's awesome-open-company)
    • Adapt/merge the awesome-open-company's guidelines for inclusion to the OCI's pledge
      • To do: Remove from website the notion that pledging is related to Gratipay contributions
      • Question: How are we to handle pledgers who stray from values or have never been in line with the values?
  • Monthly meetings schedule: On Google Hangouts on Air, on the second sunday of each month, 8pm UTC (subject to adjustments in date or time if necessary)
  • To do: triage current issues and close / resolve as appropriate. We should possibly open a tracking issue (similar to this one) to do that collaboratively.
  • To do: Consolidate teams in the github organization (remove company-reps and translator teams)
  • To do: Merge opencompany.github.io and www.opencompany.org repos
  • To do: website simplifications (details to be added below)
    • To do: Remove outdated translations until can be kept up-to-date
      • Utilize automatic translation service (Google Translate) until have custom, reliable translations?
    • Website pages:
      • Question: Keep the About and Join pages?
        • Join page is built with Jekyll and does not currently allow for companies to be submitted through it
          • Think of way to allow for company submissions
      • Delete Summit and Blog pages
    • Question: Where to present Inclusion Guidelines (hitherto called the "Pledge")?
  • "Facilitating discussion about the concept and prospect of open companies" (Comment on #166)
    • On the website: Provide a resources page listing the posts, videos, books, etc. about this topic
    • On social profiles: Track keywords on blogs, forums (reddit / hacker news, …), social media, etc. and interact (reply, retweet, etc.)
      • Maybe use Hootsuite
    • In person: Summits, OCI representatives at non-OCI events
  • Gratipay funds ("whit537 was saying ... there was 2000$")
    • Figure out how Gratipay works
      • Publicly document our findings so that other OCI members understand and so that we have a public record
    • Use funds for
      • Refunding @galuszkak for purchase of t-shirts and stickers, their shipping
      • Refunding (?) for domain renewal
      • merchandise (t-shirts, stickers, etc.)
      • shipping of t-shirts and stickers as they are sent
      • domain renewal
      • possible pro accounts for social media tools
  • Many items missing, to be completed from the document used during the meeting
This was referenced Nov 18, 2015
@tenkabuto
Copy link
Member

I updated @waldyrious's post above with all of the items that I found in the document linked to at the bottom and from the notes that I took during the meeting.

I noticed that some of the points that we discussed during the meeting weren't added to the Google Doc, so please look this over, @waldyrious @galuszkak, in case I missed something. 😄

@galuszkak
Copy link
Member

galuszkak commented Oct 18, 2016

Can we move those to seperate tickets? I think having this so long open, doesn't help tracking what's in the "month meeting" issue :).

@waldyrious
Copy link
Member Author

Agreed, separate issues is the way to go. I'm afraid we might lose some info if we don't confirm whether the notes from the meeting were all added here, but if we block on that we might not move forward at all. (Confirming that all the items were added here shouldn't take too long, though.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants