Re: [bug-gtypist] Converting legacy double spaces convention to modern single space after sentence (patch)

[Felix Natter]

geoffroy <address@hidden> writes:

hi geoffroy,

> I've never maintained a project before, but I feel gtypist could be an
> interesting learning/first maintenance project? what is needed to
> maintain the project?

Thanks for your interest. You need some C and git knowledge,
but both can be learned as you go :-)

Furthermore, there are a few processes like creating and announcing
releases and responding to bug reports (often simple changes to
lessons).

I am willing to help you with each of these :-)

Cheers and Best Regards,
Felix

>
> On April 1, 2018 9:00:27 AM GMT-06:00, Felix Natter <address@hidden> wrote:
>>Michał Parkoła <address@hidden> writes:
>>
>>> On Sat, Mar 17, 2018 at 11:25 AM, Felix Natter <address@hidden>
>>wrote:
>>>
>>>     Michał Parkoła <address@hidden> writes:
>>>     > I like the simplicity and availability of gtypist on almost
>>>     > any
>>terminal-enabled device, but I am not a fan of learning the legacy
>>double space method, so
>>>     I've
>>>     > tweaked the course files to remove it.
>>>     >
>>>     > Attached is a patch converting double spaces to single spaces
>>(along with the instructions, where relevant).
>>>     >
>>>     > If you agree with this change I will also go through the other
>>lessons.
>>>    
>>>     The question is whether this should be done programatically on
>>startup,
>>>     i.e. with --double-spaces option (default=off), or, as you
>>proposed,
>>>     statically.
>>>
>>> I know of no modern context where double spaces are appropriate. I'd
>>just change the default/official tutorial to single spaces and if
>>someone does want to
>>> experience the historical version he can easily get them online.  
>>>
>>>     Unfortunately, GTypist (2.10) currently has no maintainer. If
>>anyone
>>>     wants to step up, I will be glad to help.
>>>
>>> In the absence of an official maintainer is there any way to decide
>>on changes? Who has the commit rights?
>>
>>I think the next maintainer shall decide this. In 2.10 (master) we
>>have the problem that Tim started to use gengetopt with i18n
>>enhancements, which was never finalized, so this is blocked (probably
>>we want to revert to the normal getopt).
>>
>>Is there anybody on this list who wants to take over? I promise to
>>help, and it's not much work :-)
>>
>>Cheers and Best Regards,
>>-- Felix Natter debian/rules!
>>
>>_______________________________________________ bug-gtypist mailing
>>list address@hidden
>>https://lists.gnu.org/mailman/listinfo/bug-gtypist

-- 
Felix Natter debian/rules!