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

Create meeting-01-19-2016.md #3

Merged
merged 5 commits into from
Jan 20, 2016
Merged

Create meeting-01-19-2016.md #3

merged 5 commits into from
Jan 20, 2016

Conversation

iangcarroll
Copy link
Contributor

Info

  • Where: ##hx-admin on Freenode
  • When: January 19th, 2016 at 8:00 PM EST
  • Who: Anyone

Agenda

  • Meeting procedure, agenda, and minutes (@???)
  • Merging policies round 2 (@gsingh93)
  • Subgroups
  • [your suggestion here?]
  • General Q&A

@iangcarroll
Copy link
Contributor Author

Suggestions for a date @arirawr @frankcash?

I think @frankcash suggested Sunday, which works for me.

@frankcash
Copy link
Contributor

Sunday night or afternoon is preferred.

Monday is okay too but it is MLK day in the States.

On Thu, Jan 14, 2016 at 2:09 PM, Ian Carroll [email protected]
wrote:

Suggestions for a date @arirawr https://github.com/arirawr @frankcash
https://github.com/frankcash?

I think @frankcash https://github.com/frankcash suggested Sunday, which
works for me.


Reply to this email directly or view it on GitHub
#3 (comment).

Charles Frank Cash
FOSS Programmer
[email protected]
https://github.com/frankcash
https://keybase.io/frankcash
https://github.com/frankcash

@gsingh93
Copy link
Member

I remembered some stuff.

One thing is some of the stuff we talked about last time never got done, particularly the hackbot post. If you remember any of the other stuff that was talked about but never got done, post it here.

The other thing was discussion about how to work around some of Facebook's limitations. These aren't super urgent, but I think there are two things that would be nice to have. One is a log of all reported posts, the response to the post, and which admin responded. This log would only be visible by admins, and since I don't think you can do this with the FB API, you'd need to use a chrome extension.

The other thing was to have some log of all the posts to tell when administrators deleted something. One of the problems of HH was things going missing randomly, and it was unclear whether the OP did it or an admin, and if an admin did it, which one. While we do take a policy to close the majority of the bad threads we see, there are going to be cases eventually where we need to delete, or where we get accused of deleting. In those cases, it would be nice to have a log to prove it wasn't an admin, or figure out which admin it was.

@gsingh93
Copy link
Member

It would also be nice if you guys could leave your thoughts on the subgroups issue before the meeting.

@iangcarroll iangcarroll changed the title Create meeting-01-1?-2016.md Create meeting-01-19-2016.md Jan 18, 2016
@SCKelemen
Copy link
Member

Ban Logs - Maintain a list(database) of banned users, and reasons why, also maybe have an un-ban date. I think this should be public.
Looking for Hackers - any thoughts on why we are still getting a lot of people looking for hackers for hire, even after the name change to HX?
Mandate Content Policy Citations - We should probably require citation when removing posts. Also, perhaps it is best if we have some cookie-cutter, standard responses for closing posts.
Create FB Group File for meeting agenda addition by persons not interested in github

iangcarroll added a commit that referenced this pull request Jan 20, 2016
Create meeting-01-19-2016.md
@iangcarroll iangcarroll merged commit d176de9 into master Jan 20, 2016
@iangcarroll iangcarroll deleted the meeting-2 branch January 20, 2016 01:03
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

Successfully merging this pull request may close these issues.

4 participants