Page MenuHomePhabricator

[Outreachy 2022] Hybrid event production for QueeringWikipedia 2023 for intern
Closed, ResolvedPublic

Description

IMPORTANT: Make sure to read the Outreachy participant instructions and communication guidelines thoroughly before commenting on this task. This space is for project-specific questions, so avoid asking questions about getting started, setting up accounts, etc.
IMPORTANT: Outreachy is not first-come-first-get competition, rather focused on learning process and quality of work. If you think you are quick in doing and easy task that was made for 2 days of work in 2 hours or even less, then likely you missed some aspect of learning opportunity and quality of contribution. At minimum consider sleeping over and then again self-review your submission before asking mentor for to review it.
NOTE: Feel free to ask questions in the Zulip outreachy chat (Read: What is Zulip?!).

Project title: Hybrid event production for QueeringWikipedia 2023 for Outreachy 2022 intern

Summary: We are looking for an intern that is both informed and enthusiastic over the work with LGBT+ community *(sensitive to issues of safety and privacy) and tech savvy to help run the registration system, setup a public website and execute a plan of tech production for a live hybrid event Queering Wikipedia 2023, which is due in the first half of year.

Skills: Intermediate familiarity Free/Libre/Open Source Software and more specifically command line interface on POSIX platforms, knowledge of HTML & CSS, basic understanding of JavaScript, MediaWiki and web media (file formats, montainers, codecs), ideally familiarity with FLOSS streaming technologies and open protocols *(as used by Jitsi and BigBlueButton)* or at least the willingness to learn. Design/UX skills welcome, but not required.

Mentors:@Zblace, @OwenBlacker and @frederic_ed will co-mentor this with other QueeringWikipedia 2023 tech. organizing team members (team still to be established)

General tasks:

  • Test technical setups of server platforms (primarily FLOSS, likely Jitsi and BBB) and client side consumption/interaction for different modalities of hybrid events (with special focus on inclusivity and simplicity).
  • When possible adapt and customize software with information and branding for the explicit use case.
  • Support event participants coming from different levels of tech know-how, backgrounds/languages/parts of the world/infrastructural limitations and types of hardware/software setup to participate and contribute.
  • Document both optimal and minimum-base setups, its possible issues in practice (especially on accessibility).

MORE DETAILS on QueeringWikipedia (QW for short)

CONTEXT: In 2019 the WM LGBT+ User Group planned its first global conference of members, supporters, partners and people interested in LGBTQIA topics and Wikipedia/Wikimedia scheduled to be in May 2020, in Linz (AT) with support of Wikimedia Austria and under the name QueeringWikipedia. https://meta.wikimedia.org/wiki/Queering_Wikipedia
The pandemic delayed the conference and plans changed to develop different online and hybrid events, developed during the first annual UG meeting QW Working Days in 2021. In 2022 LGBT+ UG looks forward to organize QW Meeting sessions in October and November, to advance work to QueeringWikipedia Conf. in 2023. For this we need intern assistance.
We have several Wikimedia affiliates (including WM DE and WM UK who have explicit experience in hybrid event organizing) interested in supporting with know-how and hours.

AIMS & GOALS: For 2022 the User Group would like to develop capacity to deliver online and trans-local hybrid events that are more accessible, diverse, inclusive and equitable, as well as better online coordination, working together and online socializing. The needs include consideration of abilities to use multiple languages, access to different services/software setups, low hardware requirements, scalability for different network setups (both bandwidth and anonymity). For this reason we would like to test, setup, customize, deploy and document different services, software and hardware. Preferences would be with FLOSS and self hosting.

IMPACT: This project would ideally inform and inspire both the WM LGBT+ User Group members (with services matching specific needs and branding) and the wider Wikimedia community with proactive work in the field of hybrid event making that aligns with movement values and priorities (not just using business or entertainment commercial services). Hopefully this could also extend to FLOSS projects that can benefit from interaction (at least feedback and visibility, but also potentially mutual support).

OUTPUTS: Website and its content, including documented tests, experience and customized configurations of software and services targeting use of non-privileged participants *(both for tech accessibility, but also with safety concerns).

NEED: In the Outreachy program we would look to attract candidates that are knowledgeable of media systems and willing to spend time both following precise instructions, researching and experimenting on different setups, as well as to document them with support of the WM LGBT+ User Group. Wikimedia volunteers and affiliate staff members may also be available for support.

RESOURCES: WM LGBT+ User Group commits at least 6 hours a week for 3 months:
at least one continuously engaged mentor for 2 hours/week,
at least 2 other interchangeable mentors for another 2 hours/week and
at least 2 advisors and assistance individuals for specific issues for 2 hours/week.
Depending on funding available and support from Wikimedia professionals this might expand.

Related Objects

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes

@Zblace This looks good to me overall, thank you for adding it :) We can maybe refine this a little bit to bring more clarity, for example, to microtasks and final project outcomes, where to document them, and what they would look like.

As the deadline is in a day, I'd recommend following Step 4 here https://www.mediawiki.org/wiki/Outreachy/Mentors to upload this on the Outreachy website as an immediate step.

@srishakatux I updated few points, but not sure if that was enough.

btw @frederic_ed is in your timezone if in need of feedback and I am off.

Hi @srishakatux, where can I request permission to be added to the Outhreachy mentor group?

@frederic_ed You can ignore that for now. As an immediate step, I need one of the mentors of this project to create an account and sign up as a mentor in the Outreachy administration system https://www.outreachy.org/ and after that upload the proposal here https://www.outreachy.org/outreachy-december-2022-internship-round/communities/wikimedia/submit-project/. Deadline is in a few hours away. Though I have requested a day's extension for this project, it will be very helpful if you could upload the proposal asap. Thank you! cc @Zblace

@frederic_ed @Zblace @OwenBlacker Thanks for getting the proposal up on the Outreachy website on time :) I have a few more comments/suggestions for you to consider for making changes to proposal here on Phabricator and on Outreachy's website:

  • I see that you are asking potential interns to introduce themselves in three different chat channels, which feels like a lot to me. Could you maybe consider introducing only one of the platforms as mandatory and others as optional?
  • For microtasks, what you have listed sounds like the tasks that are part of the overall project. Microtasks are usually small, self-contained, and easy tasks that take someone 2-3 days to complete. During the contribution period, there will be many interns looking for a lot of these tasks to do over one month. So, I feel like you need to reduce the scope, break them down further and list clear steps for one to work on them. See, for example, T318453.
  • I was also wondering if there is any inspiration to gain from the following two resources regarding how to document the outcomes: https://meta.wikimedia.org/wiki/WikiProject_remote_event_participation, https://meta.wikimedia.org/wiki/Research_on_open_source_team_communication_tools

Lastly, application period opens on Saturday, so consider making your microtasks public before that and linking them from the Outreachy site.

Thank you. Hope we are not to push all the limits, though I am aware it is quite different project then what is usually proposed for Outreachy.

Thank you for fast feedback. Here are my inputs in different order:

  • Communication channels: I was not sure how to read that text and interface that gave me too many options *(rendering 3 new option forms each time I log in) with too many details... My assumption was that we all use Zulip for Outreachy *(love it if that is the way) and the rest were all optional communication channels for the community involved with QW, so I listed them all. Also I did not know which to prefer so I filled in by status and importance, but was also not sure how to mark them *(now added more descriptions).
  • Inspiration: Yes I am member of CROW almost since the start, but will check more closely into second link on how to use it for making tasks. Hope @frederic_ed, @OwenBlacker and few others can also help to create a tasks for Saturday and later in the process :-)
  • Mikrotasks: Yes that was good example to follow. I just created first few. First one is maybe 3 days of work or even more depending on research part and previous know-how? Next are twin tasks for 2 days of work or even less but they expect some work from first as done online-only events and hybrid events.

Thank you. Hope we are not to push all the limits, though I am aware it is quite different project then what is usually proposed for Outreachy.

Thank you for fast feedback. Here are my inputs in different order:

  • Communication channels: I was not sure how to read that text and interface that gave me too many options *(rendering 3 new option forms each time I log in) with too many details... My assumption was that we all use Zulip for Outreachy *(love it if that is the way) and the rest were all optional communication channels for the community involved with QW, so I listed them all. Also I did not know which to prefer so I filled in by status and importance, but was also not sure how to mark them *(now added more descriptions).

Yes, you are right. I also realized it later while reviewing another project that it's because of the way interface accepts response to the chat channels related question. If you would prefer to use your own channel, that's totally fine. But you are also welcome to use Wikimedia's Zulip and make a separate topic under https://wikimedia.zulipchat.com/#narrow/stream/336167-outreachy25 for your project to chat w/ potential candidates. But maybe just make it clear which ones for which on the Outreachy website.

  • Mikrotasks: Yes that was good example to follow. I just created first few. First one is maybe 3 days of work or even more depending on research part and previous know-how? Next are twin tasks for 2 days of work or even less but they expect some work from first as done online-only events and hybrid events.

They are looking good. I've one minor comment. I see that you say in the description, "We will send you a reply to say whether it is accepted or not on the talk page for the contribution." I'd encourage you to continuously give feedback on interns' contributions but not disclose whether they are "accepted" or "rejected," as that may discourage them from further participation. The application period is also a good learning exercise :)

Hello, I am Gbemisola Esho an outreachy applicant who will like to contribute to this project.

Hello, I’m Bishops!
Outreachy applicant and I’d love to be a part of this project as a contributor!!
Looking forward to hearing from you!

This comment was removed by Feyii.
Zblace updated the task description. (Show Details)

@Notjob consider to communicate on Zulip questions that are not specific to individual tasks.

@Zblace so sorry, i have not been settled since yesterday.
Having gone through the tasks, I'll be working on the front-end microtask. T317083

I hope that's okay? is there a deadline pls?

@Notjob consider to communicate on Zulip questions that are not specific to individual tasks.

so sorry, i have not been settled since yesterday.
Having gone through the tasks, I'll be working on the front-end microtask. T317083

I hope that's okay? is there a deadline pls?

That is not OK @Notjob. It is find that you work on that microtask, but it is owned by @Slst2020 as part of other project.

That is not OK @Notjob. It is find that you work on that microtask, but it is owned by @Slst2020 as part of other project.

wow maybe I'm mixing the whole projects up.

could you pls give a quick walk through, and is it possible to work on multiple projects?

I believe you are in charge of project T319310, yes? but I could not find the task assigned to said project.
I'm still trying to find my way around the site, could you pls point me to where the tasks are stated?

@Notjob read this page even more carefully and you will find links to where to ask questions and to tasks.

@Notjob read this page even more carefully and you will find links to where to ask questions and to tasks.

I have gone through the tasks, but it doesn't seem clear to me. I am proficient in HTML/CSS/JS(React.Js), but I don't see clear cut instructions on implementing said skills. I am confused.

I can not help individually here about general comprehension and will remove my previous comments from here, as this should be discussion in Zulip (link provided above).

I can not help individually here about general comprehension and will remove my previous comments from here, as this should be discussion in Zulip (link provided above).

Alright thanks

I am available on https://meet.jit.si/QW2023outreachy for the next hour or so if need be...

Thanks to everyone for participating in this effort.
Outreachy.org will be delivering results in 2 weeks from now if all is OK

Zblace renamed this task from Hybrid event production for QueeringWikipedia 2023 with Outreachy intern to Hybrid event production for QueeringWikipedia 2023 for Outreachy 2022 intern.Nov 18 2022, 4:11 PM
Zblace updated the task description. (Show Details)

We just got an email from Outreachy that there is 24 hour delay, but results should be available later tomorrow. Once more thank you for your efforts and hopefully continuous involvement with both Wikimedia and Wikimedia LGBT+ UserGroup regardless of results.

Zblace claimed this task.
Zblace triaged this task as Medium priority.
Zblace renamed this task from Hybrid event production for QueeringWikipedia 2023 for Outreachy 2022 intern to [Outreachy 2022] Hybrid event production for QueeringWikipedia 2023 for Outreachy 2022 intern.Nov 23 2022, 2:07 PM
Zblace renamed this task from [Outreachy 2022] Hybrid event production for QueeringWikipedia 2023 for Outreachy 2022 intern to [Outreachy 2022] Hybrid event production for QueeringWikipedia 2023 for intern.

@Zblace This is the main task related to the Outreachy project that I recommend keeping open till the project continues. If the related microtasks are complete, consider closing them and leaving them unassigned. I suggest @Andrerodriguex create a subtask of this project, self-assign it, and use it to track/update progress.

@Zblace I see that @Andrerodriguex has already added final project outcomes here: https://www.mediawiki.org/wiki/Outreachy/Past_projects#Round_25. Please consider changing the task status to resolved if you consider it as done. Thank you :)

Closing this task as Outreachy-25 finished three months ago and this task is tagged with Outreachy-25 only. (If this task should remain open, feel free to reopen and add an active project tag so this task can be found on a corresponding workboard - thanks!)