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

February 2016 Meeting #170

Open
tenkabuto opened this issue Feb 14, 2016 · 5 comments
Open

February 2016 Meeting #170

tenkabuto opened this issue Feb 14, 2016 · 5 comments

Comments

@tenkabuto
Copy link
Member

On Google Hangouts, @galuszkak, @waldyrious, and I decided that we could have a meeting this month, and it should be today (Sunday, Feb 14th).

@waldyrious offered:

I believe I can. It should be this sunday, right? I won't be able to get much done before then, but we could use that time to sort out all the tasks we discussed in the previous meeting, which was a substantial list. That would get us back on track and we'd have a proper task list we could then work on gradually before the next meeting.

We would go over the list on #168, the Nov 2015 meeting. Keeping with the time set on #167, we might meet at 8pm UTC (converted).

@tenkabuto
Copy link
Member Author

Below are the todos and notes from the 2016 Feb 14th meeting. @galuszkak could not make the meeting, but @waldyrious and I started to review the list from #168. We only had enough time to address the "Github organization" item and those that came before it, as we were not familiar with the list.

We hope to have another meeting soon, possibly next Sunday, Feb 21, for 30-45 minutes.

TODOs:

  • Create a page on the repo's wiki, listing everything we've got and who manages it
  • Google+ page: add Brandon as a manager (looks like only Kamil can do it). This also makes him a manager in the Youtube channel.
  • Move hangouts setup instructions (above) to a wiki page; moved here
    • Review/copyedit, ensure they are actually working
  • Close the Dec 2015 issue, with explanation
  • Revamp the Github organization:
    • Members/teams/owners are only public if we’ve set them as so. They might default as private.
    • Waldir and Brandon agree to make all organization members public. We should wait for Kamil’s opinion, and if he agrees, contact every member to ensure they’re OK with the idea. If no contact after some time period (6 months?), remove from current teams?
    • Get Kamil’s opinion on: Move the company-reps team to the "outside collaborators" group, it seems to have the same effect (they’ll have access to the repos) and we probably can (TODO: confirm) customize both role (member/owner) and repository access. We can use one of us to test how that works beforehand.
  • Have another meeting soon, possibly next Sunday (Feb 21) for 30-45 minutes
  • Copy transcript of Gitter exchange to wiki
    • remove unnecessary bits

Notes:

  • We cannot change an org. member’s private status to public, but we can change public to private
  • All teams were made visible to one another, but org membership statuses remain unaffected (i.e. visibility of membership to public)

@tenkabuto tenkabuto mentioned this issue Feb 14, 2016
2 tasks
@tenkabuto
Copy link
Member Author

I checked off the items above but forgot to note them here. I did the following:

@galuszkak
Copy link
Member

Waldir and Brandon agree to make all organization members public. We should wait for Kamil’s opinion, and if he agrees, contact every member to ensure they’re OK with the idea. If no contact after some time period (6 months?), remove from current teams?

I agree.

Move the company-reps team to the "outside collaborators" group, it seems to have the same effect (they’ll have access to the repos) and we probably can (TODO: confirm) customize both role (member/owner) and repository access. We can use one of us to test how that works beforehand.

I agree. When can we try this?

Google+ page: add Brandon as a manager (looks like only Kamil can do it). This also makes him a manager in the Youtube channel.

I need Brandon link to account so I'm sure I'm transfering this to right person 👍

@tenkabuto
Copy link
Member Author

@galuszkak Are you able to link it via an email? My account's email is [email protected]

@galuszkak
Copy link
Member

Brandon (@tenkabuto) I've added You. Sorry it took so long :).

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

2 participants