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
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".
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.mdthat 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
docsseems to be about "how" and "why".