You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 14, 2023. It is now read-only.
It is a little hard to figure out exactly what each "app" container is for, even thought the names are descriptive. I think it'd be helpful to have a high-level, one-sentence description of each all together in one file. Perhaps make a mediacloud/apps/README.md that looks like this:
rescrape-media - When a new media source is added, scrape it to find RSS/Atom feeds to add.
crawler-provider - Pull stories from RSS feeds by periodically adding jobs to a "fetch-RSS" queue
crawler-fetcher - Grab fetch-RSS jobs off a queue and grab any new stories
etc.
Just one sentence for each app explaining what its primary function is. I think that'd help quite a bit in terms of spinning up new people (and communicating amongst ourselves). I suggest putting it in with the code because this is about "what" the code in that folder is, while most of the stuff in docs seems to be about "how" and "why".
The text was updated successfully, but these errors were encountered:
Oh, those are great! Didn't know they were there. Many are good, but I agree some are too short - for instance "Crawler fetcher" requires a fair amount of understanding about our system to get. I think ones like "Fetch finished podcast transcripts and store them locally" are quite good. Maybe just doing one more iteration on the very short ones in there would address the difficulty I was having?
It is a little hard to figure out exactly what each "app" container is for, even thought the names are descriptive. I think it'd be helpful to have a high-level, one-sentence description of each all together in one file. Perhaps make a
mediacloud/apps/README.md
that looks like this:Just one sentence for each app explaining what its primary function is. I think that'd help quite a bit in terms of spinning up new people (and communicating amongst ourselves). I suggest putting it in with the code because this is about "what" the code in that folder is, while most of the stuff in
docs
seems to be about "how" and "why".The text was updated successfully, but these errors were encountered: