V2 begins - org, members, and access #559
Comments
|
Here is my public key, hoping I will not break anything! 😄 ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDqhcJuHapHT6675MXOIuKhCZhwWP0bWa78M/XCP9lCs6owzaY+WPO0ueSAApjBoq9sbCMLqxQufgH8hFN22gG0temvZY88qGV8RJtgJGVym/qFYrO4Rjr7o9BPI0PFDhSe96QWcO41ISft0WjK4hi3B3T4rCFFnOaqINtFJs66EeLkwQK2rvR2uj543HQgThV+L34068IKwAa9Mh5eOiHvsPgCzfoCwPGrhw+7yV+84rxEJ/phAb59vguvLCMb4aXc8IN9N9soPulu/hPiKFsGe9mpUe2gNgvCxQ4L9Y0tUCF/+rB6PxfSU+RdAGenBGE+CaOmdxc5ouxLe7uXUl8/ muchzer@martian |
|
Wait; I am in the Meritocrates list ? Last time I checked, I was far from this. |
"largely based on the current meritocracy.json file" |
|
Thanks @amoffat, I'll get to work on some things (namely core) soon. Public key: |
|
Hey @amoffat, Thanks for the invite! |
|
Thanks for the invite!
|
|
SSH key are only for those who want to work on the server ? |
|
Is there a deployment process via github hooks or if we want to deploy will we need to have access to the server? Do we have a roadmap/priority list so we can sign on to tackle certain issues? |
|
Feel free to put one on the wiki |
|
I've created a project to track features to be added and where they should be added (assuming we're still going for multiple repos). |
|
I think we can create a repo only for issue mastering. Then convert the most upvoted issue to Project card. |
|
Thanks! |
|
The trajectory of this project is concerning for the following reasons:
Let me explain how this affects contributors. @amoffat isn't going to value your work unless you can find out a way to make him see it as a valuable contribution. Traditionally this is done using copyrights, trademarks, contracts, withholding work until payment is received, and asking for promotion of work you've already done. Every time you submit a pull request to a project that has a LICENSE file that lists someone who isn't you as the copyright holder, you are implicitly assigning the copyright on your work to the individual or organization named in the LICENSE file. |
|
Jeez dude give it a rest. |
|
@rudehn why did you use a curse word? |
|
ssh keys added. @Redmega re: deployments for now we'll have to jump onto the server and do a git pull until chaos is in a workable state again. We'll probably need to figure out some kind of coordination (via gitter or something) If people think @dbpokorny is intentionally trolling and want to see him blocked from commenting on issues, give this comment a 👍 , if not 👎 |
|
Eh, he's expressing his free speech in a democracy. I think we can just ignore the odd/troll criticism. People should probably only be blocked if they're spamming and causing unnecessary emails to be sent to repo watchers. |
|
FYI SSH access appears to be for the root user, as expected. |
|
@andrewda If it continues, I'd consider it spam, or at the very least hindering discussion. I think we've made it clear that we aren't interested in the concerns. |
|
I am considering his post as spam. |
|
Not directed at anyone in particular, but if people disagreed with @amoffat's decisions and suggestions, they would say so (like @andrewda and @dbpokorny have done). |
|
Should @chaosbot be a public member of the org (to make it easier to find)? |
|
@dbpokorny I'm sorry you take personal issue with aspects of this project (so, so many aspects, apparently), but there is no need to keep finding trivial or outright false accusations to try and encourage people to abandon this project. I'd like to point out that there is some agreement from a number of people that you are hindering the project, and while I am not going to say that your contributions are unnecessary, this nitpicking is frustrating and doesn't help us progress - it only seems serves the agenda of a small minority and not the whole community. |
|
@dbpokorny Save that for after we go live my dude. Right now we need to get the bot started, then we can worry about when it'll take over the world. |
|
you are all welcome to watch me incriminate myself by advertising the anythingbot video feed at anythingbot.org/video and/or play with the controls at anythingbot.org/hello |
|
|
@Redmega is a brave man, or he trusts the Goog's spam filters a whole lot. |
|
Oops.. Hehe... It's available on my bio website anyway. In Goog we trust 🙃 |
|
@PlasmaPower Thanks - was going to leave them here in the interest of democracy and fairness, but it's fair enough if they have been archived. |
|
@chaosbotgroup please move your discussion to #564. Further discussion of of the issue here may result in a ban, as it is off topic and I've already made that clear. |
|
weird, I don't see chaosbotgroup's messages, but I get email notifications about them. |
|
@amoffat the comment appears to have been deleted. (when you delete your own comment it doesn't show up in the log) |
|
It's |
|
blocked. if we see any more mysterious users pop up with shenanigans, it's probably safe to assume those are him as well. it may be getting close to that time when we have to reach out to Github to report his accounts for abuse |
|
Sorry for the late response, but here's my key: |
|
So...is this project dead now? |
|
@SlightlyCyborg This repo, V1, is completely dead. V2, is supposted to be a re-written, improved version, but no code has been written, yet. The V2 repos are in the @Chaosthebot org. |
|
Perhaps chaotic development only works in bursts, where new projects are given life with access to everyone, then gradually tightened down. Then the process can be repeated. Surely, a bot could be written to manage such a project lifecycle.... :) |
|
Bit of a delay, but here's an ssh key for me: Cheers, I'll help break it if I can :) |
Sad to see that the new V2 never really kick-started. |
|
Yes |
|
People got bamboozled, meritocracy was instituted, the servers deathcounter kept ticking, monarchs were appointed, it was fun. Looking forward to v2 with ever more chaos. |
|
|
The Chaos repo is now owned by the Chaos organization https://github.com/Chaosthebot
Membership invitations have gone out, largely based on the current meritocracy.json file. I may have missed some core contributors, so if I forgot you, please let me know.
@andrewda, @xyproto, @rhengles, @PlasmaPower, @eukaryote31, @rudehn, @muchzer, @mark-i-m, @phil-r, @hongaar, @md678685, @Smittyvb, @Swizz, @Redmega, @mpnordland
You all have made some excellent contributions (wait why is smittyvb in the meritocracy!? :tears: ). There's a few slots open for server access to the chaosbot public server. If you're a responsible dev, post your public ssh key in this issue, and I'll add you to the authorized users. Those few devs will then be able to perform any kind of high-level admin to the server to aid in v2 development.
You all should be able to create repos and have read/write access to anything. Use that ability to create nodejs/rust/brainfuck rewrites or to break out core functionality. If you're missing a permission to do something, post about it here and we'll get you sorted.
The text was updated successfully, but these errors were encountered: