tournesol-app / tournesol-meta Goto Github PK
View Code? Open in Web Editor NEWThis repository raises non-technical issues of Tournesol.
This repository raises non-technical issues of Tournesol.
On the figure, Munin is not running because OOM, therefore, there are reports on Telegram
3. Buy a new server and migrate to it (database, website, ...). Freeze the DB for some time (showing "technical difficulties"), copy and run on the new instance. Set up a tunnel for apache traffic to go there before DNS changes
We decided to send alert to a discord channel
Our bank account details:
IBAN CH42 0900 0000 1569 4102 5
BIC POFICHBEXXX
We need to upload a paper on ArXiV describing Tournesol overall, so that we can be more easily cited by academic papers (like my upcoming papers 😜).
I'll work on a first draft to upload quickly soon.
(the advantage of ArXiV is that we can be easily cited, while regularly updating the paper)
Using the boilerplate backend django application, ensure that our ansible infra serves the application.
This might be best reviewed by @elineda
Instead of having multiple columns per feature, we want to have separated table with columns (scores x feature_name x weight)
Right now, the wiki accesses the DB using an extension https://github.com/tournesol-app/django_mediawiki_auth_postgres
A better way is to use the Token auth, or the password auth inside the php script. This way, we don't have to have access to the database from the wiki user.
Blocks wiki contributions
Endpoint /videos, GET request returns sorted list of videos using parameters:
The video must be sorted based of the sum of scores per criteria multiplied by their weights <CRITERIA_NAME_WEIGHT>
The returned video must contain most of the data about the video (most fields available on the Video and VideoCriteriaScores model)
Optional:
Add search
parameter for a text search using title / metadata of the videos. Discuss with @lfaucon and @lenhoanglnh if you want to implement this feature
PeerTube (source) is an open-source alternative to Youtube. Videos are hosted on a decentralized server network and bandwidth is shared between users.
An ethical recommendation system like Tournesol could be an interesting feature for Peertube users, who are usually concerned about Youtube supremacy.
Peertube works with plugins that can be installed by instance administrators. So creating a Tournesol plugin for Peertube is probably the way to do.
Note that it's probably a little more work than #48, because it requires to evaluate non-Youtube videos. In particular, evaluating videos that belongs to a federated network and not a central website is probably not that simple, but SepiaSearch, the new Peertube's global search engine, could be used here.
If the Tournesol organization appreciate this suggestion, it makes sense for the organization to host a Peertube instance dedicated to the Tournesol project, in order to work on this plugin and let users test it and send feedback. To kill two birds with one stone, maybe @lenhoanglnh could also use this instance to share its science videos on a more ethical platform.
Create pitch videos. Here are the scripts to be reviewed:
EN: https://docs.google.com/document/d/1imc6v6K_-zjDqBZ5ifkwEBDRqKD-Jznm2lsVxOCwioY/edit
FR: https://docs.google.com/document/d/1deA6TzFHW27x2DPndf0Jtir16MxcXzx2_YGfS0HeK10/edit
This ticket would benefit greatly from having data in one's local database #42
ml_train
.On tournesol-backend:
python manage.py runserver
does not crash)(can be discussed)
This ticket will be complete when tournesol-backend provides API endpoints for creating users, resetting passwords and authentication.
For crowdfunding.
Create endpoints for a contributor to create, update, delete, fetch, and list his/her own comparisons.
Updates must be possible with partial data for example a contributor submitted comparisons on multiple criteria, but is now sending to the server that he/she updates a single criteria.
The implementation must be careful about handling comparisons between videos X & Y, and comparisons between videos Y & X.
This is best done by keeping the API as similar as possible to the previous implementation, unless there are good reasons to change it.
Details:
The endpoint should be /comparison/
Create a short document aggreed on by @lenhoanglnh @sergeivolodin @aidanjungo and @lfaucon describing Sergei's role
For crowdfunding.
There are several open-source Youtube clients:
These are front-end alternatives that allow users to watch Youtube videos without sending too much information to Google with interesting features like the ability to follow channels without a Google account.
Since these client have a full control on the UI, they have full control on how to recommend videos to users. Therefore it makes sense here to use an alternative to the Youtube recommendation system, such as Tournesol.
Their users are probably concerned about Youtube supremacy so it could be an efficient way to offer Tournesol to people that want it, and to promote the project. Their developers may accept to add such a feature in their code base if it's well integrated on the UI.
So I wonder if the Tournesol organization and community would want to give some resources and time to contribute to these projects this way.
Edit: having a good recommendation API that allows developers to easily retrieve recommendations and use them in their project (that can be an alternative Youtube client or something else) is probably a good approach.
The script or django management command should be commited to the repository (probably in a scripts/
folder) and usage should be documented
Once the new server is ready to be online. Write a script to import the data from our old database into the new backend db.
One-shot donations: https://wemakeit.com/pages/start-a-project
Code of the current frontend should be added to tournesol-frontend repository. Additionally implement possibility to serve and develop on the app locally
Figure out whether we can:
Tournesol contributors should be able to manipulate their rate later list: The need to add, fetch, list, or delete from their rate later list using the api endpoint /rate_later
As far as I understand, here are the steps to be taken.
Once the backend exposes API enpoints for authentication. Implement such authentication on the frontend. This is best done by reusing the previous implementation, unless there are good reasons to change it.
This ticket should also include:
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.