Re: [Apertium-stuff] Potential replacement for GCI

[Shardul Chiplunkar]

  
  
On the other hand, reaching out to young
  developers so that they join our community is absolutely necessary
  for the survival of Apertium.
At the university level, perhaps faculty members who are associated
with Apertium and the (computational) linguistics department at
their university could encourage independent research projects? Or
incorporate Apertium into the syllabus of classes?

I don't have much of a suggestion for the high school level. But I
know that there are growing contest linguistics communities, e.g.
NACLO participants in the US feeding into the International
Linguistics Olympiad. Some of these students might value an
opportunity to explore their interest in linguistics in the real
world and do something real (beyond the contest environment) through
Apertium.

Shardul

On 6/10/20 11:12 PM, Mikel L. Forcada
  wrote:


  
  Samuel, thanks for the heads-up.
  
  See [1]
  A replacement for Google Code-In, Apertium Code-In, would be
hard to organize for an already quite overworked community. No
matter how much we complained about Melange, Google provided
invaluable support to run it which would be quite hard to
duplicate. And most of the money we have left comes from Google
Code-In donations (We have quite a lot of money which we could
spend, BTW, around ~40 k€).
  
  On the other hand, reaching out to young developers so that
they join our community is absolutely necessary for the survival
of Apertium.
  Any ideas?
  Mikel
  
  
  
  [1] https://groups.google.com/forum/#!msg/gci-announce/pmo3bvqYBew/vVT0-LK5AAAJ
  El 11/6/20 a les 7:09, Samuel
Sloniker ha escrit:
  
  

  It might also be good to focus more on the non-coding
ways of contributing.


  On Wed, Jun 10, 2020,
21:25 Samuel Sloniker 
wrote:
  
  
Hi,
  Google has cancelled Google Code-in. I
was wondering if Apertium could start a replacement.
Perhaps we could partner with some other FOSS
organizations?

  

  





___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

  
  -- 
Mikel L. Forcada  http://www.dlsi.ua.es/~mlf/
Departament de Llenguatges i Sistemes Informàtics
Universitat d'Alacant
E-03690 Sant Vicent del Raspeig
Spain
Office: +34 96 590 9776
  
  
  
  
  ___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff



  


___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] (no subject)

[Shardul Chiplunkar]

Hi Suraj,

A pair involving Sanskrit is a bad choice for Apertium because of *sandhi*.
For example, the sentence जानामि अहम् (*jaanaami aham*, 'I know') is
actually written as one word: जानाम्यहम् (*jaanaamyaham*, 'I know'). Any
number of words can be joined together like this with *sandhi*, regardless
of part-of-speech, and furthermore those words are inflected too (like the
example). To analyze Sanskrit text, you would have to be able to break
the *sandhi
*of arbitrarily inflected forms; this is not trivial, not easily possible
with Apertium tools (I believe), and definitely very hard to disambiguate
when you have multiple possible breaks in a word.

Maybe you can work on another language pair involving Indian languages, if
you know anything beyond Sanskrit and Hindi?

Shardul


On Sat, Mar 24, 2018 at 3:00 PM, Suraj Tamgale  wrote:

> hi everyone,
> i've submitted the proposal.i will be extremely happy if someone take a
> look at it and give review.
>
> link to my draft: hhttps://docs.google.com/document/d/11uI3WsQ5_
> L4HEyETqqgmzXTsR7fUSCd01fKe8VhekXM/edit?usp=sharing
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Apertium-stuff mailing list
> Apertium-stuff@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] GSoC wiki account

[Shardul Chiplunkar]

Hi Nitish,

I have created an account for you.

Shardul

On Mon, Mar 12, 2018 at 9:44 PM, Nitish Kumar 
wrote:

> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Apertium-stuff mailing list
> Apertium-stuff@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
> On 13-Mar-2018 10:07 AM, "Nitish Kumar" 
> wrote:
>
>> I want to work on my proposal so please provide me a wiki account
>>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Apertium-stuff mailing list
> Apertium-stuff@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Hello, introducing myself and a few questions, thanks!

[Shardul Chiplunkar]

Hi Claudi,

About access to GitHub: Since Apertium has recently shifted to GitHub, we
are still working things out, and there are two things that can happen.

1. The 'GitHub' way to do it is to create a personal fork of the
repository. After you create your personal fork, you can submit a pull
request, which Hèctor Alòs or other existing contributors can review and
merge. After a few pull requests have been approved, admins will happily
give you push access. (If you are unsure about forks/pull requests/etc.
feel free to email me.)

2. The problem with the previous method is that 'admins' are not explicitly
defined for most repositories, since we have very recently switched. We are
figuring it out on a case-by-case basis, so thank you for bringing this
case up :) However, the PMC members are admins of all repositories by
default, so either they could directly give you access, or a specific admin
could be named who would go ahead with #1.

I would suggest that you start with #1. Or maybe if you have already
contributed to the Apertium repositories in a branch or personal
repository, please share it so that you can be given access straight away.
I also request a member of the PMC to please provide their input on naming
an admin for the specific case of oci-fra, or on the permissions model for
the Romance team.

About access to the wiki: I have created an account for you.

Thanks,
Shardul


On Mon, Mar 12, 2018 at 2:01 PM, Rata Penada via Apertium-stuff <
apertium-stuff@lists.sourceforge.net> wrote:

> Hello, my name is Claudi Balaguer (username on Github: Capsot) and I am
> currently working on apertium-oci-fra with Hèctor Alòs. I would like to
> know if I could have access to the push function in Github on
> apertium-oci-fra and also how to create a profile on the Apertium wiki so I
> could work on the Pending tests. I have already worked on it and included
> many entries so far.
> Thanks a lot in advance
> Sincerely,
> Claudi
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Apertium-stuff mailing list
> Apertium-stuff@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] IDEAS AND INPUTS FOR THE PYTHON API OF APERTIUM

[Shardul Chiplunkar]

Hi Arghya,

Just my two cents: suppose you actually built the wrapper according to your
current idea. If someone was trying out the interface in an interactive
shell, what would it look like? (Just translation? Getting all the
intermediate steps? The names/organization of the modules? etc)

Often, it is easier to suggest improvements to an existing idea or to
critique it, rather than answer an open question.

Thanks,
Shardul

On Mar 11, 2018 05:55, "arghya bhattacharay"  wrote:

Greetings Everyone,


I'm working on building a Python Wrapper for the Apertium Core modules
(Lttoolbox and Apertium) using a tool called SWIG.
I need your help in the form of Ideas and suggestions as to how should the
library be organised, or how you would like the python package to be
organised.

Python users and experts please do provide your valuable inputs.


Regards,
Arghya Bhattacharya


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] Apertium has migrated to GitHub

[Shardul Chiplunkar]

Dear Apertium contributors,

Please read this email carefully, because there has been an important
change in
Apertium. The Apertium repository on SourceForge has been *locked
permanently*---it is read-only and nobody will be able to commit anymore.
The
Apertium core, monolingual modules, and bilingual modules at all stages of
development have been moved to GitHub. Tools already on GitHub have been
officially brought under Apertium. Other tools will be moved on an ad hoc
basis
upon request [2]. The GitHub repositories are available for use at [1].

Please see the previous email with the title "IMPORTANT: Apertium will be
migrating to GitHub" for details regarding this change. It is important to
note
that the permissions for committing to repositories on GitHub are not the
same
as before.

For help with using git and GitHub, or if you want to avoid using git
altogether, please see the wiki's help page [3].

Note about GitHub organization membership: by default, everyone is a
'private'
member of the Apertium organization on GitHub. If you wish to be publicly
visible on the organization page [9], please change your membership to
'public'
[10].

There was a lot of discussion about this migration, including on the wiki
page
[4] and in an email thread [5]. If you have further questions about the
migration, or problems with using the GitHub repositories, you can:
 - contact me [6] or Sushain [7]
 - send an email to apertium-stuff@lists.sourceforge.net
 - join the IRC channel #apertium on Freenode [8]

Thank you,
Shardul Chiplunkar


  [1]: https://apertium.github.io/apertium-on-github/source-browser.html
  [2]: http://wiki.apertium.org/wiki/Migrating_tools_to_GitHub
  [3]: http://wiki.apertium.org/wiki/Using_git
  [4]: http://wiki.apertium.org/wiki/PMC_proposals/Move_Apertium_to_Github
  [5]:
https://www.mail-archive.com/apertium-stuff@lists.sourceforge.net/msg06629.html
  [6]: Shardul Chiplunkar 
  [7]: Sushain Cherivirala 
  [8]: http://wiki.apertium.org/wiki/IRC
  [9]: https://github.com/apertium
  [10]:
https://help.github.com/articles/publicizing-or-hiding-organization-membership/
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: Move Apertium to Github

[Shardul Chiplunkar]

Thanks for your comments.

Felipe, I have tried to respond to your comment on the proposal page.
Please let us know if you have further questions.

It seems that making the repository read-only and later deleting it is the
best option then. As Fran and Xavi said, we would go through the wiki
pages, READMEs, Virtualbox/Docker configs, etc. to replace SourceForge
links with GitHub links in the meantime.


Shardul C.

On Tue, Feb 13, 2018 at 2:29 AM, Francis Tyers  wrote:

> El 2018-02-13 11:23, Francis Tyers escribió:
>
>> El 2018-02-13 10:40, Xavi Ivars escribió:
>>
>>> 2018-02-13 10:16 GMT+01:00 Francis Tyers :
>>>
>>>
>
 Both of these are horrible. So I propose that we just make it
 read-only for a year and then delete it.

 In the meantime the migration crew (you, Sushain, others) will have
 the responsibility of fixing the ~1000 links on the Wiki so that
 they point to the right place and people don't get 404s or outdated
 links by clicking in the documentation.

>>>
>>> I agree. I would make it read-only for a while (or deleting the
>>> content), adding READMEs in all folders pointing to the new URLs.
>>>
>>>
> Note that there are _far more_ than 7 links to the SVN code on the Wiki.
> I suggest using Google and not the (broken) Wiki search:
>
> https://www.google.ru/search?q=svn.code.sf.net+site%3Awiki.a
> pertium.org&ie=utf-8&oe=utf-8&client=firefox-b&gfe_rd=cr&dcr
> =0&ei=g72CWobnBMfBsAGP3oagDA
>
>
> Fran
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Apertium-stuff mailing list
> Apertium-stuff@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Proposal: Move Apertium to Github

[Shardul Chiplunkar]

Hi everyone,

We've now written all the scripts required for the migration. The scripts
and documentation are available here:
https://github.com/sushain97/apertium-on-github

The only issue remaining is of backwards compatibility with the SourceForge
repository. Due to the technical details of SVN, we have two options:

1. Using 'propset': (as an example) When a user checks out the top
directory or the 'incubator' directory from SVN, all the subdirectories
will actually be external pointers to the GitHub SVN bridges for the
corresponding directories, automatically using the latest code from the
GitHub repositories. However, when a user checks out just the
'apertium-eng' directory from SVN, either the directory will be empty or it
will have yet another subdirectory called 'apertium-eng' pointing to the
appropriate GitHub repository, depending on what we choose to do. It is
unfortunately not possible to directly check out an external pointer in
SVN. (Note: if we go with this option, the HTTP interface at
https://svn.code.sf.net/p/apertium/svn/ would be effectively blank.)

2. If the above option is undesirable, we would simply not have backwards
compatibility and would need a clear, not-easily-missed message wherever
required that the SourceForge repository is not updated anymore. It could
be marked read-only or deleted altogether.

We request your comments and suggestions for how to proceed. Except for
this issue, everything else required for migration is ready to go. Thank
you,

Shardul C.

​(P.S. As Apertium has been selected for GSoC this year (hooray!), we hope
this goes through as soon as possible before March 12.)​


On Wed, Feb 7, 2018 at 4:39 PM, Shardul Chiplunkar <
shardul.chiplun...@gmail.com> wrote:

> Hi Bernard,
>
> Xavi has covered a lot of points that you were asking about. I'd just like
> to add a few more.
>
> First: Github offers an SVN bridge. This means that if we shift to Github,
> developers who
> want to continue using SVN can use all the same SVN commands and workflows
> as before.
> The only difference will be, when running svn checkout, the URL will be
> github.com and not
> sourceforge.net. After that checkout the developers will not even need to
> be aware that they
> are using Github, and SVN will work exactly as before.
>
> Second: Here is how pull requests work. (As Xavi mentioned, this is an
> optional thing which
> may be used by only some packages, but I think it is important.)
>
> 1. A group of users called 'apertium' is the owner of all the repositories.
> For example, 'apertium/apertium-fra'.
>
> 2. Any developer can create a personal copy of any repository, called a
> 'fork'. The developer
> is the owner of the fork but 'apertium' is still the owner of the original
> repository.
> For example, 'shardulc' creates the fork 'shardulc/apertium-fra'.
>
> 3. The developer makes some changes on the fork.
> For example, 'shardulc' adds some commits to 'shardulc/apertium-fra'. This
> does not change
> 'apertium/apertium-fra' because it is a separate repository.
>
> 4. The developer submits a pull request to the original repository.
> Basically, this means the
> developer is saying to the original repository, "please look at the
> changes I have made and
> add them to the original repository". 'apertium/apertium-fra' is still not
> changed, but whoever
> is in charge of the package is informed that a developer wants to add some
> changes.
>
> 5. The changes are reviewed. If they are acceptable, they are added, and
> now
> 'apertium/apertium-fra' and 'shardulc/apertium-fra' have the same code. If
> they are not
> acceptable, the reviewer can tell 'shardulc' what he should change and it
> goes back to step 3.
>
> Some benefits of using this model:
> 1. It is very easy to make personal changes to Apertium. To make a fork,
> the developer just
> needs to click a button on Github. The developer does not even need to be
> related to Apertium.
> The developer can do whatever they want with the code for personal use and
> Apertium's code
> will be unchanged.
> 2. If the developer wants to add the changes to Apertium, there can be
> pull requests, and most
> importantly, there can be reviews. Of course new developers will not
> produce high quality code
> all at once, and tips from experienced developers will be very useful;
> even experienced
> developers can review each other's code (everyone makes mistakes) and this
> will improve code
> quality.
> 3. Reviewing pull requests, creating and resolving issues, assigning who
> should work on what,
> etc. is very easy on

Re: [Apertium-stuff] Proposal: Move Apertium to Github

[Shardul Chiplunkar]

Hi Bernard,

Xavi has covered a lot of points that you were asking about. I'd just like
to add a few more.

First: Github offers an SVN bridge. This means that if we shift to Github,
developers who
want to continue using SVN can use all the same SVN commands and workflows
as before.
The only difference will be, when running svn checkout, the URL will be
github.com and not
sourceforge.net. After that checkout the developers will not even need to
be aware that they
are using Github, and SVN will work exactly as before.

Second: Here is how pull requests work. (As Xavi mentioned, this is an
optional thing which
may be used by only some packages, but I think it is important.)

1. A group of users called 'apertium' is the owner of all the repositories.
For example, 'apertium/apertium-fra'.

2. Any developer can create a personal copy of any repository, called a
'fork'. The developer
is the owner of the fork but 'apertium' is still the owner of the original
repository.
For example, 'shardulc' creates the fork 'shardulc/apertium-fra'.

3. The developer makes some changes on the fork.
For example, 'shardulc' adds some commits to 'shardulc/apertium-fra'. This
does not change
'apertium/apertium-fra' because it is a separate repository.

4. The developer submits a pull request to the original repository.
Basically, this means the
developer is saying to the original repository, "please look at the changes
I have made and
add them to the original repository". 'apertium/apertium-fra' is still not
changed, but whoever
is in charge of the package is informed that a developer wants to add some
changes.

5. The changes are reviewed. If they are acceptable, they are added, and now
'apertium/apertium-fra' and 'shardulc/apertium-fra' have the same code. If
they are not
acceptable, the reviewer can tell 'shardulc' what he should change and it
goes back to step 3.

Some benefits of using this model:
1. It is very easy to make personal changes to Apertium. To make a fork,
the developer just
needs to click a button on Github. The developer does not even need to be
related to Apertium.
The developer can do whatever they want with the code for personal use and
Apertium's code
will be unchanged.
2. If the developer wants to add the changes to Apertium, there can be pull
requests, and most
importantly, there can be reviews. Of course new developers will not
produce high quality code
all at once, and tips from experienced developers will be very useful; even
experienced
developers can review each other's code (everyone makes mistakes) and this
will improve code
quality.
3. Reviewing pull requests, creating and resolving issues, assigning who
should work on what,
etc. is very easy on Github because of its superior interface. As a recent
example, you can see
the interaction between me and Sushain in these two links:
https://github.com/sushain97/apertium-on-github/issues/7
https://github.com/sushain97/apertium-on-github/pull/11(click on "show
outdated")

More benefits/concerns are mentioned on the wiki page and I have also
replied to your
comments there. Hope this helps!


Shardul C.

On Wed, Feb 7, 2018 at 9:54 AM, Bernard Chardonneau 
wrote:

> > Date: Sat, 3 Feb 2018 16:03:48 -0800
> > From: Shardul Chiplunkar 
> > To: apertium-stuff@lists.sourceforge.net,
> >  apertium-pmc 
> > Reply-To: apertium-stuff@lists.sourceforge.net
> > Subject: [Apertium-stuff] Proposal: Move Apertium to Github
> > Pièce(s) jointes(s) probable(s)>
> > To the President and members of the PMC and Apertium contributors,
> >
> > There is a new proposal to the PMC to move Apertium to Github:
> > http://wiki.apertium.org/wiki/PMC_proposals/Move_Apertium_to_Github
> >
> > Both previous proposals of a similar topic had shortcomings which this
> > proposal tries to address.
> >
> > If you are not a member of the PMC but would like to express your support
> > for this proposal, please add your name to the "Non-PMC signatories"
> > section at the bottom of the page.
> >
> > Thank you,
> > Shardul C.
> >
>
> Well, I preferred watching information about git before taking part of
> this debate.
>
> First, your proposal, as previous ones about it includes 2 changes in
> the same package :
> 1) leaving sourceforge.net to go to github.com
> 2) leaving subversion to use git
>
> According to what we need, these 2 changes can be examined separately.
>
> Do we have a reason to leave sourceforge.net ? (I heard about problems
> with this provider during the last years). if yes, we can move to another
> provider supporting subversion.
>
> Do we have a reason to leave subversion and to use git instead ?
> If yes, we ca

Re: [Apertium-stuff] Proposal: Move Apertium to Github

[Shardul Chiplunkar]

Hi everyone,

Thanks for your inputs.

Sergio:

> move all the existing user base with minimal impact (how to announce, how
> to contact

users, how to switch off the old repos, etc.)

This is a very valid concern. We have updated the wiki page for the
proposal with a brief
outline of how we would handle this.

Regarding Gitlab, I also believe that it is theoretically superior to
GitHub (because the
interface does not use proprietary JS, among other things) but the reason
for choosing
GitHub is the visibility of a very popular hosting service, and the ease of
use for newcomers
who are often already familiar with GitHub. These and other reasons are
detailed in the
proposal.

Tommi:

> all the continuous integrations, continuous deployment and github pages
> (generated
>
from dixes via xslt and bahs hacks!) experimented out a bit

Thanks! We'll surely take a look and see what can be generalized to other
packages.

Fran: Thanks for pointing out the GSoC schedule. If all goes well, I
believe March 12
is not an unreasonable deadline to finish the technical parts of the
migration.

Thanks,

Shardul C.

On Tue, Feb 6, 2018 at 3:34 AM, Benedikt Freisen  wrote:

> Alright.  Thanks for pointing me at it.  I must have scrolled right past
> that "authors.txt", assuming that it was the AUTHORS file of the
> repository.
>
> My suggestion for added clarity would be:
> - create an AUTHORS file with your names in it
> - rename authors.txt to apertium_svn_authors.txt or something like that
>
> The ...@users.sourceforge.net addresses do indeed make more sense than
> pure dummy addresses, since they are at least theoretically valid
> addresses of the respective authors.
>
> Regards
> Benedikt
>
> Am 06.02.2018 um 03:38 schrieb Sushain Cherivirala:
> > Hi Benedikt,
> >
> > Thank you for your reply. You raise a good question regarding the
> > preservation
> > of emails in a transition to Git.
> >
> > Fortunately, in managing the Apertium packages for various platforms,
> > Tino has also
> > has put together a correspondence between SVN users and emails. The
> import
> > scripts that I have written use this correspondence. The current version
> > can be
> > found here:
> > https://github.com/sushain97/apertium-on-github/blob/master/authors.txt
> > <https://github.com/sushain97/apertium-on-github/blob/master/authors.txt
> >.
> >
> > Here is some documentation for the scripts I mention:
> > https://github.com/sushain97/apertium-on-github#scripts
> > <https://github.com/sushain97/apertium-on-github#scripts>.
> >
> > If your proper email is missing, you could email Tino and I. If your
> > email in the file
> > does not correspond to the email you use from GitHub, it can be changed.
> > However, it might be easiest to just add the email to your GitHub
> > account (you
> > can ensure that it is private). Of course, a repo's authors can always
> > be modified
> > after the fact with a re-import or filter-branch operation if necessary.
> >
> > I will leave you with an example of what the import script does when
> used on
> > apertium-cat: https://github.com/mock-apertium/apertium-
> cat/graphs/contributors
> > <https://github.com/mock-apertium/apertium-cat/graphs/contributors>.
> >
> > I am happy to answer any further questions.
> >
> > --
> > Sushain K. Cherivirala
> >
> > On Mon, Feb 5, 2018 at 5:06 AM, Benedikt Freisen  > <mailto:b.frei...@gmx.net>> wrote:
> >
> > One not so unimportant issue that I do not see mentioned anywhere is
> > E-mail addresses.
> > While svn only maintains a simple user name, git requires user name +
> > E-mail address.  Tools like git-svn will only create a dummy address
> > (user@repository-hash or something like that).
> >
> > When reactos moved to github in October, a list of svn committer
> names
> > plus full (real) names and E-mail addresses was compiled and
> supplied to
> > the conversion tool, with more meaningful dummy addresses for
> previous
> > committers without a known valid E-mail address.
> > Apertium could use something like
> > svnnameofcommitterwhol...@svn.apertium.org
> > <mailto:svnnameofcommitterwhol...@svn.apertium.org> in that case.
> >
> > My suggestion is therefore to scan all AUTHORS files for E-mail
> > addresses and names corresponding to the respective committers.
> > This has the additional benefit, that if those authors have a github
> > account and use the same name+address combination with their github
> > repositories, git

[Apertium-stuff] Proposal: Move Apertium to Github

[Shardul Chiplunkar]

To the President and members of the PMC and Apertium contributors,

There is a new proposal to the PMC to move Apertium to Github:
http://wiki.apertium.org/wiki/PMC_proposals/Move_Apertium_to_Github

Both previous proposals of a similar topic had shortcomings which this
proposal tries to address.

If you are not a member of the PMC but would like to express your support
for this proposal, please add your name to the "Non-PMC signatories"
section at the bottom of the page.

Thank you,
Shardul C.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] GSOC flyer translation

[Shardul Chiplunkar]

Hi Vinit,

As we discussed on IRC, I can provide a Marathi translation of the flyer.
I'll get back to you about the Hindi.

​Thanks,
Shardul C.

On Wed, Jan 17, 2018 at 7:26 AM, Vinit Ravishankar <
vinit.ravishan...@gmail.com> wrote:

> Is it all right if I change the way a bunch of this stuff is worded?
> There's really no good way to translate stuff like "one line of code at a
> time" to Marathi, and I'm not good at writing clickbaity headings :D
>
> – V
> ­
>
> On 16 January 2018 at 11:52, Francis Tyers  wrote:
>
>> El 2018-01-16 11:41, Memduh Gokirmak escribió:
>>
>>> The GB version might as well be used as the English version. Americans
>>> should get used to provincial dialects anyway. Should we try and put
>>> it out in crimtat and kurmanji etc?
>>>
>>
>> If you can get the translations that would be great :D
>>
>>
>> F.
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> Apertium-stuff mailing list
>> Apertium-stuff@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>>
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Apertium-stuff mailing list
> Apertium-stuff@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Possessive Determiners Inflected for Possessor and Possessed

[Shardul Chiplunkar]

Hi everyone,

Thanks for the clarification.

> without the subcategory tags referring to the gender and number of the
possessor
That would mean the possessor information is lost, creating issues for
translating to and from other languages where that information is also
present. For example, Hindi also marks number of both the possessor and
possessed.

> why these aren't being called pronouns
Quoting from the Universal Dependencies page (
http://universaldependencies.org/u/pos/PRON.html):

> "Pronouns under this definition function like nouns. Note that some
languages traditionally extend the term *pronoun* to words that substitute
for adjectives. Such words are not tagged PRON under our universal scheme.
They are tagged as determiners in order to annotate the same thing the same
way across languages. It is not always crystal clear where pronouns end and
determiners start. ... The words can be pre-classified in the dictionary as
either PRON or DET, based on their *typical* syntactic distribution (and
morphology, when applicable)."

The typical use of 'tyacha' in Marathi is preceding a noun, making it like
an adjective, hence we are calling it a determiner. Using 'tyacha' on its
own as a pronoun is relatively uncommon.

According to this discussion, I think we should go with option 1 in my
first email. The complete analysis would be:
tyacha: ^to+ch

(The  tag is because 'tya' can be followed by any postposition, and
there is also a distinct nominative form of the determiner.)

Again, thanks to everyone for the clarification. And happy holidays!


Shardul C.

On Tue, Dec 26, 2017 at 8:16 AM, Jonathan Washington <
jonathan.n.washing...@gmail.com> wrote:

> Hi everyone,
>
> So the standard is to to treat the different possessor bases as separate
> lemmas, without the subcategory tags referring to the gender and number of
> the possessor, and instead only the grammatical (agreement) number and
> gender tags?
>
> tyacha/tya
>
> Something like that?  (My understanding is that personal and demonstrative
> determiners and pronouns aren't distinguished, but proximal and distal are
> for the 3rd person ones—hence the subcategory tags I used.)
>
> By the way, I'm still confused why these aren't being called pronouns.  It
> was late last night here when we were discussing it on IRC, so I probably
> missed something...
>
> Happy holidays all :)
>
> --
> Jonathan
>
>
> On Dec 26, 2017 10:44, "Vinit Ravishankar" 
> wrote:
>
> The current UD Mar standard is indeed to treat the two as separate lemmas,
> or at least split tokens, so I would go with whatever is the most similar
> to that.
>
> Sorry I'm not on IRC, bit busy over xmas. Cheers!
>
> — V
>
> On 26 Dec 2017 9:58 am, "Shardul Chiplunkar" 
> wrote:
>
>> Hi all,
>>
>> This is an issue which was briefly discussed on IRC on 2017-12-26, and
>> Jonathan advised me to post about it here. It is about possessive
>> determiners in Marathi.
>>
>> Minimal examples:
>>  1. "tyacha ghoda" = "his horse" (horse is masculine)
>>  2. "ticha ghoda" = "her horse"
>>  3. "tyachi gay" = "his cow" (cow is feminine)
>>  4. "tichi gay" = "her cow"
>>
>> What these examples show is that the possessive determiners are inflected
>> according to the gender of both the possessor and the possessed. This is
>> also true for the number of both in Marathi. (There are three genders and
>> two numbers.)
>>
>> Previously, 'tyacha' was being analyzed with the tags
>> , which is an issue for structural transfer. We
>> discussed two alternatives:
>>  1. having XYZ+ch, that is, treating the 'ch' forms as
>> separate lemmas
>>  2. having XYZ, that is, making separate tags for
>> the possessor and the possessed
>>
>> What is the best way to proceed, with these options or maybe something
>> else?
>>
>> Shardul C.
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> Apertium-stuff mailing list
>> Apertium-stuff@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>>
>>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _

[Apertium-stuff] Possessive Determiners Inflected for Possessor and Possessed

[Shardul Chiplunkar]

Hi all,

This is an issue which was briefly discussed on IRC on 2017-12-26, and
Jonathan advised me to post about it here. It is about possessive
determiners in Marathi.

Minimal examples:
 1. "tyacha ghoda" = "his horse" (horse is masculine)
 2. "ticha ghoda" = "her horse"
 3. "tyachi gay" = "his cow" (cow is feminine)
 4. "tichi gay" = "her cow"

What these examples show is that the possessive determiners are inflected
according to the gender of both the possessor and the possessed. This is
also true for the number of both in Marathi. (There are three genders and
two numbers.)

Previously, 'tyacha' was being analyzed with the tags ,
which is an issue for structural transfer. We discussed two alternatives:
 1. having XYZ+ch, that is, treating the 'ch' forms as
separate lemmas
 2. having XYZ, that is, making separate tags for
the possessor and the possessed

What is the best way to proceed, with these options or maybe something else?

Shardul C.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] Reminder about PMC Election

[Shardul Chiplunkar]

Dear apertium-stuff members,

This is a reminder about the emails regarding the PMC election that have
been sent out a few days ago, since they may have been missed for some
reason.

If you want to declare yourself as a candidate, the final date to send an
email to the election committee (Bernard, Sushain, and me; email addresses
below) is *Wednesday, 13 December, 23:59 UTC*. If you have been contacted
with a Sourceforge email address, the final date to send an email to the
election committee with your full name, username, and preferred
non-Sourceforge email address is also Wednesday.

Thank you for your attention,

Apertium PMC Election Committee:
Bernard Chardonneau 
Shardul Chiplunkar 
Sushain Cherivirala 
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] easier GCI tasks ?

[Shardul Chiplunkar]

Based on what I've seen of other organizations, I think we could benefit
from 'chains' of tasks. Each task in a chain would require the student to
have completed work equivalent to the previous tasks. The first one or two
tasks in the chain would be beginner tasks, easier than our current
beginner tasks but not as easy as the linked one above (which I think is
too easy).

Chain 1:
 - "Download and compile one Apertium translation pair, and send a
screenshot of trial translations."
 - "Add 200 words to the bilingual dictionary" or "Add 1 lexical transfer
rule"
 - "Add 500 words to the bilingual dictionary" or "Add 10 lexical transfer
rules" or "Write a constrastive grammar" or ...

Chain 2:
 - "Install a few translation pairs from your distribution software
repository (or download and compile if you want to). Fork APy and run it
locally on your computer. Send a screenshot of trial queries." or similarly
for html-tools
 - all the issue-fixing or feature-proposal tasks for APy or similarly for
html-tools
 - tasks which involve modifying or testing with components of both ("Fix
html-tools behavior when APy is down" etc.)

Similar 'chains' could be made for begiak and the lt toolbox tasks. How
does this idea sound?


Shardul C.

On Fri, Dec 1, 2017 at 10:41 AM, Francis Tyers  wrote:

> Wikimedia has this for an GCI beginner task. I think it's a pretty good
> one, but I didn't know before that this was allowed...
>
> https://codein.withgoogle.com/tasks/5103022533246976/
>
> Should we add some tasks like this ?
>
> Fran
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Apertium-stuff mailing list
> Apertium-stuff@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

[Apertium-stuff] Requesting Commit Access for Marathi

[Shardul Chiplunkar]

Hello everybody,

I am Shardul Chiplunkar (SourceForge/GitHub/IRC handle 'shardulc'), a high
school student who has worked with Apertium in the past through the Google
Code-In program. I am currently interested in helping develop Apertium's
Marathi language data and pairs involving Marathi such as mar-hin. For that
purpose, I would like to request commit access.

Thank you,
Shardul C.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff