Tsimshian Tribal Council

The Tsimshian Tribal Council was the governing coalition of the band governments of the Tsimshian people in Prince Rupert. In British Columbia, the governments of Canada started engaging in the British Columbia Treaty Process with First Nation bands in the province. Originally the Tsimshian Tribal Council pursued negotiations until late 2005 when the Tsimshian Tribal Council, the organization for treaty negotiations, dissolved amid legal and political turmoil.

This is the disbanded tribal council; for the treaty council see Tsimshian First Nations

Membership
First Nation Number First Nation Name
672 Gitxaala Nation
675 Hartley Bay Indian Band
680 Kitselas First Nation
681 Kitsumkalum First Nation
674 Lax-kw'alaams First Nation
540 Kitasoo/Xaixais First Nation
673 Metlakatla First Nation

History

The governing council was formed in 1988 through the B.C. Society Act to represent several bands of the Tsimshian people. In 1994 after the British Columbia Treaty Process started the Tsimshian Tribal Council started negotiations for a comprehensive treaty agreement. However, in April 2004 the Council disbanded due to internal conflicts.[1] The split centred on a power struggle over Treaty negotiation that became violent and resulted in the RCMP being called to stop what council members called a, "hostile takeover".[2] A new Council the Tsimshian First Nations was formed in December 2004 without the Gitxaala Nation (formerly Kitkatla) and the Lax Kw'alaams First Nation to represent members in the BC Treaty Process.[1]

gollark: Speaking specifically about the error handling, it may be "simple", but it's only "simple" in the sense of "the compiler writers do less work". It's very easy to mess it up by forgetting the useless boilerplate line somewhere, or something like that.
gollark: Speaking more generally than the type system, Go is just really... anti-abstraction... with, well, the gimped type system, lack of much metaprogramming support, and weird special cases, and poor error handling.
gollark: - They may be working on them, but they initially claimed that they weren't necessary and they don't exist now. Also, I don't trust them to not do them wrong.- Ooookay then- Well, generics, for one: they *kind of exist* in that you can have generic maps, channels, slices, and arrays, but not anything else. Also this (https://fasterthanli.me/blog/2020/i-want-off-mr-golangs-wild-ride/), which is mostly about the file handling not being good since it tries to map on concepts which don't fit. Also channels having weird special syntax. Also `for` and `range` and `new` and `make` basically just being magic stuff which do whatever the compiler writers wanted with no consistency- see above- Because there's no generic number/comparable thing type. You would need to use `interface{}` or write a new function (with identical code) for every type you wanted to compare- You can change a signature somewhere and won't be alerted, but something else will break because the interface is no longer implemented- They are byte sequences. https://blog.golang.org/strings.- It's not. You need to put `if err != nil { return err }` everywhere.
gollark: Oh, and the error handling is terrible and it's kind of the type system's fault.
gollark: If I remember right Go strings are just byte sequences with no guarantee of being valid UTF-8, but all the functions working on them just assume they are.

See also

References
  1. "Tsimshian First Nations". Executive Council of British Columbia. 2009. Retrieved July 26, 2009.
  2. Rudy Kelly (November 2005). "Tribal council shut down after years of turmoil". Raven's Eye. Retrieved August 14, 2009.


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.