As the backlog has grown ridiculously long, I have closed the proposal:
https://meta.wikimedia.org/w/index.php?title=Proposals_for_closing_projects%2FClosure_of_Lak_Wikipedia_3&diff=29720521&oldid=29549856

Am Fr., 12. Sept. 2025 um 22:50 Uhr schrieb MF-Warburg <
[email protected]>:

> Any other comments?
>
> Am Mi., 5. März 2025 um 13:52 Uhr schrieb MF-Warburg <
> [email protected]>:
>
>> I tend to think: it's still the same, so it still shouldn't be closed -
>> namely, a very low level activity but it exists and the wiki seems to be
>> somewhat actively monitored.
>>
>> Am Mo., 24. Feb. 2025 um 12:44 Uhr schrieb Sotiale Wiki <
>> [email protected]>:
>>
>>> I would like to reevaluate this at this point.
>>> It has been about 4 months since the previous point. If it is still the
>>> same, it would be better to close this project.
>>>
>>> Sotiale
>>>
>>> 2024년 10월 7일 (월) 오후 2:57, Sotiale Wiki <[email protected]>님이 작성:
>>>
>>>> I agree with you. This is different from pihwiki, where I previously
>>>> supported closure.
>>>> There is currently no active reason to close this project, and no
>>>> evidence that consensus has been reached.
>>>>
>>>> Sotiale
>>>>
>>>> 2024년 10월 7일 (월) 오전 1:25, MF-Warburg <[email protected]>님이 작성:
>>>>
>>>>>
>>>>> https://meta.wikimedia.org/wiki/Proposals_for_closing_projects/Closure_of_Lak_Wikipedia_3
>>>>>
>>>>> Previously I proposed approving the closure and obtained the Board's
>>>>> non-veto in April 2023. For better or worse, the closure was not
>>>>> implemented. Now the project is not inactive, so the proposal should be
>>>>> rejected.
>>>>> _______________________________________________
>>>>> Langcom mailing list -- [email protected]
>>>>> To unsubscribe send an email to [email protected]
>>>>>
>>>> _______________________________________________
>>> Langcom mailing list -- [email protected]
>>> To unsubscribe send an email to [email protected]
>>>
>>
_______________________________________________
Langcom mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to