Skip to content
This repository was archived by the owner on Jul 27, 2022. It is now read-only.

[CONTRIBUTION GUIDELINES] #1

Open
pielco11 opened this issue Oct 17, 2019 · 4 comments
Open

[CONTRIBUTION GUIDELINES] #1

pielco11 opened this issue Oct 17, 2019 · 4 comments
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed

Comments

@pielco11
Copy link
Member

I know we should create specific contribution guidelines, but as of now I think that we can discuss here on how to conceive them, and at the end create our standard. Every idea is absolutely welcome.

My idea is almost this:

twint_utils has to contain 3 sub directories:

  1. tweets
  2. user_info
  3. follows

tweets will contain all the script that will use the tweets as source of information (like the media downloader), user_info will contain all the scripts that will be used to play with users' information (like a script that, given a bunch of users, extracts the ones that have "New York" as location), and follows will contain all the scripts that will use only the usernames as source of information (like the "Mutual Follows")

@EmmiBevensee
@11philip22

@pielco11 pielco11 added documentation Improvements or additions to documentation help wanted Extra attention is needed labels Oct 17, 2019
@11philip22
Copy link
Collaborator

Sounds good. I tough it would be cool to make it into a module you can import and use what you need.

@pielco11
Copy link
Member Author

At this point I guess that we can create a pip package

@EmmiBevensee
Copy link
Collaborator

This all sounds great. I will be traveling over the next couple of weeks but am pulling in some others on this because it fits into our existing project. How do you all feel about including data-viz in some of the utils? Just like a simple matplotlib mock-up? (for example if i make an external link counter for an account using TWINT and then make a bar-graph of base-urls)

@pielco11
Copy link
Member Author

@EmmiBevensee sure, that would be really useful!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed
Development

No branches or pull requests

3 participants