User:Kosboot/sandbox2

Things to consider

• Consider tying the translatathon with an event that could make a positive impact in a thematic area, such as Black History Month or Womens' History Month.
• Consider inviting a speaker to give a relevant talk. For instance, a talk on historically undervalued languages or on how the Internet helps keep languages alive.
• Once the time and place are decided, create a Wikipedia page for the event providing the details. The page should additionally function as a place to sign-up for the event, and for listing potential articles or topics that attendees may want to edit. One-line descriptions of people or topics can be very helpful to those determining which article(s) to edit. As in a typical editathon, strongly encourage attendees to register Wikipedia accounts well before the event.
• Reserve a space larger than what one would need for an edit-a-thon of equivalent size. During the translathon, attendees may be distracted by ambient discussions in different languages; more space will allow attendees working in different areas to group together.
• Identify dominant languages in the community you wish to invite. For instance, what languages are spoken by students at a University?
• Assess the organizers linguistic capabilities, and identify any gaps you may wish to fill through outreach. A Central Notice Banner across different language Wikipedias will help organizers reached logged-in editors in a specific geographic location.
• Produce promotional materials in multiple languages in order to reach more people. For instance, a poster that says Wikipedia in many languages visually demonstrates the focus of the event.
• Since attendees will be editing in numerous languages, there will be a reduction in the ability to share computers or laptops. Organizers need to ensure appropriate numbers of computers and know how to change the language settings. You may have to use virtual keyboards when translators have literacy in the language but are not used to touch-typing.
• Discuss how you will teach newbie attendees to translate across Wikipedias. For instance, attendees might focus on the lead section, or use the Content Translation Tool to translate a larger portion of the article.

When to use

See also

Results learned: What worked & Recommendations for the future: Language issues

• Creating multi-language materials to enhance environment
• Creating a Wikipedia classroom assignment geared toward having it translated at the translate-a-thon. In this particular case, the articles in English Wikipedia for Jackson Heights and Queens Pride Parade were edited by students in teams prior to the translate-a-thon. Students also presented on their work at LaGuardia's Latinx Symposium, wrote a reflection on their work and, based on those reflections, will be invited to present at the upcoming Wikipedia North America conference.
• The recommended articles list with one-line lead descriptions worked well. Several editors (both mono and multi lingual) used it to begin their work; it is recommended that we keep this model to suggest articles.
• The translation of materials created much enthusiasm; beyond that, it is the right thing to do (insert discussion on de-colonization of Wikipedia). We should push to create permanent materials in as many languages as possible. It is recommended that this is done well in advance of the translate-a-thon, as it felt like a lot of work at the last minute.

Project / Task

A translate-a-thon at LaGuardia Community College.

Why (1):

[List from the 2017 planning]

• To promote the linguistic and cultural knowledge of LaGuardia students, faculty and staff
• To help students build a sense of agency around their own learning and develop critical thinking about the information they find on the Internet
• To help students appreciate the value of their access to information as part of CUNY and as bilingual or multilingual people, and consider ways to share that value

Why (2):

From 2019:

• To understand the principles that guide Wikipedia
• To experience editing Wikipedia
• To value their access to information as bilingual or multilingual people
• To share their linguistic and cultural knowledge
• To gain the ability to discuss Wikipedia's place in the information society

Preparation

Institutional Support Translate-a-thon supported by City University of new York, Wikimedia New York City, Wikitongues, Afrocrowd, and Consumer Reports.

Promotional activity

• User:Pharos created a banner to be translated into different languages and placed in Wikipedia;
• The events page was moved into meta and its header translated from English into Chinese, German, Italian, Persian, and Spanish;
• As was the case in the first year, Wikimedia NYC created a meetup page, sent FB posts, and announced the event during the 3/20 WikiWednesday meetup;
• To promote interest in the translatathon at LaGuardia Community College, faculty held three separate film screening in March. Editors then could edit or translate the articles associated with these films;
• Tara Coleman and Thomas Cleary also appeared in an episode of Hugo Fernandez' podcast "It's On" at the LaGuardia radio station: https://soundcloud.com/wlgr/hugos-itss-on-thomas-cleary-tara-coleman?in=wlgr/sets/its-on-with-hugo-fernandez
• The LaGuardia faculty had its main poster translated into Arabic, Bangla, Chinese, French, German, Hindi, Polish, Russian, Spanish and Turkish.

Methods

• Eight trainers (2 LaGuardia faculty), 4 from WMNYC, and 2 from …?
• Day 1, Thursday April 4, 4-8: 2 presentations (at 4:30 and 6 pm) on introduction to editing; lightening talk at 7 pm.
• Day 2: Talk on Wikipedia principles (at 11:30 am and 3 pm)
• Talk on Historically Undervalued Languages & Wikipedia as a Tool for Language Advocacy (12 pm)
• Talk on How the Internet Helps Keep Languages Alive (2 pm)
• Talk on Wikidata (4:30 pm)

Articles to work on

• List of neighborhoods lacking articles in Arabic, Bengali, Burmese, Chinese, German< Grench, Haitian Creole, Hindi, Japanese, Korean, Portuguese, Romanian, Russian and Spanish
• Parades in NYC
• NYC carnivals and festivals
• LGBTQ+ topics
• films
• Women in healthcare
• specific topics assigned from DoctorXgc’s class (Jackson Heights, Queens, Queens Pride parade, Julia Rivera).

Results

Results from dashboard

• 9 articles created
• 73 articles edited
• 294 total edits
• 70 editors
• 9,100 words added
• 714,000 article views
• 18 uploads to Commons

Post-event activities

• Ximena presented at Wikimedia New York City month meeting
• Thomas presented for CUNY librarians at the LACUNY Institute
• Thomas presented with Mozucat for LaGuardia Community College Center for Teaching and Learning – Languages Across Curriculum faculty seminar

Results learned: What worked & Recommendations for the future

• The two-day format works well and should be kept for the next time
• The space needs preparation:
  • Choose room with nearby computer lab so that laptops are available
  • Use project supplied by event organizer
  • Have Bluetooth speaker available
  • Create multi-language materials to enhance environment
  • Discuss in advance most advantageous days on which to hold event
• Short presentations worked well; it is recommended that they be repeated but maybe with topics geared to a general audience. Also, we might hold such talks in a separate space so that people who want to listen can hear while others can work without distraction.
• Creating a Wikipedia classroom assignment geared toward having it translated at the translate-a-thon worked well. In this particular case, the articles in English Wikipedia for Jackson Heights and Queens Pride Parade were edited by students in teams prior to the translate-a-thon. Students also presented on their work at LaGuardia's Latinx Symposium, wrote a reflection on their work and, based on those reflections, will be invited to present at the upcoming Wikipedia North America conference.
• Emphasizing account creation before the event and signing up on the meetup page helped. Therefore, it is recommended that we create the Dashboard and events page at least a month before the event to allow classes to create accounts and sign up beforehand; it is recommended that we extend the dates of the Dashboard beyond the two days of the physical meeting so as to capture the contributions of classes working before the translate-a-thon and after it.
• The recommended articles list with one-line lead descriptions worked well. Several editors (both mono and multi lingual) used it to begin their work; it is recommended that we keep this model to suggest articles.
• The translation of materials created much enthusiasm; beyond that, it is the right thing to do (insert long discussion on the de-colonization of Wikipedia that may be presented at WikiConference USA, etc.). We should push to create permanent materials in as many languages as possible. It is recommended that this is done well in advance of the translate-a-thon, as it felt like a lot of work at the last minute.
• Videos: we only did a handful of individual short interview videos. We should work on this for future events, perhaps preparing a set list of questions, and ask students to collect these video reflections. Here are the questions:
  • Please briefly introduce yourself.
  • Have you ever edited Wikipedia before? In what language or languages?
  • What entries have you worked on, or would you like to work on?
  • Has your opinion of Wikipedia changed after what you learned about it today?

The Unclear

• Handouts with assignments and mini-lessons were created, but it is not clear whether these were used by any faculty.
• Three films were screened to attract possible editors, but it is not clear if the screenings were taken as extra-credit activities INSTEAD of participating in the thon.
• Was it a good idea to have the event early in April? Do we need more time for people to create viable assignments?

What needs to be done/will be done

• April is a month with a bazillion events; we should coordinate with other campus committees/teams to attempt a coalition so they can benefit from our work and we from theirs. We also could use more working partners; as the topic for the 2020 translatathon will be Africa and related topics (African-American, AfroCaribbean, EuroAfrican, AfroAsian, etc.), it is recommended that Fall (or even before) is spent identifying and planning with partners at LaGuardia, NYC, the U.S. and the world. Suggestions: Outside LAGCC: AfroCrowd, WikiTongues, Black Lunch Table, Caribbean Wikimedians, BMCC faculty and librarians (perhaps for them to do an event in the Fall while we do one in the Spring). At LAGCC: Latinx Symposium, Black Lit committee in English, Black Lives Matter Summit, Black Action Committee, COIL, ePortfolio seminar at the Center for Teaching and Learning, selected ELA faculty.
• Wikimedia NYC has asked for $2000 to bring Native American speakers to NYC for the 2020 thon. Since we do not know if this budget will be accepted as proposed, we should be prepared to write a grant to the Wikimedia Foundation requesting the money in case Wikimedia NYC does not get that part of the budget approved.
• Sign up on Dashboard was smoother than last year but still somewhat confusing and not all contributors were included. We need to work out how to ensure we can track everyone more effectively.
• Especially if we rely more on people bringing laptops, we need more power strips to reach all of the tables.
• Getting more people to bring classes would be useful, but we should focus on bringing in classes who have already started a project rather than just bringing students who have no idea what they will be doing there.
• We will pilot pop-up events in the Fall in the E Atrium to attract more attention and to slowly create posters to then use in the Fall. These pop-ups pop-ups may be centered around events by our partners, and/or support LAGCC faculty in including Wikipedia projects related to themes/readings/speakers next year, and then the translatathon could work on translatating those articles.
• We will create an introductory pamphlet for people who might stop by an event:
• We decided to use a spreadsheet of action items to spread out the work: https://docs.google.com/spreadsheets/d/1JhvRROfkxpm78qeinVyh_si6MvM9_XBElayQRR8XwFA/edit?usp=sharing

ARTICLE I - PURPOSE

1. Purpose. The purpose of this Conflict of Interest Policy (the "Policy") is to protect the interests of Wikimedia New York City (the "Corporation") when it is contemplating entering into a transaction or arrangement that might benefit the private interest of an Officer or Director of the Corporation or might result in a possible excess benefit transaction.

2. Relationship to Laws. This policy is intended to supplement but not replace any applicable state and federal laws governing conflict of interest applicable to nonprofit and charitable organizations.

ARTICLE II - DEFINITIONS

1. Interested Person. Any Director or Officer who has a direct or indirect financial interest, as defined herein, is an interested person.

2. Financial Interest. A person has a financial interest if the person has, directly or indirectly, through business, investment, or family:

(a) An ownership or investment interest in any entity with which the Corporation has a transaction or arrangement;

(b) A compensation arrangement with the Corporation or with any entity or individual with which the Corporation has a transaction or arrangement; or

(c) A potential ownership or investment interest in, or compensation arrangement with, any entity or individual with which the Corporation is negotiating a transaction or arrangement.

3. Compensation. Compensation includes direct and indirect remuneration as well as gifts or favors that are not insubstantial.

4. Conflict of Interest. A financial interest is not necessarily a conflict of interest. A person who has a financial interest shall be deemed to have a conflict of interest only if the Board of Directors decides that a conflict of interest exists.

ARTICLE III - PROCEDURES

1. Duty to Disclose. In connection with any actual or possible conflict of interest, an interested person must disclose the existence of the financial interest and be given the opportunity to disclose all material facts to the Directors considering the proposed transaction or arrangement.

2. Determining Whether a Conflict of Interest Exists. After disclosure of the financial interest and all material facts, and after any discussion with the interested person, they shall leave the Board of Directors meeting while the determination of a conflict of interest is discussed and voted upon. The remaining Directors shall decide if a conflict of interest exists.

3. Procedures for Addressing the Conflict of Interest.

(a) An interested person may make a presentation at a Board of Directors meeting. After the presentation, they shall leave the meeting during the discussion of, and the vote on, the transaction or arrangement involving the possible conflict of interest.

(b) The presiding officer of the Board of Directors shall, if appropriate, appoint a disinterested person or committee to investigate alternatives to the proposed transaction or arrangement.

(c) After exercising due diligence, the Board of Directors shall determine whether the Corporation can obtain with reasonable efforts a more advantageous transaction or arrangement from a person or entity that would not give rise to a conflict of interest.

(d) If a more advantageous transaction or arrangement is not reasonably possible under circumstances not producing a conflict of interest, the Board of Directors shall determine by a majority vote of the disinterested Directors whether the transaction or arrangement is in the Corporations's best interest, for its own benefit, and whether it is fair and reasonable. In conformity with the above determination it shall make its decision as to whether to enter into the transaction or arrangement.

4. Violations of the Conflicts of Interest Policy.

(a) If the Board of Directors has reasonable cause to believe a person has failed to disclose actual or possible conflicts of interest, it shall inform said person of the basis for such belief and afford him or her an opportunity to explain the alleged failure to disclose.

(b) If, after hearing said person's response and after making further investigation as warranted by the circumstances, the Board of Directors determines the person has failed to disclose an actual or possible conflict of interest, it shall take appropriate disciplinary and corrective action.

ARTICLE IV - RECORDS OF PROCEEDINGS

1. Minutes. The Minutes of the Board of Directors shall contain:

(a) The names of the persons who disclosed or otherwise were found to have a financial interest in connection with an actual or possible conflict of interest, the nature of the financial interest, any action taken to determine whether a conflict of interest was present, and the Board's decision as to whether a conflict of interest in fact existed; and

(b) The names of the persons who were present for discussions and votes relating to the transaction or arrangement, the content of the discussion, including any alternatives to the proposed transaction or arrangement, and a record of any votes taken in connection with the proceedings.

ARTICLE V - COMPENSATION

1. Compensation. A voting member of the Board of Directors who receives compensation, directly or indirectly, from the Corporation for services is precluded from voting on matters pertaining to that member's compensation.

ARTICLE VI - ANNUAL STATEMENTS

1. Annual Statement. Each Director and Officer shall annually sign a statement which affirms such person:

(a) Has received a copy of the Conflict of Interest Policy;

(b) Has read and understands the Policy;

(c) Has agreed to comply with the Policy; and

(d) Understands the Corporation is charitable and in order to maintain its federal tax exemption it must engage primarily in activities which accomplish one or more of its tax-exempt purposes.

ARTICLE VII - PERIODIC REVIEWS

1. Periodic Reviews. To ensure the Corporation operates in a manner consistent with charitable purposes and does not engage in activities that could jeopardize its tax-exempt status, periodic reviews shall be conducted.

2. Content of Reviews. The periodic reviews shall, at a minimum, include the following subjects:

(a) Whether compensation arrangements and benefits are reasonable, based on competent survey information, and the result of arm's length bargaining; and

(b) Whether partnerships, joint ventures, and arrangements with management organizations conform to the Corporation's written policies, are properly recorded, reflect reasonable investment or payments for goods and services, further charitable purposes and do not result in inurement, impermissible private benefit or in an excess benefit transaction.

3. Use of Outside Experts. When conducting periodic reviews, the Corporation may, but need not, use outside advisors. If outside experts are used, their use shall not relieve the Board of Directors of its responsibility for ensuring periodic reviews are conducted.

Category:Policy