Talk:ESEAP Hub Charter
Add topicThe ESEAP Hub Charter is now open for discussion.
[edit]The ESEAP Preparatory Council enjoins the ESEAP community at large to express its views, comments and suggestions for the ESEAP Hub Charter.
General point: Where an article has a number of distinct sub points it would be good to have numbering for each sub item so we can easily identify and suggest changes.
Article 4.1
[edit]4.1.1
- The Regular Congress Meeting shall be convened during the annual ESEAP conference.
This is too prescriptive - it should just be annually (if that is the frequency intended). It could be during the conference but this may not always be possible, convenient or strategic. 4.1.2 - Unnecessary if 4.1.1 is changed AmandaSLawrence (talk) 06:08, 14 April 2024 (UTC)
4.1.3 currently:
- The ESEAP Congress shall decide the date of the ESEAP conference.
suggest:
- The ESEAP Congress shall decide the date and location of the ESEAP conference based on an expression of interest from within the ESEAP region
- The ESEAP council is to convene a sub-committee of members without a COI to review every EOI
- Following the review the two best options are to be put to the whole community for a final decision
The choice of location and date can have many influences, it should be open not only to affiliates but to partner organisations like GLAMs, and to adhoc communities based in individual cities as many of our communities are not situated on the home island of the affiliate, and significant distance from the affiliates leadership. Ideally having an affiliate to co-host the event is a significant advantage but that shouldn't deny communities from being considered. Gnangarra (talk) 01:25, 27 March 2024 (UTC)
- It has been customary that an affiliate or a community would signify first its intention of hosting a regional conference. The draft Charter states when should be the Regular Congress Meeting and it is during the annual ESEAP conference. It would be better to leave the selection of the date to the COT. We can also add that anyone in the Congress should waive from joining committees in the conference or being part of the COT to give others an opportunity to promote participation and any avoid conflict of interest. The ESEAP Congress should only decide for the date of the Regular Meeting during the ESEAP conference, and not the date of the conference itself. Last year's Wikimania venue selection encouraged participation among the stakeholders and not just to a group of representatives. Any ESEAP community members had a chance to participate in choosing the venue from the two options given by the COT. Once we have a ESEAP Congress, more people will be given the opportunity to participate in the process of short-listing the candidates for the whole ESEAP community to decide. -Filipinayzd (talk) 12:42, 28 March 2024 (UTC)
- good point it has always been the whole communities choice Gnangarra (talk) 13:11, 28 March 2024 (UTC)
Article 1.1
[edit]currently:
- to create opportunities for cooperation in the region...
Suggest
- to create opportunities for growth of new communities, cooperation in the region...
Specifically stating that supporting the growth, development, formation of new communities should be an expressed part of ESEAPs function, this is especially import as the majority of our region doesnt have a recognised affiliate. Gnangarra (talk) 01:32, 27 March 2024 (UTC)
Chapter 3 Organization, Function and Authority
[edit]Suggest a rename to Chapter 3 Leadership: ESEAP Council, and Congress. As thissection is clearly about the internal structure of the HUB Gnangarra (talk) 01:37, 27 March 2024 (UTC)
Chapter 4 Meetings
[edit]This a bit confusing as it about internal congress meetings as such a subset of Chapter 3 rather than a focus on the ESEAP community ie co-ordination of monthly public meetings, events, and conferences. Its should also include reporting and recording of activities Gnangarra (talk) 01:46, 27 March 2024 (UTC)
Missing
[edit]There is nothing about COI in any of the chapters, nothing about dispute and mediation of any kind. Also nothing about suspension of Affiliate seat, Article 3.5.3 allows for WMF to exclude someone, but there is no ability of ESEAP Congress to reject anyone, there should be something to give Congress the power to collectively remove or deny a representative. Gnangarra (talk) 02:11, 27 March 2024 (UTC)
Article 3.6
[edit]current:
- Members of the Council are elected from among the ESEAP Congress members; and shall remain members of the Congress
Suggest
- Members of the Council are independently elected by the ESEAP community; and can not remain members of the Congress once elected
- Council members can not be employees or contractors of an Affiliate, The Wikimedia Foundation, or any other associated organisation
Council needs to make decisions that are in the best interest of the community, they can not do that while being a member of the Congress subject to them being removed by Congress or their Affiliate(if in a representative seat). A person can not represent the ESEAP community and the Affiliate, nor should paid employees of an Affiliate be members of the Council as they will have a perpetual Conflict of Interest in effect a Sword of Damocles ( the imminent and ever-present peril faced by those in positions of power) to act in the interest of their employer. Gnangarra (talk) 04:42, 27 March 2024 (UTC)
Pasal 2.2
[edit]Wikimedia core free-knowledge projects: Recognized administrators, subjected to Article 2.3, of Wikimedia core free-knowledge projects.
Mengapa hanya pengurus yang dapat mewakili proyek-proyek Wikimedia? RamzyM (talk) 06:41, 27 March 2024 (UTC)
- This is a good point @RamzyM. Thanks. --Filipinayzd (talk) 11:57, 28 March 2024 (UTC)
- If I understand it correctly, for an individual to run for a seat in the Congress, this Charter draft says that one needs to be an on-wiki administrator and be allowed to do so by the Council. Is the first condition necessary? Assuming the Council has a reasonable and not too strict set of criteria, preferably a published one, I think passing the Council's preliminary vetting is enough. I'd expect a reasonable amount of online community experience will be checked there. whym (talk) 06:28, 21 July 2024 (UTC)
Peran dan tanggung jawab Hub
[edit]Tahun lalu saya memberikan masukan mengenai peran dan tanggung jawab ESEAP Hub (Talk:ESEAP_Hub/Roles_and_Responsibilities_Document#Personal_feedback). Apakah ada alasan tertentu mengapa tidak ada sama sekali penjelasan mengenai apa yang akan dilakukan oleh ESEAP Hub secara konkrit pada dokumen ini? RamzyM (talk) 06:46, 27 March 2024 (UTC)
- I remember the comments you provided which made me gave my insights however there was no more discussion followed in the talk page. Roles and Responsibilities can be incorporated here. -Filipinayzd (talk) 08:02, 31 March 2024 (UTC)
Bahasa resmi
[edit]Dengan bahasa apa ESEAP Hub melakukan kerja-kerjanya? RamzyM (talk) 06:48, 27 March 2024 (UTC)
- There is no mention about an official language but English is the de facto and [a] lingua franca of the region. Although having only English as an official language will put many communities in a disadvantage position specially in high level discussions. Translation is encouraged and is necessary in a multilingual organization like ESEAP. I understood your question using Google translate so using our own language should not be a hindrance in communication among the stakeholders. --Filipinayzd (talk) 12:05, 28 March 2024 (UTC)
- Likwise with google, ESEAP needs to have translators they can turn to for events or meetings. English has been the default/de facto there is no one common language by settting an official language and discourage participation even deny access much better if we can adjust on an as needed basis. Gnangarra (talk) 11:00, 31 March 2024 (UTC)
Article 5.2
[edit]"The following constitute the funding sources of" of what exactly? RXerself (talk) 15:52, 1 April 2024 (UTC)
ESEAP Conference 2024 attendees
[edit]The list of participants is out and can be found under ESEAP Conference 2024/Demographics. --Filipinayzd (talk) 09:40, 17 April 2024 (UTC)