twentysix26 / red-docs Goto Github PK

Windows install

With the bot changes and so on the installation page has become a giant mess, I've started working on a new branch that covers all the new installation methods, new pages and an amazingly revamped home page (Yes I'm making this one shiny text). Below is a list of the things that are needed to be done

• New home page
• Pre installation guide (covers creating bot or user account)
• Windows guide
• Linux (Debian) guide
• Linux (Fedora) guide
• Approved (Placeholder name) Repo list
• Guide on adding the approved repo's

List: beta

Repository name: RitsuCogs

Author: Ritsu / kagami#6142

Description: Some /usr/bin inspired cogs. Includes several text manipulation utilities ported from *nix. Can read input from user message, chat log, or URL. Can chain commands together via pipes and redirect output to pastebin. Also includes an anime RSS alert cog specifically built for TokyoTosho.

List: beta

Repository name: Yukirin

Author: Yukirin

Description: Various cogs.

After some discussion, we've come up with this:

Cog creator role

• Would help with voting on applications to be added to the list
• All users who currently have the role would get to keep the role. All future additions to the list need to be on the approved list to get the role

Self moderating repos

• Once a repo is on the list, the community would help moderate future additions and changes to those repos. This would best be accomplished by everyone on EITHER list having a channel with a webhook for their repo in this server

Cog promotion

• This would be a spotlight of specific cogs with some sort of info about the cog along with instructions on how to install it
• This would be for both lists

@Kowlin @Redjumpman and @irdumbs contributed to the making of this suggestion

List: approved

Repository name: ORELS-Cogs

Author: orels1

Description: Gaming / data based cogs, with a bit of some fun stuff

Should we consider using last_edited on the Markdown headers? as example, this would be Windows Requirements.

---
title: Windows requirements
sidebar: red_sidebar
permalink: /red_win_requirements/
last_edited: April 21, 2016

---

Though I think we should use dd/mm/yyyy, but thats just my bias European opinion

List: beta

Repository name: ridings-cogs

Author: Ridinginstyle00

Description: This repo adds in what I think would be some fun and useful little cogs. You have the Levels cog, which, if you know the bot that goes by the name of Mee6, then you know how his Leveling system works (when enabled). If you don't know Mee6, the Levels cog is basically a cog that, the more you chat, the more you gain EXP, and after a set amount of EXP, you level up. It's a fun little gag to see how much more you spam compared to your friends. Next is the Duels cog, that...well...lets you duel others! Although my code may look like crap for it. I tried my very hardest and accomplished the task. I even included an extra 30 actions from the first run! The third cog is the Commands cog. All it has is little commands that can be thrown around as joke commands. Some may find them very cruel and be labeled as harassment, but I find them fun things to use around. This cog also downloads the picture each time the command is called, which may cause some issues with slower internet. The last cog is the Dismissal cog. It works almost exactly the same way as irdumb's welcome cog (if I was informed correctly that was his cog), but instead of welcoming people...you guessed it, the Dismissal in fact shows a message when a specific person leaves the server. It was almost completely the same code. I changed it up though, I even updated it to dataIO instead of using the welcome cogs fileIO system. I give full props to irdumb and his code to aid me in making a dismissal cog.

If anyone finds any issues I overlooked, please tell me and I'll fix them ASAP!

About time I gave this a shot...

List: approved

Repository name: tmerc-cogs

Author: tmerc

Description: Various cogs that range from playing sounds and getting cat facts to taking surveys and storing quotes.

List: Approved [Or Beta]

Repository name: Sentry-Cogs

Author: Sentry

Description: Usefull Cogs that have a tendency to shoot at you

List: Beta

Repository name: Jake-Cogs

Author: jakesden

Description: Just a repo I put all the cogs I make on, I also do requests for custom cogs.

I'm proposing (as others have discussed) to make separate lists of repositories. One list being an "approved" list that contains repos highly beneficial to the community, made by devs who know what they're doing and who will be around to fix things if something happens to break. Admittance to this list will probably be highly subjective, so don't get your feelings hurt :P

The second list will be a "beta" list that contains repos for anyone who wants their repo to be public and comes with clear warnings that the things found in these repos is entirely unmoderated and not guaranteed to work in any way.

Name suggestions welcome.

List: beta

Repository name: Dusty-Cogs

Author: Awoonar Dust

Description: Cogs for server utilities and fun!

Link to the repo *as a note, the cogs are still being developed, but I only push stable versions

https://github.com/phantium/phantium-cogs

List: approved
Repository name: phantium-cogs
Author: Phantium
Description: Gaming related and other fun cogs

Hi there,

I started making cogs yesterday, I have finished my first cog which is for Overwatch.
I will be pushing out more cogs over the coming days/weeks and hopefully years. :)

I'd love for my repo to be added so I can share all of my cogs with others.

Cheers,
Phantium

List: beta
Repository name: beatrice-witchcogs
Author: PookaMustard
Description: General-purpose cogs made for Red-DiscordBot, mostly search cogs.

Additional notes: The Bing cog uses code from Mash's IMDb cog, namely the JSON code. The same will be of the MyAnimeList cog later on, as it will take the same makeover. Mash has allowed this.

List: beta
Repository name: Kobalt
Author: Kobalt
Description: Some cogs.

List: approved
Repository name: calebj-cogs
Author: CalebJ
Description: General and utility cogs I made or innovated upon.

List: beta

Repository name: Snap-ons

Author: SnappyDragon18

Description: Cogs based on nerd-culture and games for Red-Discord Bot.

Repository name: Jumper-Cogs (https://github.com/Redjumpman/Jumper-Cogs)
Author: Redjumpman (Redjumpman#2375 on Discord)
Description: Will be developing mostly cogs related to gaming such as Pokedex.

List: beta
Repository name: Ax-cogs
Author: Aioxas
Description: Weird cogs that might or might not be useful for your needs. Check them out!

https://github.com/ddday/anomalys-cogs/

Repository name: anomalys-cogs
Author: anomaly
Description: Fun API cogs.

List: [approved/beta] Beta because it's on the chill side

Repository name: Nerdie-Cogs

Author: NerdieTony

Description: Just some nerdie cogs for ppl. First, we got Transformice.py, which gets stats from Transformice, Botstats.py, which display botstats, and fuck.py, which provide fuck you statements for the whole family. Tonight, I'll add more fields for Transformice.py and more fuck you statements since I'm at school. I'll also update readme! I hope you enjoy the cogs and remember, love is a concept made by humans. Peace. Love. Nerdie.

Avoid using static files for the 'not officially published' cogs.
Instead rather encourage the developer to use a Github Repo and link that file.

94a300c

https://github.com/tekulvw/Squid-Plugins

Repo Name: Squid
Author name: Will
Description: A collection of cogs and tools I find useful

• Added in those pesky prereqs :P

List: beta

Repository name: Pepsi-Cogs

Author: pepsifire // Same#3094 on discord

Description: Various random cogs i mainly use for my bot, but felt like sharing them.

Applying for beta because i will mostly be improving these as the time goes by.

Well boy, here goes nothing. I only have one autistic cog in the repo, so I'm only going for beta. Expectations <= 0 == True

Currently, the only cog I've made allows any user to rate themselves or another user using emoji (see Facepunch.com, you can rate posts). I intend to make more changes in the near future, however if you look at my other main repo, you can see intentions don't often get carried out. Currently I am trying to come up with some original cog ideas, thinking maybe a source engine server info thingo

List: beta

Repository name: shigbeard-cogs

Author: Me, Shigbeard.

Description: Literally just a place where I will put some meme-level cogs that I make.

https://github.com/irdumbs/Dumb-Cogs

I also suggest using optional info.json files in the root directory for more info on the repo itself :3
Can probably just delete the DISABLED item in that info.json though

Repository name: Dumb-Cogs
Author: irdumb
Description: Example cogs as well as various silly, QOL, and community-based cogs

https://github.com/Canule/Mash-Cogs/

Repository name:
Mash

Author:
Mash/Canule

Description:
General cogs.
*oboobs = NSFW

We need to make the process as clear as possible. At the moment it is not clear that the folder name must match the cog file name exactly (capitalization included).

https://github.com/Eslyium/Eslyium-Cogs

Repository name: Eslyium-Cogs
Author: Eslyium
Description: General Cogs and NSFW Cogs.

We should move applications to a separate repo that allows users wishing to create a repo for the first time to just fork the repo. The repo will contain any tools to help them get started to become a Cog Creator. Once they feel their repo is ready, they can PR to this repo, and we can review their changes. This works better than issues, because we can have people approve changes.

The second thing is that we can see what happens to the code after acceptance. Easier way to track malicious code injection. This has been something we have been trying to remedy for a while.

The PR's never close, but can be organized. We can really get organized by using integrations like zenhub and make it look pretty. Thoughts?

No pandentias were harmed in the making of better_application.

Once a repo is approved, the author can add whatever cogs they like. This could potentially lead to a seemingly harmless repo having a malicious cog added in the future without us noticing.

I suggest we rescan repos a few times a month to prevent this.

https://github.com/FishyFing/FishyCogs

Repository name: FishyCogs
Author: fishyfing
Description: Some coding practice that may have created useful cogs.

The quality of cogs coming from newcomers isn't increasing and it doesn't seem like they're getting better any faster than the newcomers from awhile ago. This means cogs coming from our community isn't getting any better in quality as time passes.
We're getting saturated with cogs that are just random messages and posting images.

I blame partly our lack of a good tutorial. You can argue that one isn't needed, but it seems rather difficult for newcomers to understand how the community works and how the conventions around here work.

Currently we got: https://twentysix26.github.io/Red-Docs/red_guide_make_cog/
and unofficially: https://github.com/FreeCodeCampGuam/FreeCodeCampGuamHelp/blob/master/Python/README.md

should we get together and make some effort to put down a decent tutorial and write down all our conventions in a more accessible way?

Repository name: PaddoCogs (https://github.com/PaddoInWonderland/PaddoCogs)
Author: PaddoInWonderland (Paddolicious#8880 on Discord)
Description: General cogs I developed.

List: beta

Repository name: Pancake-Cogs

Author: UltimatePancake

Description: Various cogs.

List: Beta
Repository name: FlapJack-Cogs
Author: FlapJack
Description: Cogs containing features such as sfx, reaction polls, game utilities, name color management, triggered emoji reactions, a server DEFCON system, and dongers.

I've recently put a lot of work into testing, documentation, and PEP 8 compliance, and I'm ready to submit this repo for beta status.

List: beta
Repository name: Maybe-Useful-Cogs
Author: Stevy
Description: One is a pretty large and I believe resource intensive cog for osu!, a whoplays cog, an omegle-like thing cause I thought it was cool, and a markov chain text generator.

Repository name: Booru-Cogs (https://github.com/Alzarath/Booru-Cogs)
Author: Alzarath
Description: Image booru fetching cogs

This is a migration from a cog that's already in the Community repo. If the pony cog could be removed from the Community repo when this gets approved, that would be appreciated.

I do plan on expanding this and adding more, similar cogs in the future.

Hello! I'd like to apply to have my repo become beta.

List: [beta]
Repository name: RiceCogs
Author: FwiedWice
Description: Random cogs ranging from server management to utility to killing people.

https://github.com/QingyuChai/RiceCogs

List: Beta
Repository name: palmtree5-cogs
Author: palmtree5
Description: Various internet and Minecraft-related cogs

Applying for beta because tweets and reddit are still very much a work in progress

Repository name: Wolf-Cogs
Author: Wolfstorm
Description: General Cogs made for Red
Link to Repo: https://github.com/Wolfst0rm/Wolf-Cogs

Thank you for applying to have your repo added to the list of approved repositories.
Please fill out the following information

List: [approved/beta] beta

Repository name: PewCogs | https://github.com/pewbaldpew/PewCogs

Author: Pew

Description: Quirky and fun cogs.

List: beta

Repository name: Paddo-Selfbot

Author: Paddo

Description: Various cogs for selfbots only.

List: [beta] (approved if you think I'm worth it)
Repository name: https://github.com/Nop0x/Nop0xcogs
Author: Nop0x
Description: Several Cogs around countries and timezones.

Commands added:
-addcountry : Sets your country of origin and stores it in a json.
-removecountry : removes your country of origin.

-locate: prints which countries a user has set.
-location: pms all users for a given location
-location_settings: settings for the heatmap functionality
-map: generates a heatmap where users are from and uploads it to a channel

-timezone user: print the current time of the user who is issuing the command
-timezone user : prints the current time of a given user
-timezone_settings: settings needed for the timezone command

Any feedback is appreciated!

If you have questions hmu on discord Nop0x#4618 or comment here :)

List: Beta/Approved

Repository name: Scarlet-Cogs

Author: ScarletRav3n

Description: Fun and random cogs for general entertainment.

Thank you for applying to have your repo added to the list of approved repositories.
Please fill out the following information

List: approved

Repository name: https://github.com/palmtree5/palmtree5-cogs

Author: palmtree5

Description: Various cogs for Red

Putting in for a move from beta to approved as I think I'm ready. Cogs that aren't as well fleshed out will most likely wind up on a separate branch in my repo and be merged in once they're ready so that master will only be cogs that should be pretty stable

https://github.com/Skordy/Skordy-Cogs

Repository name: Skordy-Cogs
Author: Skordy
Description: Random assortment of cogs that make life easier.