V2 begins - org, members, and access
amoffat opened this issue · comments
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.
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.
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:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDAs8bi47sAjI8ZEP2YHr7EOYfgOYqExk4v9NNwRfn1dI8rxkOKOtACWBV/mMsAMhmF6n4E/T+iNihWlkl5nq4oNmY9fxID51MUwvKiLe5VY/xgG+xEs/otLZJAr45PbhlvXUYdlOmJWS2tLbhNjdYsiPay7Cb61auBETCzPUOKRxRavgNNa9DCRnc2WST3ANP1fWbHsfdv9vQcKBmxocPSF+dTQ80ACQxZGpbCGXhU/tOeP4heO85JaAEa6twY86zWNn9qYE6+NIStAbon7B1JPzRX6q3HPs+xbA3u5nBk/3j9448N7PyG6JqVaUZw1O74ek5MTC0e+15dqkoHCR3t JuiceSSH
Hey @amoffat, Thanks for the invite!
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDZjAQPW0JX5zbBxyySnHfe5KAFDttR1gY/zLDeym1V6x8oq5pXu73S4NuuWKnn3jTWgEHhNV2xqGKE525AyOmu6chIiFdpLDyYeMFSGkLwL+aJQJXSn4gfbaQ84kVl++SsbuXZAC7pbj/XUBKebhSYQhx3uvx/wuJvsbIYaL3BcvCltD4uVlWOsoz+YJpbeOcVJ1OkX9uAdijT2faTNk8+3medyAdGQrkVU6V4wtrSDszuqWVgmyPfkvTBBh6+COoQLhoMDLjBZTO0RG0vo/i0xc9TMgnXYaAsWPApoiKSeEH9Z7a1vEKN5RMpcEwDOS1TBWPxXS078PShtGfjCia3 mpnordland
Thanks for the invite!
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDu/Vm0dCOo415PlbarHCaewO/4dFM6vR0o/fSmeMwqxMF4gFYGfHMz2Jd4VP0IvgdQS6w1CBrrsc4pTeZ11cV4QeAOH/g8QO2e53audhhcIQgCAsfJsyuayn1sLi0KtGinOyjePQP4Sh81xc69qllEwFG+cYk4Kcs0NIlNtZvr1ZlFJafO0gTIMjUz813SM1Z/zZeuKp1yx6rp+LS7XdKqKUShtJenTicjoOJpijrfXEd65qndXOQPW+NxS/4wQ4h4hNg+OHCLjeTnBqUu0lJEqqnxvS9RNXQpCCKQzemAjF9tOetL4zsZKdTFJlv0Bu/SEZj1qHWpIKakFo3yp+hZ alexander@zap
SSH key are only for those who want to work on the server ?
I guess we do not need all the devs in, isnt it ?
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.
It will be great to have a massive overview without watching all the discussions.
Thanks!
ecdsa-sha2-nistp521 AAAAE2VjZHNhLXNoYTItbmlzdHA1MjEAAAAIbmlzdHA1MjEAAACFBAFaaBHoVs0SWl5fK0JMI4wlOhgOX4YHo1ejHRpuMIf1MMQ9H2gQdeAIi8IXkYw08+8jiBnoK/QmmCYyf8+LkyvGPQDxLrrIRQURMo9Pg4Rm8eUdN+exVJZcO683549ICA8m399g/encW86uO6xJpU2LYlDjJGe+/IxeY9dY3ZJLymSemg== SSH
The trajectory of this project is concerning for the following reasons:
-
@amoffat wrote this at 2 AM
-
@amoffat asked fifteen people, including the person he insulted, to contribute work for free
-
@amoffat asked those fifteen people to assign the copyrights on contributions to him
-
chaosthebot.com is down, which makes it impossible to verify the impact of the contributions on the project
-
@amoffat marginalized my work by calling it a fork
-
@amoffat said I was using the issue tracker to advertise chaosbot.org and said that was inappropriate behavior
-
@amoffat expected the community to accept his judgement of my behavior without justification or explanation
-
@amoffat, a domain owner, wants to use the github issue tracker for the purpose of exclusively promoting a domain he owns, chaosthebot.com
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.
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).
@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
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCeJUDopS6fimjvUJ8GXJCZfWm5HPst6prkObg8xUeqS9DHYUjCDigrB/y8M6NfyIa/GUixyQEIIaarlICiXtzVz3kbAdpfYwSMatGvLprUIh+7dGDjYriXMAONyo/gKetYgIESediGBZgU4gghyUIRIV1dbCBKJ05yga2h2lZ7nmQCbOP/HQ9UQ+j5SqlGaiC/xu/Lyi2bvpCQ2oaN18V4X0a5cVPjUoP24W4F7W3ai3kcwiZy4rsvW45/LglqnSPSnkxvgJSUmtVtmKGhTbY9o5u3B44leDT+PTlv5WERlNcR7qVEam79Wad0fn7WmRP6MvXEkuwhSbOZP7TsKci3 eukaryote@ubuntu-server
@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 🙃
@eukaryote31 and @Redmega, added 👍
and @dbpokorny is blocked
I'm deleting the more off topic comments. The original comment from dbpokorny will be kept, but not discussions about e.g. if someone's a bot. This issue is for chaosbot v2.
Archive before deletion: https://web.archive.org/web/20170620020106/https://github.com/Chaosthebot/Chaos/issues/559
Edit: If you'd like to continue discussion, I'm fine with that, but please create a separate issue.
@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 pretty clear my guess that @chaosbotgroup is just @dbpokorny.
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:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCdmUz+aseOv9P1WhAIeUF5ZvocvpOMHcBRQE+rUoW+IMrEkx+5exh/+OdHUZ9xXdrXcEdcwiV3+/IMlFETkFj+pyk3BN+0QTbiZyYmnHS1hvqEi7YnKSSnGBaI5jf4IpD31M2S1eOlIuuSeBwcjhLUZEzz/VtUUcDpdHv1Bf04j3ImTBKiQrVaH0T2h/D/p8lNDwk+1YbMOEOQdfpRJMlndBY/2IkklM/pU3jXoIHvonO1T62M4jZghtMPSsQGsV9U91gvMCqwqx9sECy0BGhvgnuHiTYKYYplSP+DnfjRBeO3ax+quOSAu3XFz14f6M8gMB37QZldrtJYGwH3B4Vv andrewda@server
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:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC3d48IXcJBpVtsSE5PNOpU57h2fEXw78XzmuSA1GksGWB7FJevcrZeOxrkpDTQvhRqjtQOWQX22aa5VWEiawAk5lzUQNJ/OG/3cRsxV57c9f4jdWHVurueqEaWJOWZuW4GuS2DEnxZNfcBx/H5M6dAyjixeEsjcYFtTz+0pp3RVEUDgeoDSlJl4EqLzN6hcNT4F+ZcV6JxNRIwDiQC3llpzgATEXJuTgPO/VTh4bsI4Op7DgiUrGfW/0cNofRFKER5KN8cDKZDDLUYcxG1U3AQvdYxc2EDuEt8iyWN/C4wwVlORHl4+cn8pPXZ4R58zElXC/mXVQ/5cae1WBvcHBsD patrick
Cheers, I'll help break it if I can :)
@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.
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.
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIHsdkZS1u9DuM1Ir97dqnUbNZq5qswY5elLnNQnE4aEM restruct@archlinux