Hi All,
Apart from the major task to write a Readme... ;-)
- We had some files encoded with CRLF, maybe there are still others?
- We have a lot of mixed indentation (spaces+tabs) that produce
warnings with newer compilers.
- We still have a big amount of German comments that need to be translated.
- We have a vim modeline in some files, shouldn't we use them more?
- ...
I really don't know where to stop here!
Before we talk about a timeline, let's do the basic tasks... A
"cleaner" source code may also attract volunteers/developers.
What do others think?
Regards,
Matthias
Am 24.05.23 um 07:24 schrieb Peter Kovacs:
> Hi All,
>
> Am 23.05.23 um 23:43 schrieb Matthias Seidel:
>> Hi Arrigo,
>>
>> Am 23.05.23 um 22:27 schrieb Arrigo Marchiori:
>>> Hello Matthias, All,
>>>
>>> On Sat, May 20, 2023 at 05:01:36PM +0200, Matthias Seidel wrote:
>>>
Hi all,
Am 20.05.23 um 12:17 schrieb Peter Kovacs:
> Am 20.05.23 um 10:10 schrieb Arrigo Marchiori:
>> Hello All,
>>
>> On Thu, Apr 27, 2023 at 10:49:53PM +0200, Matthias Seidel wrote:
>>
>>> Hi Peter,
> [...]
>>> After all, we are here to maintain and develop OpenOffice...
>> Isn't the "Help Wanted" page already a good list?
>> https://cwiki.apache.org/confluence/display/OOOUSERS/Help+Wanted
>>
>> It is not in the form of a roadmap, but it already contains a lot of
>> content, well structured.
> I did not have this page on my mind. I have various points not noted,
> and I would not rate the difficulties of those.
>>> The difficulty rating is a way to help newcomers understand what kind
>>> of task they should start with.
>>>
>>> Tasks whose difficulty is hardly estimated could go into an "Undecided
>>> difficulty" list... ;-)
>>>
> For example Damjan has written a patch, for getting rid of expat. but
> we need to implement a small part. However
>
> the patch is on the list but not as PR or in code.
>>> This sounds ``very challenging'' to me ;-)
>
> Damjan wrote he did the hard part. So why do you estimate very
> challenging?
>
> I assume because it is unclear what needs to be exactly done. At least
> this is my issue most of the time.
>
> If we could note what is the topic to work on, and how it needs to be
> resolved it becomes much easier, even if the plan has flaws.
>
> Also i keep loosing track what we need to finish. Or what issues can
> be combined.
>>>
>>> [...]
>> ...and just because we are discussing README.md I would
>> appreciate if
>> someone added it to the AOO41X and AOO42X branches! They are
>> worth at
>> least a minimal description...
> also +1
I added a short description at least for AOO41X now.
>>> Thank you!
>>>
>>> While re-reading my own paragraph above, I think it sounded
>>> polemical. This was not my intention, I apologize. My intention was to
>>> ask for something I did not think I could do very well.
>> No problem!
>>
>> In fact I always wanted to add a Readme and never really did it.
>>
>> But I have no idea for AOO42X, this is our "AOO Forever" branch. ;-)
>>
>> Maybe someone else has an idea?
> i hope i find time soon :(
>>
>> Regards,
>>
>> Matthias
>>
>>> Best regards,
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
smime.p7s
Description: S/MIME Cryptographic Signature
