ZCOs gives inputs to FoH
Source: The Sangai Express

Imphal, July 12 2024: Welcoming Federation of Haomee's (FoH) proposed plan to erect a monolith inscribed with the names of all indigenous tribes of Manipur, Zeliangrong Civil Organisations (ZCOs) has advised FoH to inscribe Zeliangrong and to mention Zeme, Liangmai, Rongmei and Kabui in brackets instead of segregating them as separate and distinct tribes.

As per a press release issued by the Media and Publicity Cell, ZCOs, the tableau design of the monolith has been widely circulated in various WhatsApp groups where the list of indigenous tribes and communities have been mentioned, namely, Aimol, Anal, Chiru, Inpui, Kabui, Kharam, Khoibu, Thangal, Koireng, Kom, Lamkang, Liangmai, Mao, Maram, Maring, Meetei/Meitei, Moyon, Monshang, Poumai, Purum, Rongmei, Tangkhul, Tarao, Zeme.

In this regard, ZCOs, comprising of Zeliangrong Baudi, Zeliangrong Youth Front and Zeliangrong Students' Union, has urged FoH to clearly identify the genuine names and numbers of indigenous tribes prior to concretization of their plan in order to avoid creation of more confusion for posterity.

ZCOs maintained that the Zeme, Liangmai, Rongmei and Kabui groups have one origin with a history of undisputed common ancestry.

It urged FoH to not be confused or misled by "misinformation and manipulative Government tribes' recognition orders, neither swayed by momentary emotion nor influenced by the wave of politics" .

Any attempt to fragment Zeliangrong by relying on the basis of misinformation and fabrication will be construed as anti-indigenous people's interest, said the ZCOs statement.

Pointing out that erection of a monolith inscribed with all the indigenous tribes of Manipur will remain as a historic monument, ZCOs remarked that the monument should not be the memorial pillar to dilute and confuse the history of indigenous tribes of Manipur.

ZCOs has appealed to all responsible individuals and particularly leaders of different organizations including the Government to be part of the error correction process instead.

Comment