arguellesm / faux Goto Github PK

Every PR should trigger the tests from /test on its own code. They all need to pass for the PR to be approved and merged.

As the executive department of a social network platform, we'd like to warn users about posts from news accounts that might contain fake or misleading information.

We can't currently predict whether an article contains misleading information or not. It should be possible to do something like:

article.predict()

to get a index representing how misleading or fake that article is.

Self explanatory.

To reach milestone 0.0.3 we need to create an entity that contains an article, for this I've created the class 'Article' to satisfy #2 .

We'll be using Poetry, reasons can be found here.

Once the base image from #15 is chosen, we should create our test container.

We'll be using two different tools for CI. To select these tools we stablish the following requirements:

• Free tier option, preferably with no credit card required.
• Cloud-based.
• GitHub integration.

As part of an NPO concerned with protecting users from pseudoscientific and harmful information, we'd like to contribute to flag possibly fake and dangerous information.

We'll use a container for testing purposes. To create this container we will first need to choose a docker base image. This requires:

• Stating our criteria.
• Listing options.
• Comparing those options based on said criteria.
• Choosing the best one.

Create tasks.py to set up task functions for Invoke.

As a user, I'd like to fact-check articles about things I'm not an expert on but that I believe might be fake.

There are no availble tests to ensure minimum viability on whatever product is used for Milestone 0.2.0.

These tests should at least include the Article class requirements described in Milestone 0.1.0.

Once the container from #16 is developed, we should set up a workflow that automatically pushes and builds the container whenever a relevant change is merged into our Github repository.