Hey @awight @Simulo I have made my contribution for this task by writing summary of 3 articles your feedback will be appreciated.
Analysing the use and perception of Wikipedia in the professional context of translation
Link: https://www.jostrans.org/issue23/art_alonso.pdf
Author: Elisa Alonso
Suggested by: Akansha Jaiswal

Hello @awight @Simulo , for this task I write python code which uses the csv and subprocess modules to read data from a CSV file, initialize a Git repository, and then parse the data at each commit in the repository's history. The parsed data is stored in a list of dictionaries, with each dictionary representing a row in the CSV file. parse_csv function reads the contents of a CSV file using csv.DictReader, which returns an iterator of dictionaries representing each row in the file. The function appends each row to the data list. subprocess module is used to initialize a new Git repository with git init, add the initial CSV file to the repository with git add, and commit the file with git commit. The code then loops over all commits in the Git history using git log and checks out each commit with git checkout.The timestamp of each commit is obtained using git show with the --format option and parsed using datetime.strptime. Finally, the code exports the data list as a flat structure CSV file with an additional column for commit timestamp using csv.DictWriter.
Here is my contribution link for this task - https://github.com/akanshajais/Configuration_evolution_over_time and i am looking forward for your feedback and guidance.

Hello @Simulo and @awight , I tried to do this task to record my contribution with approach of read all the .yaml files in the config directory of the cxserver repository, except for the files listed in the question. For each file, it reads the YAML data, extracts the supported language pairs, and appends them to the supported_pairs list and then stored it in csv file .
Here is my contribution link https://github.com/akanshajais/Extract-cxserver-configuration-and-export-to-CSV Looking forward for you feedback and suggestions.
I am also attaching my resulted CSV file .
{F36918181}

In T331207#8685153, @Simulo wrote:

general Feedback:

• Age: Please use brackets that go up to 70 or 80, not just "50 or older" (I used only the few first brackets in my example, simply because I did not want to write a very long list)
• Name: I am curious: Why do so many surveys ask for a name? What do you want to do with it in your analysis?
• Type of content to translate: Quite some surveys ask for "What type of online content do you translate?". The tool we analyse in this task is primarily used to tranlsate Wikipedia articles. You can ask what content people usually translate if you have a particular interest in that, but the tool in question does not aim to be used e.g. to translate social media posts.

If you just get started or review your survey draft, please also consider the newly added links in the task description:

• 12 Tips For Writing Better Survey Questions, Jeff Sauro, measuringu
• Writing surveys that work, Rebecca Weiss, Mozilla

@Simulo and @awight Could you please tell us the format like in what format we have to submit our work .Is the pdf format is good or i have to write my work in this section???

Hello @Simulo and @awight, I am Akansha Jaiswal . I read “Digital Divisions of Labor and Informational Magnetism: Mapping Participation in Wikipedia.” paper to write down a brief summary from the article and given key points, I also write a list of hypotheses and "informed guesses", anchoring each with snippets from the paper in this pdf.
I am looking forward for your feedback and suggestions.

Hello @awight and @Simulo , my contribution link for this microtask "survey for content translation users" is http://localhost:9001/p/Akansha_outreachy_contribution. I look forward for your suggestions and feedback . As according to my analysis to fill this survey a sample of population will use which comes under simple random sampling just because I add some nominal and interval relevant questions to keep survey short and informative that will be easy for analyzing the data .