APC Writer's Wiki - User contributions [en]

Style guide

2019-04-17T06:33:53Z

Namita:

[[File:style.jpg|thumb|200px]]
== '''An overview''' ==

'''Clear, simple writing''' should be the goal of all contributors. Contributors need to keep in mind our large audience, that it is international, and that the majority of our readers are not native speakers of English. When writing it is important to ask, can my reader understand this? Use clear, simple language, making sure that you do not use phrases that might not make sense when directly translated. Examples include phrases such as "keeping your hand in", "putting a lid on it" or "having a clear head".

'''Never write gender blind''', and try to use as few references as possible to gender blind material. It rarely matters what a women wears, what her age or marital status is, or her sexual orientation. These are only relevant if they are important for a point being made. Read an alternative paragraph/sentence aloud, just to see if it makes sense without that material.

Always refer to people by '''their pronoun and gender of choice'''. Do not refer to any "alternative" (such as "born a woman") unless it is relevant to the point being made.

Refer to people in a way that empowers and strengthens – survivors of sexual abuse, people living with HIV/ AIDS. '''People are not defined by trauma, disease, disability or gender.'''

GenderIT.org strives to write in a style that is less formal, but '''avoid contractions''' (e.g. don’t, I’ll, isn’t) because they are often not used in other languages and might confuse non-native English speakers.

'''Do not capitalise technological terms''' because that makes them seem Far More Important and Impenetrable than they really are. So words like '''internet, information society, free/libre and open source software, gender or civil society''' should be not capitalised unless they are within proper nouns (e.g. name of programme “Gender Equality and Information Society National Plan”).

Before you start writing, make sure you are familiar with the [https://www.apc.org/en/node/35310 '''APC style guidelines'''], which deal with house style in terms of grammar and capitalisation, also available below.

In particular:

* Do not capitalise every single word in the titles and subtitles of the article.

* All acronyms must be spelled out in full when they are first mentioned in the article (remember that our primary audience are women’s organisations who are not focussed on ICTs, and who do not need to be familiar with commonly used acronyms in the field of ICTs).

* If you are citing material that is available online, always provide a link to the original source as a matter of courtesy and good internet conduct.

* Make sure you always have permission to republish any article(s) and/or photo(s) on the website from the original author/source (with the exception of writings that are sourced as APC, including APC programmes such as APC WRP or APC CIPP).

* Keep a record of the permission provided, and forward it to the Spanish or English language editors for documentation.

* You can quote 1-2 paragraphs of an article in your writing without needing prior author’s permission. Again provide a link to the original article as a matter of courtesy and good internet conduct.

* If you republish original articles written exclusively for APCNews or GenderIT.org, you must mention these as a source. Please inform the editorial team of external sites about this condition. Please refer to the [APC Editorial Policy] for more information.

* Consistently cite all resources and sources that you use in your writing.

* For interviews, please include in your submission this information about the interviewees:

** Full name
** Where s/he is based
** Where s/he is attached to professionally
** Her/his expertise in the field that is the focus of your article.

== '''Final checklist''' ==

* '''Always run a spell check!''' Make sure that you have used international or UK English throughout your contribution.

* Have you referenced in footnotes? Don't! '''Make sure all references are at the end of the document''', and referred to in square brackets: [1].

* APCNews, including GenderIT.org, uses an adapted version of the American Psychological Association (APA) style of referencing. Please refer to the [http://www.apc.org/en/system/files/APC_ReferenceGuide_2-0.pdf APC reference guide].

== '''Some examples of referencing''' ==

'''Book'''

Author, A. (year). ''Title of Work''. Location: Publisher. URL (if the publication is available online)

Gurumurthy, A. (2004). ''Gender and ICTs: Overview Report''. Brighton: BRIDGE. www.bridge.ids.ac.uk/go/bridge-publications/cutting-edge-packs/gender-and-icts/gender-and-icts&id=52909&type=Document&langid=1

'''Journal article'''

Author, A. (Year). Title of article. ''Title of Periodical, volume number''(issue number), pages (if available). URL (if online)

Coleman, S. (2005). The lonely citizen: Indirect representation in an age of networks. ''Political Communication, 22''(2), 197-214.

Salas, M. (2010). Internet, power and politics: Gender and ICTs in the movement against CAFTA. ''The Journal of Community Informatics, 6''(1). ci-journal.net/index.php/ciej/article/view/530/468

'''Newspaper article'''

Author, A. (Year, date month published). Article title. ''Newspaper Title''. URL

Chemaly, S., Friedman, J., & Bates, L. (2013, 21 May). An Open Letter to Facebook. ''Huffington Post''. www.huffingtonpost.com/soraya-chemaly/an-open-letter-to-faceboo_1_b_3307394.html

'''Web page'''

If you are citing information about an organisation, programme, campaign, etc. from a website, you can simply provide the URL.

www.takebackthetech.net/page/about-campaign

== '''And please remember to follow the language guidelines in the APC house style guide!''' ==

'''[https://www.apc.org/en/node/35310 You can access the new and simplified APC house style guide by clicking here.]'''

How to write for GenderIT.org

2018-09-03T06:09:42Z

Namita:

[[File:tool.jpg|thumb|200px]]

=='''How to write'''==

This page provides an introduction on how to write the different types of article that appear on GenderIT.org.

==='''...a Feminist Talk'''===

A Feminist Talk blog is where you get to be yourself – use more informal language, express opinions and challenge your readers. Feminist Talk pieces are usually quite short, no more than 500 words, but be warned! They are very lightly edited, if at all. If you want a Feminist Talk piece to be spell- and grammar-checked, you need to ask the editorial team.

Check previous feminist talks for reference:

[https://www.genderit.org/articles/swipe-me-left-im-dalit Swipe me left-I'm Dalit]

[http://www.genderit.org/feminist-talk/trials-confused-feminist-internet-governance-school Trials of a confused feminist (in an internet governance school)]

[http://www.genderit.org/feminist-talk/facebook-king-laid-bare-and-drag-queens Facebook: The king laid bare and the drag queens]

[http://www.genderit.org/feminist-talk/why-internet-rights-matter-africans Why internet rights matter for Africa(ns)]

==='''…an analytical article'''===

Analytical articles are to inform readers about perspectives, issues and debates, putting forward ideas. We don't expect writers to be 'objective' or 'impartial', we expect an informed, well-reasoned feminist perspective. This means in practice that you have to cite your sources, link widely and provide readers with context for your arguments. Analytical articles are expected to be between 1,500 and 2,500 words.

Rather than news conventions, academic conventions are probably most useful here. Make one point per paragraph, cite broadly to illustrate both your expertise and the precedents for your argument, establish early on the argument you are making and guide your reader through the stages that you take to get there. Make sure that when you reference your work thoroughly, particularly when you cite others.

In your analysis you can look at the root causes of an issue, draw links between personal experiences of women and historical and global processes, or examine similarities and differences in manifestation of the issue by people living in different contexts as well as their response to this issue.

Check previous analytical articles for reference:

[https://www.genderit.org/articles/do-we-need-new-laws-address-non-consensual-circulation-intimate-images-case-brazil Do we need new laws to address non consensual circulation of intimate images? The case of Brazil]

[http://www.genderit.org/articles/south-africa-pornography-and-internet-justifiable-protection-or-entrenching-patriarchy South Africa: Pornography and the internet – justifiable protection or entrenching patriarchy?]

[http://www.genderit.org/articles/argentina-strategic-use-ict-response-violence-against-women Argentina: Strategic use of ICT as a response to violence against women]

[http://www.genderit.org/content/%E2%80%98does-your-mother-know%E2%80%99-agency-risk-and-morality-online-lives-young-women-mumbai 'Does your mother know?' Agency, risk and morality in the online lives of young women in Mumbai]

==='''…an interview'''===

The most important thing to remember about interviews is that they are not verbatim transcripts. You are expected to edit the interviewee's words to make them more concise, and easier to understand, but not to censor views or change the meaning of the words.

Ask questions that draw out the interviewee, that help non-experts understand her or his perspective and the importance of that perspective on the subject. Allow them space at the end of the interview to add anything that you may not have already covered.

Lastly, think about the power relations between yourself and the interviewee. Make sure that they are comfortable with the questions beforehand, especially if they are a survivor of violence. If they are in a marginalised or vulnerable position, give them the opportunity to read the final article before it is uploaded, and make sure that they are happy with their portrayal. If the interview was conducted over the phone or similar, quote check – send them the transcript of the quotes you are using from them, to check for accuracy.

Check previous interviews for reference:

[http://www.genderit.org/articles/interview-nana-darkoa-adventures-bedroom-african-woman Interview with Nana Darkoa: Adventures from the bedroom of an African woman]

[http://www.genderit.org/feminist-talk/interview-adolescent-girls-mobile-phone-use-bihar-jharkhand Interview: Adolescent girls' mobile phone use in Bihar, Jharkand, UP]

[http://www.genderit.org/content/copyright-copyleft-why-does-it-matter-interview-heather-ford Copyright? Copyleft? Why does it matter? An interview with Heather Ford]

[https://www.genderit.org/articles/ecurfew-kashmir Curfew on solidarities Interviews with Kashmiri activists on censorship and lockdown]

Read also :
'''[[Dealing with vulnerable interviewees]]'''

==='''…an editorial'''===

Editorial usually introduces the GenderIT.org's thematic edition, we often invite a guest writer (meaning someone who is for some reason a relevant voice on the theme in focus but not necessarily a core writer) to prepare an editorial and share her/his opinion on an issue. The usual suggested length for the editorial is no more than one page, or 350 words.

The editorial is meant to introduce the theme of the edition, promote critical thinking, and encourage readers to read the edition and/or take action on the issue. They use a personal tone, and share personal opinions and experiences, including possible solutions to the issue in focus work often bests. What is extremely important for the development of the editorial is that the guest writer has in hand all the materials for the upcoming edition, so she/he can go through them and have a sense of what the edition is about, and even be able to make reference or quote the particular articles.

Check [http://www.genderit.org/previous-editorials previous editorials] for reference:

[http://www.genderit.org/editorial/tipping-balance-local-adopters-technology Tipping the balance for local adopters of technology]

[http://www.genderit.org/editorial/internet-governance-if-we-are-not-table-we-will-be-menu Internet governance: If we are not at the table, we will be on the menu]

[http://www.genderit.org/editorial/thoughts-around-claiming-communication-rights Claiming communication rights]

==='''…a resource summary'''===

Even though resources are usually pdf formatted papers or presentations that are stand alone materials, we do not just throw them on the website without an introduction that sparks the interest of the readership. Here are some simple steps to follow when writing the summary:

1) State the purpose of a document/report. Why was it written?

2) Briefly describe the scope of the report. What problem does it solve or what issues are covered?

3) Provide an overview of the research/data collection methods used. How was information for the report gathered? (if applicable)

4) State the key results and findings detailed in the report. What did you find out?

5) Present the main conclusions and recommendations. What should the reader do about it?

6) How does it relate to women’s and internet rights?

The optimal length for a resource summary is between 500-700 words.

See example: http://www.genderit.org/resources/erotics-sex-rights-and-internet-research-study

Read more: [http://www.ehow.com/how_5108728_write-report-summary.html#ixzz1UX3KgGXp How to write a report summary]

Writing for a multilingual audience: Some Do’s and Dont's for native and near-native English language writers.
APC reference guide: A thorough list of reference types and how to use them in APC and GenderIT.org publications.

=='''Checklist for ALL articles'''==

Every article submitted to GenderIT.org should contain the elements detailed in this checklist spreadsheet: [[Media:Checklist]]

Lastly check that your references meet the reference guidelines listed above.

How to write for GenderIT.org

2018-09-03T06:08:25Z

Namita:

[[File:tool.jpg|thumb|200px]]

=='''How to write'''==

This page provides an introduction on how to write the different types of article that appear on GenderIT.org.

==='''...a Feminist Talk'''===

A Feminist Talk blog is where you get to be yourself – use more informal language, express opinions and challenge your readers. Feminist Talk pieces are usually quite short, no more than 500 words, but be warned! They are very lightly edited, if at all. If you want a Feminist Talk piece to be spell- and grammar-checked, you need to ask the editorial team.

Check previous feminist talks for reference:

[https://www.genderit.org/articles/swipe-me-left-im-dalit Swipe me left-I'm Dalit]

[http://www.genderit.org/feminist-talk/trials-confused-feminist-internet-governance-school Trials of a confused feminist (in an internet governance school)]

[http://www.genderit.org/feminist-talk/facebook-king-laid-bare-and-drag-queens Facebook: The king laid bare and the drag queens]

[http://www.genderit.org/feminist-talk/why-internet-rights-matter-africans Why internet rights matter for Africa(ns)]

==='''…an analytical article'''===

Analytical articles are to inform readers about perspectives, issues and debates, putting forward ideas. We don't expect writers to be 'objective' or 'impartial', we expect an informed, well-reasoned feminist perspective. This means in practice that you have to cite your sources, link widely and provide readers with context for your arguments. Analytical articles are expected to be between 1,500 and 2,500 words.

Rather than news conventions, academic conventions are probably most useful here. Make one point per paragraph, cite broadly to illustrate both your expertise and the precedents for your argument, establish early on the argument you are making and guide your reader through the stages that you take to get there. Make sure that when you reference your work thoroughly, particularly when you cite others.

In your analysis you can look at the root causes of an issue, draw links between personal experiences of women and historical and global processes, or examine similarities and differences in manifestation of the issue by people living in different contexts as well as their response to this issue.

Check previous analytical articles for reference:

[https://www.genderit.org/articles/do-we-need-new-laws-address-non-consensual-circulation-intimate-images-case-brazil Do we need new laws to address non consensual circulation of intimate images? The case of Brazil]

[http://www.genderit.org/articles/south-africa-pornography-and-internet-justifiable-protection-or-entrenching-patriarchy South Africa: Pornography and the internet – justifiable protection or entrenching patriarchy?]

[http://www.genderit.org/articles/argentina-strategic-use-ict-response-violence-against-women Argentina: Strategic use of ICT as a response to violence against women]

[http://www.genderit.org/content/%E2%80%98does-your-mother-know%E2%80%99-agency-risk-and-morality-online-lives-young-women-mumbai 'Does your mother know?' Agency, risk and morality in the online lives of young women in Mumbai]

==='''…an interview'''===

The most important thing to remember about interviews is that they are not verbatim transcripts. You are expected to edit the interviewee's words to make them more concise, and easier to understand, but not to censor views or change the meaning of the words.

Ask questions that draw out the interviewee, that help non-experts understand her or his perspective and the importance of that perspective on the subject. Allow them space at the end of the interview to add anything that you may not have already covered.

Lastly, think about the power relations between yourself and the interviewee. Make sure that they are comfortable with the questions beforehand, especially if they are a survivor of violence. If they are in a marginalised or vulnerable position, give them the opportunity to read the final article before it is uploaded, and make sure that they are happy with their portrayal. If the interview was conducted over the phone or similar, quote check – send them the transcript of the quotes you are using from them, to check for accuracy.

Check previous interviews for reference:

[http://www.genderit.org/articles/interview-nana-darkoa-adventures-bedroom-african-woman Interview with Nana Darkoa: Adventures from the bedroom of an African woman]

[http://www.genderit.org/feminist-talk/interview-adolescent-girls-mobile-phone-use-bihar-jharkhand Interview: Adolescent girls' mobile phone use in Bihar, Jharkand, UP]

[http://www.genderit.org/content/copyright-copyleft-why-does-it-matter-interview-heather-ford Copyright? Copyleft? Why does it matter? An interview with Heather Ford]

[https://www.genderit.org/articles/ecurfew-kashmir: Curfew on solidarities Interviews with Kashmiri activists on censorship and lockdown]

Read also :
'''[[Dealing with vulnerable interviewees]]'''

==='''…an editorial'''===

Editorial usually introduces the GenderIT.org's thematic edition, we often invite a guest writer (meaning someone who is for some reason a relevant voice on the theme in focus but not necessarily a core writer) to prepare an editorial and share her/his opinion on an issue. The usual suggested length for the editorial is no more than one page, or 350 words.

The editorial is meant to introduce the theme of the edition, promote critical thinking, and encourage readers to read the edition and/or take action on the issue. They use a personal tone, and share personal opinions and experiences, including possible solutions to the issue in focus work often bests. What is extremely important for the development of the editorial is that the guest writer has in hand all the materials for the upcoming edition, so she/he can go through them and have a sense of what the edition is about, and even be able to make reference or quote the particular articles.

Check [http://www.genderit.org/previous-editorials previous editorials] for reference:

[http://www.genderit.org/editorial/tipping-balance-local-adopters-technology Tipping the balance for local adopters of technology]

[http://www.genderit.org/editorial/internet-governance-if-we-are-not-table-we-will-be-menu Internet governance: If we are not at the table, we will be on the menu]

[http://www.genderit.org/editorial/thoughts-around-claiming-communication-rights Claiming communication rights]

==='''…a resource summary'''===

Even though resources are usually pdf formatted papers or presentations that are stand alone materials, we do not just throw them on the website without an introduction that sparks the interest of the readership. Here are some simple steps to follow when writing the summary:

1) State the purpose of a document/report. Why was it written?

2) Briefly describe the scope of the report. What problem does it solve or what issues are covered?

3) Provide an overview of the research/data collection methods used. How was information for the report gathered? (if applicable)

4) State the key results and findings detailed in the report. What did you find out?

5) Present the main conclusions and recommendations. What should the reader do about it?

6) How does it relate to women’s and internet rights?

The optimal length for a resource summary is between 500-700 words.

See example: http://www.genderit.org/resources/erotics-sex-rights-and-internet-research-study

Read more: [http://www.ehow.com/how_5108728_write-report-summary.html#ixzz1UX3KgGXp How to write a report summary]

Writing for a multilingual audience: Some Do’s and Dont's for native and near-native English language writers.
APC reference guide: A thorough list of reference types and how to use them in APC and GenderIT.org publications.

=='''Checklist for ALL articles'''==

Every article submitted to GenderIT.org should contain the elements detailed in this checklist spreadsheet: [[Media:Checklist]]

Lastly check that your references meet the reference guidelines listed above.

How to write for GenderIT.org

2018-09-03T06:06:36Z

Namita:

[[File:tool.jpg|thumb|200px]]

=='''How to write'''==

This page provides an introduction on how to write the different types of article that appear on GenderIT.org.

==='''...a Feminist Talk'''===

A Feminist Talk blog is where you get to be yourself – use more informal language, express opinions and challenge your readers. Feminist Talk pieces are usually quite short, no more than 500 words, but be warned! They are very lightly edited, if at all. If you want a Feminist Talk piece to be spell- and grammar-checked, you need to ask the editorial team.

Check previous feminist talks for reference:

[https://www.genderit.org/articles/swipe-me-left-im-dalit: Swipe me left: I'm Dalit]

[http://www.genderit.org/feminist-talk/trials-confused-feminist-internet-governance-school Trials of a confused feminist (in an internet governance school)]

[http://www.genderit.org/feminist-talk/facebook-king-laid-bare-and-drag-queens Facebook: The king laid bare and the drag queens]

[http://www.genderit.org/feminist-talk/why-internet-rights-matter-africans Why internet rights matter for Africa(ns)]

==='''…an analytical article'''===

Analytical articles are to inform readers about perspectives, issues and debates, putting forward ideas. We don't expect writers to be 'objective' or 'impartial', we expect an informed, well-reasoned feminist perspective. This means in practice that you have to cite your sources, link widely and provide readers with context for your arguments. Analytical articles are expected to be between 1,500 and 2,500 words.

Rather than news conventions, academic conventions are probably most useful here. Make one point per paragraph, cite broadly to illustrate both your expertise and the precedents for your argument, establish early on the argument you are making and guide your reader through the stages that you take to get there. Make sure that when you reference your work thoroughly, particularly when you cite others.

In your analysis you can look at the root causes of an issue, draw links between personal experiences of women and historical and global processes, or examine similarities and differences in manifestation of the issue by people living in different contexts as well as their response to this issue.

Check previous analytical articles for reference:

[https://www.genderit.org/articles/do-we-need-new-laws-address-non-consensual-circulation-intimate-images-case-brazil: Do we need new laws to address non consensual circulation of intimate images? The case of Brazil]

[http://www.genderit.org/articles/south-africa-pornography-and-internet-justifiable-protection-or-entrenching-patriarchy South Africa: Pornography and the internet – justifiable protection or entrenching patriarchy?]

[http://www.genderit.org/articles/argentina-strategic-use-ict-response-violence-against-women Argentina: Strategic use of ICT as a response to violence against women]

[http://www.genderit.org/content/%E2%80%98does-your-mother-know%E2%80%99-agency-risk-and-morality-online-lives-young-women-mumbai 'Does your mother know?' Agency, risk and morality in the online lives of young women in Mumbai]

==='''…an interview'''===

The most important thing to remember about interviews is that they are not verbatim transcripts. You are expected to edit the interviewee's words to make them more concise, and easier to understand, but not to censor views or change the meaning of the words.

Ask questions that draw out the interviewee, that help non-experts understand her or his perspective and the importance of that perspective on the subject. Allow them space at the end of the interview to add anything that you may not have already covered.

Lastly, think about the power relations between yourself and the interviewee. Make sure that they are comfortable with the questions beforehand, especially if they are a survivor of violence. If they are in a marginalised or vulnerable position, give them the opportunity to read the final article before it is uploaded, and make sure that they are happy with their portrayal. If the interview was conducted over the phone or similar, quote check – send them the transcript of the quotes you are using from them, to check for accuracy.

Check previous interviews for reference:

[http://www.genderit.org/articles/interview-nana-darkoa-adventures-bedroom-african-woman Interview with Nana Darkoa: Adventures from the bedroom of an African woman]

[http://www.genderit.org/feminist-talk/interview-adolescent-girls-mobile-phone-use-bihar-jharkhand Interview: Adolescent girls' mobile phone use in Bihar, Jharkand, UP]

[http://www.genderit.org/content/copyright-copyleft-why-does-it-matter-interview-heather-ford Copyright? Copyleft? Why does it matter? An interview with Heather Ford]

[https://www.genderit.org/articles/ecurfew-kashmir: Curfew on solidarities: Interviews with Kashmiri activists on censorship and lockdown]

Read also :
'''[[Dealing with vulnerable interviewees]]'''

==='''…an editorial'''===

Editorial usually introduces the GenderIT.org's thematic edition, we often invite a guest writer (meaning someone who is for some reason a relevant voice on the theme in focus but not necessarily a core writer) to prepare an editorial and share her/his opinion on an issue. The usual suggested length for the editorial is no more than one page, or 350 words.

The editorial is meant to introduce the theme of the edition, promote critical thinking, and encourage readers to read the edition and/or take action on the issue. They use a personal tone, and share personal opinions and experiences, including possible solutions to the issue in focus work often bests. What is extremely important for the development of the editorial is that the guest writer has in hand all the materials for the upcoming edition, so she/he can go through them and have a sense of what the edition is about, and even be able to make reference or quote the particular articles.

Check [http://www.genderit.org/previous-editorials previous editorials] for reference:

[http://www.genderit.org/editorial/tipping-balance-local-adopters-technology Tipping the balance for local adopters of technology]

[http://www.genderit.org/editorial/internet-governance-if-we-are-not-table-we-will-be-menu Internet governance: If we are not at the table, we will be on the menu]

[http://www.genderit.org/editorial/thoughts-around-claiming-communication-rights Claiming communication rights]

==='''…a resource summary'''===

Even though resources are usually pdf formatted papers or presentations that are stand alone materials, we do not just throw them on the website without an introduction that sparks the interest of the readership. Here are some simple steps to follow when writing the summary:

1) State the purpose of a document/report. Why was it written?

2) Briefly describe the scope of the report. What problem does it solve or what issues are covered?

3) Provide an overview of the research/data collection methods used. How was information for the report gathered? (if applicable)

4) State the key results and findings detailed in the report. What did you find out?

5) Present the main conclusions and recommendations. What should the reader do about it?

6) How does it relate to women’s and internet rights?

The optimal length for a resource summary is between 500-700 words.

See example: http://www.genderit.org/resources/erotics-sex-rights-and-internet-research-study

Read more: [http://www.ehow.com/how_5108728_write-report-summary.html#ixzz1UX3KgGXp How to write a report summary]

Writing for a multilingual audience: Some Do’s and Dont's for native and near-native English language writers.
APC reference guide: A thorough list of reference types and how to use them in APC and GenderIT.org publications.

=='''Checklist for ALL articles'''==

Every article submitted to GenderIT.org should contain the elements detailed in this checklist spreadsheet: [[Media:Checklist]]

Lastly check that your references meet the reference guidelines listed above.

GenderIT.org editorial team

2017-06-14T14:58:49Z

Namita:

[[File:team.jpg|thumb|200px]]

Twitter: [https://twitter.com/GenderITorg @GenderITorg] and [https://twitter.com/GenderITes @GenderITes] (Spanish)

=== ''Namita Aavriti ===

GenderIT.org Project Coordinator and English Editor

Based in Bangalore, India

Language: English

Contact: namita@apcwomen.org

----

=== ''Dafne Sabanes Plou'' ===

GenderIT.org Spanish editor

Based in Buenos Aires, Argentina

Language: Spanish and English

Contact: daphne@apcwomen.org

----

== ''To reach us by mail or phone'' ==

APC Executive Director’s Office

PO Box 29755

Melville 2109

South Africa

Tel: +27 11 726 1692

Fax: +27 11 726 1692

GenderIT.org editorial team

2017-06-14T14:46:34Z

Namita:

[[File:team.jpg|thumb|200px]]

Twitter: [https://twitter.com/GenderITorg @GenderITorg] and [https://twitter.com/GenderITes @GenderITes] (Spanish)

=== ''Namita Aavriti ===

GenderIT.org Project Coordinator and English Editor

Based in Bangalore, India

Language: English

Contact: namita@apcwomen.org

----

=== ''Dafne Sabanes Plou'' ===

GenderIT.org Spanish editor

Based in Buenos Aires, Argentina

Language: Spanish and English

Contact: daphne@apcwomen.org

----

=== ''Katerina Fialova'' ===

Knowledge Building Coordinator

Based in Czech republic

Language: English

Contact: katerina.fialova@apcwomen.org

----

== ''To reach us by mail or phone'' ==

APC Executive Director’s Office

PO Box 29755

Melville 2109

South Africa

Tel: +27 11 726 1692

Fax: +27 11 726 1692

GenderIT.org editorial team

2017-06-14T14:44:20Z

Namita:

[[File:team.jpg|thumb|200px]]

Twitter: [https://twitter.com/GenderITorg @GenderITorg] and [https://twitter.com/GenderITes @GenderITes] (Spanish)

=== ''Namita Aavriti ===

GenderIT.org Project Coordinator and English Editor

Based in Bangalore, India

Language: English

Contact: namita@apcwomen.org

----

=== ''Dafne Sabanes Plou'' ===

GenderIT.org Spanish editor

Based in Buenos Aires, Argentina

Language: Spanish and English

Contact: daphne@apcwomen.org

== ''To reach us by mail or phone'' ==

APC Executive Director’s Office

PO Box 29755

Melville 2109

South Africa

Tel: +27 11 726 1692

Fax: +27 11 726 1692

GenderIT.org editorial team

2017-06-14T14:42:32Z

Namita: /* Namita Aavriti */

[[File:team.jpg|thumb|200px]]

Twitter: [https://twitter.com/GenderITorg @GenderITorg] and [https://twitter.com/GenderITes @GenderITes] (Spanish)

=== ''Namita Aavriti ===

GenderIT.org Project Coordinator and English Editor

Based in Bangalore, India

Language: English

Contact: namita@apcwomen.org

----

=== ''Namita Aavriti'' ===

GenderIT.org Content Coordinator and English Editor

Based in Bangalore, India

Language: English

Contact: namita@apcwomen.org

----

=== ''Dafne Sabanes Plou'' ===

GenderIT.org Spanish editor

Based in Buenos Aires, Argentina

Language: Spanish and English

Contact: daphne@apcwomen.org

== ''To reach us by mail or phone'' ==

APC Executive Director’s Office

PO Box 29755

Melville 2109

South Africa

Tel: +27 11 726 1692

Fax: +27 11 726 1692

Main Page

2017-02-03T11:03:54Z

Namita: /* Orientation for new writers and editors */

== '''[[our ideas|Article ideas]]''' ==

[[Image:Ideas.jpg|50px|link=Our_ideas]] In this page we drop all those good ideas that we have for future articles. Check out [[our ideas]]!

== '''Introducing GenderIT.org''' ==

[[Image:doc.jpg|50px|link=What_is_GenderIT.org]] '''[[What is GenderIT.org]]'''

This page is designed to tell you who GenderIT.org is and to show you where the website sits in relation to other websites of the Association for Progressive Communications.

[[Image:doc.jpg|50px|link=The_GenderIT.org_manifesto]] '''[[The GenderIT.org manifesto|GenderIT.org's manifesto: What we do and why]]'''

This document aims to give a concise overview of what drives GenderIT.org and the editorial principles by which it operates.

[[Image:doc.jpg|50px|link=Our_code_of_ethics]] '''[[Our code of ethics]]'''

The aim of this document is to provide a clear understanding of the ethical responsibilities of those who write for the website, whether authors of articles or those leaving comments.

[[Image:audience.jpg|50px|link=Who_does_GenderIT.org_speak_to]] '''[[Who does GenderIT.org speak to]]'''

Here you will find an overview of our main audiences and an explanation of why they are relevant for us.

[[Image:team.jpg|50px|link=GenderIT.org_editorial_team]] '''[[GenderIT.org editorial team]]'''

Here you will find names, definition of roles, contact details and guidance on who to talk to about all that relates to GenderIT.org.

== '''Introducing APCNews''' ==

[[Image:doc.jpg|50px|link=What_is_APCNews]]''' [[What is APCNews]]'''

This page is designed to tell you who APCNews is and to show you where the content produced for APCNews sits in relation to other websites of the Association for Progressive Communications.

[[Image:doc.jpg|50px|link=Editorial_policy]]''' [[Editorial policy]]'''

APCNews editorial policy establishes the focus of interest, values, language and other standards that information produced by the APC must follow.

[[Image:audience.jpg|50px|link=Who_does_APCNews_speak_to]]''' [[Who does APCNews speak to]]'''

Here you will find an overview of our main audiences and an explanation of why they are relevant for us.

[[Image:team.jpg|50px|link=APCNews_editorial_team]]''' [[APCNews editorial team]]'''

Here you will find names, definition of roles, contact details and guidance on who to talk to about all that relates to APCNews.

== '''Orientation for new writers and editors''' ==

[[Image:tool.jpg|50px|link=Orientation to GenderIT.org]] '''[[Orientation to GenderIT.org]]'''

Starting as a writer in GenderIT.org? You must have lots of questions on the procedures and expectations, so we put together this page to orientate you in this process.

[[Image:tool.jpg|50px|link=Orientation to APCNews]] '''[[Orientation to APCNews]]'''

Starting as a writer in APCNews? You must have lots of questions on the procedures and expectations, so we put together this page to orientate you in this process.

[[Image:tool.jpg|50px|link=How to write for GenderIT.org or APCNews]] '''[[How to write for GenderIT.org]]'''

This page provides an introduction on how to write the different types of articles that appear on GenderIT.org.

[[Image:style.jpg|50px|link=A guide for new editors]] '''[[A guide for new editors]]'''

This is a series of guides to help editors new to GenderIT.org and APCNews to understand the priorities for the sites and provide a quick reference to important documents that you may need in your work.

[[Image:FAQ.jpg|50px|link=Frequently asked questions]] '''[[Frequently asked questions]]'''

Here are many of the questions our writers have raised before, and we answer them for you in case you share them.

[[Image:tool.jpg|50px|link=Orientation to GenderIT.org]] '''[[TOR Columnist]]'''

Our columnists are carefully selected for their knowledge and writing. Here are terms of reference for column writing for GenderIT.org

== '''Resources and references''' ==

[[Image:notes.jpg|50px|link=Meetings and notes]] '''[[Meetings and notes]]'''

This is a repository of all editorial meeting notes and a calendar of upcoming meetings.

[[Image:style.jpg|50px|link=Style guide]] '''[[Style guide]]'''

This page gives advice and guidelines on the technicalities of writing for both GenderIT.org and APCNews.

[[Image:style.jpg|50px|link=Reference guide]] '''[[Reference guide]]'''

APCNews, including GenderIT.org, follows an adapted version of the American Psychological Association (APA) style of referencing. Here you will find useful reminders and examples on how to apply it.

[[Image:style.jpg|50px|link=http://www.apc.org/system/files/multilingual_audience_guidelines.pdf]] '''[http://www.apc.org/system/files/multilingual_audience_guidelines.pdf Writing English texts for a multilingual audience]'''

Here you will find some do’s and dont's for native and near-native English language writers

[[Image:audio.jpg|50px|link=How to work with audio]] '''[[How to work with audio]]'''

The aim of this guide is to offer information and resources that will provide a road-map for those new to the medium of audio, while also providing quick links and reference for those with some experience who want a refresher on particular topics or questions.

[[Image:video.jpg|50px|link=How to work with video]] '''[[How to work with video]]'''

The aim of this guide is to offer information and resources that will provide a road-map for those new to the medium of video, while also providing quick links and reference for those with some experience who want a refresher on particular topics or questions.

[[Image:photo.jpg|50px|link=How to work with images]] '''[[How to work with images]]'''

The aim of this guide is to offer information and resources that will help provide technical tips on how to take a good photograph, while also providing quick links and reference for those with some experience who want a refresher on particular topics or questions.

[[Image:aid.jpg|50px|link=How to deal with vulnerable interviewees]] '''[[How to deal with vulnerable interviewees]]'''

This guide contains resources and important considerations to be put in place when conducting interviews, particularly with survivors of violence and sexual harassment.

[[Image:coverage.jpg|50px|link=General orientation for events coverage]] '''[[General orientation for events coverage]]'''

GenderIT.org and APCNews have been recognised for the coverage done in events by readers and writers, becoming one of its substantial outputs. Here you will find a guide on how to proceed during an event coverage.

[[Image:security.jpg|50px|link=Secure online communications]] '''[[Secure online communications]]'''

Security is an important issue for us. As The Lorax say in the Dr Seuss film “Unless someone like you cares a whole awful lot, Nothing is going to get better. It’s not.” Here you will find APC's secure online communications policy on how to keep yourself safe, and the people you work with.

[[Image:far.jpg|50px|link=Closer than ever]] '''[[Closer than ever]]'''

We are far away, but working close. This section will help you understand how we develop our work being in different parts of the world and rarely seeing our colleagues face-to-face.

[[Image:style.jpg|50px|link=http://www.apc.org/en/glossary/6 Glossary]] '''[http://www.apc.org/en/glossary/6 Glossary]'''

The APC glossary is a work-in-progress one. All the terms that are in the glossary appear highlighted throughout the website, with a link to its definition. So it’s a tool both for language workers and for the general public. If you feel that a new term should be added, please write to translation@apc.org

[[Image:photo.jpg|50px|link=Picture gallery]] '''[[Picture gallery]]'''

Looking for images to illustrate your material? Or just curious to see some of the team members at work? Then this is the place!

TOR Columnist

2017-02-03T10:57:40Z

Namita: Terms of Reference for Columnists for GenderIT

'''Terms of Reference for Columnists
'''

'''Background:'''

GenderIT.org provides a space for reflection, influence and advocacy on internet policy and culture, to help ensure that they meet needs of women, gender non-conforming people, queers, and others and do not infringe on their rights. The site maps the intersections between women’s and sexual rights issues and internet rights issues, and concentrates on bringing voices from the global South into the discussion of these issues, since the discussion is often dominated by voices from the North. Topics of interest are online gender based violence, labour rights, diversity in science and tech, cyberfeminism and transfeminism, gaming, freedom of expression for all, policy and legal changes across the world. GenderIT is an affirming space that seeks not to appropriate voices, but to provide people with a platform to write on issues related to technology, gender and sexuality that are of interest to them.

In pursuance of these ideals, GenderIT supports columnists to write for a period of 5 months on the genderIT platform. Columnists are expected to cover issues related to gender, technology, sexuality and other multiple axis of discrimination and exclusion across the world. The column is a space for the writer's own opinions and for them to explore their ideas with the regular audience of GenderIT, consisting of activists, policy advocates and makers, lawyers, writers, feminists and others.

'''Objectives, Issues and Methodology:'''

The columnist will communicate with the respective language editor for GenderIT, either the English language editor or the Spanish language editor.

The columnist is expected to submit one column per month on a fixed day of the month, as agreed upon with the respective editor. This is for a period of 5 months.

The five columns should work together as a series and also independently as an exploration of the main themes agreed upon with the editor.

To know more about how to write for GenderIT, please also refer to [[Our code of ethics]], [[the GenderIT.org manifesto]], and [[How to write for GenderIT.org]]

The columnist will be paid 100$ per column or a total of 500$ for 5 columns over a period of 5 to 6 months. The timings of payment will be as agreed upon between the columnist and editor, depending on convenience. It can be after 2 columns are submitted at the midway point, or a full transfer at the midway point or at the end.

On the submission of the second column, the columnist will also get feedback from the editor. The columns are an open, exploratory and independent space for the columnist, and the nature of the feedback will be in terms of readability and outreach. The editor can also share analytics on the articles (number of reads, retweets etc.) with the columnist.

'''The timely submission of articles on a monthly basis is of utmost importance to ensure the freshness of the ideas and continuity for the readers.''' If however this is not possible, the columnist must communicate this promptly to the respective editor.