@NForrester and I will have a conversation next week to address the closure of this ticket, so I will edit the task to update the Due Date accordingly, thanks @Aklapper!

Weekly updates

In T347281#9708851, @leila wrote:

@Pablo is it fair to say you're done with this task and I should move it to review and take it from there?

Weekly updates

@fkaelin thanks to you for the quick fix! I will therefore proceed to close this ticket as solved.

@fkaelin: @KCVelaga just reported that the latest time partition of risk_observatory.revert_risk_predictions is 2023-12. As I would expect having data from January and February 2024, did something happen with the airflow dag?

Weekly updates

In T356740#9636143, @Aklapper wrote:

Then I'm afraid this is the wrong tool. Phabricator tasks are used for planning and managing work, not for retrospectives. :)

Thanks @Aklapper! (although weekly updates via Phabricator is a well-established practice in our team for managing work)

In T358095#9667238, @Kn138 wrote:

Am I still able to submit a notebook before April 2? I've been working on my notebook since my first post on March 19 and it would be very unfortunate for my work to go to waste :(

@Kn138 Yes! Although we have no longer capacity to provide feedback on notebooks, candidates (having received feedback or not) may submit their final notebook by April 2.

@Ansha_Pashine: the dataset we have provided for this task only contains articles maintained by WikiProject Climate change, so there is no need to explore other Wikiprojects at this time.

Message from the project mentors regarding generative AI

In the process of providing feedback to applicants we have found some notebooks with very similar responses to specific to-dos. Their style resembles that generated by AI tools such as ChatGPT. We believe that these tools can be useful in some specific cases (e.g., proofreading for non-native speakers of English). However, if AI tools are used, the final notebook must clearly indicate where and for what purpose.

In T356498#9658551, @MahimaSinghal wrote:

In T356498#9658497, @Pablo wrote:

Message from the project mentors regarding submission

• The project already has strong applicants and we will no longer provide feedback to any more applicants.
• We are working on the feedback to applicants that shared their notebook with us by last Friday’s deadline.
• If you have received feedback from the mentors, we recommend that you include a section in your final notebook briefly listing all the changes you made to address our comments.
• Please remember that April 2, 2024 4pm UTC is the deadline for ALL applicants to record contributions and create a final application.

Thank you, @Pablo, for the valuable information. I would like to clarify whether we should include the feedback received and how we addressed it in the contributions recorded on the Outreachy website, or if it should only be documented in the final notebook.

@MahimaSinghal: briefly listing in your final notebook all the changes you made to address our feeback is enough.

1. Message from the project mentors regarding submission

1. Message from the project mentors regarding submission

Weekly update:

Weekly updates

Hi @Shail_pujan8 @Anshikaagarwal024 @Iprincyy! Please read the task description above and visit the microtask (T358095) to start contributing.

Weekly updates

Weekly update:

Weekly update:

@fkaelin, since you already managed to automate the data collection process, are you OK with me closing this ticket?

Weekly update:

Weekly update:

Weekly updates

@Maryann-Onyinye got it, thanks for the quick response!

@leila we will share the next version of the document for your review once is completed, but please let us know if you prefer to close this ticket and handle everything in T347281.

Hi @Maryann-Onyinye. This task and T358095 are shared in the submission description on Outreachy for applicants to engage with the project and its tasks. However, the visibility of both tasks is no longer public. Please let us know how we should proceed, thanks!

Weekly updates

Weekly update:

Thanks @Maryann-Onyinye for the reminder! We are currently working on the submission on Outreachy's website.

Weekly updates

Weekly update:

Weekly update:

Resolving this ticket as I already shared the data with @Samwalton9-WMF and @jsn.sherman (thanks @fkaelin!)

Thanks @Maryann-Onyinye! I just added the project to Mediawiki. In the next few days we will be working on the definition of the MicroTasks, submit the project on Outreachy's website and promote it via the mailing lists.

Weekly updates

• The two sample notebooks and related doc were reviewed
• I started pulling data to get familiar with Prometheus and Webrequest info

Weekly update:

Weekly update

Weekly updates

Thanks @Peachey88! The purpose of this ticket is to report my weekly updates to my manager @XiaoXiao-WMF on a sensitive Security project described at https://phabricator.wikimedia.org/T353547, so there is no ideal ACL group for that purpose. Wouldn't access to individuals be the best option in this case?

@Aklapper: How can I make this task only visible to those I subscribe to (for now @XiaoXiao-WMF)?

@fkaelin: if you have the values already computed and stored in the cluster, please share the path with @Samwalton9-WMF and @jsn.sherman

Weekly update

• An executive summary has been added to the document.
• The structure of the document has also been slightly modified to make it easier to read for people less familiar with this work.

Weekly update

Weekly update:

As @TAndic mentioned above, our work on this task for Q2 is complete.

Weekly updates

Weekly updates

Weekly update:

Weekly update:

Weekly updates

Weekly updates

Weekly updates

Weekly updates

Weekly update:

Hi @FNavas-foundation! Please find my answer to your questions below:

Weekly updates

Weekly updates

Weekly update:

• @leila and @Cervisiarius shared their feeback to our proposal (thanks!), so @KinneretG and I will review it during our next week's 1:1.

Weekly update

Weekly update

• We reviewed/contributed to the draft metric logic and relationships slide, the EasyRetro board, and the summary of the working group process.

@XiaoXiao-WMF, good topic for our today's 1:1 conversation :)

Weekly updates

Weekly update

Weekly updates

Weekly updates