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

Why the Youtube meetings were public but not anymore? #8

Closed
a0viedo opened this issue Oct 16, 2014 · 12 comments
Closed

Why the Youtube meetings were public but not anymore? #8

a0viedo opened this issue Oct 16, 2014 · 12 comments

Comments

@a0viedo
Copy link
Member

a0viedo commented Oct 16, 2014

At least the ones at Oct 3 and Oct 9.

@bnoordhuis
Copy link
Member

@rvagg I saw you uploaded the video to YouTube. Has it been published yet?

@rvagg
Copy link

rvagg commented Oct 17, 2014

Yes, its accessible but unlisted. Link is in the email thread about it. I just didn't want to be the one to share it here yet given the sensitivities of the current situation and seeing how the previous ones we're temporarily unlisted. If you want to share it, go ahead, though it might make sense to wait until some dust settles. @mikeal?

To everyone else reading this: it's probably frustrating watching this semi-closed and not well communicated process but please be aware that everyone involved here is working together towards and better future for Node, one that's also much more inclusive and open, and involves things like public recordings of TC meetings. There's just some sensitive politiking going on on our way there.

@mbonaci
Copy link

mbonaci commented Oct 17, 2014

@rvagg 👍 for the initiative, but what dust?
We don't know shit, so the explanation is rather useless :)

I cannot fathom what could be the reason for making those videos private?
Open all the things! Say it loud and clear.

Just my uninformed guess:
http://youtu.be/-zRN7XLCRhc
So fork, yeah, but tell us what's going on.

@a0viedo
Copy link
Member Author

a0viedo commented Oct 17, 2014

"forkphobia", that's an awesome term introduced by @bcantrill

@dshaw
Copy link
Member

dshaw commented Oct 17, 2014

@mbonaci
Copy link

mbonaci commented Nov 12, 2014

@rvagg @dshaw @mikeal so there's still no explanation about what's going on?
Aren't node community supposed to be open in every possible way (as open mind, not as open window :)
Can you at least give us a good reason why you made this look like an elitist gathering, conspiring behind a closed door?

I'm not trolling, I genuinely feel that way. I'm writing this because I care.
It pisses me off that I'm almost in a complete dark.

I was very surprised to see that you made videos (anything) private.
I expected to see the whole story after Joyent formed advisory board. Nothing happened.
I expected to get some info from the last nodeup. Nothing there.

Couple of private videos, tablespoon of mysterious "dust settling" and a pinch of "sensitivities of the current situation". What a hell?

I would have never expected this kind of behavior from the node community rock stars!?!

Now please, would you be so kind to ignore me a bit more, it feels so welcoming :(
You can throw away all those "noobs welcome" efforts, as long as things like this are happening.

Would you feel welcome?

@Albert-IV
Copy link
Member

@mbonaci Calm down man, I don't think anyone is deliberately snubbing you here. I think there are some legalities and political maneuvering going on that can't be made public yet, and I don't think making a scene will help.

Best advice I can give you is to watch this repo, as well as the node repo. Keep up with the issue trackers on both. Keeping up with the issues and fixes should give you a better idea on where the node.js project is going.

There have been some hints that v12 will be getting released in the next few weeks, which I'd imagine would clear some of this mystery up. That being said I'm in the dark about all of this as well, so we're all waiting to find out what's happening.

@ijroth
Copy link

ijroth commented Nov 12, 2014

You may want to listen to the next Joyent advisory board meeting:

https://nodejs.org/advisory-board/2014-11-06/minutes.html#minutes_md_next_meeting

@mbonaci
Copy link

mbonaci commented Nov 12, 2014

@droppedoncaprica so you're in the dark too and that doesn't bother you?
OK, but please allow that it bothers me.
Can I express my honest opinion without being accused of making a scene?

So if someone explained what's going on, she/he could be sued? Come on, really?
Can someone "that's not in the dark" confirm that?
That would certainly be a viable explanation, but it seems a bit stretched.

Thanks @droppedoncaprica though, for at least trying to clarify.
Thanks @ijroth.

@mbonaci
Copy link

mbonaci commented Nov 12, 2014

@domenic you don't mean sued for laying down the facts?

Thanks for that, but you'll understand that this is just another hint in the long line of hints about something that is very important to me.

@mikeal
Copy link
Member

mikeal commented Nov 14, 2014

I've sent the Nodejs Advisory Board a pull request with the governance and contribution policy adopted by Node Forward.

joyent/nodejs-advisory-board#11

This is now in the public and all of you have a chance to participate and support to hate on that policy.

@a0viedo
Copy link
Member Author

a0viedo commented Aug 13, 2015

Closing, it's not relevant anymore.

@a0viedo a0viedo closed this as completed Aug 13, 2015
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

8 participants