https://wiki.apertium.org/w/api.php?action=feedcontributions&user=ScoopGracie&feedformat=atomApertium - User contributions [en]2024-03-29T10:50:19ZUser contributionsMediaWiki 1.34.1https://wiki.apertium.org/w/index.php?title=Apertium_Android&diff=72307Apertium Android2020-06-04T01:06:22Z<p>ScoopGracie: </p>
<hr />
<div>{{TOCD}}<br />
== CURRENTLY BANNED FROM PLAY STORE ==<br />
This app (and presumably others based on it) is currently banned from the Play Store because it downloads code from non-Play servers.)<br />
<br />
The goal of the 'official' Apertium Android app is to provide example code on how to integrate Apertium offline translation into an Android app.<br />
<br />
It requires internet permission to enable users to download language pairs (and developers to showcase their work from a phone).<br />
<br />
If you want a more fully-featured app, try [[Mitzuli]].<br />
<br />
<br />
<gallery><br />
Image:Device-2012-08-07-051235.png|Main screen<br />
</gallery><br />
<br />
<br />
The current version can be downloaded [https://play.google.com/store/apps/details?id=org.apertium.android here].<br />
<br />
The source code is available at https://github.com/apertium/apertium-android.<br />
<br />
Ideas for further improvements:<br />
<br />
* theme/colors doesent provide correct visual feedback (you can't see if you press buttons)<br />
* language detection - for example using https://code.google.com/p/language-detection/<br />
* factor unused stuff from Arink's original work into 'Apertium extended' app<br />
<br />
<br />
Stuff can go in the 'basic Apertium app' if 1) it doesent require scary permissions and 2) it doesent make the app harder to understand as example code on how to integrate Apertium offline translation into other apps.<br />
<br />
<br />
=== Developers: Integrating Apertium into your own Android app ===<br />
<br />
Here are the recommended places to store stuff.<br />
We recommend that you use the ApertiumInstallation utility class included in the demo app.<br />
<br />
<pre><br />
File packagesDir = new File(getFilesDir(), "packages"); // where packages' data are installed<br />
File bytecodeDir = new File(getFilesDir(), "bytecode"); // where packages' bytecode are installed. Must be private<br />
File bytecodeCacheDir = new File(getCacheDir(), "bytecodecache"); // where bytecode cache is kept. Must be private<br />
IOUtils.cacheDir = new File(getCacheDir(), "apertium-index-cache"); // where cached transducerindexes are kept<br />
ai = new ApertiumInstallation(packagesDir, bytecodeDir, bytecodeCacheDir);<br />
ai.rescanForPackages();<br />
</pre><br />
<br />
<br />
And then use apertiumInstallation.installJar(tmpjarfilelocation, pkg); to install pairs.<br />
<br />
To do a translation, use<br />
<pre><br />
String mode = ai.titleToMode.get(currentModeTitle);<br />
String pkg = ai.modeToPackage.get(mode);<br />
Translator.setBase(ai.getBasedirForPackage(pkg), ai.getClassLoaderForPackage(pkg));<br />
Translator.setMode(mode);<br />
</pre><br />
<br />
<br />
And lastly.... Translator.translate() to translate :-)<br />
<br />
<br />
<br />
== Apertium extended ==<br />
<br />
Apertium extended Android app would be a full-feature app with:<br />
* store pairs in SD card (requires permission to read SD card)<br />
* load pairs from SD card (for example experimental pairs or pairs not hosted in Apertium regi)<br />
* a cool Android 4 interface using loads of cool visual libraries<br />
* OCR, <br />
* SMS translation, <br />
* TTS, STT <br />
* and a zillion of scary permissions (internet + read SMS + read SD card should scare you off unless you really trust the source of the app).<br />
* option to use online translation API(s?)<br />
* mind reading?<br />
<br />
== History ==<br />
<br />
* GSOC 2012 [[User:Arinkverma/Apertium on mobile]]<br />
* Decemter 2012 Enhancements WRT memory, see https://sourceforge.net/mailarchive/message.php?msg_id=30266147<br />
<br />
<br />
<br />
[[Category:User interfaces]]<br />
[[Category:Mobile]]<br />
[[Category:Android]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=User:GSoC19_AMR-KELEG_proposal&diff=72138User:GSoC19 AMR-KELEG proposal2020-04-27T15:30:38Z<p>ScoopGracie: ScoopGracie moved page User:GSoC19 AMR-KELEG proposal to User:AMR-KELEG/GSoC19 Proposal: These go under individual user's pages</p>
<hr />
<div>#REDIRECT [[User:AMR-KELEG/GSoC19 Proposal]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=User:AMR-KELEG/GSoC19_Proposal&diff=72137User:AMR-KELEG/GSoC19 Proposal2020-04-27T15:30:37Z<p>ScoopGracie: ScoopGracie moved page User:GSoC19 AMR-KELEG proposal to User:AMR-KELEG/GSoC19 Proposal: These go under individual user's pages</p>
<hr />
<div>= Personal Information =<br />
<br />
* Name: Amr Keleg<br />
<br />
* E-mail address: amr.keleg@eng.asu.edu.eg / amr_mohamed@live.com<br />
<br />
* IRC: AMR-KELEG<br />
<br />
* Location: Cairo, Egypt<br />
<br />
* Timezone: UTC+02<br />
<br />
* Github: https://github.com/AMR-KELEG<br />
<br />
* LinkedIn: https://www.linkedin.com/in/amr-mohamed-hosny/<br />
<br />
* Twitter: https://twitter.com/amrkeleg<br />
<br />
*Current job: A MSc student and a teacher assistant at Computer and systems department, Faculty of Engineering, Ain Shams university, Cairo, Egypt.<br />
<br />
*Experimental blog: https://ak-blog.herokuapp.com<br />
<br />
=== Qualifications ===<br />
<br />
* I graduated as the first of my class of 138 students (Computer and systems department, Faculty of Engineering, Ain Shams University).<br />
<br />
* I have successfully participated as a student in GSoC 2016 as part of the GNU Octave organisation(https://summerofcode.withgoogle.com/archive/2016/projects/5461783343005696/)<br />
<br />
* I have worked for one year as a full-time machine learning engineer. My role was developing sentiment analysis model for Arabic language.<br />
<br />
* As a student, I have participated in online (Google codejam)and on-site (ACM Collegiate programming contest) competitive programming contests.<br />
Throughout those participations, I solved more than 700 problems on different online judges.<br />
<br />
* I am interested in open source communities and have made several contributions to open source projects (cltk - gensim - asciinema - octave and apertium).<br />
<br />
* I have Completed Udacity's data analysis nanodegree. Throughout those courses, I had to use python/ R and Tableau to perform analysis on different data-sets.<br />
<br />
=== Skills ===<br />
* Experience in coding with C++ and python.<br />
<br />
* Good command of git and the GitHub process of contribution.<br />
<br />
* Usage of Ubuntu as the main OS for more than 3 years.<br />
<br />
* Basic knowledge of shell scripting.<br />
<br />
* Basic knowledge of using gdb to debug large C++ projects.<br />
<br />
= Project Information =<br />
== Why is it that you are interested in Apertium? ==<br />
I am interested in NLP and especially the idea of how to enable machines to understand and reason about human languages. This field have made it possible to perform tasks that couldn't be done before. One of the interesting applications of NLP is Machine Translation. Machine Translation programs such as: Apertium have permitted people to automatically translate text from other languages. This has improved the way that we people share knowledge and experience.<br />
<br />
One of the main points that attracted me to Apertium is the fact that most of the maintainers are actually researchers. So not only the program is developed by experienced and skilled developers but also it's maintained by academic researchers that have good understanding of the field and the limitations/difficulties of automatic machine translation.<br />
<br />
== Which of the published tasks are you interested in? What do you plan to do? ==<br />
I am interested in working on "Unsupervised weighting of automata".<br />
The task's main aim is to reduce the ambiguity of the analyses generated by non-deterministic finite state transducers. The task should in return improve the way Apertium ranks its analyses for most if not all of the developed language pairs.<br />
<br />
== Reasons why Google and Apertium should sponsor it ==<br />
I am currently pursuing my masters degree in computer science. Participation in GSoC will for sure be a great step towards becoming a better researcher. The project will give me the chance to read, understand and implement the ideas mentioned in different publications. This will be a great experience and will help me acquire new and necessary skills.<br />
<br />
== How and who the project will benefit in society?==<br />
The project should help developers and users generate weights for FST in an unsupervised way. This has the advantage of using large corpus to generate these weights without the requirement of manual annotation.<br />
<br />
Developers and users aiming at using Apertium to translate documents whose vocabulary is too specific to be included in the available annotated datasets will be able to adjust the weights of the FST according to a large un-annotated corpus of relevant documents.<br />
<br />
== Coding challenge ==<br />
<br />
Code repository: https://github.com/AMR-KELEG/apertium-unsupervised-weighting-of-automata<br />
<br />
Steps completed: <br />
* Used Apertium's analyser to generate the analyses for each tagged token.<br />
* Created a unigram counter to estimate the probability of each analysis given a token.<br />
* Used the unigram counts to rank the generated analyses for each token.<br />
* Generate weighted string-pairs from the corpus.<br />
* Use hfst-strings2fst and hfst-fst2txt to convert the weighted FST into att format.<br />
* Use lt-comp to generate a bin file for the FST using apertium's lttoolbox.<br />
* Use lt-proc given the new weighted fst.<br />
<br />
Note: You will need to build the master branch of lttoolbox so that the analyses weights are computed correctly.<br />
(https://github.com/apertium/lttoolbox/commit/473766aba1704e0fa2b5c1c5672a728a0a20d390)<br />
<br />
== Relevant publications ==<br />
=== Weighting of automata ===<br />
* Parameter Estimation for Probabilistic Finite-State Transducers (https://aclweb.org/anthology/P02-1001)<br />
<br />
=== Background papers ===<br />
* Weighted Finite-State Transducers in Speech Recognition (2002) (https://cs.nyu.edu/~mohri/postscript/csl01.pdf)<br />
** Main points:<br />
*** Basic concepts (Semi-ring/ Types of semi-rings/ Basic operations on transducers (Composition - Determinization - Minimization))<br />
<br />
* An Efficient Algorithm for the n-Best-Strings Problem (2002) (https://pdfs.semanticscholar.org/aa78/148fd79b10962a15c5aa7ec95c573250c3f6.pdf)<br />
** Main points:<br />
*** Basic concepts (Determinization of WFST (Extension of subset construction method))<br />
*** An efficient algorithm for determining the n-best paths other than brute forcing (The main idea is to only allow n-paths to visit any node of the transducer.<br />
e.g: If you visited a node for more than n times then for sure the n best paths should have been part of the previous visits).<br />
<br />
<br />
== Work Plan ==<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
| Community Bonding<br />
| Communicate with the maintainers and get to know Apertium better.<br />
<br />
Solve some issues on Github.<br />
<br />
Prepare a better list of publications that are going to be implemented.<br />
<br />
Implement a baseline model for weigthing automata.<br />
<br />
Solve some issues on Github.<br />
<br />
Prepare a better list of publications that are going to be implemented.<br />
<br />
Implement a baseline model for weighting automata.<br />
<br />
|-<br />
| Week 1<br />
(27 May - 3 June) *<br />
| Develop the first supervised model (Unigram counts).<br />
<br />
Write a shell script for generating weights using a tagged corpus.<br />
|-<br />
| Week 2<br />
(4 June - 10 June) *<br />
| Read, Understand and plan for implementing the publication for the first unsupervised model.<br />
<br />
Document the findings in a blog post.<br />
|-<br />
| Week 3-4<br />
(11 June - 28 June)<br />
| Finalise the first unsupervised model and compare it to the supervised one.<br />
|-<br />
|-<br />
| '''Evaluation 1'''<br />
'''Deliverables: Two shell scripts for generating weights using both supervised and unsupervised techniques.'''<br />
|-<br />
| Week 5<br />
(29 June - 5 July)<br />
| Read, Understand and plan for implementing the publication for the second unsupervised model.<br />
<br />
Document the findings in a blog post.<br />
|-<br />
| Week 6<br />
(6 July - 12 July)<br />
| Implement the second unsupervised model.<br />
|-<br />
| Week 7<br />
(13 July - 22 July)<br />
| Read, Understand and plan for implementing the publication for the second unsupervised model.<br />
<br />
Document the findings in a blog post.<br />
|-<br />
| Week 8<br />
(23 July - 26 July)<br />
| Implement the third unsupervised model.<br />
|-<br />
| '''Evaluation 2'''<br />
'''Deliverables: A shell script for using the second unsupervised model and a plan for implementing the third one.'''<br />
|-<br />
| Week 9-10<br />
(27 July - 9 August)<br />
| Solve issues related to the developed models.<br />
<br />
Finalise and package the scripts.<br />
|-<br />
| Week 11-12<br />
(10 August - 26 August)<br />
| Write the required documentation and merge the code into Apertium's repositories.<br />
|-<br />
| '''Final evaluation'''<br />
| <br />
|}<br />
<br />
* Note: I will have an examination as part of my Masters degree in June. I will inform my mentor whenever the schedule is announced. (I will need to study three days before the exam so my working hours will decrease during these days).<br />
<br />
== Contributions to Apertium ==<br />
I have managed to fix multiple issues in different repositories of Apertium's code-base.<br />
<br />
Merged pull requests:<br />
* apertium-ml-ar: Update the README file https://github.com/apertium/apertium-mlt-ara/pull/3<br />
* phenny: Fix the generated url for the logs file https://github.com/apertium/phenny/pull/475<br />
* lttoolbox: Fix the analysis weight computation bug https://github.com/apertium/lttoolbox/pull/49<br />
[[Category:GSoC 2019 student proposals]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=User:ScoopGracie&diff=72135User:ScoopGracie2020-04-27T15:26:50Z<p>ScoopGracie: Election is over</p>
<hr />
<div>Hi! I'm ScoopGracie! I'm a GCI 2019 student. I like Python, as well as Web development. I like to work on [[Begiak]]-related tasks. More importantly, however, I'm a Christian. I have some plans to use Apertium to help create a Bible translation for languages that do not have any versions. Anyone who's interested in helping, please ping me on [[IRC]]!<br />
<br />
Check out [https://scoopgracie.com/ my website]!<br />
<br />
As I said before, I like Python. I also like JavaScript, but ONLY vanilla JS. If you think you need a framework for cross-browser compatibility, use polyfills, not a framework!</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=Morphological_analysis&diff=72028Morphological analysis2020-04-13T01:29:39Z<p>ScoopGracie: </p>
<hr />
<div>[[Analyse morphologique|En français]]<br />
<br />
'''Morphological analysis''' attempts to model the rules that govern the internal structure of words in a language. For example, speakers of English realise that the words "dog" and "dogs" are related, that "dogs" is to "dog" as "cats" is to "cat". The rules understood by the speaker reflect specific patterns and regularities in the way in which words are formed from smaller units and how those smaller units interact.<br />
<br />
Another way to understand it is splitting a source language word into its lemma and grammatical info.<br />
* cats -> cat<n><pl><br />
* dog -> dog<n><sg><br />
<br />
==See also==<br />
<br />
* [[Surface form]] and [[lexical form]]<br />
* [[Part-of-speech tagging]]<br />
* [[Morphological dictionaries]]<br />
<br />
[[Category:Terminology]]<br />
[[Category:Documentation in English]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=Begiak&diff=72027Begiak2020-04-13T00:27:24Z<p>ScoopGracie: /* Development */</p>
<hr />
<div>{{TOCD}}<br />
'''begiak''' is the IRC bot in the #apertium [[IRC]] channel. It serves several purposes, including to showcase some applications of the apertium translation [[API]], getting information about languages and other topics, and providing various forms of reminders, as well as a couple features that are just for fun.<br />
<br />
== Background ==<br />
Begiak was set up by conor_f for [[Google Code-in|GCI 2012]], and several modules were written and fixed by [[User:Sushain|sushain]], Qasim, and a number of other GCI students since then. The core code base is the [https://github.com/mutantmonkey/phenny mutantmonkey port] to Python3 of the [http://inamidst.com/phenny/ phenny] bot. Our codebase is currently hosted at [https://github.com/apertium/phenny].<br />
<br />
Begiak means "the eyes" in [[Basque]].<br />
<br />
== Features ==<br />
Begiak recognises the following commands.<br />
<br />
* <code>.awikstats update <lang></code> — update the wikipage apertium-LANG/stats (note: will dump a bunch of info in private chat)<br />
* <code>.follow <nick> <lg1-lg2> [follower]</code> — Follow someone and translate as they speak. (Translations are sent as notices to the follower (follower feature is admin only!))<br />
* <code>.following</code> — List people currently being followed.<br />
* <code>.iso639 <lg></code> — look up [http://en.wikipedia.org/wiki/ISO_639 ISO 639]-1, -2 and -3 language codes either by code or by language name. Codes sourced from Ethnologue.com (639-3) and Wikipedia (-1 and -2)<br />
* <code>.isodb status</code> — see if the database updater (.isodb update) is running<br />
* <code>.issue <title></code> — create a new GitHub issue.<br />
* <code>.listpairs <lg></code> — List language pairs available for apertium translation<br />
* <code>.listlangs</code> — List languages available for apertium translation<br />
* <code>.t <lg1-lg2> [ | lg2-lg3 ...] <text>''</code> — Apertium translate<br />
* <code>.unfollow <nick></code> — Stop following a user.<br />
* <code>.8ball</code> — magic 8 ball<br />
* <code>.beats</code> — Shows the internet time in Swatch beats<br />
* <code>.botsnack</code> — Give begiak a snack for being good<br />
* <code>.c</code> — Calculator using SymPy.<br />
* <code>.chill</code> — Measure the current channel chillness level.<br />
* <code>.choose <choice1> <choice2></code> — begiak will choose one of the two options (randomly).<br />
* <code>.ety</code> — Look up the etymology of a word<br />
* <code>.fcc <callsign></code> — Look up a callsign issued by the FCC<br />
* <code>.fight <nick></code> — have begiak fight someone for you.<br />
* <code>.hug <nick></code> — have begiak hug someone for you.<br />
* <code>.in <time></code> — Set a reminder<br />
* <code>.linx <url></code> — Upload ''url'' to linx.li<br />
* <code>.npl</code> — Shows the time from NPL's SNTP server<br />
* <code>.nsfw <link></code> — for when a link isn't safe for work<br />
* <code>.pesters<br />
** begiak: pester <nick> <message></code> — Sends a message to nick every hour they're around (or something. settable in config)<br />
** <code>.pesters snooze <nick></code> — 'snooze' a pester from nick<br />
** <code>.pesters <dismiss|rm|remove> <to|from> <nick></code> — to stop pestering/being pestered by nick<br />
* Search commands:<br />
** The search commands are used to point other users to the output of several supported commands which are as follows:<br />
*** Apertium Wiki (<code>.awik</code>)<br />
*** Wikipedia (<code>.wik</code>)<br />
*** Urban Dictionary (<code>.urb</code>)<br />
*** Wiktionary (<code>.w</code>)<br />
*** DuckDuckGo Search (<code>.search</code>)<br />
** Replace <code>.wik</code> or <code>.awik</code> with any of the above commands for appropriate output like 'svineet, "India, officially the Republic of India (Bhārat Gaṇarājya),[18][19][c] is a country in South Asia" - https://en.wikipedia.org/wiki/India' for <code>.wik India -> svineet</code><br />
*** <code>.awik Begiak -> svineet</code><br />
*** <code>.awik Begiak → svineet</code><br />
*** <code>nick: .wik India</code><br />
*** <code>nick, .wik India</code><br />
*** <code>.awik India -> nick</code><br />
* <code>.seen</code> — When was the last time a user was seen?<br />
* <code>.time [timezone]</code> — Returns current time in timezone (can be a city or a time zone e.g UTC). If timezone is empty, returns current time in GMT time zone. <br />
* <code>.tz</code> — Timezone converter Converts a time from one timezone to another. (e.g., .tz 335EST in CET, or .tz 335EST in London)<br />
* <code>.tells</code> — See a summary of outstanding reminders you've sent to others using "begiak: tell"<br />
** begiak: tell <nick> <message> [**pm**]</code> — Tells someone something the next time they say something in a channel begiak is monitoring. The **pm** option has the message sent privately.<br />
** <code>.tells <nick></code> — List your reminders currently queued to that nick<br />
** <code>.tells rm <num></code> — Delete a queued reminder using its number from .tells nick <br />
* <code>.alias</code> — manage aliases<br />
** <code>.alias add <nick></code> — adds an alias for your nick of nick<br />
** <code>.alias rm <nick></code> — removes an alias for nick nick<br />
** <code>.alias list <nick></code> — lists existing aliases for nick<br />
* <code>.u <char></code> — Search for a unicode character<br />
* <code>.weather <city></code> — Get the weather for a city<br />
* <code>.yi</code> — Shows whether it is currently yi or not<br />
<br />
=== Admin ===<br />
These are admin-only, or only useful to admins.<br />
* <code>.isodb update</code> — update the local database of ISO 639 codes<br />
* <code>.greeting</code> — Manage Greetings<br />
** <code>.greeting add <name> <message></code> — Add a greeting<br />
** <code>.greeting del <name></code> - Delete a greeting<br />
* <code>.gitserver [status|start|stop]</code> — get the githook-server's status/start it/stop it. See [[Begiak's git plugin]] for more info.<br />
* <code>.tzdb</code> — Manage timezone database<br />
** <code>.tzdb update</code> — Updates a timezones database (admin only)<br />
** <code>.tzdb status</code> — Returns a status of updating a timezones database<br />
<br />
=== Unknown ===<br />
These functions/plugins either don't seem to work or need some figuring out:<br />
* .tfw<br />
* lastfm<br />
* mylife (.fml .mlia)<br />
* oblique<br />
* .whereis ''nick'' — Tells you nick's current status.<br />
* .queue — Manage lists.<br />
** .queue new ''name'' [''item1'', ''item2'' ...] — Make a new queue<br />
** .queue ''name'' — Display a queue<br />
** .queue delete ''name'' — Delete a queue<br />
** .queue ''name'' add ''item'' — Add an item<br />
** .queue ''name'' remove ''item'' — Remove an item<br />
** .queue ''name'' pop — Pop an item off the queue<br />
** .queue ''name'' swap ''item1'', ''item2'' — Swap two items<br />
* .py — Evaluate an expression in python (This runs as a sandboxed web service, not on your computer)<br />
* .wikicount ''lg'' — Get the number of articles an official or incubated Wikipedia for the specified language has, given a Wikipedia code or partial language name.<br />
* .(ml|mailinglist) poll — Poll for new messages in apertium mailing lists (this is automatically done every five minutes).<br />
* .(ml|mailinglist) last <list> — Get the last message in a specified list.<br />
<br />
== Help! It crashed!==<br />
Begiak has a known bug that causes it to repeatedly quit and rejoin. A few recent changes have reduced this, but it still occasionally occurs. Please don't report this as an issue; we already know about it. If you know how to fix it, however, please do tell us.<br />
<br />
== Development ==<br />
A good tutorial on creating Phenny modules can be found [https://github.com/myano/jenni/wiki/How-to-create-a-phenny-module here]. Also, note that some commands start with a period and others start with "begiak: "; new commands should use a period.<br />
<br />
== Administration ==<br />
Begiak is controlled by an init script (/etc/init.d/begiak.sh, found at [https://github.com/apertium/phenny/blob/master/init.sh]) on Bytemark, and can be started, stopped, and restarted by anyone with sudo access.<br />
<br />
[[Category:Bots]]<br />
[[Category:Tools]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=Begiak&diff=72026Begiak2020-04-13T00:23:24Z<p>ScoopGracie: .. -> .</p>
<hr />
<div>{{TOCD}}<br />
'''begiak''' is the IRC bot in the #apertium [[IRC]] channel. It serves several purposes, including to showcase some applications of the apertium translation [[API]], getting information about languages and other topics, and providing various forms of reminders, as well as a couple features that are just for fun.<br />
<br />
== Background ==<br />
Begiak was set up by conor_f for [[Google Code-in|GCI 2012]], and several modules were written and fixed by [[User:Sushain|sushain]], Qasim, and a number of other GCI students since then. The core code base is the [https://github.com/mutantmonkey/phenny mutantmonkey port] to Python3 of the [http://inamidst.com/phenny/ phenny] bot. Our codebase is currently hosted at [https://github.com/apertium/phenny].<br />
<br />
Begiak means "the eyes" in [[Basque]].<br />
<br />
== Features ==<br />
Begiak recognises the following commands.<br />
<br />
* <code>.awikstats update <lang></code> — update the wikipage apertium-LANG/stats (note: will dump a bunch of info in private chat)<br />
* <code>.follow <nick> <lg1-lg2> [follower]</code> — Follow someone and translate as they speak. (Translations are sent as notices to the follower (follower feature is admin only!))<br />
* <code>.following</code> — List people currently being followed.<br />
* <code>.iso639 <lg></code> — look up [http://en.wikipedia.org/wiki/ISO_639 ISO 639]-1, -2 and -3 language codes either by code or by language name. Codes sourced from Ethnologue.com (639-3) and Wikipedia (-1 and -2)<br />
* <code>.isodb status</code> — see if the database updater (.isodb update) is running<br />
* <code>.issue <title></code> — create a new GitHub issue.<br />
* <code>.listpairs <lg></code> — List language pairs available for apertium translation<br />
* <code>.listlangs</code> — List languages available for apertium translation<br />
* <code>.t <lg1-lg2> [ | lg2-lg3 ...] <text>''</code> — Apertium translate<br />
* <code>.unfollow <nick></code> — Stop following a user.<br />
* <code>.8ball</code> — magic 8 ball<br />
* <code>.beats</code> — Shows the internet time in Swatch beats<br />
* <code>.botsnack</code> — Give begiak a snack for being good<br />
* <code>.c</code> — Calculator using SymPy.<br />
* <code>.chill</code> — Measure the current channel chillness level.<br />
* <code>.choose <choice1> <choice2></code> — begiak will choose one of the two options (randomly).<br />
* <code>.ety</code> — Look up the etymology of a word<br />
* <code>.fcc <callsign></code> — Look up a callsign issued by the FCC<br />
* <code>.fight <nick></code> — have begiak fight someone for you.<br />
* <code>.hug <nick></code> — have begiak hug someone for you.<br />
* <code>.in <time></code> — Set a reminder<br />
* <code>.linx <url></code> — Upload ''url'' to linx.li<br />
* <code>.npl</code> — Shows the time from NPL's SNTP server<br />
* <code>.nsfw <link></code> — for when a link isn't safe for work<br />
* <code>.pesters<br />
** begiak: pester <nick> <message></code> — Sends a message to nick every hour they're around (or something. settable in config)<br />
** <code>.pesters snooze <nick></code> — 'snooze' a pester from nick<br />
** <code>.pesters <dismiss|rm|remove> <to|from> <nick></code> — to stop pestering/being pestered by nick<br />
* Search commands:<br />
** The search commands are used to point other users to the output of several supported commands which are as follows:<br />
*** Apertium Wiki (<code>.awik</code>)<br />
*** Wikipedia (<code>.wik</code>)<br />
*** Urban Dictionary (<code>.urb</code>)<br />
*** Wiktionary (<code>.w</code>)<br />
*** DuckDuckGo Search (<code>.search</code>)<br />
** Replace <code>.wik</code> or <code>.awik</code> with any of the above commands for appropriate output like 'svineet, "India, officially the Republic of India (Bhārat Gaṇarājya),[18][19][c] is a country in South Asia" - https://en.wikipedia.org/wiki/India' for <code>.wik India -> svineet</code><br />
*** <code>.awik Begiak -> svineet</code><br />
*** <code>.awik Begiak → svineet</code><br />
*** <code>nick: .wik India</code><br />
*** <code>nick, .wik India</code><br />
*** <code>.awik India -> nick</code><br />
* <code>.seen</code> — When was the last time a user was seen?<br />
* <code>.time [timezone]</code> — Returns current time in timezone (can be a city or a time zone e.g UTC). If timezone is empty, returns current time in GMT time zone. <br />
* <code>.tz</code> — Timezone converter Converts a time from one timezone to another. (e.g., .tz 335EST in CET, or .tz 335EST in London)<br />
* <code>.tells</code> — See a summary of outstanding reminders you've sent to others using "begiak: tell"<br />
** begiak: tell <nick> <message> [**pm**]</code> — Tells someone something the next time they say something in a channel begiak is monitoring. The **pm** option has the message sent privately.<br />
** <code>.tells <nick></code> — List your reminders currently queued to that nick<br />
** <code>.tells rm <num></code> — Delete a queued reminder using its number from .tells nick <br />
* <code>.alias</code> — manage aliases<br />
** <code>.alias add <nick></code> — adds an alias for your nick of nick<br />
** <code>.alias rm <nick></code> — removes an alias for nick nick<br />
** <code>.alias list <nick></code> — lists existing aliases for nick<br />
* <code>.u <char></code> — Search for a unicode character<br />
* <code>.weather <city></code> — Get the weather for a city<br />
* <code>.yi</code> — Shows whether it is currently yi or not<br />
<br />
=== Admin ===<br />
These are admin-only, or only useful to admins.<br />
* <code>.isodb update</code> — update the local database of ISO 639 codes<br />
* <code>.greeting</code> — Manage Greetings<br />
** <code>.greeting add <name> <message></code> — Add a greeting<br />
** <code>.greeting del <name></code> - Delete a greeting<br />
* <code>.gitserver [status|start|stop]</code> — get the githook-server's status/start it/stop it. See [[Begiak's git plugin]] for more info.<br />
* <code>.tzdb</code> — Manage timezone database<br />
** <code>.tzdb update</code> — Updates a timezones database (admin only)<br />
** <code>.tzdb status</code> — Returns a status of updating a timezones database<br />
<br />
=== Unknown ===<br />
These functions/plugins either don't seem to work or need some figuring out:<br />
* .tfw<br />
* lastfm<br />
* mylife (.fml .mlia)<br />
* oblique<br />
* .whereis ''nick'' — Tells you nick's current status.<br />
* .queue — Manage lists.<br />
** .queue new ''name'' [''item1'', ''item2'' ...] — Make a new queue<br />
** .queue ''name'' — Display a queue<br />
** .queue delete ''name'' — Delete a queue<br />
** .queue ''name'' add ''item'' — Add an item<br />
** .queue ''name'' remove ''item'' — Remove an item<br />
** .queue ''name'' pop — Pop an item off the queue<br />
** .queue ''name'' swap ''item1'', ''item2'' — Swap two items<br />
* .py — Evaluate an expression in python (This runs as a sandboxed web service, not on your computer)<br />
* .wikicount ''lg'' — Get the number of articles an official or incubated Wikipedia for the specified language has, given a Wikipedia code or partial language name.<br />
* .(ml|mailinglist) poll — Poll for new messages in apertium mailing lists (this is automatically done every five minutes).<br />
* .(ml|mailinglist) last <list> — Get the last message in a specified list.<br />
<br />
== Help! It crashed!==<br />
Begiak has a known bug that causes it to repeatedly quit and rejoin. A few recent changes have reduced this, but it still occasionally occurs. Please don't report this as an issue; we already know about it. If you know how to fix it, however, please do tell us.<br />
<br />
== Development ==<br />
A good tutorial on creating Phenny modules can be found [https://github.com/myano/jenni/wiki/How-to-create-a-phenny-module here]. Also, note that some commands start with a period and others start with "begiak: "; new commands should probably use a period.<br />
<br />
== Administration ==<br />
Begiak is controlled by an init script (/etc/init.d/begiak.sh, found at [https://github.com/apertium/phenny/blob/master/init.sh]) on Bytemark, and can be started, stopped, and restarted by anyone with sudo access.<br />
<br />
[[Category:Bots]]<br />
[[Category:Tools]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=User_talk:Jacob_Nordfalk&diff=72025User talk:Jacob Nordfalk2020-04-13T00:01:39Z<p>ScoopGracie: /* Your edit on Lttoolbox-java */ new section</p>
<hr />
<div>Welcome! - [[User:Francis Tyers|Francis Tyers]] 08:39, 25 August 2008 (UTC)<br />
<br />
Thx :-) --[[User:Jacob Nordfalk|Jacob Nordfalk]] 08:40, 25 August 2008 (UTC)<br />
<br />
:I've started a page for [[English and Esperanto]] where we can leave notes. - [[User:Francis Tyers|Francis Tyers]] 10:55, 25 August 2008 (UTC)<br />
<br />
<br />
==Google Summer Intern==<br />
<br />
[[User:Ameya420|Ameya Shendre]]<br />
<br />
Sir,<br />
I am second year mathematics and computing(5 year integrated M.Tech)<br />
student of IIT,Delhi.<br />
I will like to do project under you. Please tell me where can talk about it.<br />
I can ensure you full dedication from me.<br />
<br />
Relevant courses I have done<br /><br />
-Analysis and Design of Algorithms<br /><br />
-Numerical Methods and Computation<br /><br />
-Probability Theory and Stochastic Processes<br /><br />
-Introduction to Computers and Programming<br /><br />
-Data Structure<br /><br />
-Numerical Methods<br /><br />
-Differential Equations<br /><br />
<br />
My interest area<br /><br />
-Algorithms Related to Graph analysis<br /><br />
-Large data Handling Algorithm<br /><br />
-Numerical Methods<br /><br />
<br />
Note- I am in second year(will complete this summer). i have done courses on Numerical Methods and Differential equations. I will like to create library in Java of all functions I have learnt. (e.g. Integration using 1/3 Simpson rule etc)<br />
<br />
So,Please tell me where can we discuss about it.<br />
<br />
=== Reply to Ameya ===<br />
Please subscribe to and send questions to apertium-stuff mailing list.<br />
<br />
== Your edit on [[Lttoolbox-java]] ==<br />
<br />
Just wondering why you changed Openoffice.org to LibreOffice? --[[User:ScoopGracie|ScoopGracie]] {[[User talk:ScoopGracie|Talk]]~|~[[Special:Contributions/ScoopGracie|Contributions]]} 02:01, 13 April 2020 (CEST)</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=PMC_proposals/Use_Material_Design&diff=72016PMC proposals/Use Material Design2020-04-09T19:30:45Z<p>ScoopGracie: /* In detail */</p>
<hr />
<div>== Summary ==<br />
I propose to standardize that new or substantially redesigned Web interfaces and sites for Apertium be standardized to use Material Design.<br />
<br />
== In detail ==<br />
Currently, Apertium has no standard for user interfaces, creating a discontinuity. I propose to adopt Material Design as the standard for Apertium Web interfaces.<br />
<br />
To be clear, I am not proposing that existing interfaces should be immediately rewritten. I believe we should encourage this, but this proposal, if accepted, would not require this. It would only be required for new or substantially rewritten interfaces.<br />
<br />
Over time, however, the interfaces would be rewritten or migrated. The Wiki would at least switch to the Timeless skin (which, although not Material, clashes much less than Monobook), and preferably the Material skin if it is deemed usable. There are already current discussions on rewriting html-tools, and the new version would use Material Design if this is accepted.<br />
<br />
Additionally, desktop program and mobile app interfaces should continue to be designed to match the OSes they run on. (Of course, this would mean Material Design for Android and Chrome OS.)<br />
<br />
=== Pros ===<br />
* It's quite popular (not a reason in and of itself, but with UIs, some users may be more comfortable with Material Design)<br />
* One of the most common ways to discover Apertium is GCI/GSoC. It may help a bit if Apertium "matches" the GCI and GSOC interfaces.<br />
* There are many libraries for Material Design. Being one of the most popular UI specifications, any Web framework we could use (including no framework) will have at least one Material library.<br />
<br />
=== Cons ===<br />
* Not everyone likes it<br />
* Looking "Google-y" may not be good<br />
<br />
Proposed by: [[User:ScoopGracie|ScoopGracie]] {[[User talk:ScoopGracie|Talk]]~|~[[Special:Contributions/ScoopGracie|Contributions]]}<br />
<br />
== Comments ==<br />
<br />
== Voting ==<br />
=== For ===<br />
=== Against ===<br />
=== Abstain ===</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=PMC_proposals/Use_Material_Design&diff=72014PMC proposals/Use Material Design2020-04-08T20:12:04Z<p>ScoopGracie: oops</p>
<hr />
<div>== Summary ==<br />
I propose to standardize that new or substantially redesigned Web interfaces and sites for Apertium be standardized to use Material Design.<br />
<br />
== In detail ==<br />
Currently, Apertium has no standard for user interfaces, creating a discontinuity. I propose to adopt Material Design as the standard for Apertium Web interfaces.<br />
<br />
To be clear, I am not proposing that existing interfaces should be immediately rewritten. I believe we should encourage this, but this proposal, if accepted, would not require this. It would only be required for new or substantially rewritten interfaces.<br />
<br />
Over time, however, the interfaces would be rewritten or migrated. The Wiki would at least switch to the Timeless skin (which, although not Material, clashes much less than Monobook), and preferably the Material skin if it is deemed usable. There are already current discussions on rewriting html-tools, and the new version would use Material Design if this is accepted.<br />
<br />
Additionally, desktop program and mobile app interfaces should continue to be designed to match the OSes they run on. (Of course, this would mean Material Design for Android and Chrome OS.)<br />
<br />
Proposed by: [[User:ScoopGracie|ScoopGracie]] {[[User talk:ScoopGracie|Talk]]~|~[[Special:Contributions/ScoopGracie|Contributions]]}<br />
<br />
== Comments ==<br />
<br />
== Voting ==<br />
=== For ===<br />
=== Against ===<br />
=== Abstain ===</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=PMC_proposals/Use_Material_Design&diff=72013PMC proposals/Use Material Design2020-04-08T19:58:59Z<p>ScoopGracie: Add Material Design proposal</p>
<hr />
<div>== Summary ==<br />
I propose to standardize that new or substantially redesigned Web interfaces and sites for Apertium be standardized to use Material Design.<br />
<br />
== In detail ==<br />
Currently, Apertium has no standard for user interfaces, creating a discontinuity. I propose to adopt Material Design as the standard for Apertium Web interfaces.<br />
<br />
To be clear, I am not proposing that existing interfaces should be immediately rewritten. I believe we should encourage this, but this proposal, if accepted, would not require this. It would only be required for new or substantially rewritten interfaces.<br />
<br />
Over time, however, the interfaces would be rewritten or migrated. The Wiki would at least switch to the Timeless skin (which, although not Material, clashes much less than Monobook), and preferably the Material skin if it is deemed usable. There are already current discussions on rewriting html-tools, and the new version would use Material Design if this is accepted.<br />
<br />
Additionally, desktop program and mobile app interfaces should continue to be designed to match the OSes they run on. (Of course, this would mean Material Design for Android and Chrome OS.)<br />
<br />
Proposed by: [[User:ScoopGracie|ScoopGracie]] {[[User talk:ScoopGracie|Talk]]~|~[[Special:Contributions/ScoopGracie|Contributions]]}<br />
<br />
== Comments<br />
== Voting ==<br />
=== For ===<br />
=== Against ===<br />
=== Abstain ===</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=PMC_proposals/Migrate_to_Google_Groups&diff=72003PMC proposals/Migrate to Google Groups2020-04-04T20:28:34Z<p>ScoopGracie: Add migration proposal</p>
<hr />
<div>== Summary ==<br />
I propose that apertium-stuff be replaced with a Google Groups and apertium-contact be replaced with a Gmail account.<br />
<br />
== Comments ==<br />
<br />
== Voting ==<br />
=== For ===<br />
=== Against ===<br />
=== Abstain ===</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=PMC_proposals/New_bylaws&diff=72002PMC proposals/New bylaws2020-04-04T20:15:11Z<p>ScoopGracie: Add new bylaws</p>
<hr />
<div>== Summary ==<br />
I propose that [[User:ScoopGracie/PMC/Proposed_bylaws]] be accepted as the new Bylaws of the Apertium project.<br />
<br />
This proposal is not officially put forward until the new PMC elected in 2020 is in office.<br />
<br />
Proposed by: [[User:ScoopGracie|ScoopGracie]] {[[User talk:ScoopGracie|Talk]]~|~[[Special:Contributions/ScoopGracie|Contributions]]}<br />
<br />
== Comments ==<br />
<br />
== Voting ==<br />
=== For ===<br />
=== Against ===<br />
=== Abstain ===</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=PMC_proposals&diff=72001PMC proposals2020-04-04T04:53:53Z<p>ScoopGracie: Pluto proposal has a vote</p>
<hr />
<div>This page collects proposals that have been put to the Project Management Committee.<br />
<br />
; 2010-03-20<br />
# [[PMC proposals/Apertium membership in EAMT|Apertium membership in EAMT]] -- '''Approved (8, 0, 1)'''<br />
<br />
; 2011-02-08<br />
# [[PMC proposals/Repository reorganisation|Repository reorganisation]] -- '''Approved (7,0,0)'''<br />
# <strike>[[PMC proposals/Pre-releases|Pre-releases]]</strike> -- '''Withdrawn'''<br />
<br />
; 2011-04-05<br />
# <s>[[PMC proposals/Supporting open formats on the mailing list|Supporting open formats on the mailing list]]</s> -- '''Expired (3,0,0)'''<br />
<br />
; 2011-07-19<br />
# <s>[[PMC proposals/PayPal account to accept donations|PayPal account to accept donations]]</s> -- '''Expired (0,0,0)'''<br />
# [[PMC proposals/Migrate webspace and Wiki to Bytemark server|Migrate webspace and Wiki to Bytemark server]] -- '''Approved (6,0,0)'''<br />
# <s>[[PMC Proposals/Accept donations through Sourceforge|Accept donations through Sourceforge]]</s> -- '''Expired (0,0,0)'''<br />
<br />
; 2011-11-02<br />
<br />
# [[PMC proposals/Apertium Workshop in Russia|Apertium Workshop in Russia]] -- '''Approved (4,0,2)'''<br />
<br />
; 2012-11-27<br />
<br />
# [[PMC proposals/Debian package mantainer|Debian package mantainer]] -- Approved? (4,0,0) (in practice anyway)<br />
<br />
; 2013-03-17<br />
<br />
# [[PMC proposals/Stable version of apertium-sh-sl|Stable version of apertium-sh-sl]] -- '''Approved (5,0,0)'''<br />
# [[PMC proposals/New naming of the Bosnian-Croatian-Montenegrin-Serbian Sprachbund|New naming of the Bosnian-Croatian-Montenegrin-Serbian Sprachbund]] -- '''Approved (4,0,0)'''<br />
<br />
; 2013-09-06<br />
<br />
# <s>[[PMC proposals/Move apertium to github]]</s> -- '''Expired (0,0,0)'''<br />
<br />
; 2014-08-18<br />
<br />
# [[PMC proposals/Adding of bylaw 13|Add a new bylaw, on the removal of Committers]]<br />
# [[PMC proposals/Interpretation of bylaw 11|Interpretation of bylaw 11, on the adding of Committers]]<br />
# [[PMC proposals/Removal of bylaws 24-26|Removal of Transitional provisions from bylaws]]<br />
<br />
; 2015-01-13<br />
# <s>[[PMC proposals/Allow some code under github.com/apertium]]</s> '''Expired (3,2,1)'''<br />
<br />
; 2017-10-24<br />
<br />
# <s>[[PMC proposals/Move Apertium to Github]]</s> '''Approved'''<br />
<br />
; 2020-04-01<br />
<br />
# [[PMC proposals/Replanetize Pluto]] '''(0,1,0)'''<br />
<br />
<br />
<br />
[[Category:Project Management Committee]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=PMC_proposals&diff=71982PMC proposals2020-04-02T01:53:30Z<p>ScoopGracie: Add plutoplanetization</p>
<hr />
<div>This page collects proposals that have been put to the Project Management Committee.<br />
<br />
; 2010-03-20<br />
# [[PMC proposals/Apertium membership in EAMT|Apertium membership in EAMT]] -- '''Approved (8, 0, 1)'''<br />
<br />
; 2011-02-08<br />
# [[PMC proposals/Repository reorganisation|Repository reorganisation]] -- '''Approved (7,0,0)'''<br />
# <strike>[[PMC proposals/Pre-releases|Pre-releases]]</strike> -- '''Withdrawn'''<br />
<br />
; 2011-04-05<br />
# <s>[[PMC proposals/Supporting open formats on the mailing list|Supporting open formats on the mailing list]]</s> -- '''Expired (3,0,0)'''<br />
<br />
; 2011-07-19<br />
# <s>[[PMC proposals/PayPal account to accept donations|PayPal account to accept donations]]</s> -- '''Expired (0,0,0)'''<br />
# [[PMC proposals/Migrate webspace and Wiki to Bytemark server|Migrate webspace and Wiki to Bytemark server]] -- '''Approved (6,0,0)'''<br />
# <s>[[PMC Proposals/Accept donations through Sourceforge|Accept donations through Sourceforge]]</s> -- '''Expired (0,0,0)'''<br />
<br />
; 2011-11-02<br />
<br />
# [[PMC proposals/Apertium Workshop in Russia|Apertium Workshop in Russia]] -- '''Approved (4,0,2)'''<br />
<br />
; 2012-11-27<br />
<br />
# [[PMC proposals/Debian package mantainer|Debian package mantainer]] -- Approved? (4,0,0) (in practice anyway)<br />
<br />
; 2013-03-17<br />
<br />
# [[PMC proposals/Stable version of apertium-sh-sl|Stable version of apertium-sh-sl]] -- '''Approved (5,0,0)'''<br />
# [[PMC proposals/New naming of the Bosnian-Croatian-Montenegrin-Serbian Sprachbund|New naming of the Bosnian-Croatian-Montenegrin-Serbian Sprachbund]] -- '''Approved (4,0,0)'''<br />
<br />
; 2013-09-06<br />
<br />
# <s>[[PMC proposals/Move apertium to github]]</s> -- '''Expired (0,0,0)'''<br />
<br />
; 2014-08-18<br />
<br />
# [[PMC proposals/Adding of bylaw 13|Add a new bylaw, on the removal of Committers]]<br />
# [[PMC proposals/Interpretation of bylaw 11|Interpretation of bylaw 11, on the adding of Committers]]<br />
# [[PMC proposals/Removal of bylaws 24-26|Removal of Transitional provisions from bylaws]]<br />
<br />
; 2015-01-13<br />
# <s>[[PMC proposals/Allow some code under github.com/apertium]]</s> '''Expired (3,2,1)'''<br />
<br />
; 2017-10-24<br />
<br />
# <s>[[PMC proposals/Move Apertium to Github]]</s> '''Approved'''<br />
<br />
; 2020-04-01<br />
<br />
# [[PMC proposals/Replanetize Pluto]] '''(0,0,0)'''<br />
<br />
<br />
<br />
[[Category:Project Management Committee]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=PMC_proposals/Replanetize_Pluto&diff=71981PMC proposals/Replanetize Pluto2020-04-02T01:44:31Z<p>ScoopGracie: !'sloof lirpA</p>
<hr />
<div>== Summary ==<br />
I propose that Pluto be declared a planet.<br />
<br />
Nominated by: [[User:ScoopGracie|ScoopGracie]] {[[User talk:ScoopGracie|Talk]]~|~[[Special:Contributions/ScoopGracie|Contributions]]}<br />
<br />
Seconded by: Pluto<br />
<br />
== Comments ==<br />
<br />
== Voting ==<br />
=== For ===<br />
=== Against ===<br />
=== Abstain ===</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=User:Pmodi&diff=71501User:Pmodi2020-03-27T00:58:27Z<p>ScoopGracie: Userspace</p>
<hr />
<div>#REDIRECT [[User:Pmodi/GSOC 2020 proposal: Hindi-Punjabi]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=Hectoralos/GSOC_2020_proposal:_French-Arpitan&diff=71500Hectoralos/GSOC 2020 proposal: French-Arpitan2020-03-27T00:56:41Z<p>ScoopGracie: ScoopGracie moved page Hectoralos/GSOC 2020 proposal: French-Arpitan to User:Hectoralos/GSOC 2020 proposal: French-Arpitan: These go in userspace</p>
<hr />
<div>#REDIRECT [[User:Hectoralos/GSOC 2020 proposal: French-Arpitan]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=User:Hectoralos/GSOC_2020_proposal:_French-Arpitan&diff=71499User:Hectoralos/GSOC 2020 proposal: French-Arpitan2020-03-27T00:56:40Z<p>ScoopGracie: ScoopGracie moved page Hectoralos/GSOC 2020 proposal: French-Arpitan to User:Hectoralos/GSOC 2020 proposal: French-Arpitan: These go in userspace</p>
<hr />
<div>== Contact Information ==<br />
<br />
'''Name:''' Hèctor Alòs i Font<br />
<br />
'''Location:''' [https://en.wikipedia.org/wiki/Cheboksary Shupashkar, Chuvashia, Russia]<br />
<br />
'''E-mail:''' hectoralos@gmail.com<br />
<br />
'''IRC:''' hector2<br />
<br />
'''GitHub:''' [https://github.com/hectoralos hectoralos]<br />
<br />
'''Telegram:''' hectoralos<br />
<br />
'''Skype:''' hectoralos<br />
<br />
== Why is it you are interested in machine translation? ==<br />
<br />
I’m a sociolinguist working on language maintenance and shift. I'm very interested in creating resources for minoritised languages.<br />
<br />
== Why is it that you are interested in Apertium? ==<br />
<br />
*Because Apertium is free/open-source software.<br />
*Because its community is strongly committed to under-resourced and minoritised/marginalised languages.<br />
*Because there is a lot of good work done and being done in it.<br />
*Because it is not only machine translation, but also free resources than can be used for other purposes: e.g. dictionaries, morphological analysers, spellcheckers, etc.<br />
<br />
== Which of the published tasks are you interested in? What do you plan to do? ==<br />
<br />
'''Adopt an unreleased language pair''': I'd like to create the pair French-Arpitan (Franco-Provençal).<br />
<br />
Arpitan does not currently have any support in Apertium (and elsewhere its support is very scarce).<br />
<br />
== My proposal ==<br />
<br />
=== Title ===<br />
Adopting the French-Arpitan language pair.<br />
<br />
=== Major goals ===<br />
* Creating an Arpitan repository in Apertium using the ORB orthography. This should include:<br />
**A morphological dictionary with a naive coverage of at least 92% of non-Wikipedia texts written in ORB Arpitan<br />
**A morphological disambiguation tool using both statistical disambiguation and Constraint Grammar Tools<br />
**A set of post-generation rules<br />
*Developing a translator from French to ORB Arpitan with a WER below 20% and a translator from ORB Arpitan to French with a WER below 25%.<br />
<br />
=== Reasons why Google and Apertium should sponsor it ===<br />
Arpitan is an endangered and heavily under-resourced language. This would be the first translator for it and, as far as I know, its first morphological analyser. From this project a first spell-checker for the language could be generated.<br />
<br />
Arpitan (often called Franco-Provençal) is a Gallo-Romance language spoken in France, Switzerland and Italy. According to the UNESCO Atlas of the World’s Languages in Danger, it has c. 100,000 speakers and is “definitely endangered”. In Switzerland and France the family transmission of the language is almost, if not completely, broken. The result is that more than one third of the speakers are concentrated in the relatively small Aosta Valley, in Italy, and this proportion is increasing. In fact, only in Italy does Arpitan enjoy a certain institutional support, although recently also Switzerland has included it among the languages under the protection of the European Charter for Regional or Minority Languages. In France, it is the only non-oil regional language that is not officially taught in schools (in practice, it is taught in a handful of them in Savoy, on the pretext that Alpine Provençal is taught, and also Occitan teachers examine the students, allegedly for this variety of Occitan, in the French ''Baccalauréat''; this is the only possible way to circumvent the French authorities' complete lack of interest in Arpitan).<br />
<br />
Arpitan was recognized by the Romanists as a language in its own right as early as the end of the 19th century. However, it has not been standardised. It is highly dialectalised, with numerous variants for each word and also multiple morphological and phonetic variants. In a context of centuries-old marginalisation, its written use has been scarce. Several phonetic orthographies have been developed and are used in small circles, each in a different region. As each one is based on a local variety, they do not really help communication across regions. The adoption of any of them by speakers of other varieties is virtually impossible.<br />
<br />
In this context, at the end of the 1990s a supra-dialectal spelling was proposed, which was later followed by a dictionary that also tries to find forms that are as general as possible for the whole linguistic domain. These proposals are also accompanied by others on word inflection. This proposal, called ORB (reference spelling B), is the one I would use in this project.<br />
<br />
The relatively small amount of texts in Arpitan, its great variety and the different competing spellings make it quite difficult to work on. However, it is a language with a dire need of modern linguistic resources to help increase its written use, as well as its status. To this end, Apertium is particularly suitable and ORB seems to be the best bet for the standardization of Arpitan.<br />
<br />
===Resources===<br />
I’m not a speaker of Arpitan, but I know French pretty well, and often read in Occitan too. ORB Arpitan is very easily if one knows these two languages. I have a long-standing friendship with two Arpitan activists (one from Savoy, the other from Switzerland), who are already helping me in this project. I have also contacted Dominique Stich, the creator of ORB, who has given me different resources, answered doubts on the language and is willing to continue helping me in the project.<br />
<br />
From him I got an electronic version of his French-Arpitan and Arpitan-French dictionary together with his permission and that of his publisher (one of my friends: the world is small) to publish the content under a GPL licence. The site arpitan.eu is also helpful. Stich gave me also two translations of him into Arpitan (c. 65,000 words) which I began to use as a corpus. I’m also collecting other texts in ORB.<br />
<br />
The morphology of the (standardised version of the) language is pretty well described in Stich’s works, although still there is often more than one possibility in verb inflection. Clearly, despite Stich's hard work, many decisions will have to be made when generating Arpitan in Apertium, so I’d make maximum use of the corpus and my informants.<br />
<br />
It should be added that dictionaries cover general vocabulary well, but in the current state of language standardization there is a clear lack of specialized terms. If we take into consideration the two fields for which Apertium translators are usually designed (encyclopedic and journalistic articles), this lack will be noticed in the coverage results. To give an example of a highly topical matter, not only are the words "coronavirus" and "Covid" (logically) missing from the dictionaries, but also the Arpitan equivalents of "virus", "contagion", "contagieux", "pandémie", "confinement", "confiner", "épidémiologie", "épidémiologiste/logue". Hopefully, with the help of the collaborators, we will be able to help propose some new terms, although this issue takes up a lot of time and exceeds the goals of this three-month project.<br />
<br />
===Design decisions===<br />
*Dictionaries will not support non-ORB Arpitan since spelling conventions are quite different and so is inflection.<br />
*I plan to use the traditional system of structural transfer in three steps. I consider the new recursive transfer very promising, and I indeed want to use in the new version of the French-Catalan pair in which I regularly work, but for such an under-resourced language as Arpitan, I prefer to use a proven and safe technology, which I am familiar with and which I know it will work well with two (very) close-related languages.<br />
<br />
=== Workplan ===<br />
<br />
{|class="wikitable"<br />
! style="width: 10%" | Week<br />
! style="width: 15%" | Dates<br />
! style="width: 36%" | Goals<br />
! style="width: 13%" | Bidix<br>(excluding<br>proper names)<br />
! style="width: 13%" | WER<br />
! style="width: 13%" | Coverage<br />
|-<br />
! Post-application period<br />
| style="text-align:center" | 1 April - 17 May<br />
|<br />
* Find language resources for Arpitan<br />
*Create an Arpitan corpus<br />
*Continue learning Arpitan and reading in it<br />
| <br />
| <br />
| <br />
|-<br />
! 1<br />
| style="text-align:center" | 18 May - 24 May<br />
|<br />
* Closed categories: determinants, prepositions, conjunctions, relative pronouns, other pronouns<br />
| style="text-align:center" |<br />
| style="text-align:center" | <br />
| style="text-align:center" |<br />
|-<br />
! 2<br />
| style="text-align:center" | 25 May - 31 May<br />
|<br />
* apertium-frp: verbal paradigms<br />
* Expand bilingual dictionary<br />
* Lexical selection rules<br />
| style="text-align:center" | ~1,500<br />
| style="text-align:center" | <br />
| style="text-align:center" |<br />
|-<br />
! 3<br />
| style="text-align:center" | 1 June - 7 June<br />
|<br />
* Expand bilingual dictionary<br />
* Lexical selection rules<br />
| style="text-align:center" | ~3,000<br />
| style="text-align:center" | <br />
| style="text-align:center" | <br />
|-<br />
! 4<br />
| style="text-align:center" | 8 June - 14 June<br />
|<br />
* Expand bilingual dictionary<br />
* Lexical selection rules<br />
| style="text-align:center" | ~4,500<br />
| style="text-align:center" | <br />
| style="text-align:center" | <br />
|-<br />
! 5<br />
| style="text-align:center" | 15 June - 21 June<br />
|<br />
* Expand bilingual dictionary<br />
* Lexical selection rules<br />
'''First evaluation''' (15-19 June)<br />
| style="text-align:center" | ~6,000<br />
| style="text-align:center" | <br />
| style="text-align:center" | >80% (fra > frp)<br>>85% (frp > fra)<br />
<br />
|-<br />
! 6<br />
| style="text-align:center" | 22 June - 28 June<br />
|<br />
* Expand bilingual dictionary<br />
* Lexical selection rules<br />
| style="text-align:center" | ~7,500<br />
| style="text-align:center" | <br />
| style="text-align:center" | <br />
|-<br />
! 7<br />
| style="text-align:center" | 29 June - 5 July<br />
|<br />
* Expand bilingual dictionary<br />
* Lexical selection rules<br />
* Transfer rules fra-frp<br />
| style="text-align:center" | ~8,500<br />
| style="text-align:center" | <br />
| style="text-align:center" | <br />
|-<br />
! 8<br />
| style="text-align:center" | 6 July - 12 July<br />
|<br />
* Expand bilingual dictionary<br />
* Lexical selection rules<br />
* Transfer rules fra-frp<br />
* Manual disambiguation of frp texts<br />
| style="text-align:center" | ~9,500<br />
| style="text-align:center" | <br />
| style="text-align:center" | <br />
|-<br />
! 9<br />
| style="text-align:center" | 13 July - 19 July<br />
|<br />
* Expand bilingual dictionary<br />
* Lexical selection rules<br />
* Transfer rules fra-frp<br />
* Manual disambiguation of frp texts<br />
* Disambiguation rules frp<br />
'''Second evaluation''' (13-17 July)<br />
| style="text-align:center" | ~10,500<br />
| style="text-align:center" | <25% (fra-frp)<br />
| style="text-align:center" | ~89% (fra > frp)<br>~92% (frp > fra)<br />
<br />
|-<br />
! 10<br />
| style="text-align:center" | 20 July - 26 July<br />
|<br />
* Expand bilingual dictionary<br />
* Lexical selection rules<br />
* Disambiguation rules frp<br />
* Transfer rules frp-fra<br />
| style="text-align:center" | ~11,500<br />
| style="text-align:center" | <br />
| style="text-align:center" | <br />
|-<br />
! 11<br />
| style="text-align:center" | 27 July - 2 August<br />
|<br />
* Expand bilingual dictionary<br />
* Lexical selection rules<br />
* Transfer rules frp-fra<br />
* Testvoc frp-fra, fra-frp: closed categories, vblex<br />
| style="text-align:center" | ~12,500<br />
| style="text-align:center" | <br />
| style="text-align:center" | <br />
|-<br />
! 12<br />
| style="text-align:center" | 3 August - 9 August<br />
|<br />
* Testing the frp-fra translator<br />
* Add words, rules<br />
* Testvoc frp-fra, fra-frp: adj, adv<br />
| style="text-align:center" | ~12,750<br />
| style="text-align:center" | <br />
| style="text-align:center" |<br />
|-<br />
! 13<br />
| style="text-align:center" | 10 August - 16 August<br />
|<br />
* Testing the fra-frp translator<br />
* Add words, rules<br />
* Testvoc frp-fra, fra-frp: n<br />
'''Final evaluation''' (10-17 August)<br />
| style="text-align:center" | ~13,000<br />
| style="text-align:center" | <20% (fra > frp)<br><25% (frp > fra)<br />
| style="text-align:center" | ~90.0% (fra > frp)<br>~93.0% (frp > fra)<br />
|}<br />
<br />
== List your skills and give evidence of your qualifications ==<br />
I once got a computer engineering (Universitat Politècnica de Catalunya, 1988), but I’ve forgotten almost everything on programming (except vi, regular expressions and writing short Perl scripts). I also got a BA on linguistics (Universitat de Barcelona, 2008). I’ve been working on Apertium for several years. In 2011, I created the Esperanto-French pair and new releases of the Esperanto-Catalan and Esperanto-Spanish pairs. I’ve also been working on new releases of the French-Catalan pair (2017, 2018, 2019 and 2020).<br />
<br />
I’ve mentored and was strongly involved in the GSoC projects on Italian-Sardinian (2016), Catalan-Sardinian (2017) and French-Occitan (2018). In all of them we released new one-way language pairs just after the end of the GSoC. In 2019, I got myself a GSoC stipend and created new releases for the Catalan-Italian and Catalan-Portuguese pairs. These new releases included the direction Catalan > Italian, which was new, and the generation of three “flavours” of Portuguese.<br />
<br />
I’m a fluent speaker of French, as well as a fluent reader of most of Romance languages, including ORB Arpitan. I’ll have help for the evaluation of the translations into Arpitan, since I don’t speak it and have become familiar with it only in the last few months, so I can't see only part of the errors when generating texts in it.<br />
<br />
== Coding challenge ==<br />
I have created [https://github.com/apertium/apertium-frp apertium-frp] and [https://github.com/apertium/apertium-fra-frp apertium-fra-frp]. You can test the challenge by cloning, compiling and typing in apertium-fra-frp:<br />
<blockquote><br />
cat [https://github.com/apertium/apertium-fra/blob/master/texts/cuento.fra.txt ../apertium-fra/texts/cuento.fra.txt] | apertium -d . fra-frp<br><br />
cat [https://github.com/apertium/apertium-frp/blob/master/texts/cuento.frp.txt ../apertium-frp/texts/cuento.frp.txt] | apertium -d . frp-fra<br />
</blockquote><br />
<br />
The translation into Arpitan is [https://github.com/apertium/apertium-fra-frp/blob/master/challenge/cuento-fra-frp.txt here].<br />
<br />
The translation into French is [https://github.com/apertium/apertium-fra-frp/blob/master/challenge/cuento-frp-fra.txt here].<br />
<br />
There are still a few unknown words. Almost all are irregular verbs, for which and I haven’t yet entered the paradigm.<br />
<br />
== List any non-Summer-of-Code plans you have for the Summer ==<br />
<br />
I can guarantee at least 30 hours per week of work during the whole Summer. As I love this kind of work, I'm sure I'll be engaged quite more.<br />
<br />
I have to submit the last two short works for two subjects of the master I am studying on June 1 and 8, but I should be able to finish the last one in the beginning of May. Due to coronavius, it is hardly possible that I will travel on holiday with my family for a couple of weeks in July, as I did last year (and I still was able to work 30 hours or more in the project). In the unlikely event that one week I do not reach 30 hours of work, I would recover these hours.<br />
<br />
<br />
[[Category:GSoC 2020 student proposals]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=User:Pmodi/GSOC_2020_proposal:_Hindi-Punjabi&diff=71497User:Pmodi/GSOC 2020 proposal: Hindi-Punjabi2020-03-27T00:56:08Z<p>ScoopGracie: ScoopGracie moved page Pmodi/GSOC 2020 proposal: Hindi-Punjabi to User:Pmodi/GSOC 2020 proposal: Hindi-Punjabi: These go in userspace</p>
<hr />
<div><br />
== Contact Information ==<br />
'''Name:''' Priyank Modi<br /><br />
'''Email:''' priyankmodi99@gmail.com<br /><br />
'''Current Designation:''' Undergraduate Researcher in the LTRC Lab, IIIT Hyderabad (completing 6th semester/3rd year in April '20) and a Teaching Assistant for Linguistics courses <br /><br />
'''IRC:''' pmodi<br /><br />
'''Timezone:''' GMT +0530 hrs<br /><br />
'''Linkedin:''' https://www.linkedin.com/in/priyank-modi-81584b175/ <br /><br />
'''Github:''' https://github.com/priyankmodiPM <br /><br />
<br />
== Why I am interested in Apertium ==<br />
Because Apertium is free/open-source software.<br /><br />
Because its community is strongly committed to under-resourced and minoritised/marginalised languages. <br /><br />
Because there is lot of good work done and being done in it. <br /><br />
Because it is not only machine translation, but also free resources than can be used for other purposes: e.g. dictionaries, morphological analysers, spellcheckers, etc. <br /><br />
<br />
== Which of the published tasks are you interested in? What do you plan to do? ==<br />
Adopt an unreleased language pair. I plan on developing the Hindi-Punjabi language pair in both directions i.e. hin-pan and pan-hin. This'll involve improving the monolingual dictionaries for both languages, the hin-pan bilingual dictionary and writing suitable transfer rules to bring this pair to a releasable state.<br />
<br />
== My Proposal ==<br />
<br />
=== Why Google and Apertium should sponsor it ===<br />
* Both Hindi and Punjabi are widely spoken languages, both by number of speakers and geographic spread. Despite that, Punjabi especially has very limited online resources. <br />
* Services like Google Translate give unsatisfactory results when it comes to translation of this pair(see Section 2.1) On the contrary, I was able to achieve close to human translation for some sentences using minimal rules and time(see Section 3 : Coding Challenge). <br />
* I believe the Apertium architecture is suited perfectly for this pair and can replace the current state-of-art translator for this pair.<br />
* This is an important project(since it adds diversity to Apertium and translation systems in general) which requires at least 2-3 months of dedicated work and can be an important resource.<br />
<br />
=== How and who it will benefit in society ===<br />
As mentioned above, the Apertium community is strongly committed to under-resourced and minoritised/marginalised languages and Google helps its own way via programs like GSoC and GCI. There exist many local cultural movements in Africa with the goal of developing language and opening to the world but they generally fail to duel on a scientific basis. This project will definitely mark a starting point or proof of concept in Machine Translation in Cameroon and will greatly have a positive impact on language development.<br />
<br />
=== Google Translate : Analysis and comparison ===<br />
Google Translate provides an interface to translate the pair in question. I have analysed the results of the translation into Punjabi from Google. The numerical results(computed on a small set of sentences from the coding challenge. The human translation which has been reviewed by 3 annotators is also available in the repo) are given below(source-target):<br />
* hin-pan: 14.0% WER<br />
* pan-hin: 21.6% WER<br />
<br />
The results are far from wonderful, especially when it comes to longer sentences with less frequently used words. Seemingly, Google translates using both Spanish and English as bridge languages, as can be seen, for example, by words that appear in these two languages in the final text (supposedly in Catalan) and that were not in the original Italian or Portuguese text. The use of English as intermediate between Romance languages causes problems known to all users, such as the translation of p2.pl verb forms with elided subject to p2.sg, the incorrect choice of past times in the verbs and the disappearance of some pronouns. Here is an example of the last case of the Italian test text (randomly obtained):<br />
<br />
Original text (bold mine):<br />
<blockquote><br />
altri invece '''ne''' hanno apprezzato la spontaneità, la tenacia e l'affettuosità<br />
</blockquote><br />
<br />
Google translation:<br />
<blockquote><br />
altres han apreciat '''la seva''' espontaneïtat, tenacitat i afecte<br />
</blockquote><br />
<br />
Post-edited translation:<br />
<blockquote><br />
altres '''n''''han apreciat l'espontaneïtat, tenacitat i afecte<br />
</blockquote><br />
<br />
It should be added that, although Google translations tend to be more phraseological than the ones obtained by rules, they are also much more difficult to post-edit. The reason is that, while the translation by rules often makes evident and even expected errors, the neuronal translation significantly changes the text, reordering parts of the sentence, removing or putting words, changing singular to plural or plural to singular (!), and modifying expressions. The evaluation of whether the meaning is the same as the original requires a lot more time. This has been quite clear when I have made the post-edition of both the Apertium and Google translations for the Italian and Portuguese texts.<br />
<br />
=== Current state of dictionaries ===<br />
A released module already exists for Hindi(as part of the urd-hin pair). However there still exist a lot of anomalies in the Hindi mono-dictionary. I've compiled a preliminary version of list of some these here[insert link]. Apart from these, the existing state of the hin-pan bi-dictionary also needs massive improvement. The first step of this project will be to revise these lists of issues and come up with a sustainable solution. It'll be crucial that the changes made, especially to the Hindi mono-dictionary do no affect the urd-hin pair(and the hindi-begali, hindi-marathi and hindi-gujarati pairs which also have little but some work done) in a negative way.<br />
<br />
=== Resources ===<br />
[to be added - under confirmation for public use]<br />
<br />
=== Workplan ===<br />
<br />
{| class="wikitable" style="background-color:#b3ffb3;"<br />
! style="width: 13%" | PHASE<br />
! style="width: 12%" | DURATION<br />
! style="width: 36%" | GOALS OF THE WEEK<br />
! style="width: 13%" | BIDIX<br />
! style="width: 13%" | WER<br />
! style="width: 13%" | Coverage<br />
|-style="background-color:#dbfedb;"<br />
| style="text-align:center" | COMMUNITY BONDING PERIOD<br />
| <br />
* START:April 26th<br />
* END:May 17th<br />
| <br />
* List and discuss implementation choices of hin-pan bidix and urd-hin pair<br />
* Reading up on the details of Transfer rules(whether or not a 3-stage transfer is the best way for this pair) and assigning weights<br />
* Finding Language Resources<br />
* Making Frequency lists<br />
| <br />
| <br />
| <br />
|-style="background-color:#b3ffb3;"<br />
| style="text-align:center" | Week ONE : CLOSED CATEGORIES<br />
| <br />
* START:May 18th <br />
* END:May 24th<br />
| <br />
* Function words(voc prn, cnj, det, prn, post, gen_endings)<br />
* Transfer rules for post-positions<br />
| <br />
|<br />
|-style="background-color:#aaffaa;"<br />
| style="text-align:center" | Week TWO : Adjectives<br />
| <br />
* START:May 25th<br />
* END:May 31st<br />
| <br />
* Punjabi mono-dictionary : adj and adv<br />
* Expanding bilingual dictionary<br />
* Lexical selection rules for adj and adv<br />
| <br />
|<br />
|<br />
|-style="background-color:#91f991;;"<br />
| style="text-align:center" | WEEK THREE: Verbal Paradigms<br />
| <br />
* START:June 1st<br />
* END:June 7th<br />
| <br />
* Punjabi mono-dictionary : Verbal paradigms(vblex, vbser, vaux)<br />
* Expanding bilingual dictionary<br />
* Lexical selection rules for verbs<br />
* test adj, adv<br />
| style="text-align:center" | ~ 1,000<br />
|<br />
|<br />
* Third version of the wrapper with all functions importable from python.<br />
|-style="background-color:#82fa82;"<br />
| style="text-align:center" | Week FOUR: Dictionary Expansion<br />
| <br />
* START:June 8th<br />
* END:June 14th<br />
| <br />
* Expanding bilingual dictionary<br />
* Lexical selection rules<br />
| style="text-align:center" | ~ 3,500<br />
| <br />
|<br />
|-style="background-color: #64ff64;"<br />
| style="text-align:center" | Week FIVE<br />
| <br />
* START:June 15th<br />
* END:June 21st<br />
| <br />
* Expanding bilingual dictionary<br />
* Lexical selection rules<br />
| style="text-align:center" | ~ 5,500<br />
| <br />
|<br />
|-style="background-color:#3dff3d;"<br />
| style="text-align:center" | Week SIX<br />
| <br />
* START:June 15th<br />
* END:June 21st<br />
| <br />
* Expanding bilingual dictionary<br />
* Lexical selection rules<br />
| style="text-align:center" | ~ 7,500<br />
| <br />
|<br />
|-style="background-color:#13ff13;"<br />
| style="text-align:center" | Week SEVEN<br />
| <br />
* START:June 22nd<br />
* END:June 28th<br />
| <br />
* Expanding bilingual dictionary<br />
* Lexical selection rules<br />
| style="text-align:center" | ~ 9,000<br />
| <br />
|<br />
|-style="background-color:#00ee00;"<br />
| style="text-align:center" | Week EIGHT<br />
| <br />
* START:June 29th<br />
* END:July 5th<br />
| <br />
* Expanding bilingual dictionary<br />
* Lexical selection rules<br />
'''First Evaluation(June 29th - July 3rd)'''<br />
| style="text-align:center" | ~ 7,500<br />
| <br />
|<br />
|-style="background-color: #00df00;"<br />
| style="text-align:center" | Week NINE<br />
| <br />
* START:July 6th<br />
* END:July 12th<br />
| <br />
* Expanding bilingual dictionary<br />
* Lexical selection rules<br />
| style="text-align:center" | ~ 7,500<br />
| <br />
|<br />
|-style="background-color:#00d700;"<br />
| style="text-align:center" | Week TEN<br />
| <br />
* START:July 13th<br />
* END:July 19th<br />
| <br />
* Expanding bilingual dictionary<br />
* Lexical selection rules<br />
| style="text-align:center" | ~ 7,500<br />
| <br />
|<br />
|-style="background-color:#00b600;"<br />
| style="text-align:center" | Week ELEVEN<br />
| <br />
* START:July 20th<br />
* END:July 26th<br />
| <br />
* Expanding bilingual dictionary<br />
* Lexical selection rules<br />
| style="text-align:center" | ~ 7,500<br />
| <br />
|<br />
|-style="background-color:#009d00;"<br />
| style="text-align:center" | Week TWELVE<br />
| <br />
* START:July 27th<br />
* END:August 2nd<br />
| <br />
* Expanding bilingual dictionary<br />
* Lexical selection rules<br />
'''Second Evaluation(July 27th - Jult 31st)'''<br />
| style="text-align:center" | ~ 7,500<br />
| <br />
|<br />
|-style="background-color:#008a00;"<br />
| style="text-align:center" | Week THIRTEEN<br />
| <br />
* START:August 3rd<br />
* END:August 9th<br />
| <br />
* Expanding bilingual dictionary<br />
* Lexical selection rules<br />
| style="text-align:center" | ~ 7,500<br />
| <br />
|<br />
|-style="background-color:#007e00;"<br />
| style="text-align:center" | Week FOURTEEN<br />
| <br />
* START:August 10th<br />
* END:August 16th<br />
| <br />
* Expanding bilingual dictionary<br />
* Lexical selection rules<br />
| style="text-align:center" | ~ 7,500<br />
| <br />
|<br />
|-style="background-color:#006d00;"<br />
| style="text-align:center" | Week FIFTEEN<br />
| <br />
* START:August 17th<br />
* END:August 23rd<br />
| <br />
* Expanding bilingual dictionary<br />
* Lexical selection rules<br />
| style="text-align:center" | ~ 7,500<br />
| <br />
|<br />
|-style="background-color:#005a00;"<br />
| style="text-align:center" | Week FIFTEEN<br />
| <br />
* START:August 24th<br />
* END:August 30th<br />
| <br />
* Expanding bilingual dictionary<br />
* Lexical selection rules<br />
'''Final evaluation(August 24th - August 31st)<br />
| style="text-align:center" | ~ 7,500<br />
| <br />
|<br />
|}<br />
<br />
== Skills ==<br />
I'm currently a third year(commencing start of April '20 hopefully :D ) student at IIIT Hyderabad where I'm studying Computational Linguistics. It is a dual degree course where we study Computer Science, Linguistics, NLP and more.<br />
<br />
I've been interested in linguistics from the very beginning and due to the rigorous programming courses, I'm also adept at several programming languages like Python, C++, XML, Bash Scripting, etc. I'm skilled in writing Algorithms. Data Structures, and Machine Learning Algorithms as well.<br />
<br />
I also have a lot of experience studying and generating data which I feel is essential in solving any problem, especially the one mentioned in this proposal. My paper on ''''Hindi TimeBank: An ISO-TimeML Annotated Reference Corpus'''' recently got accepted in 16th Joint ACL - ISO Workshop on Interoperable Semantic Annotation at '''LREC 2020'''. I am working on extending the same for Punjabi using Transfer learning.<br />
<br />
I am also closely involved with the committee conducting Asia-Pacific Linguistics Olympiad(which holds a camp, mentors and prepares students for the International Linguistics Olympiad) and help with the organisation and judging for the same.<br />
<br />
Due to the focused nature of our courses, I have worked in several projects, such as building Anaphora Resolution systems, Abstractive Summarizers(using Pointer-generators, hierarchical attention and transformers), POS Taggers, Named Entity Recognisers, simple Q-A systems, etc. all of which required a working understanding of Natural Language Processing. Some of these projects aren't available on GitHub because of the privacy settings but can be provided if required.<br />
<br />
I am fluent in English, Hindi and Punjabi.<br />
<br />
== Coding challenge ==<br />
I've completed the coding challenge for translation from Hindi into Punjabi. You can find my work here : <br />
Original corpus(source lang-hin) - <br />
Translated output(target lang-pan) -<br />
Human Translation(pan) - <br />
<br />
== Non-Summer-of-Code plans for the Summer ==<br />
Since I'll be having my college summer vacations for almost the entire duration of the project, I can easily spend 30-40 hours per week on the project. Since, the academic schedule might vary a little bit due to lock downs for prevention of COVID-19, I'll be starting work early and cover the problems in the post-application period. I've also kept workload slightly heavier in the first 2 weeks to cover up any unlikely, uncertain extensions in academics that might show up. Even then, I can spend around 20 hours a week in any case(note that this is a very unlikely situation and even then this period won't last more than a couple of weeks since the coursework is already underway online and is expected to be over before start of the project).</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=Pmodi/GSOC_2020_proposal:_Hindi-Punjabi&diff=71498Pmodi/GSOC 2020 proposal: Hindi-Punjabi2020-03-27T00:56:08Z<p>ScoopGracie: ScoopGracie moved page Pmodi/GSOC 2020 proposal: Hindi-Punjabi to User:Pmodi/GSOC 2020 proposal: Hindi-Punjabi: These go in userspace</p>
<hr />
<div>#REDIRECT [[User:Pmodi/GSOC 2020 proposal: Hindi-Punjabi]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=Lemma&diff=71496Lemma2020-03-27T00:55:23Z<p>ScoopGracie: Add examples</p>
<hr />
<div>[[Lemme|En français]]<br />
<br />
The '''lemma''' (or citation form, base form, head word) is the canonical form of a word. It is the form of the word that is typically used in paper dictionaries.<br />
<br />
==Examples==<br />
The lemma of "are" is "be".<br />
<br />
The lemma of "cats" is "cat".<br />
<br />
The lemma of "children" is "child".<br />
<br />
The lemma of "lemmas" is "lemma".<br />
<br />
==See also==<br />
<br />
* [[Surface form]]<br />
* [[Lexical unit]]<br />
<br />
[[Category:Terminology]]<br />
[[Category:Documentation in English]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=User:Purplemoon/GSOC_2020_proposal:_IRAQI_T%C3%9CRKMEN&diff=71494User:Purplemoon/GSOC 2020 proposal: IRAQI TÜRKMEN2020-03-27T00:51:59Z<p>ScoopGracie: ScoopGracie moved page Sevilay BAYATLI/GSOC 2020 proposal: IRAQI TÜRKMEN to User:Purplemoon/GSOC 2020 proposal: IRAQI TÜRKMEN: These belong in userspace</p>
<hr />
<div>== Contact Information ==<br />
<br />
'''Name:''' Sevilay BAYATLI<br />
<br />
'''Location:''' [https://en.wikipedia.org/wiki/Istanbul Istanbul, Turkey]<br />
<br />
'''E-mail:''' sevilaybayatli@gmail.com<br />
<br />
'''IRC:''' piraye<br />
<br />
'''GitHub:''' [https://github.com/sevilaybayatli sevilaybayatli]<br />
<br />
'''Time Zone''' UTC+3<br />
<br />
== Why is it you are interested in machine translation? ==<br />
<br />
== Why is it that you are interested in Apertium? ==<br />
<br />
*Apertium is free/open-source platform with good structured for rule based machine translation systems that makes it a facility to work on under-resourced and minorities/marginalised languages.<br />
*It has very generous and energetic community.</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=Sevilay_BAYATLI/GSOC_2020_proposal:_IRAQI_T%C3%9CRKMEN&diff=71495Sevilay BAYATLI/GSOC 2020 proposal: IRAQI TÜRKMEN2020-03-27T00:51:59Z<p>ScoopGracie: ScoopGracie moved page Sevilay BAYATLI/GSOC 2020 proposal: IRAQI TÜRKMEN to User:Purplemoon/GSOC 2020 proposal: IRAQI TÜRKMEN: These belong in userspace</p>
<hr />
<div>#REDIRECT [[User:Purplemoon/GSOC 2020 proposal: IRAQI TÜRKMEN]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=List_of_Apertium_mentors&diff=71468List of Apertium mentors2020-03-25T23:46:32Z<p>ScoopGracie: I'm willing to help as a mentor</p>
<hr />
<div>We know that some people might be interested in working on Apertium, but not know where to start. We have lots of [[documentation]], but sometimes what you really want to do is sit down and have a chat and ask questions with someone who knows a lot about the project. You might want to tell them what your skills are, what you think you are good at, and ask if they have any ideas for how you might get started. That's where Apertium mentors come in! <br />
<br />
If you decide to contact one of our mentors, the best way would be either on [[IRC]], or by emailing them. Each mentor has a link next to their name that allows you to write them an email (but you'll need an account on the Wiki first!).<br />
<br />
Each of our mentors has a list of languages which they speak (in bold) and which they understand, so you can communicate in the language which you prefer.<br />
<br />
==Mentor profiles==<br />
<br />
{|class="wikitable sortable"<br />
! Photo !! Name !! IRC nick !! Language(s) !! Interests !! Bio <br />
|-<br />
| [[Image:Spectie.260.jpg|100px|center]] || Francis&nbsp;Morton&nbsp;Tyers<br/>([[User:Francis Tyers|wiki]] · [[Special:Emailuser/Francis Tyers|email]]) || spectie, spectei, spectre || '''english''', '''castellano''', '''català''',<br/> norsk, português, français, русский || Under-resourced, regional, and marginalised languages. || I'm a postdoc at UiT Norgga árktalaš universtehta. Apart from machine translation, I'm interested in rule-based approaches to morphological analysis and disambiguation, dependency grammars and lexical selection.<br />
|-<br />
| [[Image:unhammer.jpg|100px|center]] || Kevin&nbsp;Brubeck&nbsp;Unhammer<br/>([[User:Unhammer|wiki]] · [[Special:Emailuser/Unhammer|email]]) || unhammer, unhammerd, rehammer || '''norsk''', '''english''', <br/> deutsch, nederlands || Rule-based NLP, marginalised languages. || I've worked mostly on Norwegian and Sámi language pairs in Apertium, as well as Constraint Grammar disambiguation, but take an interest in pretty much anything related to natural language text processing.<br />
|-<br />
| [[Image:Jonathan at Gullfoss 2.jpg|100px|center]] || Jonathan&nbsp;North&nbsp;Washington<br />([[User:Firespeaker|wiki]] · [[Special:Emailuser/Firespeaker|email]]) || firespeaker, jonorthwash, kd5cfx || '''english''', '''қазақша''', '''кыргызча''', '''русский''', <br/> татарча, ўзбекча/o'zbekcha, türkçe, халх/монгол, français, español || Phonetics/phonology, language documentation, Turkic languages || I'm an Assistant Professor of Linguistics at Swarthmore College. Besides computational linguistics, I work on phonetics, phonology, historical linguistics, and language documentation, and spend as much time as I can on Turkic languages. I am especially well versed in developing computational morphologies and phonologies using [[lexc]] and [[twol]].<br />
|-<br />
| [[Image:Jacob.jpg|100px|center]] || Jacob&nbsp;Nordfalk<br/>([[User:Jacob_Nordfalk|wiki]] · [[Special:Emailuser/Jacob_Nordfalk|email]]) || jacobEo || '''dansk''', '''esperanto''', '''norsk''', '''english''', <br/> svenska, deutsch, nepali || java, mobile computing, esperanto || I am an associate professor in computer science. I've worked mostly on the Esperanto-English and a little on Swedish-Danish pairs in Apertium, as well as the core code ([[lttoolbox-java]]), Android, dixtools.<br />
|-<br />
| [[Image:Zfe.jpg|100px|center]] || Gianluca&nbsp;Grossi<br/>([[User:Zfe|wiki]]) || zfe || '''italiano''', '''american''', '''türkçe'''<br/>english || mobile computing, modern Anatolian Turkish, Italian, Latin || I am teaching Italian in Istanbul. I've worked mostly on Turkish (see [[turmorph]]). Interested in potential uses of apertium on iOS platform, dictionaries fetishist.<br />
|-<br />
| [[Image:mlf-photo.jpg|100px|center]] || Mikel L. Forcada<br/>([[User:mlforcada|wiki]] · [[Special:Emailuser/Mlforcada|email]]) || mlforcada || '''euskara''', '''català'''. '''español''', '''english''', <br/>português, français, italiano, hrvatsko-bosansko-srpski; esperanto, interlingua || finite-state theory, machine translation and computer-aided translation || Professor of Computer Science at the Universitat d'Alacant (Spain).<br />
|-<br />
| [[Image:japerez-photo.jpg|100px|center]] || Juan Antonio Pérez-Ortiz<br/>([[User:Japerez|wiki]] · [[Special:Emailuser/Japerez|email]]) || japerez || '''català''', '''español''', '''english''' || machine translation, computer-aided translation, web interfaces for machine translation || Associate professor of Computer Science at the Universitat d'Alacant (Spain). <br />
|-<br />
| [[Image:trond.jpeg|100px|center]] || Trond Trosterud<br/>([[User:Trondtr|wiki]] · [[Special:Emailuser/Trondtr|email]]) || ttr000 || '''norsk''', '''suomi''', '''english''' <br> deutsch, ...|| morphological analysis, machine translation, minority languages || Linguist (Norway).<br />
|-<br />
| [[Image:Fulup.jpg|100px|center]] || Fulup Jakez<br/>([[User:Fulup|wiki]] · [[Special:Emailuser/Fulup|email]]) || no account || '''Breton''', '''French''', '''Spanish''' <br> English, some Namtrik, Welsh, Basque & Catalan...|| machine translation, lexicography, minority languages, language policy || Director of a language planning body (Brittany).<br />
|-<br />
| [[File:Xavivars.jpg|100px|center]] || Xavi Ivars<br/>([[User:Xavivars|wiki]] · [[Special:Emailuser/Xavivars|email]]) || xavivars || '''català''' <small>(or '''valencià''', I don't care about the name)</small><br /> '''español''', '''English''',<br /> un peu de français|| Catalan resources, under-resourced languages, NLP tools || Software engineer, some background on NLP tools<br />
|-<br />
| || Youssef Oualmakran ([[User:Youssefsan|wiki]] · [[Special:Emailuser/Youssefsan|email]]) || youssef || '''Français''', '''Español''', '''English''', '''Català''', '''Neederlands''', a bit of German, Arabic and much less of some other languages || Interested in Maltese, Arabic and a few other languages || Degree in translation and in power engineering<br />
|-<br />
| [[Image:Flammie.jpg|100px|center]] || Flammie<br/>([[User:TommiPirinen|wiki]] · [[Special:Emailuser/TommiPirinen|email]]) || Flammie (Flammie[m]) || '''fin''', '''krl''', '''Urj''' || Uralic languages, some software engineering, FSTs, || I'm a working at [http://hzsk.de|HZSK] at the moment. Apart from machine translation, I'm interested in rule-based approaches to morphological analysis and disambiguation, dependency grammars. I also stubbornly expect people to follow Usenet-era netiquette. Know your [[http://www.catb.org/esr/faqs/smart-questions.html|how to ask questions in a smart way]], and other rants by ESR et al. and profit ;-)<br />
|-<br />
| [[File:Sushain_GCI.jpg|100px|center]] || Sushain Cherivirala<br/>([[User:Sushain|wiki]] · [[Special:Emailuser/Sushain|email]]) || sushain, sushain97 || '''English''', Telugu, español || Python, web development, software systems, computer law || I'm a Computer Science graduate student at Stanford University. I've worn different hats at Facebook, Palantir, Citadel and Stripe in the past and am an amateur numismatist.<br />
|-<br />
| || Memduh Gökırmak<br/>([[User:Memduh|wiki]] · [[Special:Emailuser/Memduh|email]]) || fotonzade || '''English''', '''Turkish''', Kurdish, Farsi || Turkic languages, Iranian languages || Undergraduate at the Istanbul Technical University. <br />
|-<br />
| || Ilnar Salimzianov<br/>([[User:Ilnar.salimzyan|wiki]] · [[Special:Emailuser/Ilnar.salimzyan|email]]) || selimcan || '''Tatar''', '''Russian''', '''English''', '''German''', Kazakh, Turkish || Machine translation between Turkic languages & from Turkic languages to English and Russian || Recent master's graduate in Computational Linguistics from University of Stuttgart. Currently working on a Tatar-to-English machine translator. <br />
|-<br />
| || ScoopGracie<br/>([[User:ScoopGracie|wiki]]) || scoopgracie, graciescoop || '''English''', a bit of Spanish || [[Begiak]], Apertium's IRC bot; Web development; NLP || High school student<br />
|}<br />
<br />
[[Category:Users|*]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=User:Weizhe/GSOC_2020_proposal&diff=71350User:Weizhe/GSOC 2020 proposal2020-03-24T19:10:39Z<p>ScoopGracie: ScoopGracie moved page Weizhe/GSOC 2020 proposal to User:Weizhe/GSOC 2020 proposal: Move to userspace</p>
<hr />
<div><br />
<br />
== Contact ==<br />
<br />
<br />
Name: Weizhe Yang <br />
<br />
E-mail: gavinwzmails@gmail.com <br />
<br />
IRC nick: Weizhe <br />
<br />
Location: Shandong, China <br />
<br />
Time zone: UTC/GMT+8 <br />
<br />
Github: https://github.com/GavinWz<br />
<br />
<br />
<br />
== Self Introduction ==<br />
<br />
<br />
I am a software engineering student. I am familiar with C++ and Python, and proficient in mainstream Linux distribution environments and Bash scripting skills. I have a basic understanding of Unicode encoding and Tokenization flow, and have made some progress in ICU.<br />
<br />
In my first year in university, I joined the '''high-performance computing center'''[http://cs.wfu.edu.cn/2014/0603/c1227a33048/page.htm] of the university as a research assistant. Through research and learning during the period, I have a deep understanding of software architecture and open source projects. In March 2019, I participated in the "LanQiao" national programming competition - a programming skill and algorithm contest - and won the second prize.<br />
<br />
I am committed to improving my skills through project practice, so I think I will learn more professional knowledge through this exercise in Apertium.<br />
<br />
<br />
<br />
== The reason of why I am interested in Apertium ==<br />
<br />
<br />
Apertium focuses on open source software development for translation and lexical analysis. I'm very interested in the various encoding formats and the lexical analysis. Fortunately this is what Apertium does, it can easily translate between different languages and analyze various words.<br />
<br />
<br />
== Target Project ==<br />
<br />
<br />
I found the project I was interested in: "'''Robust tokenization in lttoolbox'''"[http://wiki.apertium.org/wiki/Ideas_for_Google_Summer_of_Code/Robust_tokenisation]. I started this project a month ago and completed the Coding Challenge. The source code and documents for the Coding Challenge are kept in my '''Repository'''[https://github.com/GavinWz/Apertium]. At the same time I also configured the Apertium kernel and lttoolbox environment on my PC, carried out some operations, and had a general understanding of their works. For now I can understand the target project better and deeper so that lexical analysis and tokenization could be handled better.<br />
<br />
<br />
== Proposal ==<br />
<br />
<br />
=== Abstract ===<br />
<br />
<br />
Apertium's lttoolbox tool currently implements the reading and tokenization of characters from input streams, but still has some trouble handling Unicode non-alphabetic characters. When dealing with the longest matched string, it may encounter an unspecified character in the alphabet, which may cause the character read to be aborted, causing the analysis process from left to right (lr) to get out of control, producing unexpected results, and causing more future work to fail.<br />
<br />
My task will be to write algorithms so that the character reading and recognition process can proceed smoothly, regardless of the character type. And after reading, the input text can be separated into some lexemes by a given class of delimiters. Then, a new tokenization operation is carried out to assign the matching token to the obtained lexemes. <br />
<br />
The tokenization process should be divided into four separate processes: read, partition, identify, and tag. For each process, the algorithm should be designed or modified separately from the original code. Before the algorithm design of each process, there will be a ready-made test case, the algorithm design goal is to pass the test. After passing the basic test, it is necessary to propose an in-depth test case, and then update the algorithm to get the latest test results. Through this loop, the program will gradually become more robust and satisfactory. Eventually, the test documentation and source code for each unit will be generated and progressively enhanced. After all the unit designs are completed, splicing of the units may be necessary, and before that there should be a basic test case. After the same iterative approach, the splicing process will be completed quickly. The new tokenization design will then be completed successfully.<br />
<br />
<br />
<br />
=== Benefits to society(Deliverable) ===<br />
<br />
<br />
Upon completion of this project, A smooth lexical analysis provided by lttoolbox will be developed, a complete test documentation will be saved, the compiler is updated, and the documents are upgraded.<br />
<br />
After this, Apertium users using the lttoolbox as a analysis tool will no longer be bothered by Unicode restrictions. It will also give more people access to apertium for a useful lexical analysis software.<br />
<br />
<br />
=== Proposed Plan ===<br />
<br />
<br />
I will start from April 1st. From April 1 to April 28, I have four weeks to prepare for the start, familiarize myself with the way apertium works, and begin to learn the necessary knowledge, such as Unicode encoding, tokenization flow, and ICU syntax. I will contribute to the project as early as possible. So I have a total of 20 weeks to work on the project. There may be a buffer week for the semester exam period (from June 22 to July 3).<br />
<br />
<br />
'''Preparation before start''' (1 April - 28 April)<br />
<br />
<br />
'''Week 1:'''<br />
<br />
<br />
* Read the Unicode literature to gain an in-depth understanding of it<br />
* Learn the working mode and details of tokenization.<br />
* Communicate specific work with mentors and follow advice.<br />
<br />
<br />
'''Week 2 and 3:'''<br />
<br />
<br />
* Learn the ICU, pick out the header files and functions that may be used in future, and get familiar with the query way of the official ICU documents, so that the official explanation will be quickly found when meeting a strange function calls in the future.<br />
* In own program, try to read and tokenize the Unicode string for the longest matching rule from the standard input stream<br />
<br />
<br />
'''Week 4:'''<br />
<br />
<br />
* Read apertium documentation<br />
* Configure the lttoolbox environment<br />
<br />
<br />
'''Official start''' (April 28 - August 18)<br />
<br />
<br />
'''Stage 1''' (April 28-may 26): Familiarity with how lttoolbox works<br />
<br />
<br />
'''Week 1:'''<br />
<br />
<br />
* Discuss specific study plans with Mentors. Identify the specific code that needs to be updated<br />
* Complete the problems left over from the last few weeks and study them further<br />
<br />
<br />
'''Week 2:'''<br />
<br />
<br />
* Familiar with the use of the three commonly used tools of lttoolbox, especially the analytical tool lt-proc<br />
* Select and compile 2-3 dictionaries and test each option them<br />
<br />
<br />
'''Week 3 and 4:'''<br />
<br />
<br />
* Read the relevant code in the lttoolbox repository<br />
* Start with the FSTProcessor::analysis() function and read the lttoolbox source code again<br />
* Understand how lttoolbox implements tokenization<br />
<br />
Deliverable: Familiar with the way apertium works and the use of lttoolbox<br />
<br />
<br />
'''Stage 2''' (May 27-june 23): Algorithms design<br />
<br />
<br />
'''Weeks 5:'''<br />
<br />
<br />
* Discuss with the mentors how to improve the compatibility of lttoolbox with Unicode by combining the ICU with the original code<br />
* Divide tokenization process into four separate processes: reading, partition, identify, and tokenization<br />
<br />
<br />
'''Week 6:'''<br />
<br />
<br />
* Following the TDD pattern, complete the reading and partition processes<br />
<br />
<br />
'''Week 7:'''<br />
<br />
<br />
* Complete the identify processes<br />
<br />
<br />
'''Week 8:'''<br />
<br />
<br />
* Complete the tokenization processes<br />
* First Evaluation<br />
<br />
Deliverable: The algorithms to realize these four functions are obtained<br />
<br />
<br />
'''Stage 3''' (June 24-july 28): Completion of updates to lttoolbox<br />
<br />
<br />
'''Week 9 and 10''' (take the exam) :<br />
<br />
<br />
* Debug the algorithms of Stage 2<br />
<br />
<br />
'''Week 11 and 12:'''<br />
<br />
<br />
* Splice the above four functions together<br />
* Design a function that facilitate user to operate tokenization<br />
<br />
<br />
'''Week 13:'''<br />
<br />
<br />
* Debug<br />
* Optimize the code<br />
* Second Evaluation<br />
<br />
Deliverable: Unit splicing is completed and project functions are all realized<br />
<br />
<br />
'''Stage 4''' (July 29- August 18): Update the compiler and documentation<br />
<br />
<br />
'''Week 14 and 15:'''<br />
<br />
<br />
* Update the compiler so that it can compile the new version of lttoolbox<br />
* Update the lttoolbox documentation<br />
<br />
<br />
'''Week 16:'''<br />
<br />
<br />
* Complete all the unfinished tasks above<br />
* Delivery of the project<br />
<br />
Deliverable: Complete the update of the compiler and documentation<br />
<br />
=== Time Commitment ===<br />
<br />
During the school period (from April 28 to July 3), I will work six days a week. During the working day (Tuesday to Friday), I can guarantee to work more than four hours a day, more than six hours on weekends, more than 30 hours a week.<br />
<br />
During the summer vacation (July 3 - August 18), I will focus on the contribution to Apertium. There is no other work or study tasks. I will work at least 6 days a week (Monday to Saturday), more than 6 hours a day, more than 36 hours a week.<br />
<br />
If everything goes according to plan, the project would hopefully be finished ahead of time.</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=Weizhe/GSOC_2020_proposal&diff=71351Weizhe/GSOC 2020 proposal2020-03-24T19:10:39Z<p>ScoopGracie: ScoopGracie moved page Weizhe/GSOC 2020 proposal to User:Weizhe/GSOC 2020 proposal: Move to userspace</p>
<hr />
<div>#REDIRECT [[User:Weizhe/GSOC 2020 proposal]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=Srj31/GSOC_2020_proposal:Bengali-Hindi_pair&diff=71349Srj31/GSOC 2020 proposal:Bengali-Hindi pair2020-03-24T19:09:25Z<p>ScoopGracie: ScoopGracie moved page Srj31/GSOC 2020 proposal:Bengali-Hindi pair to User:Srj31/GSOC 2020 proposal:Bengali-Hindi pair: Move to userspace</p>
<hr />
<div>#REDIRECT [[User:Srj31/GSOC 2020 proposal:Bengali-Hindi pair]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=User:Srj31/GSOC_2020_proposal:Bengali-Hindi_pair&diff=71348User:Srj31/GSOC 2020 proposal:Bengali-Hindi pair2020-03-24T19:09:24Z<p>ScoopGracie: ScoopGracie moved page Srj31/GSOC 2020 proposal:Bengali-Hindi pair to User:Srj31/GSOC 2020 proposal:Bengali-Hindi pair: Move to userspace</p>
<hr />
<div><br />
== Contact information ==<br />
<br />
Name: Sourabh Raj Jaiswal<br />
<br />
Location: Noida, India<br />
<br />
E-mail address: sourabhrj31@gmail.com<br />
<br />
IRC: srj31<br />
<br />
Timezone: UTC +5:30<br />
<br />
Github: https://github.com/srj31<br />
<br />
<br />
<br />
== '''Why is it that you are interested in Machine Translation and Apertium?''' ==<br />
<br />
I had the honor of representing Team India at the International Linguistics Olympiad 2019 at South Korea. It was this experience and the 3 years of indulging in Linguistics along with my interest in NLP, that got me interested in a Machine Translation project. Apertium being an open source platform for developing rule-based machine translation systems, has intrigued me to contribute to this platform and I will have the opportunity to further create more language pairs for the various languages of India.<br />
<br />
<br />
<br />
== '''Which of the published tasks are you interested in? What do you plan to do?''' ==<br />
<br />
I plan on working on Adopting the unreleased language pair Hindi-Bengali. I plan on improving the pair to be able to translate sentences coherently. As Bengali and Hindi are similar in various linguistic aspects, they will have similar rules thus machine translation would give correct sentences if done correctly.</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=Format_dictionaries&diff=71333Format dictionaries2020-03-24T00:18:28Z<p>ScoopGracie: </p>
<hr />
<div>{{Otherlang|Formatage de dictionnaires|{{French}}}}<br />
<br />
You can use the [[Apertium-dixtools]] package to format each '''<code><e></code>''' tag in the dictionary.<br />
<br />
$ apertium-dixtools '''format-1line''' <dic> <dic.out><br />
<br />
(''Note that the first character in the '''1line''' parameter is the digit '''1''' (one), not the lowercase "L".'')<br />
<br />
For example, these lines:<br />
<br />
<pre><br />
...<br />
<e><br />
<p><br />
<l>estilo<s n="n"/></l><br />
<r>estil<s n="n"/></r><br />
</p><br />
</e><br />
...<br />
</pre><br />
<br />
will be displayed in one line, instead of being indented to various levels on six lines:<br />
<br />
<pre><br />
...<br />
<e><p><l>estilo<s n="n"/></l><r>estil<s n="n"/></r></p></e><br />
...<br />
</pre><br />
<br />
This single-line format can be useful if you use [http://es.wikipedia.org/wiki/Grep grep] or any similar tool to process dictionaries.<br />
<br />
== Aligned formatting ==<br />
You can also add two parameters, namely the positon of the &lt;p&gt; element and the position of the &lt;r&gt; element.<br />
Here alignP = 10 and alignR = 50:<br />
<pre><br />
<!-- Conjunctions - Conjunctive adverb --><br />
<br />
<e> <p><l>antaŭ<b/>ol<s n="cnjadv"/></l> <r>before<s n="cnjadv"/></r></p></e><br />
<e> <p><l>tiel<b/>ke<s n="cnjadv"/></l> <r>so<b/>that<s n="cnjadv"/></r></p></e><br />
<e> <p><l>krom<b/>se<s n="cnjadv"/></l> <r>unless<s n="cnjadv"/></r></p></e><br />
<e> <p><l>dum<s n="cnjadv"/></l> <r>whereas<s n="cnjadv"/></r></p></e><br />
<e> <p><l>ĉar<s n="cnjadv"/></l> <r>because<s n="cnjadv"/></r></p></e><br />
<e r="RL"><p><l>dum<s n="cnjadv"/></l> <r>while<s n="cnjadv"/></r></p></e><br />
<e> <p><l>ĝis<s n="cnjadv"/></l> <r>until<s n="cnjadv"/></r></p></e><br />
<e> <p><l>kiam<s n="cnjadv"/></l> <r>when<s n="cnjadv"/></r></p></e><br />
<e i="yes"><p><l>kiam<s n="cnjadv"/></l> <r>as<s n="cnjadv"/></r></p></e><br />
<e> <p><l>kiel<s n="cnjadv"/></l> <r>as<s n="cnjadv"/></r></p></e><br />
<e r="LR"><p><l>pro<b/>tio<b/>ke<s n="cnjadv"/></l><r>since<s n="cnjadv"/></r></p></e><br />
</pre><br />
<br />
If either value is zero or negative, no alignment will be done.<br />
<br />
==Usage==<br />
<pre><br />
Usage: apertium-dixtools format-1line [alignP alignR] <input-dic> <output-dic><br />
where alignP / alignR: column to align <p> and <r> entries. 0 = no indent.<br />
<br />
Example: ' format-1line old.dix new.dix ' will give indent à la<br />
<e><p><l>dum<s n="cnjadv"/></l><r>whereas<s n="cnjadv"/></r></p></e><br />
<br />
Example: ' format-1line 10 50 old.dix new.dix ' will give indent à la<br />
<e> <p><l>dum<s n="cnjadv"/></l> <r>whereas<s n="cnjadv"/></r></p></e><br />
<br />
Example: ' format-1line 0 50 old.dix new.dix ' will give indent à la<br />
<e><p><l>dum<s n="cnjadv"/></l> <r>whereas<s n="cnjadv"/></r></p></e><br />
<br />
Example: ' format-1line 10 0 old.dix new.dix ' will give indent à la<br />
<e> <p><l>dum<s n="cnjadv"/></l><r>whereas<s n="cnjadv"/></r></p></e><br />
</pre><br />
<br />
<br />
[[Category:Tools]]<br />
[[Category:Dixtools]]<br />
[[Category:Documentation in English]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=Vim&diff=71332Vim2020-03-23T19:35:41Z<p>ScoopGracie: </p>
<hr />
<div>Vim is a text editor. <br />
<br />
It edits text.<br />
<br />
It is a "modal" editor, meaning that you can switch "modes."<br />
Vim starts in Command mode. More on this below.<br />
By pressing 'i', you can switch to Insert mode. In Insert mode, you just move around with the arrow keys or mouse like in a normal editor. To type, well, just type. To get back to Command mode, press Esc.<br />
<br />
==Command mode==<br />
Vim has literally hundreds of different commands. However, you don't need to be overwhelmed. Just know the following, and you'll be fine for starting out.<br />
<br />
* <code>ZZ</code> - save and exit<br />
* <code>:open <file></code> - open <file><br />
* <code>:qa!</code> - discard all changes and exit<br />
* <code>:w</code> - save changes but do not exit<br />
* <code>:w <file></code> - save as <file> (note that this must be followed by <code>:open <file></code> if future <code>:w</code>s should use <file>)<br />
* <code>:%s/<find>/<replace>/g</code> - find <find> and replace it with <replace><br />
* <code>i</code> - switch to Insert mode<br />
<br />
==Editing XML (dix, transfer rules) in vim==<br />
http://www.pinkjuice.com/howto/vimxml/ is a nice guide to editing XML in vim.<br />
<br />
==Editing Xerox formats in vim==<br />
Various people have created lexc/twol syntax files for vim:<br />
* https://github.com/arnsholt/proiel-morphology/tree/master/vim<br />
* https://github.com/flammie/vim-finitestatemorphology (works with vundle as flammie/vim-finitestatemorphology)<br />
* https://github.com/jonorthwash/dotfiles/tree/master/vim<br />
<br />
See also [[Apertium-specific conventions for lexc#Syntax highlighting and folding in vim]]<br />
<br />
[[Category:Documentation in English]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=User:ScoopGracie/PMC/Proposed_bylaws&diff=71326User:ScoopGracie/PMC/Proposed bylaws2020-03-22T21:40:06Z<p>ScoopGracie: </p>
<hr />
<div>'''THESE ARE NOT THE BYLAWS!''' I'm running for PMC, and these are my suggestion. If you have any feedback, please let me know!<br />
== Preamble ==<br />
The mission of the Apertium project is to collaboratively develop free/open-source machine translation for as many languages as possible, and in particular:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To give everyone free, unlimited access to the best possible machine-translation technologies.</li><br />
<li>To maintain a modular, documented, open platform for machine translation and other human language processing tasks</li><br />
<li>To favour the interchange and reuse of existing linguistic data.</li><br />
<li>To make integration with other free/open-source technologies easier.</li><br />
<li>To radically guarantee the reproducibility of machine translation and natural language processing research</li><br />
</ol><br />
And additionally:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To promote the usage of free and open source software.</li><br />
<li>To help combat gender and racial bias in technology.</li><br />
<li>To help support and preserve less widespread languages.</li><br />
</ol><br />
<br />
== Roles and responsibilities ==<br />
<br />
=== Users ===<br />
<br />
<ol start="1"><br />
<li>The most important participants in the project are people who use Apertium. The majority of our developers start out as users and guide their development efforts from the user's perspective</li><br />
<li>Users contribute to the Apertium project by providing feedback to developers in the form of bug reports and feature suggestions. As well, users participate in the Apertium community by helping other users.</li><br />
</ol><br />
<br />
=== Developers ===<br />
<br />
<ol start="3"><br />
<li>Developers are volunteers who are contributing time, code, documentation, or resources to Apertium.</li><br />
<li>For the purposes of these bylaws, a Developer is anyone who has submitted at least one pull request or commit to any Apertium repository in the past twenty-four weeks (168 days, or approximately six months).</li><br />
<li>The Developers of Apertium constitute the Assembly of Developers of Apertium.</li><br />
<li>The project's Developers are responsible for the project's technical management.</li><br />
<li>The Assembly of Developers elects the Project Management Committee of Apertium every even-numbered year in February or whenever a vacancy occurs, whether by resignation, or loss of Developer status.</li><br />
<li>The number of members of the Assembly of Developers of Apertium has no limit.</li><br />
<li>The President of the Project Management Committee will, immediately after a new Project Management Committee begins functioning, nominate a President of the Assembly of Developers, who must be a Developer and may not be a member of the Project Management Committee or of the latest election board. This President will be confirmed by a vote of the Assembly of Developers, and may be referred to as the President of Apertium.</li><br />
<li>The Assembly of Developers decides only on subjects proposed by the Project Management Committee.</li><br />
<li>Once submitted to it, the decisions of the Assembly of Developers are final and binding and cannot be overturned, except as explicitly noted in these Bylaws.</li><br />
<li>One tenth of the Assembly of Developers may decide to attempt to overturn a decision of the Assembly of Developers or Project Management Committee, and the resolution must be passed by three fourths of the Developers.</li><br />
</ol><br />
<br />
=== Project Management Committee ===<br />
<br />
<ol start="13"><br />
<li>The Project Management Committee is formed by seven members of the Assembly designated by it to make the day to day decisions.</li><br />
<li>The Project Management Committee is headed by a President and has six more members, one of whom will act as Secretary and another as Treasurer.</li><br />
<li>All members of the Project Management Committee must be at least thirteen years of age, and the Treasurer must be at least eighteen years of age.</li><br />
<li>The responsibilities of the Project Management Committee include</li><br />
<ol style="list-style-type:lower-alpha" ><br />
<li>Deciding what is distributed as products of Apertium project. In particular, all releases must be approved by the PMC.</li><br />
<li>Maintaining the project's shared resources, including the codebase repository, mailing lists, websites.</li><br />
<li>Speaking on behalf of the project; although, the PMC could give the right to speak on behalf of Apertium to a member of the Assembly of Developers.</li><br />
<li>Resolving licence disputes regarding products of the project.</li><br />
<li>Maintaining these bylaws and other guidelines of the project.</li><br />
<li>Promoting the active engagement of Apertium in larger free/open-source initiatives</li><br />
<li>Attracting external funds to further the objectives of the Apertium project</li><br />
<li>Deciding how to distribute the funds the Apertium project may get as the result of participating in externally-funded initiatives</li><br />
</ol></li><br />
<li>The Project Management Committee votes on all of its decisions.</li><br />
<li>The Project Management Committee has the obligation to submit to the Assembly of Developers the decisions that affect the work of the half or more of the members of the Assembly of Developers, being able to consult in other subjects if believed necessary. </li><br />
<li>Decisions of the PMC are accepted or rejected by the President of the Assembly of Committers, but the PMC may pass a decision despite rejection by the President of the Assembly of Developers with the agreement of five members.</li><br />
<li>Decisions of the Project Management Committee made other than in consultation with the Assembly are immediately filed in a public diary. The Assembly may overturn a PMC decision as described in Bylaw 12.</li><br />
<li>The secretary of the Project Management Committee has the obligation of preparing the diary and presenting it to the Assembly of Developers.</li><br />
<li>While the Treasurer is responsible for financial management, all actions must be approved by a PMC vote.</li><br />
</ol><br />
<br />
=== Bylaw Violation Court of Apertium ===<br />
<ol start="23"><br />
<li>In the case of an alleged violation of the Bylaws by any Developer, a temporary Bylaw Violation Court shall be established.</li><br />
<li>The Bylaw Violation Court of Apertium shall consist of seven Developers chosen at random, who must not be members of the Project Management Committee or include the accused Developer.</li><br />
<li>All members of the Bylaw Violation Court shall agree to a Pledge of Non-bias, as follows:<br />
<br><br />
I, <name>, hereby pledge that I will not act in my own personal interest, in the interest of the accused Developer, or in the interest of the accuser(s), but in the interest of the Apertium project as a whole. My decisions will not be biased based on who the accused or accusing Developer(s) is/are.</li><br />
<li>The Bylaw Violation Court of Apertium shall decide by consensus if the accused Developer has violated the bylaws, and may take action against the Developer up to, and including, permanent loss of Developer status.</li><br />
</ol><br />
<br />
== Election of the Project Management Committee ==<br />
<br />
<ol start="27"><br />
<li>The Assembly of Developers will elect a new Project Management Committee as follows:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>An Election Board of 3 developers (with at least one substitute member; ideally with one substitute each) will run the election. Election Board membership is a volunteer position on a first-come first-served basis.</li><br />
<li>The Project Management Committee will provide the Election Board with all the information needed to run the election</li><br />
<li>Any Developer may run for member of the Project Management Committee</li><br />
<li>Any Developer may run for president of the Project Management Committee</li><br />
<li>Candidates cannot be part of the Election Board</li><br />
<li>When an election is called, the Election Board will publish a census of Developers with right to vote.</li><br />
<li>There will be 7 days for candidates to member and president to come forward</li><br />
<li>The Election Board will proclaim the candidates to President and to Members of the Project Management Committee</li><br />
<li>Once candidates are proclaimed, Developers with the right to vote will send a ballot with:<br />
<ol style="list-style-type:lower-roman" ><br />
<li>The name of a candidate to president of the Project Management Committee, and</li><br />
<li>The name of up to four candidates to members of the Project Management Committee</li><br />
</ol></li><br />
<li>There will be 7 days to send the ballots</li><br />
<li>The Election Board will proclaim as President the candidate to president having received most votes for President and as members the six candidates to member having received the most votes as members</li><br />
<li>The new Project Management Committee will start to function 48 hours after being proclaimed.</li><br />
</li><br />
</ol></li><br />
</ol><br />
<br />
== Amendments ==<br />
<ol start="28"><br />
<li>To begin the bylaw amendment process, one tenth of the Assembly of Developers must submit a proposal to the PMC.</li><br />
<li>If the PMC accepts an amendment, the Assembly of Developers shall vote on the amendment.</li><br />
<li>If half plus one of the Assembly of Developers accept the amendment, it shall become part of these Bylaws.</li><br />
</ol><br />
<br />
== Transitional provisions ==<br />
<br />
<ol start="31"><br />
<li>Bylaw 12 does not apply to the acceptance of these bylaws.</li><br />
<li>Bylaw 12 does not apply to decisions made by the Project Management Committee or Assembly of Committers under the previous Bylaws. These may only be overturned by a replacement decision made using the standard process under these Bylaws.</li><br />
</ol><br />
<br />
[[Category:PMC campaigns 2020]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=User:ScoopGracie/PMC/Proposed_bylaws&diff=71325User:ScoopGracie/PMC/Proposed bylaws2020-03-22T21:19:29Z<p>ScoopGracie: </p>
<hr />
<div>'''THESE ARE NOT THE BYLAWS!''' I'm running for PMC, and these are my suggestion. If you have any feedback, please let me know!<br />
== Preamble ==<br />
The mission of the Apertium project is to collaboratively develop free/open-source machine translation for as many languages as possible, and in particular:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To give everyone free, unlimited access to the best possible machine-translation technologies.</li><br />
<li>To maintain a modular, documented, open platform for machine translation and other human language processing tasks</li><br />
<li>To favour the interchange and reuse of existing linguistic data.</li><br />
<li>To make integration with other free/open-source technologies easier.</li><br />
<li>To radically guarantee the reproducibility of machine translation and natural language processing research</li><br />
</ol><br />
And additionally:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To promote the usage of free and open source software.</li><br />
<li>To help combat gender and racial bias in technology.</li><br />
<li>To help support and preserve less widespread languages.</li><br />
</ol><br />
<br />
== Roles and responsibilities ==<br />
<br />
=== Users ===<br />
<br />
<ol start="1"><br />
<li>The most important participants in the project are people who use Apertium. The majority of our developers start out as users and guide their development efforts from the user's perspective</li><br />
<li>Users contribute to the Apertium project by providing feedback to developers in the form of bug reports and feature suggestions. As well, users participate in the Apertium community by helping other users.</li><br />
</ol><br />
<br />
=== Developers ===<br />
<br />
<ol start="3"><br />
<li>Developers are volunteers who are contributing time, code, documentation, or resources to Apertium.</li><br />
<li>For the purposes of these bylaws, a Developer is anyone who has submitted at least one pull request or commit to any Apertium repository in the past twenty-four weeks (168 days, or approximately six months).</li><br />
<li>The Developers of Apertium constitute the Assembly of Developers of Apertium.</li><br />
<li>The project's Developers are responsible for the project's technical management.</li><br />
<li>The Assembly of Developers elects the Project Management Committee of Apertium every even-numbered year in February or whenever a vacancy occurs, whether by resignation, or loss of Developer status.</li><br />
<li>The number of members of the Assembly of Developers of Apertium has no limit.</li><br />
<li>The President of the Project Management Committee will, immediately after a new Project Management Committee begins functioning, nominate a President of the Assembly of Developers, who must be a Developer and may not be a member of the Project Management Committee or of the latest election board. This President will be confirmed by a vote of the Assembly of Developers, and may be referred to as the President of Apertium.</li><br />
<li>The Assembly of Developers decides only on subjects proposed by the Project Management Committee.</li><br />
<li>Once submitted to it, the decisions of the Assembly of Developers are final and binding and cannot be overturned, except as explicitly noted in these Bylaws.</li><br />
<li>One tenth of the Assembly of Developers may decide to attempt to overturn a decision of the Assembly of Developers or Project Management Committee, and the resolution must be passed by three fourths of the Developers.</li><br />
</ol><br />
<br />
=== Project Management Committee ===<br />
<br />
<ol start="13"><br />
<li>The Project Management Committee is formed by seven members of the Assembly designated by it to make the day to day decisions.</li><br />
<li>The Project Management Committee is headed by a President and has six more members, one of whom will act as Secretary and another as Treasurer.</li><br />
<li>All members of the Project Management Committee must be at least thirteen years of age, and the Treasurer must be at least eighteen years of age.</li><br />
<li>The responsibilities of the Project Management Committee include</li><br />
<ol style="list-style-type:lower-alpha" ><br />
<li>Deciding what is distributed as products of Apertium project. In particular, all releases must be approved by the PMC.</li><br />
<li>Maintaining the project's shared resources, including the codebase repository, mailing lists, websites.</li><br />
<li>Speaking on behalf of the project; although, the PMC could give the right to speak on behalf of Apertium to a member of the Assembly of Developers.</li><br />
<li>Resolving licence disputes regarding products of the project.</li><br />
<li>Maintaining these bylaws and other guidelines of the project.</li><br />
<li>Promoting the active engagement of Apertium in larger free/open-source initiatives</li><br />
<li>Attracting external funds to further the objectives of the Apertium project</li><br />
<li>Deciding how to distribute the funds the Apertium project may get as the result of participating in externally-funded initiatives</li><br />
</ol></li><br />
<li>The Project Management Committee votes on all of its decisions.</li><br />
<li>The Project Management Committee has the obligation to submit to the Assembly of Developers the decisions that affect the work of the half or more of the members of the Assembly of Developers, being able to consult in other subjects if believed necessary. </li><br />
<li>Decisions of the PMC are accepted or rejected by the President of the Assembly of Committers, but the PMC may pass a decision despite rejection by the President of the Assembly of Developers with the agreement of five members.</li><br />
<li>Decisions of the Project Management Committee made other than in consultation with the Assembly are immediately filed in a public diary. The Assembly may overturn a PMC decision as described in Bylaw 12.</li><br />
<li>The secretary of the Project Management Committee has the obligation of preparing the diary and presenting it to the Assembly of Developers.</li><br />
<li>While the Treasurer is responsible for financial management, all actions must be approved by a PMC vote.</li><br />
</ol><br />
<br />
=== Bylaw Violation Court of Apertium ===<br />
<ol start="23"><br />
<li>In the case of an alleged violation of the Bylaws by any Developer, a temporary Bylaw Violation Court shall be established.</li><br />
<li>The Bylaw Violation Court of Apertium shall consist of seven Developers chosen at random, who must not be members of the Project Management Committee or include the accused Developer.</li><br />
<li>All members of the Bylaw Violation Court shall agree to a Pledge of Non-bias, as follows:<br />
<br><br />
I, <name>, hereby pledge that I will not act in my own personal interest, in the interest of the accused Developer, or in the interest of the accuser(s), but in the interest of the Apertium project as a whole. My decisions will not be biased based on who the accused or accusing Developer(s) is/are.</li><br />
<li>The Bylaw Violation Court of Apertium shall decide by consensus if the accused Developer has violated the bylaws, and may take action against the Developer up to, and including, permanent loss of Developer status.</li><br />
</ol><br />
<br />
== Election of the Project Management Committee ==<br />
<br />
<ol start="27"><br />
<li>The Assembly of Developers will elect a new Project Management Committee as follows:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>An Election Board of 3 developers (with at least one substitute member; ideally with one substitute each) will run the election. Election Board membership is a volunteer position on a first-come first-served basis.</li><br />
<li>The Project Management Committee will provide the Election Board with all the information needed to run the election</li><br />
<li>Any Developer may run for member of the Project Management Committee</li><br />
<li>Any Developer may run for president of the Project Management Committee</li><br />
<li>Candidates cannot be part of the Election Board</li><br />
<li>When an election is called, the Election Board will publish a census of Developers with right to vote.</li><br />
<li>There will be 7 days for candidates to member and president to come forward</li><br />
<li>The Election Board will proclaim the candidates to President and to Members of the Project Management Committee</li><br />
<li>Once candidates are proclaimed, Developers with the right to vote will send a ballot with:<br />
<ol style="list-style-type:lower-roman" ><br />
<li>The name of a candidate to president of the Project Management Committee, and</li><br />
<li>The name of up to four candidates to members of the Project Management Committee</li><br />
</ol></li><br />
<li>There will be 7 days to send the ballots</li><br />
<li>The Election Board will proclaim as President the candidate to president having received most votes for President and as members the six candidates to member having received the most votes as members</li><br />
<li>The new Project Management Committee will start to function 48 hours after being proclaimed</li><br />
</li><br />
</ol></li><br />
</ol><br />
<br />
== Amendments ==<br />
<ol start="28"><br />
<li>To begin the bylaw amendment process, one tenth of the Assembly of Developers must submit a proposal to the PMC.</li><br />
<li>If the PMC accepts an amendment, the Assembly of Developers shall vote on the amendment.</li><br />
<li>If half plus one of the Assembly of Developers accept the amendment, it shall become part of these Bylaws.</li><br />
</ol><br />
<br />
== Transitional provisions ==<br />
<br />
<ol start="31"><br />
<li>Bylaw 12 does not apply to the acceptance of these bylaws.</li><br />
<li>Bylaw 12 does not apply to decisions made by the Project Management Committee or Assembly of Committers under the previous Bylaws. These may only be overturned by a replacement decision made using the standard process under these Bylaws.</li><br />
</ol><br />
<br />
[[Category:PMC campaigns 2020]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=User:ScoopGracie/PMC/Proposed_bylaws&diff=71324User:ScoopGracie/PMC/Proposed bylaws2020-03-22T20:47:46Z<p>ScoopGracie: Change it to something more easily calculable</p>
<hr />
<div>'''THESE ARE NOT THE BYLAWS!''' I'm running for PMC, and these are my suggestion. If you have any feedback, please let me know!<br />
== Preamble ==<br />
The mission of the Apertium project is to collaboratively develop free/open-source machine translation for as many languages as possible, and in particular:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To give everyone free, unlimited access to the best possible machine-translation technologies.</li><br />
<li>To maintain a modular, documented, open platform for machine translation and other human language processing tasks</li><br />
<li>To favour the interchange and reuse of existing linguistic data.</li><br />
<li>To make integration with other free/open-source technologies easier.</li><br />
<li>To radically guarantee the reproducibility of machine translation and natural language processing research</li><br />
</ol><br />
And additionally:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To promote the usage of free and open source software.</li><br />
<li>To help combat gender and racial bias in technology.</li><br />
<li>To help support and preserve less widespread languages.</li><br />
</ol><br />
<br />
== Roles and responsibilities ==<br />
<br />
=== Users ===<br />
<br />
<ol start="1"><br />
<li>The most important participants in the project are people who use Apertium. The majority of our developers start out as users and guide their development efforts from the user's perspective</li><br />
<li>Users contribute to the Apertium project by providing feedback to developers in the form of bug reports and feature suggestions. As well, users participate in the Apertium community by helping other users.</li><br />
</ol><br />
<br />
=== Developers ===<br />
<br />
<ol start="3"><br />
<li>Developers are volunteers who are contributing time, code, documentation, or resources to Apertium.</li><br />
<li>For the purposes of these bylaws, a Developer is anyone who has submitted at least three pull requests or commits to any Apertium repository in the past twenty-four weeks (168 days, or approximately six months).</li><br />
<li>The Developers of Apertium constitute the Assembly of Developers of Apertium.</li><br />
<li>The project's Developers are responsible for the project's technical management.</li><br />
<li>The Assembly of Developers elects the Project Management Committee of Apertium every even-numbered year in February or whenever a vacancy occurs, whether by resignation, or loss of Developer status.</li><br />
<li>The number of members of the Assembly of Developers of Apertium has no limit.</li><br />
<li>The President of the Project Management Committee will, immediately after a new Project Management Committee begins functioning, nominate a President of the Assembly of Developers, who must be a Developer and may not be a member of the Project Management Committee or of the latest election board. This President will be confirmed by a vote of the Assembly of Developers, and may be referred to as the President of Apertium.</li><br />
<li>The Assembly of Developers decides only on subjects proposed by the Project Management Committee.</li><br />
<li>Once submitted to it, the decisions of the Assembly of Developers are final and binding and cannot be overturned, except as explicitly noted in these Bylaws.</li><br />
<li>One tenth of the Assembly of Developers may decide to attempt to overturn a decision of the Assembly of Developers or Project Management Committee, and the resolution must be passed by half plus one of the Developers.</li><br />
</ol><br />
<br />
=== Project Management Committee ===<br />
<br />
<ol start="13"><br />
<li>The Project Management Committee is formed by seven members of the Assembly designated by it to make the day to day decisions.</li><br />
<li>The Project Management Committee is headed by a President and has six more members, one of whom will act as Secretary and another as Treasurer.</li><br />
<li>All members of the Project Management Committee must be at least thirteen years of age, and the Treasurer must be at least eighteen years of age.</li><br />
<li>The responsibilities of the Project Management Committee include</li><br />
<ol style="list-style-type:lower-alpha" ><br />
<li>Deciding what is distributed as products of Apertium project. In particular, all releases must be approved by the PMC.</li><br />
<li>Maintaining the project's shared resources, including the codebase repository, mailing lists, websites.</li><br />
<li>Speaking on behalf of the project; although, the PMC could give the right to speak on behalf of Apertium to a member of the Assembly of Developers.</li><br />
<li>Resolving licence disputes regarding products of the project.</li><br />
<li>Maintaining these bylaws and other guidelines of the project.</li><br />
<li>Promoting the active engagement of Apertium in larger free/open-source initiatives</li><br />
<li>Attracting external funds to further the objectives of the Apertium project</li><br />
<li>Deciding how to distribute the funds the Apertium project may get as the result of participating in externally-funded initiatives</li><br />
</ol></li><br />
<li>The Project Management Committee votes on all of its decisions.</li><br />
<li>The Project Management Committee has the obligation to submit to the Assembly of Developers the decisions that affect the work of the half or more of the members of the Assembly of Developers, being able to consult in other subjects if believed necessary. </li><br />
<li>Decisions of the PMC are accepted or rejected by the President of the Assembly of Committers, but the PMC may pass a decision despite rejection by the President of the Assembly of Developers with the agreement of five members.</li><br />
<li>Decisions of the Project Management Committee made other than in consultation with the Assembly are immediately filed in a public diary. The Assembly may overturn a PMC decision as described in Bylaw 12.</li><br />
<li>The secretary of the Project Management Committee has the obligation of preparing the diary and presenting it to the Assembly of Developers.</li><br />
<li>While the Treasurer is responsible for financial management, all actions must be approved by a PMC vote.</li><br />
</ol><br />
<br />
=== Bylaw Violation Court of Apertium ===<br />
<ol start="23"><br />
<li>In the case of an alleged violation of the Bylaws by any Developer, a temporary Bylaw Violation Court shall be established.</li><br />
<li>The Bylaw Violation Court of Apertium shall consist of seven Developers chosen at random, who must not be members of the Project Management Committee or include the accused Developer.</li><br />
<li>All members of the Bylaw Violation Court shall agree to a Pledge of Non-bias, as follows:<br />
<br><br />
I, <name>, hereby pledge that I will not act in my own personal interest, in the interest of the accused Developer, or in the interest of the accuser(s), but in the interest of the Apertium project as a whole. My decisions will not be biased based on who the accused or accusing Developer(s) is/are.</li><br />
<li>The Bylaw Violation Court of Apertium shall decide by consensus if the accused Developer has violated the bylaws, and may take action against the Developer up to, and including, permanent loss of Developer status.</li><br />
</ol><br />
<br />
== Election of the Project Management Committee ==<br />
<br />
<ol start="27"><br />
<li>The Assembly of Developers will elect a new Project Management Committee as follows:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>An Election Board of 3 developers (with at least one substitute member; ideally with one substitute each) will run the election. Election Board membership is a volunteer position on a first-come first-served basis.</li><br />
<li>The Project Management Committee will provide the Election Board with all the information needed to run the election</li><br />
<li>Any Developer may run for member of the Project Management Committee</li><br />
<li>Any Developer may run for president of the Project Management Committee</li><br />
<li>Candidates cannot be part of the Election Board</li><br />
<li>When an election is called, the Election Board will publish a census of Developers with right to vote.</li><br />
<li>There will be 7 days for candidates to member and president to come forward</li><br />
<li>The Election Board will proclaim the candidates to President and to Members of the Project Management Committee</li><br />
<li>Once candidates are proclaimed, Developers with the right to vote will send a ballot with:<br />
<ol style="list-style-type:lower-roman" ><br />
<li>The name of a candidate to president of the Project Management Committee, and</li><br />
<li>The name of up to four candidates to members of the Project Management Committee</li><br />
</ol></li><br />
<li>There will be 7 days to send the ballots</li><br />
<li>The Election Board will proclaim as President the candidate to president having received most votes for President and as members the six candidates to member having received the most votes as members</li><br />
<li>The new Project Management Committee will start to function 48 hours after being proclaimed</li><br />
</li><br />
</ol></li><br />
</ol><br />
<br />
== Amendments ==<br />
<ol start="28"><br />
<li>To begin the bylaw amendment process, one tenth of the Assembly of Developers must submit a proposal to the PMC.</li><br />
<li>If the PMC accepts an amendment, the Assembly of Developers shall vote on the amendment.</li><br />
<li>If half plus one of the Assembly of Developers accept the amendment, it shall become part of these Bylaws.</li><br />
</ol><br />
<br />
== Transitional provisions ==<br />
<br />
<ol start="31"><br />
<li>Bylaw 12 does not apply to the acceptance of these bylaws.</li><br />
<li>Bylaw 12 does not apply to decisions made by the Project Management Committee or Assembly of Committers under the previous Bylaws. These may only be overturned by a replacement decision made using the standard process under these Bylaws.</li><br />
</ol><br />
<br />
[[Category:PMC campaigns 2020]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=User:ScoopGracie/PMC/Proposed_bylaws&diff=71233User:ScoopGracie/PMC/Proposed bylaws2020-03-18T19:07:21Z<p>ScoopGracie: Undo revision 71222 by ScoopGracie (talk)</p>
<hr />
<div>'''THESE ARE NOT THE BYLAWS!''' I'm running for PMC, and these are my suggestion. If you have any feedback, please let me know!<br />
== Preamble ==<br />
The mission of the Apertium project is to collaboratively develop free/open-source machine translation for as many languages as possible, and in particular:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To give everyone free, unlimited access to the best possible machine-translation technologies.</li><br />
<li>To maintain a modular, documented, open platform for machine translation and other human language processing tasks</li><br />
<li>To favour the interchange and reuse of existing linguistic data.</li><br />
<li>To make integration with other free/open-source technologies easier.</li><br />
<li>To radically guarantee the reproducibility of machine translation and natural language processing research</li><br />
</ol><br />
And additionally:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To promote the usage of free and open source software.</li><br />
<li>To help combat gender and racial bias in technology.</li><br />
<li>To help support and preserve less widespread languages.</li><br />
</ol><br />
<br />
== Roles and responsibilities ==<br />
<br />
=== Users ===<br />
<br />
<ol start="1"><br />
<li>The most important participants in the project are people who use Apertium. The majority of our developers start out as users and guide their development efforts from the user's perspective</li><br />
<li>Users contribute to the Apertium project by providing feedback to developers in the form of bug reports and feature suggestions. As well, users participate in the Apertium community by helping other users.</li><br />
</ol><br />
<br />
=== Developers ===<br />
<br />
<ol start="3"><br />
<li>Developers are volunteers who are contributing time, code, documentation, or resources to Apertium.</li><br />
<li>For the purposes of these bylaws, a Developer is anyone who has submitted at least three pull requests or commits to any Apertium repository in the past six months.</li><br />
<li>The Developers of Apertium constitute the Assembly of Developers of Apertium.</li><br />
<li>The project's Developers are responsible for the project's technical management.</li><br />
<li>The Assembly of Developers elects the Project Management Committee of Apertium every even-numbered year in February or whenever a vacancy occurs, whether by resignation, or loss of Developer status.</li><br />
<li>The number of members of the Assembly of Developers of Apertium has no limit.</li><br />
<li>The President of the Project Management Committee will, immediately after a new Project Management Committee begins functioning, nominate a President of the Assembly of Developers, who must be a Developer and may not be a member of the Project Management Committee or of the latest election board. This President will be confirmed by a vote of the Assembly of Developers, and may be referred to as the President of Apertium.</li><br />
<li>The Assembly of Developers decides only on subjects proposed by the Project Management Committee.</li><br />
<li>Once submitted to it, the decisions of the Assembly of Developers are final and binding and cannot be overturned, except as explicitly noted in these Bylaws.</li><br />
<li>One tenth of the Assembly of Developers may decide to attempt to overturn a decision of the Assembly of Developers or Project Management Committee, and the resolution must be passed by half plus one of the Developers.</li><br />
</ol><br />
<br />
=== Project Management Committee ===<br />
<br />
<ol start="13"><br />
<li>The Project Management Committee is formed by seven members of the Assembly designated by it to make the day to day decisions.</li><br />
<li>The Project Management Committee is headed by a President and has six more members, one of whom will act as Secretary and another as Treasurer.</li><br />
<li>All members of the Project Management Committee must be at least thirteen years of age, and the Treasurer must be at least eighteen years of age.</li><br />
<li>The responsibilities of the Project Management Committee include</li><br />
<ol style="list-style-type:lower-alpha" ><br />
<li>Deciding what is distributed as products of Apertium project. In particular, all releases must be approved by the PMC.</li><br />
<li>Maintaining the project's shared resources, including the codebase repository, mailing lists, websites.</li><br />
<li>Speaking on behalf of the project; although, the PMC could give the right to speak on behalf of Apertium to a member of the Assembly of Developers.</li><br />
<li>Resolving licence disputes regarding products of the project.</li><br />
<li>Maintaining these bylaws and other guidelines of the project.</li><br />
<li>Promoting the active engagement of Apertium in larger free/open-source initiatives</li><br />
<li>Attracting external funds to further the objectives of the Apertium project</li><br />
<li>Deciding how to distribute the funds the Apertium project may get as the result of participating in externally-funded initiatives</li><br />
</ol></li><br />
<li>The Project Management Committee votes on all of its decisions.</li><br />
<li>The Project Management Committee has the obligation to submit to the Assembly of Developers the decisions that affect the work of the half or more of the members of the Assembly of Developers, being able to consult in other subjects if believed necessary. </li><br />
<li>Decisions of the PMC are accepted or rejected by the President of the Assembly of Committers, but the PMC may pass a decision despite rejection by the President of the Assembly of Developers with the agreement of five members.</li><br />
<li>Decisions of the Project Management Committee made other than in consultation with the Assembly are immediately filed in a public diary. The Assembly may overturn a PMC decision as described in Bylaw 12.</li><br />
<li>The secretary of the Project Management Committee has the obligation of preparing the diary and presenting it to the Assembly of Developers.</li><br />
<li>While the Treasurer is responsible for financial management, all actions must be approved by a PMC vote.</li><br />
</ol><br />
<br />
=== Bylaw Violation Court of Apertium ===<br />
<ol start="23"><br />
<li>In the case of an alleged violation of the Bylaws by any Developer, a temporary Bylaw Violation Court shall be established.</li><br />
<li>The Bylaw Violation Court of Apertium shall consist of seven Developers chosen at random, who must not be members of the Project Management Committee or include the accused Developer.</li><br />
<li>All members of the Bylaw Violation Court shall agree to a Pledge of Non-bias, as follows:<br />
<br><br />
I, <name>, hereby pledge that I will not act in my own personal interest, in the interest of the accused Developer, or in the interest of the accuser(s), but in the interest of the Apertium project as a whole. My decisions will not be biased based on who the accused or accusing Developer(s) is/are.</li><br />
<li>The Bylaw Violation Court of Apertium shall decide by consensus if the accused Developer has violated the bylaws, and may take action against the Developer up to, and including, permanent loss of Developer status.</li><br />
</ol><br />
<br />
== Election of the Project Management Committee ==<br />
<br />
<ol start="27"><br />
<li>The Assembly of Developers will elect a new Project Management Committee as follows:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>An Election Board of 3 developers (with at least one substitute member; ideally with one substitute each) will run the election. Election Board membership is a volunteer position on a first-come first-served basis.</li><br />
<li>The Project Management Committee will provide the Election Board with all the information needed to run the election</li><br />
<li>Any Developer may run for member of the Project Management Committee</li><br />
<li>Any Developer may run for president of the Project Management Committee</li><br />
<li>Candidates cannot be part of the Election Board</li><br />
<li>When an election is called, the Election Board will publish a census of Developers with right to vote.</li><br />
<li>There will be 7 days for candidates to member and president to come forward</li><br />
<li>The Election Board will proclaim the candidates to President and to Members of the Project Management Committee</li><br />
<li>Once candidates are proclaimed, Developers with the right to vote will send a ballot with:<br />
<ol style="list-style-type:lower-roman" ><br />
<li>The name of a candidate to president of the Project Management Committee, and</li><br />
<li>The name of up to four candidates to members of the Project Management Committee</li><br />
</ol></li><br />
<li>There will be 7 days to send the ballots</li><br />
<li>The Election Board will proclaim as President the candidate to president having received most votes for President and as members the six candidates to member having received the most votes as members</li><br />
<li>The new Project Management Committee will start to function 48 hours after being proclaimed</li><br />
</li><br />
</ol></li><br />
</ol><br />
<br />
== Amendments ==<br />
<ol start="28"><br />
<li>To begin the bylaw amendment process, one tenth of the Assembly of Developers must submit a proposal to the PMC.</li><br />
<li>If the PMC accepts an amendment, the Assembly of Developers shall vote on the amendment.</li><br />
<li>If half plus one of the Assembly of Developers accept the amendment, it shall become part of these Bylaws.</li><br />
</ol><br />
<br />
== Transitional provisions ==<br />
<br />
<ol start="31"><br />
<li>Bylaw 12 does not apply to the acceptance of these bylaws.</li><br />
<li>Bylaw 12 does not apply to decisions made by the Project Management Committee or Assembly of Committers under the previous Bylaws. These may only be overturned by a replacement decision made using the standard process under these Bylaws.</li><br />
</ol><br />
<br />
[[Category:PMC campaigns 2020]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=User:ScoopGracie/PMC/Proposed_bylaws&diff=71222User:ScoopGracie/PMC/Proposed bylaws2020-03-17T16:06:53Z<p>ScoopGracie: /* Project Management Committee */</p>
<hr />
<div>'''THESE ARE NOT THE BYLAWS!''' I'm running for PMC, and these are my suggestion. If you have any feedback, please let me know!<br />
== Preamble ==<br />
The mission of the Apertium project is to collaboratively develop free/open-source machine translation for as many languages as possible, and in particular:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To give everyone free, unlimited access to the best possible machine-translation technologies.</li><br />
<li>To maintain a modular, documented, open platform for machine translation and other human language processing tasks</li><br />
<li>To favour the interchange and reuse of existing linguistic data.</li><br />
<li>To make integration with other free/open-source technologies easier.</li><br />
<li>To radically guarantee the reproducibility of machine translation and natural language processing research</li><br />
</ol><br />
And additionally:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To promote the usage of free and open source software.</li><br />
<li>To help combat gender and racial bias in technology.</li><br />
<li>To help support and preserve less widespread languages.</li><br />
</ol><br />
<br />
== Roles and responsibilities ==<br />
<br />
=== Users ===<br />
<br />
<ol start="1"><br />
<li>The most important participants in the project are people who use Apertium. The majority of our developers start out as users and guide their development efforts from the user's perspective</li><br />
<li>Users contribute to the Apertium project by providing feedback to developers in the form of bug reports and feature suggestions. As well, users participate in the Apertium community by helping other users.</li><br />
</ol><br />
<br />
=== Developers ===<br />
<br />
<ol start="3"><br />
<li>Developers are volunteers who are contributing time, code, documentation, or resources to Apertium.</li><br />
<li>For the purposes of these bylaws, a Developer is anyone who has submitted at least three pull requests or commits to any Apertium repository in the past six months.</li><br />
<li>The Developers of Apertium constitute the Assembly of Developers of Apertium.</li><br />
<li>The project's Developers are responsible for the project's technical management.</li><br />
<li>The Assembly of Developers elects the Project Management Committee of Apertium every even-numbered year in February or whenever a vacancy occurs, whether by resignation, or loss of Developer status.</li><br />
<li>The number of members of the Assembly of Developers of Apertium has no limit.</li><br />
<li>The President of the Project Management Committee will, immediately after a new Project Management Committee begins functioning, nominate a President of the Assembly of Developers, who must be a Developer and may not be a member of the Project Management Committee or of the latest election board. This President will be confirmed by a vote of the Assembly of Developers, and may be referred to as the President of Apertium.</li><br />
<li>The Assembly of Developers decides only on subjects proposed by the Project Management Committee.</li><br />
<li>Once submitted to it, the decisions of the Assembly of Developers are final and binding and cannot be overturned, except as explicitly noted in these Bylaws.</li><br />
<li>One tenth of the Assembly of Developers may decide to attempt to overturn a decision of the Assembly of Developers or Project Management Committee, and the resolution must be passed by half plus one of the Developers.</li><br />
</ol><br />
<br />
=== Project Management Committee ===<br />
<br />
<ol start="13"><br />
<li>The Project Management Committee is formed by seven members of the Assembly designated by it to make the day to day decisions.</li><br />
<li>The Project Management Committee is headed by a President and has six more members, one of whom will act as Secretary and another as Treasurer.</li><br />
<li>All members of the Project Management Committee must be at least thirteen years of age, and the Treasurer must be at least eighteen years of age.</li><br />
<li>The responsibilities of the Project Management Committee include</li><br />
<ol style="list-style-type:lower-alpha" ><br />
<li>Deciding what is distributed as products of Apertium project. In particular, all releases must be approved by the PMC.</li><br />
<li>Maintaining the project's shared resources, including the codebase repository, mailing lists, websites.</li><br />
<li>Speaking on behalf of the project; although, the PMC could give the right to speak on behalf of Apertium to a member of the Assembly of Developers.</li><br />
<li>Resolving licence disputes regarding products of the project.</li><br />
<li>Maintaining these bylaws and other guidelines of the project.</li><br />
<li>Promoting the active engagement of Apertium in larger free/open-source initiatives</li><br />
<li>Attracting external funds to further the objectives of the Apertium project</li><br />
<li>Deciding how to distribute the funds the Apertium project may get as the result of participating in externally-funded initiatives</li><br />
</ol></li><br />
<li>The Project Management Committee votes on all of its decisions.</li><br />
<li>The Project Management Committee has the obligation to submit to the Assembly of Developers the decisions that affect the work of the half or more of the members of the Assembly of Developers, being able to consult in other subjects if believed necessary. </li><br />
<li>Decisions of the PMC are accepted or rejected by the President of the Assembly of Committers, but the PMC may pass a decision despite rejection by the President of the Assembly of Developers with the agreement of five members.</li><br />
<li>Decisions of the Project Management Committee made other than in consultation with the Assembly are immediately filed in a public diary. The Assembly may overturn a PMC decision as described in Bylaw 12.</li><br />
<li>The secretary of the Project Management Committee has the obligation of preparing the diary and presenting it to the Assembly of Developers.</li><br />
<li>While the Treasurer is responsible for financial management, all actions must be approved by a PMC vote.</li><br />
<li>If a member of the PMC decides to participate in Google Summer of Code or Google Code-in, that member shall temporarily resign. His/her space on the PMC will be held until GSoC/GCI is over.<br />
</ol><br />
<br />
=== Bylaw Violation Court of Apertium ===<br />
<ol start="23"><br />
<li>In the case of an alleged violation of the Bylaws by any Developer, a temporary Bylaw Violation Court shall be established.</li><br />
<li>The Bylaw Violation Court of Apertium shall consist of seven Developers chosen at random, who must not be members of the Project Management Committee or include the accused Developer.</li><br />
<li>All members of the Bylaw Violation Court shall agree to a Pledge of Non-bias, as follows:<br />
<br><br />
I, <name>, hereby pledge that I will not act in my own personal interest, in the interest of the accused Developer, or in the interest of the accuser(s), but in the interest of the Apertium project as a whole. My decisions will not be biased based on who the accused or accusing Developer(s) is/are.</li><br />
<li>The Bylaw Violation Court of Apertium shall decide by consensus if the accused Developer has violated the bylaws, and may take action against the Developer up to, and including, permanent loss of Developer status.</li><br />
</ol><br />
<br />
== Election of the Project Management Committee ==<br />
<br />
<ol start="27"><br />
<li>The Assembly of Developers will elect a new Project Management Committee as follows:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>An Election Board of 3 developers (with at least one substitute member; ideally with one substitute each) will run the election. Election Board membership is a volunteer position on a first-come first-served basis.</li><br />
<li>The Project Management Committee will provide the Election Board with all the information needed to run the election</li><br />
<li>Any Developer may run for member of the Project Management Committee</li><br />
<li>Any Developer may run for president of the Project Management Committee</li><br />
<li>Candidates cannot be part of the Election Board</li><br />
<li>When an election is called, the Election Board will publish a census of Developers with right to vote.</li><br />
<li>There will be 7 days for candidates to member and president to come forward</li><br />
<li>The Election Board will proclaim the candidates to President and to Members of the Project Management Committee</li><br />
<li>Once candidates are proclaimed, Developers with the right to vote will send a ballot with:<br />
<ol style="list-style-type:lower-roman" ><br />
<li>The name of a candidate to president of the Project Management Committee, and</li><br />
<li>The name of up to four candidates to members of the Project Management Committee</li><br />
</ol></li><br />
<li>There will be 7 days to send the ballots</li><br />
<li>The Election Board will proclaim as President the candidate to president having received most votes for President and as members the six candidates to member having received the most votes as members</li><br />
<li>The new Project Management Committee will start to function 48 hours after being proclaimed</li><br />
</li><br />
</ol></li><br />
</ol><br />
<br />
== Amendments ==<br />
<ol start="28"><br />
<li>To begin the bylaw amendment process, one tenth of the Assembly of Developers must submit a proposal to the PMC.</li><br />
<li>If the PMC accepts an amendment, the Assembly of Developers shall vote on the amendment.</li><br />
<li>If half plus one of the Assembly of Developers accept the amendment, it shall become part of these Bylaws.</li><br />
</ol><br />
<br />
== Transitional provisions ==<br />
<br />
<ol start="31"><br />
<li>Bylaw 12 does not apply to the acceptance of these bylaws.</li><br />
<li>Bylaw 12 does not apply to decisions made by the Project Management Committee or Assembly of Committers under the previous Bylaws. These may only be overturned by a replacement decision made using the standard process under these Bylaws.</li><br />
</ol><br />
<br />
[[Category:PMC campaigns 2020]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=User:StemCounterBot&diff=71219User:StemCounterBot2020-03-17T00:33:13Z<p>ScoopGracie: </p>
<hr />
<div>Hi!<br />
<br />
I'm the friendly Stem Counter Bot. [https://github.com/apertium/apertium-wiki-tools/blob/master/bot.py Here] are my insides. Come over to [[IRC|#apertium]] and try me out with <code>.awikstats update</code>.</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=User:ScoopGracie&diff=71218User:ScoopGracie2020-03-16T00:47:54Z<p>ScoopGracie: </p>
<hr />
<div>Hi! I'm ScoopGracie! I'm a GCI 2019 student. I like Python, as well as Web development. I like to work on [[Begiak]]-related tasks. More importantly, however, I'm a Christian. I have some plans to use Apertium to help create a Bible translation for languages that do not have any versions. Anyone who's interested in helping, please ping me on [[IRC]]!<br />
<br />
Check out [https://scoopgracie.com/ my website]!<br />
<br />
As I said before, I like Python. I also like JavaScript, but ONLY vanilla JS. If you think you need a framework for cross-browser compatibility, use polyfills, not a framework!<br />
<br />
I'm also running for PMC.</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=Langues_nord_germaniques&diff=71217Langues nord germaniques2020-03-15T23:26:20Z<p>ScoopGracie: </p>
<hr />
<div>{{{Otherlang|North Germanic languages|In English}}}<br />
<br />
Les '''langues nord germaniques''' comprennent le danois (<code>da</code>), le faroese (<code>fo</code>), l'islandais (<code>is</code>), le norvégien (Nynorsk, <code>nn</code> et Bokmål, <code>nb</code>) et le suédois (<code>sv</code>). Ces langues sont proches avec des niveaux d'intelligibilité mutuelle variables. Ce groupe pourrait faire un bon groupe pour les systèmes Apertium.<br />
<br />
== État ==<br />
<br />
Le texte en ''italique'' indique des couples de langues non distribués.<br />
<br />
{{North Germanic language translations}}<br />
<br />
== Existant ==<br />
<br />
;Dictionnaires<br />
<br />
Voir aussi : [[List of dictionaries]] (quand la page sera exploitable !)<br />
<br />
{|class="wikitable sortable"<br />
! Langue !! Fichier !! Paradigmes !! Lemmes<br />
|-<br />
| Norvégien nynorsk || [https://svn.code.sf.net/p/apertium/svn/trunk/apertium-nn-nb/apertium-nn-nb.nn.dix apertium-nn-nb.nn.dix] || 770 || 83,584<br />
|-<br />
| Norvégien bokmål || [https://svn.code.sf.net/p/apertium/svn/trunk/apertium-nn-nb/apertium-nn-nb.nb.dix apertium-nn-nb.nb.dix] || 705 || 119,567<br />
|-<br />
| Suédois || [https://svn.code.sf.net/p/apertium/svn/trunk/apertium-sv-da/apertium-sv-da.sv.dix apertium-sv-da.sv.dix] || 277 || 5,177<br />
|-<br />
| Danois || [https://svn.code.sf.net/p/apertium/svn/trunk/apertium-sv-da/apertium-sv-da.da.dix apertium-sv-da.da.dix] || 341 || 10,709 <br />
|-<br />
| Faroese || [https://svn.code.sf.net/p/apertium/svn/incubator/apertium-fo-is.fo.dix apertium-fo-is.fo.dix] || 113 || 1,864<br />
|-<br />
| Islandais || [https://svn.code.sf.net/p/apertium/svn/trunk/apertium-is-en/apertium-is-en.is.dix apertium-is-en.is.dix] || 1,881 || 9,134<br />
|-<br />
|}<br />
<br />
== Ressources ==<br />
<br />
Les ressources énumérés ci-dessous seront utiles pour la construction de systèmes de traduction automatique pour ces langues.<br />
<br />
;Unilingue<br />
<br />
{|class=wikitable<br />
! Langue !! Ressource !! Description !! Voir aussi<br />
|-<br />
| Norvégien || [http://www.edd.uio.no/prosjekt/ordbanken/ Norsk ordbank] || Gros dictionnaire morphologique (> 100 000 lemmes) à la fois de nynorsk et de bokmål, sous licence GPL. || [[Norsk ordbank]], [[Norwegian]]<br />
|-<br />
| Norvégien || [http://maximos.aksis.uib.no/Aksis-wiki/Oslo-Bergen_Tagger Oslo-Bergen tagger] || Baliseur de contrainte grammaticale pour norvégien, sous licence GPL. (converti pour CG-3) || [[Norwegian]]<br />
|-<br />
| Suédois || [http://w3.msi.vxu.se/~nivre/research/Talbanken05.html Talbanken] || Une banque de données arborescente de 300 000 mots : c'est en XML, tous les mots sont bien étiquetées avec des étiquettes de style PAROLE. ||<br />
|-<br />
| Suédois || [http://spraakbanken.gu.se/sal/eng/ SALDO] || Lexique suédois inflectionnel, sous licence LGPL ||<br />
|-<br />
| Danois || [http://www.isv.cbs.dk/~mbk/treebank/ Danish Dependency Treebank] || Une banque de données arborescente danoise de 100 000 mots : c'est en XML, étiqueté PAROLE, sous licence GPL. ||<br />
|-<br />
| Danois || [http://wordnet.dk/dannet/menu?item=0&lang=1 DanNet] || WordNet danois (~32 000 mots), licence MIT.<br />
|-<br />
| Islandais || || || [[Icelandic and English]]<br />
|-<br />
| Faroese || [https://svn.code.sf.net/p/apertium/svn/trunk/incubator/apertium-fo-is.fo.rlx apertium-fo-is.fo.rlx] || Des [[contraintes grammaticales]] pour la disambiguisation morphologique avec ~120 règles || <br />
|-<br />
|}<br />
<br />
;Bilingual<br />
<br />
{|class=wikitable<br />
! Language pair !! Resource !! Description !! See also<br />
|-<br />
|Islandais&mdash;Danois || Apertium bidix avec ~960 entrées || || <br />
|-<br />
|Islandais&mdash;Faroese || Apertium bidix avec ~30 entrées || || <br />
|-<br />
|Norvégien (Nynorsk)&mdash;Norvégien (Bokmål) || Apertium bidix avec ~36,000 entrées || || [[Norwegian]]<br />
|-<br />
|Suédois&mdash;Danois || Apertium bidix avec ~2,000 entrées || || [[Swedish and Danish]]<br />
|}<br />
<br />
== Possibilités de financement ==<br />
<br />
* [http://www.norden.org/start/start.asp Nordic Council]<br />
<br />
== Échantillons ==<br />
<br />
{|class=wikitable<br />
! Langue !! Texte<br />
|-<br />
| Danois || Alle mennesker er født frie og lige i værdighed og rettigheder. De er udstyret med fornuft og samvittighed, og de bør handle mod hverandre i en broderskabets ånd.<br />
|-<br />
| Norvégien&nbsp;(bokmål) || Alle mennesker er født frie og med samme menneskeverd og menneskerettigheter. De er utstyrt med fornuft og samvittighet og bør handle mot hverandre i brorskapets ånd. <br />
|-<br />
| Norvégien&nbsp;(nynorsk) || Alle menneske er fødde til fridom og med same menneskeverd og menneskerettar. Dei har fått fornuft og samvit og skal leve med kvarandre som brør.<br />
|-<br />
| Suédois || Alla människor är födda fria och lika i värde och rättigheter. De har utrustats med förnuft och samvete och bör handla gentemot varandra i en anda av gemenskap.<br />
|-<br />
| Faroese || Øll menniskju eru fødd fræls og jøvn til virðingar og mannarættindi. Tey hava skil og samvitsku og eiga at fara hvørt um annað í bróðuranda.<br />
|-<br />
| Islandais || Hver maður er borinn frjáls og jafn öðrum að virðingu og réttindum. Menn eru gæddir vitsmunum og samvizku, og ber þeim að breyta bróðurlega hverjum við annan.<br />
|-<br />
|}<br />
<br />
[[Category:Languages]]<br />
[[Category:North Germanic languages]]<br />
[[Category:Documentation en français]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=User:ScoopGracie/PMC/Proposed_bylaws&diff=71215User:ScoopGracie/PMC/Proposed bylaws2020-03-14T23:11:28Z<p>ScoopGracie: </p>
<hr />
<div>'''THESE ARE NOT THE BYLAWS!''' I'm running for PMC, and these are my suggestion. If you have any feedback, please let me know!<br />
== Preamble ==<br />
The mission of the Apertium project is to collaboratively develop free/open-source machine translation for as many languages as possible, and in particular:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To give everyone free, unlimited access to the best possible machine-translation technologies.</li><br />
<li>To maintain a modular, documented, open platform for machine translation and other human language processing tasks</li><br />
<li>To favour the interchange and reuse of existing linguistic data.</li><br />
<li>To make integration with other free/open-source technologies easier.</li><br />
<li>To radically guarantee the reproducibility of machine translation and natural language processing research</li><br />
</ol><br />
And additionally:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To promote the usage of free and open source software.</li><br />
<li>To help combat gender and racial bias in technology.</li><br />
<li>To help support and preserve less widespread languages.</li><br />
</ol><br />
<br />
== Roles and responsibilities ==<br />
<br />
=== Users ===<br />
<br />
<ol start="1"><br />
<li>The most important participants in the project are people who use Apertium. The majority of our developers start out as users and guide their development efforts from the user's perspective</li><br />
<li>Users contribute to the Apertium project by providing feedback to developers in the form of bug reports and feature suggestions. As well, users participate in the Apertium community by helping other users.</li><br />
</ol><br />
<br />
=== Developers ===<br />
<br />
<ol start="3"><br />
<li>Developers are volunteers who are contributing time, code, documentation, or resources to Apertium.</li><br />
<li>For the purposes of these bylaws, a Developer is anyone who has submitted at least three pull requests or commits to any Apertium repository in the past six months.</li><br />
<li>The Developers of Apertium constitute the Assembly of Developers of Apertium.</li><br />
<li>The project's Developers are responsible for the project's technical management.</li><br />
<li>The Assembly of Developers elects the Project Management Committee of Apertium every even-numbered year in February or whenever a vacancy occurs, whether by resignation, or loss of Developer status.</li><br />
<li>The number of members of the Assembly of Developers of Apertium has no limit.</li><br />
<li>The President of the Project Management Committee will, immediately after a new Project Management Committee begins functioning, nominate a President of the Assembly of Developers, who must be a Developer and may not be a member of the Project Management Committee or of the latest election board. This President will be confirmed by a vote of the Assembly of Developers, and may be referred to as the President of Apertium.</li><br />
<li>The Assembly of Developers decides only on subjects proposed by the Project Management Committee.</li><br />
<li>Once submitted to it, the decisions of the Assembly of Developers are final and binding and cannot be overturned, except as explicitly noted in these Bylaws.</li><br />
<li>One tenth of the Assembly of Developers may decide to attempt to overturn a decision of the Assembly of Developers or Project Management Committee, and the resolution must be passed by half plus one of the Developers.</li><br />
</ol><br />
<br />
=== Project Management Committee ===<br />
<br />
<ol start="13"><br />
<li>The Project Management Committee is formed by seven members of the Assembly designated by it to make the day to day decisions.</li><br />
<li>The Project Management Committee is headed by a President and has six more members, one of whom will act as Secretary and another as Treasurer.</li><br />
<li>All members of the Project Management Committee must be at least thirteen years of age, and the Treasurer must be at least eighteen years of age.</li><br />
<li>The responsibilities of the Project Management Committee include</li><br />
<ol style="list-style-type:lower-alpha" ><br />
<li>Deciding what is distributed as products of Apertium project. In particular, all releases must be approved by the PMC.</li><br />
<li>Maintaining the project's shared resources, including the codebase repository, mailing lists, websites.</li><br />
<li>Speaking on behalf of the project; although, the PMC could give the right to speak on behalf of Apertium to a member of the Assembly of Developers.</li><br />
<li>Resolving licence disputes regarding products of the project.</li><br />
<li>Maintaining these bylaws and other guidelines of the project.</li><br />
<li>Promoting the active engagement of Apertium in larger free/open-source initiatives</li><br />
<li>Attracting external funds to further the objectives of the Apertium project</li><br />
<li>Deciding how to distribute the funds the Apertium project may get as the result of participating in externally-funded initiatives</li><br />
</ol></li><br />
<li>The Project Management Committee votes on all of its decisions.</li><br />
<li>The Project Management Committee has the obligation to submit to the Assembly of Developers the decisions that affect the work of the half or more of the members of the Assembly of Developers, being able to consult in other subjects if believed necessary. </li><br />
<li>Decisions of the PMC are accepted or rejected by the President of the Assembly of Committers, but the PMC may pass a decision despite rejection by the President of the Assembly of Developers with the agreement of five members.</li><br />
<li>Decisions of the Project Management Committee made other than in consultation with the Assembly are immediately filed in a public diary. The Assembly may overturn a PMC decision as described in Bylaw 12.</li><br />
<li>The secretary of the Project Management Committee has the obligation of preparing the diary and presenting it to the Assembly of Developers.</li><br />
<li>While the Treasurer is responsible for financial management, all actions must be approved by a PMC vote.</li><br />
</ol><br />
<br />
=== Bylaw Violation Court of Apertium ===<br />
<ol start="23"><br />
<li>In the case of an alleged violation of the Bylaws by any Developer, a temporary Bylaw Violation Court shall be established.</li><br />
<li>The Bylaw Violation Court of Apertium shall consist of seven Developers chosen at random, who must not be members of the Project Management Committee or include the accused Developer.</li><br />
<li>All members of the Bylaw Violation Court shall agree to a Pledge of Non-bias, as follows:<br />
<br><br />
I, <name>, hereby pledge that I will not act in my own personal interest, in the interest of the accused Developer, or in the interest of the accuser(s), but in the interest of the Apertium project as a whole. My decisions will not be biased based on who the accused or accusing Developer(s) is/are.</li><br />
<li>The Bylaw Violation Court of Apertium shall decide by consensus if the accused Developer has violated the bylaws, and may take action against the Developer up to, and including, permanent loss of Developer status.</li><br />
</ol><br />
<br />
== Election of the Project Management Committee ==<br />
<br />
<ol start="27"><br />
<li>The Assembly of Developers will elect a new Project Management Committee as follows:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>An Election Board of 3 developers (with at least one substitute member; ideally with one substitute each) will run the election. Election Board membership is a volunteer position on a first-come first-served basis.</li><br />
<li>The Project Management Committee will provide the Election Board with all the information needed to run the election</li><br />
<li>Any Developer may run for member of the Project Management Committee</li><br />
<li>Any Developer may run for president of the Project Management Committee</li><br />
<li>Candidates cannot be part of the Election Board</li><br />
<li>When an election is called, the Election Board will publish a census of Developers with right to vote.</li><br />
<li>There will be 7 days for candidates to member and president to come forward</li><br />
<li>The Election Board will proclaim the candidates to President and to Members of the Project Management Committee</li><br />
<li>Once candidates are proclaimed, Developers with the right to vote will send a ballot with:<br />
<ol style="list-style-type:lower-roman" ><br />
<li>The name of a candidate to president of the Project Management Committee, and</li><br />
<li>The name of up to four candidates to members of the Project Management Committee</li><br />
</ol></li><br />
<li>There will be 7 days to send the ballots</li><br />
<li>The Election Board will proclaim as President the candidate to president having received most votes for President and as members the six candidates to member having received the most votes as members</li><br />
<li>The new Project Management Committee will start to function 48 hours after being proclaimed</li><br />
</li><br />
</ol></li><br />
</ol><br />
<br />
== Amendments ==<br />
<ol start="28"><br />
<li>To begin the bylaw amendment process, one tenth of the Assembly of Developers must submit a proposal to the PMC.</li><br />
<li>If the PMC accepts an amendment, the Assembly of Developers shall vote on the amendment.</li><br />
<li>If half plus one of the Assembly of Developers accept the amendment, it shall become part of these Bylaws.</li><br />
</ol><br />
<br />
== Transitional provisions ==<br />
<br />
<ol start="31"><br />
<li>Bylaw 12 does not apply to the acceptance of these bylaws.</li><br />
<li>Bylaw 12 does not apply to decisions made by the Project Management Committee or Assembly of Committers under the previous Bylaws. These may only be overturned by a replacement decision made using the standard process under these Bylaws.</li><br />
</ol><br />
<br />
[[Category:PMC campaigns 2020]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=User:ScoopGracie/PMC/Proposed_bylaws&diff=71213User:ScoopGracie/PMC/Proposed bylaws2020-03-14T22:04:27Z<p>ScoopGracie: </p>
<hr />
<div>'''THESE ARE NOT THE BYLAWS!''' I'm running for PMC, and these are my suggestion. If you have any feedback, please let me know!<br />
<br />
== Mission ==<br />
<br />
<ol start="1"><br />
<li>The mission of the Apertium project is to collaboratively develop free/open-source machine translation for as many languages as possible, and in particular:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To give everyone free, unlimited access to the best possible machine-translation technologies.</li><br />
<li>To maintain a modular, documented, open platform for machine translation and other human language processing tasks</li><br />
<li>To favour the interchange and reuse of existing linguistic data.</li><br />
<li>To make integration with other free/open-source technologies easier.</li><br />
<li>To radically guarantee the reproducibility of machine translation and natural language processing research</li><br />
</ol><br />
And additionally:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To promote the usage of free and open source software.</li><br />
<li>To help combat gender and racial bias in technology.</li><br />
<li>To help support and preserve less widespread languages.</li><br />
</ol><br />
</li><br />
</ol><br />
<br />
== Roles and responsibilities ==<br />
<br />
=== Users ===<br />
<br />
<ol start="2"><br />
<li>The most important participants in the project are people who use Apertium. The majority of our developers start out as users and guide their development efforts from the user's perspective</li><br />
<li>Users contribute to the Apertium project by providing feedback to developers in the form of bug reports and feature suggestions. As well, users participate in the Apertium community by helping other users.</li><br />
</ol><br />
<br />
=== Developers ===<br />
<br />
<ol start="4"><br />
<li>Developers are volunteers who are contributing time, code, documentation, or resources to Apertium.</li><br />
<li>For the purposes of these bylaws, a Developer is anyone who has submitted at least three pull requests or commits to any Apertium repository in the past six months.</li><br />
<li>The Developers of Apertium constitute the Assembly of Developers of Apertium.</li><br />
<li>The project's Developers are responsible for the project's technical management.</li><br />
<li>The Assembly of Developers elects the Project Management Committee of Apertium every even-numbered year in February or whenever a vacancy occurs, whether by resignation, or loss of Developer status.</li><br />
<li>The number of members of the Assembly of Developers of Apertium has no limit.</li><br />
<li>The President of the Project Management Committee will, immediately after a new Project Management Committee begins functioning, nominate a President of the Assembly of Developers, who must be a Developer and may not be a member of the Project Management Committee or of the latest election board. This President will be confirmed by a vote of the Assembly of Developers, and may be referred to as the President of Apertium.</li><br />
<li>The Assembly of Developers decides only on subjects proposed by the Project Management Committee.</li><br />
<li>Once submitted to it, the decisions of the Assembly of Developers are final and binding and cannot be overturned, except as explicitly noted in these Bylaws.</li><br />
<li>One tenth of the Assembly of Developers may decide to attempt to overturn a decision of the Assembly of Developers or Project Management Committee, and the resolution must be passed by half plus one of the Developers.</li><br />
</ol><br />
<br />
=== Project Management Committee ===<br />
<br />
<ol start="14"><br />
<li>The Project Management Committee is formed by seven members of the Assembly designated by it to make the day to day decisions.</li><br />
<li>The Project Management Committee is headed by a President and has six more members, one of whom will act as Secretary and another as Treasurer.</li><br />
<li>All members of the Project Management Committee must be at least thirteen years of age, and the Treasurer must be at least eighteen years of age.</li><br />
<li>The responsibilities of the Project Management Committee include</li><br />
<ol style="list-style-type:lower-alpha" ><br />
<li>Deciding what is distributed as products of Apertium project. In particular, all releases must be approved by the PMC.</li><br />
<li>Maintaining the project's shared resources, including the codebase repository, mailing lists, websites.</li><br />
<li>Speaking on behalf of the project; although, the PMC could give the right to speak on behalf of Apertium to a member of the Assembly of Developers.</li><br />
<li>Resolving licence disputes regarding products of the project.</li><br />
<li>Maintaining these bylaws and other guidelines of the project.</li><br />
<li>Promoting the active engagement of Apertium in larger free/open-source initiatives</li><br />
<li>Attracting external funds to further the objectives of the Apertium project</li><br />
<li>Deciding how to distribute the funds the Apertium project may get as the result of participating in externally-funded initiatives</li><br />
</ol></li><br />
<li>The Project Management Committee votes on all of its decisions.</li><br />
<li>The Project Management Committee has the obligation to submit to the Assembly of Developers the decisions that affect the work of the half or more of the members of the Assembly of Developers, being able to consult in other subjects if believed necessary. </li><br />
<li>Decisions of the Project Management Committee made other than in consultation with the Assembly are immediately filed in a public diary. The Assembly may overturn a PMC decision as described in Bylaw 13.</li><br />
<li>The secretary of the Project Management Committee has the obligation of preparing the diary and presenting it to the Assembly of Developers.</li><br />
<li>While the Treasurer is responsible for financial management, all actions must be approved by a PMC vote.</li><br />
</ol><br />
<br />
=== Bylaw Violation Court of Apertium ===<br />
<ol start="23"><br />
<li>In the case of an alleged violation of the Bylaws by any Developer, a temporary Bylaw Violation Court shall be established.</li><br />
<li>The Bylaw Violation Court of Apertium shall consist of seven Developers chosen at random, who must not be members of the Project Management Committee or include the accused Developer.</li><br />
<li>All members of the Bylaw Violation Court shall agree to a Pledge of Non-bias, as follows:<br />
<br><br />
I, <name>, hereby pledge that I will not act in my own personal interest, in the interest of the accused Developer, or in the interest of the accuser(s), but in the interest of the Apertium project as a whole. My decisions will not be biased based on who the accused or accusing Developer(s) is/are.</li><br />
<li>The Bylaw Violation Court of Apertium shall decide by consensus if the accused Developer has violated the bylaws, and may take action against the Developer up to, and including, permanent loss of Developer status.</li><br />
</ol><br />
<br />
== Election of the Project Management Committee ==<br />
<br />
<ol start="27"><br />
<li>The Assembly of Developers will elect a new Project Management Committee as follows:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>An Election Board of 3 developers (with at least one substitute member; ideally with one substitute each) will run the election. Election Board membership is a volunteer position on a first-come first-served basis.</li><br />
<li>The Project Management Committee will provide the Election Board with all the information needed to run the election</li><br />
<li>Any Developer may run for member of the Project Management Committee</li><br />
<li>Any Developer may run for president of the Project Management Committee</li><br />
<li>Candidates cannot be part of the Election Board</li><br />
<li>When an election is called, the Election Board will publish a census of Developers with right to vote.</li><br />
<li>There will be 7 days for candidates to member and president to come forward</li><br />
<li>The Election Board will proclaim the candidates to President and to Members of the Project Management Committee</li><br />
<li>Once candidates are proclaimed, Developers with the right to vote will send a ballot with:<br />
<ol style="list-style-type:lower-roman" ><br />
<li>The name of a candidate to president of the Project Management Committee, and</li><br />
<li>The name of up to four candidates to members of the Project Management Committee</li><br />
</ol></li><br />
<li>There will be 7 days to send the ballots</li><br />
<li>The Election Board will proclaim as President the candidate to president having received most votes for President and as members the six candidates to member having received the most votes as members</li><br />
<li>The new Project Management Committee will start to function 48 hours after being proclaimed</li><br />
</li><br />
</ol></li><br />
</ol><br />
<br />
== Amendments ==<br />
<ol start="28"><br />
<li>To begin the bylaw amendment process, one tenth of the Assembly of Developers must submit a proposal to the PMC.</li><br />
<li>If the PMC accepts an amendment, the Assembly of Developers shall vote on the amendment.</li><br />
<li>If half plus one of the Assembly of Developers accept the amendment, it shall become part of these Bylaws.</li><br />
</ol><br />
<br />
== Transitional provisions ==<br />
<br />
<ol start="31"><br />
<li>Bylaw 13 does not apply to the acceptance of these bylaws.</li><br />
<li>Bylaw 13 does not apply to decisions made by the Project Management Committee or Assembly of Committers under the previous Bylaws. These may only be overturned by a replacement decision made using the standard process under these Bylaws.</li><br />
</ol><br />
<br />
[[Category:PMC campaigns 2020]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=User:ScoopGracie/PMC/Proposed_bylaws&diff=71211User:ScoopGracie/PMC/Proposed bylaws2020-03-14T21:57:54Z<p>ScoopGracie: /* Transitional provisions */</p>
<hr />
<div>'''THESE ARE NOT THE BYLAWS!''' I'm running for PMC, and these are my suggestion. If you have any feedback, please let me know!<br />
<br />
== Mission ==<br />
<br />
<ol start="1"><br />
<li>The mission of the Apertium project is to collaboratively develop free/open-source machine translation for as many languages as possible, and in particular:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To give everyone free, unlimited access to the best possible machine-translation technologies.</li><br />
<li>To maintain a modular, documented, open platform for machine translation and other human language processing tasks</li><br />
<li>To favour the interchange and reuse of existing linguistic data.</li><br />
<li>To make integration with other free/open-source technologies easier.</li><br />
<li>To radically guarantee the reproducibility of machine translation and natural language processing research</li><br />
</ol><br />
And additionally:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To promote the usage of free and open source software.</li><br />
<li>To help combat gender and racial bias in technology.</li><br />
<li>To help support and preserve less widespread languages.</li><br />
</ol><br />
</li><br />
</ol><br />
<br />
== Roles and responsibilities ==<br />
<br />
=== Users ===<br />
<br />
<ol start="2"><br />
<li>The most important participants in the project are people who use Apertium. The majority of our developers start out as users and guide their development efforts from the user's perspective</li><br />
<li>Users contribute to the Apertium project by providing feedback to developers in the form of bug reports and feature suggestions. As well, users participate in the Apertium community by helping other users.</li><br />
</ol><br />
<br />
=== Developers ===<br />
<br />
<ol start="4"><br />
<li>Developers are volunteers who are contributing time, code, documentation, or resources to Apertium.</li><br />
<li>For the purposes of these bylaws, a Developer is anyone who has submitted at least three pull requests or commits to any Apertium repository in the past six months.</li><br />
<li>The Developers of Apertium constitute the Assembly of Developers of Apertium.</li><br />
<li>The project's Developers are responsible for the project's technical management.</li><br />
<li>The Assembly of Developers elects the Project Management Committee of Apertium every even-numbered year in February or whenever a vacancy occurs, whether by resignation, or loss of Developer status.</li><br />
<li>The number of members of the Assembly of Developers of Apertium has no limit.</li><br />
<li>The President of the Project Management Committee will, immediately after a new Project Management Committee begins functioning, nominate a President of the Assembly of Developers, who must be a Developer and may not be a member of the Project Management Committee or of the latest election board. This President will be confirmed by a vote of the Assembly of Developers, and may be referred to as the President of Apertium.</li><br />
<li>The Assembly of Developers decides only on subjects proposed by the Project Management Committee.</li><br />
<li>Once submitted to it, the decisions of the Assembly of Developers are final and binding and cannot be overturned, except as explicitly noted in these Bylaws.</li><br />
<li>One tenth of the Assembly of Developers may decide to attempt to overturn a decision of the Assembly of Developers or Project Management Committee, and the resolution must be passed by half plus one of the Developers.</li><br />
</ol><br />
<br />
=== Project Management Committee ===<br />
<br />
<ol start="14"><br />
<li>The Project Management Committee is formed by seven members of the Assembly designated by it to make the day to day decisions.</li><br />
<li>The Project Management Committee is headed by a President and has six more members, one of whom will act as Secretary and another as Treasurer.</li><br />
<li>All members of the Project Management Committee must be at least thirteen years of age, and the Treasurer must be at least eighteen years of age.</li><br />
<li>The responsibilities of the Project Management Committee include</li><br />
<ol style="list-style-type:lower-alpha" ><br />
<li>Deciding what is distributed as products of Apertium project. In particular, all releases must be approved by the PMC.</li><br />
<li>Maintaining the project's shared resources, including the codebase repository, mailing lists, websites.</li><br />
<li>Speaking on behalf of the project; although, the PMC could give the right to speak on behalf of Apertium to a member of the Assembly of Developers.</li><br />
<li>Resolving licence disputes regarding products of the project.</li><br />
<li>Maintaining these bylaws and other guidelines of the project.</li><br />
<li>Promoting the active engagement of Apertium in larger free/open-source initiatives</li><br />
<li>Attracting external funds to further the objectives of the Apertium project</li><br />
<li>Deciding how to distribute the funds the Apertium project may get as the result of participating in externally-funded initiatives</li><br />
</ol></li><br />
<li>The Project Management Committee votes on all of its decisions.</li><br />
<li>The Project Management Committee has the obligation to submit to the Assembly of Developers the decisions that affect the work of the half or more of the members of the Assembly of Developers, being able to consult in other subjects if believed necessary. </li><br />
<li>Decisions of the Project Management Committee made other than in consultation with the Assembly are immediately filed in a public diary. The Assembly may overturn a PMC decision as described in Bylaw 15.</li><br />
<li>The secretary of the Project Management Committee has the obligation of preparing the diary and presenting it to the Assembly of Developers.</li><br />
<li>While the Treasurer is responsible for financial management, all actions must be approved by a PMC vote.</li><br />
</ol><br />
<br />
=== Bylaw Violation Court of Apertium ===<br />
<ol start="23"><br />
<li>In the case of an alleged violation of the Bylaws by any Developer, a temporary Bylaw Violation Court shall be established.</li><br />
<li>The Bylaw Violation Court of Apertium shall consist of seven Developers chosen at random, who must not be members of the Project Management Committee or include the accused Developer.</li><br />
<li>The Bylaw Violation Court of Apertium shall decide by consensus if the accused Developer has violated the bylaws, and may take action against the Developer up to, and including, permanent loss of Developer status.</li><br />
</ol><br />
<br />
== Election of the Project Management Committee ==<br />
<br />
<ol start="26"><br />
<li>The Assembly of Developers will elect a new Project Management Committee as follows:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>An Election Board of 3 developers (with at least one substitute member; ideally with one substitute each) will run the election. Election Board membership is a volunteer position on a first-come first-served basis.</li><br />
<li>The Project Management Committee will provide the Election Board with all the information needed to run the election</li><br />
<li>Any Developer may run for member of the Project Management Committee</li><br />
<li>Any Developer may run for president of the Project Management Committee</li><br />
<li>Candidates cannot be part of the Election Board</li><br />
<li>When an election is called, the Election Board will publish a census of Developers with right to vote.</li><br />
<li>There will be 7 days for candidates to member and president to come forward</li><br />
<li>The Election Board will proclaim the candidates to President and to Members of the Project Management Committee</li><br />
<li>Once candidates are proclaimed, Developers with the right to vote will send a ballot with:<br />
<ol style="list-style-type:lower-roman" ><br />
<li>The name of a candidate to president of the Project Management Committee, and</li><br />
<li>The name of up to four candidates to members of the Project Management Committee</li><br />
</ol></li><br />
<li>There will be 7 days to send the ballots</li><br />
<li>The Election Board will proclaim as President the candidate to president having received most votes for President and as members the six candidates to member having received the most votes as members</li><br />
<li>The new Project Management Committee will start to function 48 hours after being proclaimed</li><br />
</li><br />
</ol></li><br />
</ol><br />
<br />
== Amendments ==<br />
<ol start="27"><br />
<li>To begin the bylaw amendment process, one tenth of the Assembly of Developers must submit a proposal to the PMC.</li><br />
<li>If the PMC accepts an amendment, the Assembly of Developers shall vote on the amendment.</li><br />
<li>If half plus one of the Assembly of Developers accept the amendment, it shall become part of these Bylaws.</li><br />
</ol><br />
<br />
== Transitional provisions ==<br />
<br />
<ol start="30"><br />
<li>Bylaw 15 does not apply to the acceptance of these bylaws.</li><br />
<li>All PMC or Assembly decisions made prior to the acceptance of these bylaws are final, and Bylaw 15 does not apply to these decisions.</li><br />
</ol><br />
<br />
[[Category:PMC campaigns 2020]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=User:ScoopGracie/PMC/Proposed_bylaws&diff=71210User:ScoopGracie/PMC/Proposed bylaws2020-03-14T21:57:34Z<p>ScoopGracie: /* Amendments */</p>
<hr />
<div>'''THESE ARE NOT THE BYLAWS!''' I'm running for PMC, and these are my suggestion. If you have any feedback, please let me know!<br />
<br />
== Mission ==<br />
<br />
<ol start="1"><br />
<li>The mission of the Apertium project is to collaboratively develop free/open-source machine translation for as many languages as possible, and in particular:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To give everyone free, unlimited access to the best possible machine-translation technologies.</li><br />
<li>To maintain a modular, documented, open platform for machine translation and other human language processing tasks</li><br />
<li>To favour the interchange and reuse of existing linguistic data.</li><br />
<li>To make integration with other free/open-source technologies easier.</li><br />
<li>To radically guarantee the reproducibility of machine translation and natural language processing research</li><br />
</ol><br />
And additionally:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To promote the usage of free and open source software.</li><br />
<li>To help combat gender and racial bias in technology.</li><br />
<li>To help support and preserve less widespread languages.</li><br />
</ol><br />
</li><br />
</ol><br />
<br />
== Roles and responsibilities ==<br />
<br />
=== Users ===<br />
<br />
<ol start="2"><br />
<li>The most important participants in the project are people who use Apertium. The majority of our developers start out as users and guide their development efforts from the user's perspective</li><br />
<li>Users contribute to the Apertium project by providing feedback to developers in the form of bug reports and feature suggestions. As well, users participate in the Apertium community by helping other users.</li><br />
</ol><br />
<br />
=== Developers ===<br />
<br />
<ol start="4"><br />
<li>Developers are volunteers who are contributing time, code, documentation, or resources to Apertium.</li><br />
<li>For the purposes of these bylaws, a Developer is anyone who has submitted at least three pull requests or commits to any Apertium repository in the past six months.</li><br />
<li>The Developers of Apertium constitute the Assembly of Developers of Apertium.</li><br />
<li>The project's Developers are responsible for the project's technical management.</li><br />
<li>The Assembly of Developers elects the Project Management Committee of Apertium every even-numbered year in February or whenever a vacancy occurs, whether by resignation, or loss of Developer status.</li><br />
<li>The number of members of the Assembly of Developers of Apertium has no limit.</li><br />
<li>The President of the Project Management Committee will, immediately after a new Project Management Committee begins functioning, nominate a President of the Assembly of Developers, who must be a Developer and may not be a member of the Project Management Committee or of the latest election board. This President will be confirmed by a vote of the Assembly of Developers, and may be referred to as the President of Apertium.</li><br />
<li>The Assembly of Developers decides only on subjects proposed by the Project Management Committee.</li><br />
<li>Once submitted to it, the decisions of the Assembly of Developers are final and binding and cannot be overturned, except as explicitly noted in these Bylaws.</li><br />
<li>One tenth of the Assembly of Developers may decide to attempt to overturn a decision of the Assembly of Developers or Project Management Committee, and the resolution must be passed by half plus one of the Developers.</li><br />
</ol><br />
<br />
=== Project Management Committee ===<br />
<br />
<ol start="14"><br />
<li>The Project Management Committee is formed by seven members of the Assembly designated by it to make the day to day decisions.</li><br />
<li>The Project Management Committee is headed by a President and has six more members, one of whom will act as Secretary and another as Treasurer.</li><br />
<li>All members of the Project Management Committee must be at least thirteen years of age, and the Treasurer must be at least eighteen years of age.</li><br />
<li>The responsibilities of the Project Management Committee include</li><br />
<ol style="list-style-type:lower-alpha" ><br />
<li>Deciding what is distributed as products of Apertium project. In particular, all releases must be approved by the PMC.</li><br />
<li>Maintaining the project's shared resources, including the codebase repository, mailing lists, websites.</li><br />
<li>Speaking on behalf of the project; although, the PMC could give the right to speak on behalf of Apertium to a member of the Assembly of Developers.</li><br />
<li>Resolving licence disputes regarding products of the project.</li><br />
<li>Maintaining these bylaws and other guidelines of the project.</li><br />
<li>Promoting the active engagement of Apertium in larger free/open-source initiatives</li><br />
<li>Attracting external funds to further the objectives of the Apertium project</li><br />
<li>Deciding how to distribute the funds the Apertium project may get as the result of participating in externally-funded initiatives</li><br />
</ol></li><br />
<li>The Project Management Committee votes on all of its decisions.</li><br />
<li>The Project Management Committee has the obligation to submit to the Assembly of Developers the decisions that affect the work of the half or more of the members of the Assembly of Developers, being able to consult in other subjects if believed necessary. </li><br />
<li>Decisions of the Project Management Committee made other than in consultation with the Assembly are immediately filed in a public diary. The Assembly may overturn a PMC decision as described in Bylaw 15.</li><br />
<li>The secretary of the Project Management Committee has the obligation of preparing the diary and presenting it to the Assembly of Developers.</li><br />
<li>While the Treasurer is responsible for financial management, all actions must be approved by a PMC vote.</li><br />
</ol><br />
<br />
=== Bylaw Violation Court of Apertium ===<br />
<ol start="23"><br />
<li>In the case of an alleged violation of the Bylaws by any Developer, a temporary Bylaw Violation Court shall be established.</li><br />
<li>The Bylaw Violation Court of Apertium shall consist of seven Developers chosen at random, who must not be members of the Project Management Committee or include the accused Developer.</li><br />
<li>The Bylaw Violation Court of Apertium shall decide by consensus if the accused Developer has violated the bylaws, and may take action against the Developer up to, and including, permanent loss of Developer status.</li><br />
</ol><br />
<br />
== Election of the Project Management Committee ==<br />
<br />
<ol start="26"><br />
<li>The Assembly of Developers will elect a new Project Management Committee as follows:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>An Election Board of 3 developers (with at least one substitute member; ideally with one substitute each) will run the election. Election Board membership is a volunteer position on a first-come first-served basis.</li><br />
<li>The Project Management Committee will provide the Election Board with all the information needed to run the election</li><br />
<li>Any Developer may run for member of the Project Management Committee</li><br />
<li>Any Developer may run for president of the Project Management Committee</li><br />
<li>Candidates cannot be part of the Election Board</li><br />
<li>When an election is called, the Election Board will publish a census of Developers with right to vote.</li><br />
<li>There will be 7 days for candidates to member and president to come forward</li><br />
<li>The Election Board will proclaim the candidates to President and to Members of the Project Management Committee</li><br />
<li>Once candidates are proclaimed, Developers with the right to vote will send a ballot with:<br />
<ol style="list-style-type:lower-roman" ><br />
<li>The name of a candidate to president of the Project Management Committee, and</li><br />
<li>The name of up to four candidates to members of the Project Management Committee</li><br />
</ol></li><br />
<li>There will be 7 days to send the ballots</li><br />
<li>The Election Board will proclaim as President the candidate to president having received most votes for President and as members the six candidates to member having received the most votes as members</li><br />
<li>The new Project Management Committee will start to function 48 hours after being proclaimed</li><br />
</li><br />
</ol></li><br />
</ol><br />
<br />
== Amendments ==<br />
<ol start="27"><br />
<li>To begin the bylaw amendment process, one tenth of the Assembly of Developers must submit a proposal to the PMC.</li><br />
<li>If the PMC accepts an amendment, the Assembly of Developers shall vote on the amendment.</li><br />
<li>If half plus one of the Assembly of Developers accept the amendment, it shall become part of these Bylaws.</li><br />
</ol><br />
<br />
== Transitional provisions ==<br />
<br />
<ol start="32"><br />
<li>Bylaw 15 does not apply to the acceptance of these bylaws.</li><br />
<li>All PMC or Assembly decisions made prior to the acceptance of these bylaws are final, and Bylaw 15 does not apply to these decisions.</li><br />
</ol><br />
<br />
[[Category:PMC campaigns 2020]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=User:ScoopGracie/PMC/Proposed_bylaws&diff=71209User:ScoopGracie/PMC/Proposed bylaws2020-03-14T21:54:12Z<p>ScoopGracie: /* Election of the Project Management Committee */</p>
<hr />
<div>'''THESE ARE NOT THE BYLAWS!''' I'm running for PMC, and these are my suggestion. If you have any feedback, please let me know!<br />
<br />
== Mission ==<br />
<br />
<ol start="1"><br />
<li>The mission of the Apertium project is to collaboratively develop free/open-source machine translation for as many languages as possible, and in particular:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To give everyone free, unlimited access to the best possible machine-translation technologies.</li><br />
<li>To maintain a modular, documented, open platform for machine translation and other human language processing tasks</li><br />
<li>To favour the interchange and reuse of existing linguistic data.</li><br />
<li>To make integration with other free/open-source technologies easier.</li><br />
<li>To radically guarantee the reproducibility of machine translation and natural language processing research</li><br />
</ol><br />
And additionally:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To promote the usage of free and open source software.</li><br />
<li>To help combat gender and racial bias in technology.</li><br />
<li>To help support and preserve less widespread languages.</li><br />
</ol><br />
</li><br />
</ol><br />
<br />
== Roles and responsibilities ==<br />
<br />
=== Users ===<br />
<br />
<ol start="2"><br />
<li>The most important participants in the project are people who use Apertium. The majority of our developers start out as users and guide their development efforts from the user's perspective</li><br />
<li>Users contribute to the Apertium project by providing feedback to developers in the form of bug reports and feature suggestions. As well, users participate in the Apertium community by helping other users.</li><br />
</ol><br />
<br />
=== Developers ===<br />
<br />
<ol start="4"><br />
<li>Developers are volunteers who are contributing time, code, documentation, or resources to Apertium.</li><br />
<li>For the purposes of these bylaws, a Developer is anyone who has submitted at least three pull requests or commits to any Apertium repository in the past six months.</li><br />
<li>The Developers of Apertium constitute the Assembly of Developers of Apertium.</li><br />
<li>The project's Developers are responsible for the project's technical management.</li><br />
<li>The Assembly of Developers elects the Project Management Committee of Apertium every even-numbered year in February or whenever a vacancy occurs, whether by resignation, or loss of Developer status.</li><br />
<li>The number of members of the Assembly of Developers of Apertium has no limit.</li><br />
<li>The President of the Project Management Committee will, immediately after a new Project Management Committee begins functioning, nominate a President of the Assembly of Developers, who must be a Developer and may not be a member of the Project Management Committee or of the latest election board. This President will be confirmed by a vote of the Assembly of Developers, and may be referred to as the President of Apertium.</li><br />
<li>The Assembly of Developers decides only on subjects proposed by the Project Management Committee.</li><br />
<li>Once submitted to it, the decisions of the Assembly of Developers are final and binding and cannot be overturned, except as explicitly noted in these Bylaws.</li><br />
<li>One tenth of the Assembly of Developers may decide to attempt to overturn a decision of the Assembly of Developers or Project Management Committee, and the resolution must be passed by half plus one of the Developers.</li><br />
</ol><br />
<br />
=== Project Management Committee ===<br />
<br />
<ol start="14"><br />
<li>The Project Management Committee is formed by seven members of the Assembly designated by it to make the day to day decisions.</li><br />
<li>The Project Management Committee is headed by a President and has six more members, one of whom will act as Secretary and another as Treasurer.</li><br />
<li>All members of the Project Management Committee must be at least thirteen years of age, and the Treasurer must be at least eighteen years of age.</li><br />
<li>The responsibilities of the Project Management Committee include</li><br />
<ol style="list-style-type:lower-alpha" ><br />
<li>Deciding what is distributed as products of Apertium project. In particular, all releases must be approved by the PMC.</li><br />
<li>Maintaining the project's shared resources, including the codebase repository, mailing lists, websites.</li><br />
<li>Speaking on behalf of the project; although, the PMC could give the right to speak on behalf of Apertium to a member of the Assembly of Developers.</li><br />
<li>Resolving licence disputes regarding products of the project.</li><br />
<li>Maintaining these bylaws and other guidelines of the project.</li><br />
<li>Promoting the active engagement of Apertium in larger free/open-source initiatives</li><br />
<li>Attracting external funds to further the objectives of the Apertium project</li><br />
<li>Deciding how to distribute the funds the Apertium project may get as the result of participating in externally-funded initiatives</li><br />
</ol></li><br />
<li>The Project Management Committee votes on all of its decisions.</li><br />
<li>The Project Management Committee has the obligation to submit to the Assembly of Developers the decisions that affect the work of the half or more of the members of the Assembly of Developers, being able to consult in other subjects if believed necessary. </li><br />
<li>Decisions of the Project Management Committee made other than in consultation with the Assembly are immediately filed in a public diary. The Assembly may overturn a PMC decision as described in Bylaw 15.</li><br />
<li>The secretary of the Project Management Committee has the obligation of preparing the diary and presenting it to the Assembly of Developers.</li><br />
<li>While the Treasurer is responsible for financial management, all actions must be approved by a PMC vote.</li><br />
</ol><br />
<br />
=== Bylaw Violation Court of Apertium ===<br />
<ol start="23"><br />
<li>In the case of an alleged violation of the Bylaws by any Developer, a temporary Bylaw Violation Court shall be established.</li><br />
<li>The Bylaw Violation Court of Apertium shall consist of seven Developers chosen at random, who must not be members of the Project Management Committee or include the accused Developer.</li><br />
<li>The Bylaw Violation Court of Apertium shall decide by consensus if the accused Developer has violated the bylaws, and may take action against the Developer up to, and including, permanent loss of Developer status.</li><br />
</ol><br />
<br />
== Election of the Project Management Committee ==<br />
<br />
<ol start="26"><br />
<li>The Assembly of Developers will elect a new Project Management Committee as follows:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>An Election Board of 3 developers (with at least one substitute member; ideally with one substitute each) will run the election. Election Board membership is a volunteer position on a first-come first-served basis.</li><br />
<li>The Project Management Committee will provide the Election Board with all the information needed to run the election</li><br />
<li>Any Developer may run for member of the Project Management Committee</li><br />
<li>Any Developer may run for president of the Project Management Committee</li><br />
<li>Candidates cannot be part of the Election Board</li><br />
<li>When an election is called, the Election Board will publish a census of Developers with right to vote.</li><br />
<li>There will be 7 days for candidates to member and president to come forward</li><br />
<li>The Election Board will proclaim the candidates to President and to Members of the Project Management Committee</li><br />
<li>Once candidates are proclaimed, Developers with the right to vote will send a ballot with:<br />
<ol style="list-style-type:lower-roman" ><br />
<li>The name of a candidate to president of the Project Management Committee, and</li><br />
<li>The name of up to four candidates to members of the Project Management Committee</li><br />
</ol></li><br />
<li>There will be 7 days to send the ballots</li><br />
<li>The Election Board will proclaim as President the candidate to president having received most votes for President and as members the six candidates to member having received the most votes as members</li><br />
<li>The new Project Management Committee will start to function 48 hours after being proclaimed</li><br />
</li><br />
</ol></li><br />
</ol><br />
<br />
== Amendments ==<br />
<ol start="29"><br />
<li>To begin the bylaw amendment process, one tenth of the Assembly of Developers must submit a proposal to the PMC.</li><br />
<li>If the PMC accepts an amendment, the Assembly of Developers shall vote on the amendment.</li><br />
<li>If half plus one of the Assembly of Developers accept the amendment, it shall become part of these Bylaws.</li><br />
</ol><br />
<br />
== Transitional provisions ==<br />
<br />
<ol start="32"><br />
<li>Bylaw 15 does not apply to the acceptance of these bylaws.</li><br />
<li>All PMC or Assembly decisions made prior to the acceptance of these bylaws are final, and Bylaw 15 does not apply to these decisions.</li><br />
</ol><br />
<br />
[[Category:PMC campaigns 2020]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=User:ScoopGracie/PMC/Proposed_bylaws&diff=71208User:ScoopGracie/PMC/Proposed bylaws2020-03-14T21:53:42Z<p>ScoopGracie: /* Bylaw Violation Court of Apertium */</p>
<hr />
<div>'''THESE ARE NOT THE BYLAWS!''' I'm running for PMC, and these are my suggestion. If you have any feedback, please let me know!<br />
<br />
== Mission ==<br />
<br />
<ol start="1"><br />
<li>The mission of the Apertium project is to collaboratively develop free/open-source machine translation for as many languages as possible, and in particular:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To give everyone free, unlimited access to the best possible machine-translation technologies.</li><br />
<li>To maintain a modular, documented, open platform for machine translation and other human language processing tasks</li><br />
<li>To favour the interchange and reuse of existing linguistic data.</li><br />
<li>To make integration with other free/open-source technologies easier.</li><br />
<li>To radically guarantee the reproducibility of machine translation and natural language processing research</li><br />
</ol><br />
And additionally:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To promote the usage of free and open source software.</li><br />
<li>To help combat gender and racial bias in technology.</li><br />
<li>To help support and preserve less widespread languages.</li><br />
</ol><br />
</li><br />
</ol><br />
<br />
== Roles and responsibilities ==<br />
<br />
=== Users ===<br />
<br />
<ol start="2"><br />
<li>The most important participants in the project are people who use Apertium. The majority of our developers start out as users and guide their development efforts from the user's perspective</li><br />
<li>Users contribute to the Apertium project by providing feedback to developers in the form of bug reports and feature suggestions. As well, users participate in the Apertium community by helping other users.</li><br />
</ol><br />
<br />
=== Developers ===<br />
<br />
<ol start="4"><br />
<li>Developers are volunteers who are contributing time, code, documentation, or resources to Apertium.</li><br />
<li>For the purposes of these bylaws, a Developer is anyone who has submitted at least three pull requests or commits to any Apertium repository in the past six months.</li><br />
<li>The Developers of Apertium constitute the Assembly of Developers of Apertium.</li><br />
<li>The project's Developers are responsible for the project's technical management.</li><br />
<li>The Assembly of Developers elects the Project Management Committee of Apertium every even-numbered year in February or whenever a vacancy occurs, whether by resignation, or loss of Developer status.</li><br />
<li>The number of members of the Assembly of Developers of Apertium has no limit.</li><br />
<li>The President of the Project Management Committee will, immediately after a new Project Management Committee begins functioning, nominate a President of the Assembly of Developers, who must be a Developer and may not be a member of the Project Management Committee or of the latest election board. This President will be confirmed by a vote of the Assembly of Developers, and may be referred to as the President of Apertium.</li><br />
<li>The Assembly of Developers decides only on subjects proposed by the Project Management Committee.</li><br />
<li>Once submitted to it, the decisions of the Assembly of Developers are final and binding and cannot be overturned, except as explicitly noted in these Bylaws.</li><br />
<li>One tenth of the Assembly of Developers may decide to attempt to overturn a decision of the Assembly of Developers or Project Management Committee, and the resolution must be passed by half plus one of the Developers.</li><br />
</ol><br />
<br />
=== Project Management Committee ===<br />
<br />
<ol start="14"><br />
<li>The Project Management Committee is formed by seven members of the Assembly designated by it to make the day to day decisions.</li><br />
<li>The Project Management Committee is headed by a President and has six more members, one of whom will act as Secretary and another as Treasurer.</li><br />
<li>All members of the Project Management Committee must be at least thirteen years of age, and the Treasurer must be at least eighteen years of age.</li><br />
<li>The responsibilities of the Project Management Committee include</li><br />
<ol style="list-style-type:lower-alpha" ><br />
<li>Deciding what is distributed as products of Apertium project. In particular, all releases must be approved by the PMC.</li><br />
<li>Maintaining the project's shared resources, including the codebase repository, mailing lists, websites.</li><br />
<li>Speaking on behalf of the project; although, the PMC could give the right to speak on behalf of Apertium to a member of the Assembly of Developers.</li><br />
<li>Resolving licence disputes regarding products of the project.</li><br />
<li>Maintaining these bylaws and other guidelines of the project.</li><br />
<li>Promoting the active engagement of Apertium in larger free/open-source initiatives</li><br />
<li>Attracting external funds to further the objectives of the Apertium project</li><br />
<li>Deciding how to distribute the funds the Apertium project may get as the result of participating in externally-funded initiatives</li><br />
</ol></li><br />
<li>The Project Management Committee votes on all of its decisions.</li><br />
<li>The Project Management Committee has the obligation to submit to the Assembly of Developers the decisions that affect the work of the half or more of the members of the Assembly of Developers, being able to consult in other subjects if believed necessary. </li><br />
<li>Decisions of the Project Management Committee made other than in consultation with the Assembly are immediately filed in a public diary. The Assembly may overturn a PMC decision as described in Bylaw 15.</li><br />
<li>The secretary of the Project Management Committee has the obligation of preparing the diary and presenting it to the Assembly of Developers.</li><br />
<li>While the Treasurer is responsible for financial management, all actions must be approved by a PMC vote.</li><br />
</ol><br />
<br />
=== Bylaw Violation Court of Apertium ===<br />
<ol start="23"><br />
<li>In the case of an alleged violation of the Bylaws by any Developer, a temporary Bylaw Violation Court shall be established.</li><br />
<li>The Bylaw Violation Court of Apertium shall consist of seven Developers chosen at random, who must not be members of the Project Management Committee or include the accused Developer.</li><br />
<li>The Bylaw Violation Court of Apertium shall decide by consensus if the accused Developer has violated the bylaws, and may take action against the Developer up to, and including, permanent loss of Developer status.</li><br />
</ol><br />
<br />
== Election of the Project Management Committee ==<br />
<br />
<ol start="28"><br />
<li>The Assembly of Developers will elect a new Project Management Committee as follows:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>An Election Board of 3 developers (with at least one substitute member; ideally with one substitute each) will run the election. Election Board membership is a volunteer position on a first-come first-served basis.</li><br />
<li>The Project Management Committee will provide the Election Board with all the information needed to run the election</li><br />
<li>Any Developer may run for member of the Project Management Committee</li><br />
<li>Any Developer may run for president of the Project Management Committee</li><br />
<li>Candidates cannot be part of the Election Board</li><br />
<li>When an election is called, the Election Board will publish a census of Developers with right to vote.</li><br />
<li>There will be 7 days for candidates to member and president to come forward</li><br />
<li>The Election Board will proclaim the candidates to President and to Members of the Project Management Committee</li><br />
<li>Once candidates are proclaimed, Developers with the right to vote will send a ballot with:<br />
<ol style="list-style-type:lower-roman" ><br />
<li>The name of a candidate to president of the Project Management Committee, and</li><br />
<li>The name of up to four candidates to members of the Project Management Committee</li><br />
</ol></li><br />
<li>There will be 7 days to send the ballots</li><br />
<li>The Election Board will proclaim as President the candidate to president having received most votes for President and as members the six candidates to member having received the most votes as members</li><br />
<li>The new Project Management Committee will start to function 48 hours after being proclaimed</li><br />
</li><br />
</ol></li><br />
</ol><br />
<br />
== Amendments ==<br />
<ol start="29"><br />
<li>To begin the bylaw amendment process, one tenth of the Assembly of Developers must submit a proposal to the PMC.</li><br />
<li>If the PMC accepts an amendment, the Assembly of Developers shall vote on the amendment.</li><br />
<li>If half plus one of the Assembly of Developers accept the amendment, it shall become part of these Bylaws.</li><br />
</ol><br />
<br />
== Transitional provisions ==<br />
<br />
<ol start="32"><br />
<li>Bylaw 15 does not apply to the acceptance of these bylaws.</li><br />
<li>All PMC or Assembly decisions made prior to the acceptance of these bylaws are final, and Bylaw 15 does not apply to these decisions.</li><br />
</ol><br />
<br />
[[Category:PMC campaigns 2020]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=User:ScoopGracie/PMC/Proposed_bylaws&diff=71207User:ScoopGracie/PMC/Proposed bylaws2020-03-14T21:52:41Z<p>ScoopGracie: Remove the Motion of Censure</p>
<hr />
<div>'''THESE ARE NOT THE BYLAWS!''' I'm running for PMC, and these are my suggestion. If you have any feedback, please let me know!<br />
<br />
== Mission ==<br />
<br />
<ol start="1"><br />
<li>The mission of the Apertium project is to collaboratively develop free/open-source machine translation for as many languages as possible, and in particular:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To give everyone free, unlimited access to the best possible machine-translation technologies.</li><br />
<li>To maintain a modular, documented, open platform for machine translation and other human language processing tasks</li><br />
<li>To favour the interchange and reuse of existing linguistic data.</li><br />
<li>To make integration with other free/open-source technologies easier.</li><br />
<li>To radically guarantee the reproducibility of machine translation and natural language processing research</li><br />
</ol><br />
And additionally:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To promote the usage of free and open source software.</li><br />
<li>To help combat gender and racial bias in technology.</li><br />
<li>To help support and preserve less widespread languages.</li><br />
</ol><br />
</li><br />
</ol><br />
<br />
== Roles and responsibilities ==<br />
<br />
=== Users ===<br />
<br />
<ol start="2"><br />
<li>The most important participants in the project are people who use Apertium. The majority of our developers start out as users and guide their development efforts from the user's perspective</li><br />
<li>Users contribute to the Apertium project by providing feedback to developers in the form of bug reports and feature suggestions. As well, users participate in the Apertium community by helping other users.</li><br />
</ol><br />
<br />
=== Developers ===<br />
<br />
<ol start="4"><br />
<li>Developers are volunteers who are contributing time, code, documentation, or resources to Apertium.</li><br />
<li>For the purposes of these bylaws, a Developer is anyone who has submitted at least three pull requests or commits to any Apertium repository in the past six months.</li><br />
<li>The Developers of Apertium constitute the Assembly of Developers of Apertium.</li><br />
<li>The project's Developers are responsible for the project's technical management.</li><br />
<li>The Assembly of Developers elects the Project Management Committee of Apertium every even-numbered year in February or whenever a vacancy occurs, whether by resignation, or loss of Developer status.</li><br />
<li>The number of members of the Assembly of Developers of Apertium has no limit.</li><br />
<li>The President of the Project Management Committee will, immediately after a new Project Management Committee begins functioning, nominate a President of the Assembly of Developers, who must be a Developer and may not be a member of the Project Management Committee or of the latest election board. This President will be confirmed by a vote of the Assembly of Developers, and may be referred to as the President of Apertium.</li><br />
<li>The Assembly of Developers decides only on subjects proposed by the Project Management Committee.</li><br />
<li>Once submitted to it, the decisions of the Assembly of Developers are final and binding and cannot be overturned, except as explicitly noted in these Bylaws.</li><br />
<li>One tenth of the Assembly of Developers may decide to attempt to overturn a decision of the Assembly of Developers or Project Management Committee, and the resolution must be passed by half plus one of the Developers.</li><br />
</ol><br />
<br />
=== Project Management Committee ===<br />
<br />
<ol start="14"><br />
<li>The Project Management Committee is formed by seven members of the Assembly designated by it to make the day to day decisions.</li><br />
<li>The Project Management Committee is headed by a President and has six more members, one of whom will act as Secretary and another as Treasurer.</li><br />
<li>All members of the Project Management Committee must be at least thirteen years of age, and the Treasurer must be at least eighteen years of age.</li><br />
<li>The responsibilities of the Project Management Committee include</li><br />
<ol style="list-style-type:lower-alpha" ><br />
<li>Deciding what is distributed as products of Apertium project. In particular, all releases must be approved by the PMC.</li><br />
<li>Maintaining the project's shared resources, including the codebase repository, mailing lists, websites.</li><br />
<li>Speaking on behalf of the project; although, the PMC could give the right to speak on behalf of Apertium to a member of the Assembly of Developers.</li><br />
<li>Resolving licence disputes regarding products of the project.</li><br />
<li>Maintaining these bylaws and other guidelines of the project.</li><br />
<li>Promoting the active engagement of Apertium in larger free/open-source initiatives</li><br />
<li>Attracting external funds to further the objectives of the Apertium project</li><br />
<li>Deciding how to distribute the funds the Apertium project may get as the result of participating in externally-funded initiatives</li><br />
</ol></li><br />
<li>The Project Management Committee votes on all of its decisions.</li><br />
<li>The Project Management Committee has the obligation to submit to the Assembly of Developers the decisions that affect the work of the half or more of the members of the Assembly of Developers, being able to consult in other subjects if believed necessary. </li><br />
<li>Decisions of the Project Management Committee made other than in consultation with the Assembly are immediately filed in a public diary. The Assembly may overturn a PMC decision as described in Bylaw 15.</li><br />
<li>The secretary of the Project Management Committee has the obligation of preparing the diary and presenting it to the Assembly of Developers.</li><br />
<li>While the Treasurer is responsible for financial management, all actions must be approved by a PMC vote.</li><br />
</ol><br />
<br />
=== Bylaw Violation Court of Apertium ===<br />
<ol start="25"><br />
<li>In the case of an alleged violation of the Bylaws by any Developer, a temporary Bylaw Violation Court shall be established.</li><br />
<li>The Bylaw Violation Court of Apertium shall consist of seven Developers chosen at random, who must not be members of the Project Management Committee or include the accused Developer.</li><br />
<li>The Bylaw Violation Court of Apertium shall decide by consensus if the accused Developer has violated the bylaws, and may take action against the Developer up to, and including, permanent loss of Developer status.</li><br />
</ol><br />
<br />
== Election of the Project Management Committee ==<br />
<br />
<ol start="28"><br />
<li>The Assembly of Developers will elect a new Project Management Committee as follows:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>An Election Board of 3 developers (with at least one substitute member; ideally with one substitute each) will run the election. Election Board membership is a volunteer position on a first-come first-served basis.</li><br />
<li>The Project Management Committee will provide the Election Board with all the information needed to run the election</li><br />
<li>Any Developer may run for member of the Project Management Committee</li><br />
<li>Any Developer may run for president of the Project Management Committee</li><br />
<li>Candidates cannot be part of the Election Board</li><br />
<li>When an election is called, the Election Board will publish a census of Developers with right to vote.</li><br />
<li>There will be 7 days for candidates to member and president to come forward</li><br />
<li>The Election Board will proclaim the candidates to President and to Members of the Project Management Committee</li><br />
<li>Once candidates are proclaimed, Developers with the right to vote will send a ballot with:<br />
<ol style="list-style-type:lower-roman" ><br />
<li>The name of a candidate to president of the Project Management Committee, and</li><br />
<li>The name of up to four candidates to members of the Project Management Committee</li><br />
</ol></li><br />
<li>There will be 7 days to send the ballots</li><br />
<li>The Election Board will proclaim as President the candidate to president having received most votes for President and as members the six candidates to member having received the most votes as members</li><br />
<li>The new Project Management Committee will start to function 48 hours after being proclaimed</li><br />
</li><br />
</ol></li><br />
</ol><br />
<br />
== Amendments ==<br />
<ol start="29"><br />
<li>To begin the bylaw amendment process, one tenth of the Assembly of Developers must submit a proposal to the PMC.</li><br />
<li>If the PMC accepts an amendment, the Assembly of Developers shall vote on the amendment.</li><br />
<li>If half plus one of the Assembly of Developers accept the amendment, it shall become part of these Bylaws.</li><br />
</ol><br />
<br />
== Transitional provisions ==<br />
<br />
<ol start="32"><br />
<li>Bylaw 15 does not apply to the acceptance of these bylaws.</li><br />
<li>All PMC or Assembly decisions made prior to the acceptance of these bylaws are final, and Bylaw 15 does not apply to these decisions.</li><br />
</ol><br />
<br />
[[Category:PMC campaigns 2020]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=User:ScoopGracie/PMC/Proposed_bylaws&diff=71193User:ScoopGracie/PMC/Proposed bylaws2020-03-09T17:05:18Z<p>ScoopGracie: /* Mission */</p>
<hr />
<div>'''THESE ARE NOT THE BYLAWS!''' I'm running for PMC, and these are my suggestion. If you have any feedback, please let me know!<br />
<br />
== Mission ==<br />
<br />
<ol start="1"><br />
<li>The mission of the Apertium project is to collaboratively develop free/open-source machine translation for as many languages as possible, and in particular:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To give everyone free, unlimited access to the best possible machine-translation technologies.</li><br />
<li>To maintain a modular, documented, open platform for machine translation and other human language processing tasks</li><br />
<li>To favour the interchange and reuse of existing linguistic data.</li><br />
<li>To make integration with other free/open-source technologies easier.</li><br />
<li>To radically guarantee the reproducibility of machine translation and natural language processing research</li><br />
</ol><br />
And additionally:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To promote the usage of free and open source software.</li><br />
<li>To help combat gender and racial bias in technology.</li><br />
<li>To help support and preserve less widespread languages.</li><br />
</ol><br />
</li><br />
</ol><br />
<br />
== Roles and responsibilities ==<br />
<br />
=== Users ===<br />
<br />
<ol start="2"><br />
<li>The most important participants in the project are people who use Apertium. The majority of our developers start out as users and guide their development efforts from the user's perspective</li><br />
<li>Users contribute to the Apertium project by providing feedback to developers in the form of bug reports and feature suggestions. As well, users participate in the Apertium community by helping other users.</li><br />
</ol><br />
<br />
=== Developers ===<br />
<br />
<ol start="4"><br />
<li>Developers are volunteers who are contributing time, code, documentation, or resources to Apertium.</li><br />
<li>For the purposes of these bylaws, a Developer is anyone who has submitted at least three pull requests or commits to any Apertium repository in the past six months.</li><br />
<li>The Developers of Apertium constitute the Assembly of Developers of Apertium.</li><br />
<li>The project's Developers are responsible for the project's technical management.</li><br />
<li>The Assembly of Developers elects the Project Management Committee of Apertium every even-numbered year in February or whenever a vacancy occurs, whether by resignation, lack of activity (resulting in loss of Developer status, and therefore of PMC membership), or censure.</li><br />
<li>One tenth of the Assembly of Developers may propose a motion of censure to overturn the Project Management Committee or any one or more member(s), which must be approved by half plus one of the members of the Assembly of Developers.</li><br />
<li>The Assembly of Developers must censure the entire Project Management Committee if it has not been acting in accordance with these bylaws.</li><br />
<li>The number of members of the Assembly of Developers of Apertium has no limit.</li><br />
<li>The President of the Project Management Committee will, immediately after a new Project Management Committee begins functioning, nominate a President of the Assembly of Developers, who must be a Developer and may not be a member of the Project Management Committee or of the latest election board. This President will be confirmed by a vote of the Assembly of Developers.<strong>This needs to be discussed. Does the Assembly need a President?</strong></li><br />
<li>The Assembly of Developers decides only on subjects proposed by the Project Management Committee.</li><br />
<li>Once submitted to it, the decisions of the Assembly of Developers are final and binding and cannot be overturned, except as explicitly noted in these Bylaws.</li><br />
<li>One tenth of the Assembly of Developers may decide to attempt to overturn a decision of the Assembly of Developers or Project Management Committee, and the resolution must be passed by half plus one of the Developers.</li><br />
</ol><br />
<br />
=== Project Management Committee ===<br />
<br />
<ol start="16"><br />
<li>The Project Management Committee is formed by seven members of the Assembly designated by it to make the day to day decisions.</li><br />
<li>The Project Management Committee is headed by a President and has six more members, one of whom will act as Secretary and another as Treasurer.</li><br />
<li>All members of the Project Management Committee must be at least thirteen years of age, and the Treasurer must be at least eighteen years of age.</li><br />
<li>The responsibilities of the Project Management Committee include</li><br />
<ol style="list-style-type:lower-alpha" ><br />
<li>Deciding what is distributed as products of Apertium project. In particular, all releases must be approved by the PMC.</li><br />
<li>Maintaining the project's shared resources, including the codebase repository, mailing lists, websites.</li><br />
<li>Speaking on behalf of the project; although, the PMC could give the right to speak on behalf of Apertium to a member of the Assembly of Developers.</li><br />
<li>Resolving licence disputes regarding products of the project.</li><br />
<li>Maintaining these bylaws and other guidelines of the project.</li><br />
<li>Promoting the active engagement of Apertium in larger free/open-source initiatives</li><br />
<li>Attracting external funds to further the objectives of the Apertium project</li><br />
<li>Deciding how to distribute the funds the Apertium project may get as the result of participating in externally-funded initiatives</li><br />
</ol></li><br />
<li>The Project Management Committee votes on all of its decisions.</li><br />
<li>The Project Management Committee has the obligation to submit to the Assembly of Developers the decisions that affect the work of the half or more of the members of the Assembly of Developers, being able to consult in other subjects if believed necessary. </li><br />
<li>Decisions of the Project Management Committee made other than in consultation with the Assembly are immediately filed in a public diary. The Assembly may overturn a PMC decision as described in Bylaw 15.</li><br />
<li>The secretary of the Project Management Committee has the obligation of preparing the diary and presenting it to the Assembly of Developers.</li><br />
<li>While the Treasurer is responsible for financial management, all actions must be approved by a PMC vote. The Treasurer shall be immediately censured from the PMC upon making any financial decisions without a vote.<br />
</ol><br />
<br />
=== Bylaw Violation Court of Apertium ===<br />
<ol start="25"><br />
<li>In the case of an alleged violation of the Bylaws by any Developer, a temporary Bylaw Violation Court shall be established.</li><br />
<li>The Bylaw Violation Court of Apertium shall consist of seven Developers chosen at random, who must not be members of the Project Management Committee or include the accused Developer.</li><br />
<li>The Bylaw Violation Court of Apertium shall decide by consensus if the accused Developer has violated the bylaws, and may take action against the Developer up to, and including, permanent loss of Developer status.</li><br />
</ol><br />
<br />
== Election of the Project Management Committee ==<br />
<br />
<ol start="28"><br />
<li>The Assembly of Developers will elect a new Project Management Committee as follows:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>An Election Board of 3 developers (with at least one substitute member; ideally with one substitute each) will run the election. Election Board membership is a volunteer position on a first-come first-served basis.</li><br />
<li>The Project Management Committee will provide the Election Board with all the information needed to run the election</li><br />
<li>Any Developer may run for member of the Project Management Committee</li><br />
<li>Any Developer may run for president of the Project Management Committee</li><br />
<li>Candidates cannot be part of the Election Board</li><br />
<li>When an election is called, the Election Board will publish a census of Developers with right to vote.</li><br />
<li>There will be 7 days for candidates to member and president to come forward</li><br />
<li>The Election Board will proclaim the candidates to President and to Members of the Project Management Committee</li><br />
<li>Once candidates are proclaimed, Developers with the right to vote will send a ballot with:<br />
<ol style="list-style-type:lower-roman" ><br />
<li>The name of a candidate to president of the Project Management Committee, and</li><br />
<li>The name of up to four candidates to members of the Project Management Committee</li><br />
</ol></li><br />
<li>There will be 7 days to send the ballots</li><br />
<li>The Election Board will proclaim as President the candidate to president having received most votes for President and as members the six candidates to member having received the most votes as members</li><br />
<li>The new Project Management Committee will start to function 48 hours after being proclaimed</li><br />
</li><br />
</ol></li><br />
</ol><br />
<br />
== Amendments ==<br />
<ol start="29"><br />
<li>To begin the bylaw amendment process, one tenth of the Assembly of Developers must submit a proposal to the PMC.</li><br />
<li>If the PMC accepts an amendment, the Assembly of Developers shall vote on the amendment.</li><br />
<li>If half plus one of the Assembly of Developers accept the amendment, it shall become part of these Bylaws.</li><br />
</ol><br />
<br />
== Transitional provisions ==<br />
<br />
<ol start="32"><br />
<li>Bylaw 15 does not apply to the acceptance of these bylaws.</li><br />
<li>All PMC or Assembly decisions made prior to the acceptance of these bylaws are final, and Bylaw 15 does not apply to these decisions.</li><br />
</ol><br />
<br />
[[Category:PMC campaigns 2020]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=User:ScoopGracie/PMC/Proposed_bylaws&diff=71192User:ScoopGracie/PMC/Proposed bylaws2020-03-09T17:04:09Z<p>ScoopGracie: /* Transitional provisions */</p>
<hr />
<div>'''THESE ARE NOT THE BYLAWS!''' I'm running for PMC, and these are my suggestion. If you have any feedback, please let me know!<br />
<br />
== Mission ==<br />
<br />
<ol start="1"><br />
<li>The mission of the Apertium project is to collaboratively develop free/open-source machine translation for as many languages as possible, and in particular:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To give everyone free, unlimited access to the best possible machine-translation technologies.</li><br />
<li>To maintain a modular, documented, open platform for machine translation and other human language processing tasks</li><br />
<li>To favour the interchange and reuse of existing linguistic data.</li><br />
<li>To make integration with other free/open-source technologies easier.</li><br />
<li>To radically guarantee the reproducibility of machine translation and natural language processing research</li><br />
</ol><br />
And additionally:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To promote the usage of free and open source software.</li><br />
<li>To help combat the bias toward white males in technology.</li><br />
<li>To help support and preserve less widespread languages.</li><br />
</ol><br />
</li><br />
</ol><br />
<br />
== Roles and responsibilities ==<br />
<br />
=== Users ===<br />
<br />
<ol start="2"><br />
<li>The most important participants in the project are people who use Apertium. The majority of our developers start out as users and guide their development efforts from the user's perspective</li><br />
<li>Users contribute to the Apertium project by providing feedback to developers in the form of bug reports and feature suggestions. As well, users participate in the Apertium community by helping other users.</li><br />
</ol><br />
<br />
=== Developers ===<br />
<br />
<ol start="4"><br />
<li>Developers are volunteers who are contributing time, code, documentation, or resources to Apertium.</li><br />
<li>For the purposes of these bylaws, a Developer is anyone who has submitted at least three pull requests or commits to any Apertium repository in the past six months.</li><br />
<li>The Developers of Apertium constitute the Assembly of Developers of Apertium.</li><br />
<li>The project's Developers are responsible for the project's technical management.</li><br />
<li>The Assembly of Developers elects the Project Management Committee of Apertium every even-numbered year in February or whenever a vacancy occurs, whether by resignation, lack of activity (resulting in loss of Developer status, and therefore of PMC membership), or censure.</li><br />
<li>One tenth of the Assembly of Developers may propose a motion of censure to overturn the Project Management Committee or any one or more member(s), which must be approved by half plus one of the members of the Assembly of Developers.</li><br />
<li>The Assembly of Developers must censure the entire Project Management Committee if it has not been acting in accordance with these bylaws.</li><br />
<li>The number of members of the Assembly of Developers of Apertium has no limit.</li><br />
<li>The President of the Project Management Committee will, immediately after a new Project Management Committee begins functioning, nominate a President of the Assembly of Developers, who must be a Developer and may not be a member of the Project Management Committee or of the latest election board. This President will be confirmed by a vote of the Assembly of Developers.<strong>This needs to be discussed. Does the Assembly need a President?</strong></li><br />
<li>The Assembly of Developers decides only on subjects proposed by the Project Management Committee.</li><br />
<li>Once submitted to it, the decisions of the Assembly of Developers are final and binding and cannot be overturned, except as explicitly noted in these Bylaws.</li><br />
<li>One tenth of the Assembly of Developers may decide to attempt to overturn a decision of the Assembly of Developers or Project Management Committee, and the resolution must be passed by half plus one of the Developers.</li><br />
</ol><br />
<br />
=== Project Management Committee ===<br />
<br />
<ol start="16"><br />
<li>The Project Management Committee is formed by seven members of the Assembly designated by it to make the day to day decisions.</li><br />
<li>The Project Management Committee is headed by a President and has six more members, one of whom will act as Secretary and another as Treasurer.</li><br />
<li>All members of the Project Management Committee must be at least thirteen years of age, and the Treasurer must be at least eighteen years of age.</li><br />
<li>The responsibilities of the Project Management Committee include</li><br />
<ol style="list-style-type:lower-alpha" ><br />
<li>Deciding what is distributed as products of Apertium project. In particular, all releases must be approved by the PMC.</li><br />
<li>Maintaining the project's shared resources, including the codebase repository, mailing lists, websites.</li><br />
<li>Speaking on behalf of the project; although, the PMC could give the right to speak on behalf of Apertium to a member of the Assembly of Developers.</li><br />
<li>Resolving licence disputes regarding products of the project.</li><br />
<li>Maintaining these bylaws and other guidelines of the project.</li><br />
<li>Promoting the active engagement of Apertium in larger free/open-source initiatives</li><br />
<li>Attracting external funds to further the objectives of the Apertium project</li><br />
<li>Deciding how to distribute the funds the Apertium project may get as the result of participating in externally-funded initiatives</li><br />
</ol></li><br />
<li>The Project Management Committee votes on all of its decisions.</li><br />
<li>The Project Management Committee has the obligation to submit to the Assembly of Developers the decisions that affect the work of the half or more of the members of the Assembly of Developers, being able to consult in other subjects if believed necessary. </li><br />
<li>Decisions of the Project Management Committee made other than in consultation with the Assembly are immediately filed in a public diary. The Assembly may overturn a PMC decision as described in Bylaw 15.</li><br />
<li>The secretary of the Project Management Committee has the obligation of preparing the diary and presenting it to the Assembly of Developers.</li><br />
<li>While the Treasurer is responsible for financial management, all actions must be approved by a PMC vote. The Treasurer shall be immediately censured from the PMC upon making any financial decisions without a vote.<br />
</ol><br />
<br />
=== Bylaw Violation Court of Apertium ===<br />
<ol start="25"><br />
<li>In the case of an alleged violation of the Bylaws by any Developer, a temporary Bylaw Violation Court shall be established.</li><br />
<li>The Bylaw Violation Court of Apertium shall consist of seven Developers chosen at random, who must not be members of the Project Management Committee or include the accused Developer.</li><br />
<li>The Bylaw Violation Court of Apertium shall decide by consensus if the accused Developer has violated the bylaws, and may take action against the Developer up to, and including, permanent loss of Developer status.</li><br />
</ol><br />
<br />
== Election of the Project Management Committee ==<br />
<br />
<ol start="28"><br />
<li>The Assembly of Developers will elect a new Project Management Committee as follows:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>An Election Board of 3 developers (with at least one substitute member; ideally with one substitute each) will run the election. Election Board membership is a volunteer position on a first-come first-served basis.</li><br />
<li>The Project Management Committee will provide the Election Board with all the information needed to run the election</li><br />
<li>Any Developer may run for member of the Project Management Committee</li><br />
<li>Any Developer may run for president of the Project Management Committee</li><br />
<li>Candidates cannot be part of the Election Board</li><br />
<li>When an election is called, the Election Board will publish a census of Developers with right to vote.</li><br />
<li>There will be 7 days for candidates to member and president to come forward</li><br />
<li>The Election Board will proclaim the candidates to President and to Members of the Project Management Committee</li><br />
<li>Once candidates are proclaimed, Developers with the right to vote will send a ballot with:<br />
<ol style="list-style-type:lower-roman" ><br />
<li>The name of a candidate to president of the Project Management Committee, and</li><br />
<li>The name of up to four candidates to members of the Project Management Committee</li><br />
</ol></li><br />
<li>There will be 7 days to send the ballots</li><br />
<li>The Election Board will proclaim as President the candidate to president having received most votes for President and as members the six candidates to member having received the most votes as members</li><br />
<li>The new Project Management Committee will start to function 48 hours after being proclaimed</li><br />
</li><br />
</ol></li><br />
</ol><br />
<br />
== Amendments ==<br />
<ol start="29"><br />
<li>To begin the bylaw amendment process, one tenth of the Assembly of Developers must submit a proposal to the PMC.</li><br />
<li>If the PMC accepts an amendment, the Assembly of Developers shall vote on the amendment.</li><br />
<li>If half plus one of the Assembly of Developers accept the amendment, it shall become part of these Bylaws.</li><br />
</ol><br />
<br />
== Transitional provisions ==<br />
<br />
<ol start="32"><br />
<li>Bylaw 15 does not apply to the acceptance of these bylaws.</li><br />
<li>All PMC or Assembly decisions made prior to the acceptance of these bylaws are final, and Bylaw 15 does not apply to these decisions.</li><br />
</ol><br />
<br />
[[Category:PMC campaigns 2020]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=User:ScoopGracie/PMC/Proposed_bylaws&diff=71191User:ScoopGracie/PMC/Proposed bylaws2020-03-09T17:03:46Z<p>ScoopGracie: /* Amendments */</p>
<hr />
<div>'''THESE ARE NOT THE BYLAWS!''' I'm running for PMC, and these are my suggestion. If you have any feedback, please let me know!<br />
<br />
== Mission ==<br />
<br />
<ol start="1"><br />
<li>The mission of the Apertium project is to collaboratively develop free/open-source machine translation for as many languages as possible, and in particular:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To give everyone free, unlimited access to the best possible machine-translation technologies.</li><br />
<li>To maintain a modular, documented, open platform for machine translation and other human language processing tasks</li><br />
<li>To favour the interchange and reuse of existing linguistic data.</li><br />
<li>To make integration with other free/open-source technologies easier.</li><br />
<li>To radically guarantee the reproducibility of machine translation and natural language processing research</li><br />
</ol><br />
And additionally:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To promote the usage of free and open source software.</li><br />
<li>To help combat the bias toward white males in technology.</li><br />
<li>To help support and preserve less widespread languages.</li><br />
</ol><br />
</li><br />
</ol><br />
<br />
== Roles and responsibilities ==<br />
<br />
=== Users ===<br />
<br />
<ol start="2"><br />
<li>The most important participants in the project are people who use Apertium. The majority of our developers start out as users and guide their development efforts from the user's perspective</li><br />
<li>Users contribute to the Apertium project by providing feedback to developers in the form of bug reports and feature suggestions. As well, users participate in the Apertium community by helping other users.</li><br />
</ol><br />
<br />
=== Developers ===<br />
<br />
<ol start="4"><br />
<li>Developers are volunteers who are contributing time, code, documentation, or resources to Apertium.</li><br />
<li>For the purposes of these bylaws, a Developer is anyone who has submitted at least three pull requests or commits to any Apertium repository in the past six months.</li><br />
<li>The Developers of Apertium constitute the Assembly of Developers of Apertium.</li><br />
<li>The project's Developers are responsible for the project's technical management.</li><br />
<li>The Assembly of Developers elects the Project Management Committee of Apertium every even-numbered year in February or whenever a vacancy occurs, whether by resignation, lack of activity (resulting in loss of Developer status, and therefore of PMC membership), or censure.</li><br />
<li>One tenth of the Assembly of Developers may propose a motion of censure to overturn the Project Management Committee or any one or more member(s), which must be approved by half plus one of the members of the Assembly of Developers.</li><br />
<li>The Assembly of Developers must censure the entire Project Management Committee if it has not been acting in accordance with these bylaws.</li><br />
<li>The number of members of the Assembly of Developers of Apertium has no limit.</li><br />
<li>The President of the Project Management Committee will, immediately after a new Project Management Committee begins functioning, nominate a President of the Assembly of Developers, who must be a Developer and may not be a member of the Project Management Committee or of the latest election board. This President will be confirmed by a vote of the Assembly of Developers.<strong>This needs to be discussed. Does the Assembly need a President?</strong></li><br />
<li>The Assembly of Developers decides only on subjects proposed by the Project Management Committee.</li><br />
<li>Once submitted to it, the decisions of the Assembly of Developers are final and binding and cannot be overturned, except as explicitly noted in these Bylaws.</li><br />
<li>One tenth of the Assembly of Developers may decide to attempt to overturn a decision of the Assembly of Developers or Project Management Committee, and the resolution must be passed by half plus one of the Developers.</li><br />
</ol><br />
<br />
=== Project Management Committee ===<br />
<br />
<ol start="16"><br />
<li>The Project Management Committee is formed by seven members of the Assembly designated by it to make the day to day decisions.</li><br />
<li>The Project Management Committee is headed by a President and has six more members, one of whom will act as Secretary and another as Treasurer.</li><br />
<li>All members of the Project Management Committee must be at least thirteen years of age, and the Treasurer must be at least eighteen years of age.</li><br />
<li>The responsibilities of the Project Management Committee include</li><br />
<ol style="list-style-type:lower-alpha" ><br />
<li>Deciding what is distributed as products of Apertium project. In particular, all releases must be approved by the PMC.</li><br />
<li>Maintaining the project's shared resources, including the codebase repository, mailing lists, websites.</li><br />
<li>Speaking on behalf of the project; although, the PMC could give the right to speak on behalf of Apertium to a member of the Assembly of Developers.</li><br />
<li>Resolving licence disputes regarding products of the project.</li><br />
<li>Maintaining these bylaws and other guidelines of the project.</li><br />
<li>Promoting the active engagement of Apertium in larger free/open-source initiatives</li><br />
<li>Attracting external funds to further the objectives of the Apertium project</li><br />
<li>Deciding how to distribute the funds the Apertium project may get as the result of participating in externally-funded initiatives</li><br />
</ol></li><br />
<li>The Project Management Committee votes on all of its decisions.</li><br />
<li>The Project Management Committee has the obligation to submit to the Assembly of Developers the decisions that affect the work of the half or more of the members of the Assembly of Developers, being able to consult in other subjects if believed necessary. </li><br />
<li>Decisions of the Project Management Committee made other than in consultation with the Assembly are immediately filed in a public diary. The Assembly may overturn a PMC decision as described in Bylaw 15.</li><br />
<li>The secretary of the Project Management Committee has the obligation of preparing the diary and presenting it to the Assembly of Developers.</li><br />
<li>While the Treasurer is responsible for financial management, all actions must be approved by a PMC vote. The Treasurer shall be immediately censured from the PMC upon making any financial decisions without a vote.<br />
</ol><br />
<br />
=== Bylaw Violation Court of Apertium ===<br />
<ol start="25"><br />
<li>In the case of an alleged violation of the Bylaws by any Developer, a temporary Bylaw Violation Court shall be established.</li><br />
<li>The Bylaw Violation Court of Apertium shall consist of seven Developers chosen at random, who must not be members of the Project Management Committee or include the accused Developer.</li><br />
<li>The Bylaw Violation Court of Apertium shall decide by consensus if the accused Developer has violated the bylaws, and may take action against the Developer up to, and including, permanent loss of Developer status.</li><br />
</ol><br />
<br />
== Election of the Project Management Committee ==<br />
<br />
<ol start="28"><br />
<li>The Assembly of Developers will elect a new Project Management Committee as follows:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>An Election Board of 3 developers (with at least one substitute member; ideally with one substitute each) will run the election. Election Board membership is a volunteer position on a first-come first-served basis.</li><br />
<li>The Project Management Committee will provide the Election Board with all the information needed to run the election</li><br />
<li>Any Developer may run for member of the Project Management Committee</li><br />
<li>Any Developer may run for president of the Project Management Committee</li><br />
<li>Candidates cannot be part of the Election Board</li><br />
<li>When an election is called, the Election Board will publish a census of Developers with right to vote.</li><br />
<li>There will be 7 days for candidates to member and president to come forward</li><br />
<li>The Election Board will proclaim the candidates to President and to Members of the Project Management Committee</li><br />
<li>Once candidates are proclaimed, Developers with the right to vote will send a ballot with:<br />
<ol style="list-style-type:lower-roman" ><br />
<li>The name of a candidate to president of the Project Management Committee, and</li><br />
<li>The name of up to four candidates to members of the Project Management Committee</li><br />
</ol></li><br />
<li>There will be 7 days to send the ballots</li><br />
<li>The Election Board will proclaim as President the candidate to president having received most votes for President and as members the six candidates to member having received the most votes as members</li><br />
<li>The new Project Management Committee will start to function 48 hours after being proclaimed</li><br />
</li><br />
</ol></li><br />
</ol><br />
<br />
== Amendments ==<br />
<ol start="29"><br />
<li>To begin the bylaw amendment process, one tenth of the Assembly of Developers must submit a proposal to the PMC.</li><br />
<li>If the PMC accepts an amendment, the Assembly of Developers shall vote on the amendment.</li><br />
<li>If half plus one of the Assembly of Developers accept the amendment, it shall become part of these Bylaws.</li><br />
</ol><br />
<br />
== Transitional provisions ==<br />
<br />
<ol start="29"><br />
<li>Bylaw 15 does not apply to the acceptance of these bylaws.</li><br />
<li>All PMC or Assembly decisions made prior to the acceptance of these bylaws are final, and Bylaw 15 does not apply to these decisions.</li><br />
</ol><br />
<br />
[[Category:PMC campaigns 2020]]</div>ScoopGraciehttps://wiki.apertium.org/w/index.php?title=User:ScoopGracie/PMC/Proposed_bylaws&diff=71190User:ScoopGracie/PMC/Proposed bylaws2020-03-09T17:02:51Z<p>ScoopGracie: /* Bylaw Violation Court of Apertium */</p>
<hr />
<div>'''THESE ARE NOT THE BYLAWS!''' I'm running for PMC, and these are my suggestion. If you have any feedback, please let me know!<br />
<br />
== Mission ==<br />
<br />
<ol start="1"><br />
<li>The mission of the Apertium project is to collaboratively develop free/open-source machine translation for as many languages as possible, and in particular:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To give everyone free, unlimited access to the best possible machine-translation technologies.</li><br />
<li>To maintain a modular, documented, open platform for machine translation and other human language processing tasks</li><br />
<li>To favour the interchange and reuse of existing linguistic data.</li><br />
<li>To make integration with other free/open-source technologies easier.</li><br />
<li>To radically guarantee the reproducibility of machine translation and natural language processing research</li><br />
</ol><br />
And additionally:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>To promote the usage of free and open source software.</li><br />
<li>To help combat the bias toward white males in technology.</li><br />
<li>To help support and preserve less widespread languages.</li><br />
</ol><br />
</li><br />
</ol><br />
<br />
== Roles and responsibilities ==<br />
<br />
=== Users ===<br />
<br />
<ol start="2"><br />
<li>The most important participants in the project are people who use Apertium. The majority of our developers start out as users and guide their development efforts from the user's perspective</li><br />
<li>Users contribute to the Apertium project by providing feedback to developers in the form of bug reports and feature suggestions. As well, users participate in the Apertium community by helping other users.</li><br />
</ol><br />
<br />
=== Developers ===<br />
<br />
<ol start="4"><br />
<li>Developers are volunteers who are contributing time, code, documentation, or resources to Apertium.</li><br />
<li>For the purposes of these bylaws, a Developer is anyone who has submitted at least three pull requests or commits to any Apertium repository in the past six months.</li><br />
<li>The Developers of Apertium constitute the Assembly of Developers of Apertium.</li><br />
<li>The project's Developers are responsible for the project's technical management.</li><br />
<li>The Assembly of Developers elects the Project Management Committee of Apertium every even-numbered year in February or whenever a vacancy occurs, whether by resignation, lack of activity (resulting in loss of Developer status, and therefore of PMC membership), or censure.</li><br />
<li>One tenth of the Assembly of Developers may propose a motion of censure to overturn the Project Management Committee or any one or more member(s), which must be approved by half plus one of the members of the Assembly of Developers.</li><br />
<li>The Assembly of Developers must censure the entire Project Management Committee if it has not been acting in accordance with these bylaws.</li><br />
<li>The number of members of the Assembly of Developers of Apertium has no limit.</li><br />
<li>The President of the Project Management Committee will, immediately after a new Project Management Committee begins functioning, nominate a President of the Assembly of Developers, who must be a Developer and may not be a member of the Project Management Committee or of the latest election board. This President will be confirmed by a vote of the Assembly of Developers.<strong>This needs to be discussed. Does the Assembly need a President?</strong></li><br />
<li>The Assembly of Developers decides only on subjects proposed by the Project Management Committee.</li><br />
<li>Once submitted to it, the decisions of the Assembly of Developers are final and binding and cannot be overturned, except as explicitly noted in these Bylaws.</li><br />
<li>One tenth of the Assembly of Developers may decide to attempt to overturn a decision of the Assembly of Developers or Project Management Committee, and the resolution must be passed by half plus one of the Developers.</li><br />
</ol><br />
<br />
=== Project Management Committee ===<br />
<br />
<ol start="16"><br />
<li>The Project Management Committee is formed by seven members of the Assembly designated by it to make the day to day decisions.</li><br />
<li>The Project Management Committee is headed by a President and has six more members, one of whom will act as Secretary and another as Treasurer.</li><br />
<li>All members of the Project Management Committee must be at least thirteen years of age, and the Treasurer must be at least eighteen years of age.</li><br />
<li>The responsibilities of the Project Management Committee include</li><br />
<ol style="list-style-type:lower-alpha" ><br />
<li>Deciding what is distributed as products of Apertium project. In particular, all releases must be approved by the PMC.</li><br />
<li>Maintaining the project's shared resources, including the codebase repository, mailing lists, websites.</li><br />
<li>Speaking on behalf of the project; although, the PMC could give the right to speak on behalf of Apertium to a member of the Assembly of Developers.</li><br />
<li>Resolving licence disputes regarding products of the project.</li><br />
<li>Maintaining these bylaws and other guidelines of the project.</li><br />
<li>Promoting the active engagement of Apertium in larger free/open-source initiatives</li><br />
<li>Attracting external funds to further the objectives of the Apertium project</li><br />
<li>Deciding how to distribute the funds the Apertium project may get as the result of participating in externally-funded initiatives</li><br />
</ol></li><br />
<li>The Project Management Committee votes on all of its decisions.</li><br />
<li>The Project Management Committee has the obligation to submit to the Assembly of Developers the decisions that affect the work of the half or more of the members of the Assembly of Developers, being able to consult in other subjects if believed necessary. </li><br />
<li>Decisions of the Project Management Committee made other than in consultation with the Assembly are immediately filed in a public diary. The Assembly may overturn a PMC decision as described in Bylaw 15.</li><br />
<li>The secretary of the Project Management Committee has the obligation of preparing the diary and presenting it to the Assembly of Developers.</li><br />
<li>While the Treasurer is responsible for financial management, all actions must be approved by a PMC vote. The Treasurer shall be immediately censured from the PMC upon making any financial decisions without a vote.<br />
</ol><br />
<br />
=== Bylaw Violation Court of Apertium ===<br />
<ol start="25"><br />
<li>In the case of an alleged violation of the Bylaws by any Developer, a temporary Bylaw Violation Court shall be established.</li><br />
<li>The Bylaw Violation Court of Apertium shall consist of seven Developers chosen at random, who must not be members of the Project Management Committee or include the accused Developer.</li><br />
<li>The Bylaw Violation Court of Apertium shall decide by consensus if the accused Developer has violated the bylaws, and may take action against the Developer up to, and including, permanent loss of Developer status.</li><br />
</ol><br />
<br />
== Election of the Project Management Committee ==<br />
<br />
<ol start="28"><br />
<li>The Assembly of Developers will elect a new Project Management Committee as follows:<br />
<ol style="list-style-type:lower-alpha" ><br />
<li>An Election Board of 3 developers (with at least one substitute member; ideally with one substitute each) will run the election. Election Board membership is a volunteer position on a first-come first-served basis.</li><br />
<li>The Project Management Committee will provide the Election Board with all the information needed to run the election</li><br />
<li>Any Developer may run for member of the Project Management Committee</li><br />
<li>Any Developer may run for president of the Project Management Committee</li><br />
<li>Candidates cannot be part of the Election Board</li><br />
<li>When an election is called, the Election Board will publish a census of Developers with right to vote.</li><br />
<li>There will be 7 days for candidates to member and president to come forward</li><br />
<li>The Election Board will proclaim the candidates to President and to Members of the Project Management Committee</li><br />
<li>Once candidates are proclaimed, Developers with the right to vote will send a ballot with:<br />
<ol style="list-style-type:lower-roman" ><br />
<li>The name of a candidate to president of the Project Management Committee, and</li><br />
<li>The name of up to four candidates to members of the Project Management Committee</li><br />
</ol></li><br />
<li>There will be 7 days to send the ballots</li><br />
<li>The Election Board will proclaim as President the candidate to president having received most votes for President and as members the six candidates to member having received the most votes as members</li><br />
<li>The new Project Management Committee will start to function 48 hours after being proclaimed</li><br />
</li><br />
</ol></li><br />
</ol><br />
<br />
== Amendments ==<br />
<ol start="26"><br />
<li>To begin the bylaw amendment process, one tenth of the Assembly of Developers must submit a proposal to the PMC.</li><br />
<li>If the PMC accepts an amendment, the Assembly of Developers shall vote on the amendment.</li><br />
<li>If half plus one of the Assembly of Developers accept the amendment, it shall become part of these Bylaws.</li><br />
</ol><br />
<br />
== Transitional provisions ==<br />
<br />
<ol start="29"><br />
<li>Bylaw 15 does not apply to the acceptance of these bylaws.</li><br />
<li>All PMC or Assembly decisions made prior to the acceptance of these bylaws are final, and Bylaw 15 does not apply to these decisions.</li><br />
</ol><br />
<br />
[[Category:PMC campaigns 2020]]</div>ScoopGracie