Discussion Forum: All Replies to Message 1465074 |
|
|
| | Author: | Admin_Russell | Posted: | Apr 17, 2024 00:53 | Subject: | Re: Variants Thread - April 16 | Viewed: | 91 times | Topic: | Catalog | |
|
|
BrickLink ID CardAdmin_Russell
|
Location: USA, California |
Member Since |
Contact |
Type |
Status |
May 9, 2017 |
|
Admin |
|
|
BrickLink Administrator |
|
| In Catalog, axaday writes:
| In Catalog, rickcraine writes:
| In Catalog, axaday writes:
| In Catalog, Admin_Russell writes:
I didn't realize 32064b was on the chopping block.
|
Wasn't there that whole controversy with that guy who claimed to have used
it in a "moc on top of a stud so therefore it was useful" even though
it cannot fit on top of a stud
|
32064b could go on a hollow stud. I would have spoken up on it, but I didn't
realize it was on the block.
We definitely could have talked about it on the catalog panel if the catalog
panel had EVER been consulted about this.
|
The catalog panel was informed of this merge project months before it was announced
publicly. But the purpose of the panel is to bring community voice to the development
team, not contribute to catalog policy.
We do address catalog policy when it comes up, but it's definitely a sideline
issue, as are all issues that relate to other BrickLink teams, like Marketplace
and Studio. Panel meetings are not the place to debate proposed variant merges.
The Forum is, and there was plenty of debate and even opportunity for more debate.
| There went a double handful of my catalog work and all the give-a-darn that I
had stockpiled. I think I'll go touch grass and see if it is everything
people talk it up to be.
|
We knew the hardest thing about this project was having to undo some work that
the community had done. The important thing moving forward, though, is that no
one is going to keep investing in that handful of variants that we removed. This
will also force us to consider more closely the addition of variants in the future,
to avoid this happening again.
And, like I said clearly before, we have a complete record of all modern inventory
change requests. They are all preserved in the Forum for those that want to see
what you discovered in your sealed sets. And the vast majority of your work is
still completely intact and helping other members, so let's not paint this
as a total loss.
|
|
|
| | | | | |
| | | | Author: | axaday | Posted: | Apr 17, 2024 05:43 | Subject: | Re: Variants Thread - April 16 | Viewed: | 69 times | Topic: | Catalog | |
|
| In Catalog, Admin_Russell writes:
The important thing moving forward, though, is that no
| one is going to keep investing in that handful of variants that we removed.
|
This is a serious understatement. From now until I don't know when, I'm
not investing in any of the variants.
|
|
| | | | | | | | | |
| | | | | | Author: | Saitobricks.ca | Posted: | Apr 17, 2024 19:57 | Subject: | (Cancelled) | Viewed: | 51 times | Topic: | Catalog | |
|
| (Cancelled) |
|
| | | | | |
| | | | Author: | jennnifer | Posted: | Apr 17, 2024 10:39 | Subject: | Re: Variants Thread - April 16 | Viewed: | 55 times | Topic: | Catalog | |
|
| In Catalog, Admin_Russell writes:
| |
We definitely could have talked about it on the catalog panel if the catalog
panel had EVER been consulted about this.
|
The catalog panel was informed of this merge project months before it was announced
publicly. But the purpose of the panel is to bring community voice to the development
team, not contribute to catalog policy.
|
Unless there was a meeting I missed somehow, I do not recollect that we were
informed of this project or asked to give any input or suggestions. There was
a brief mention that there was a variant project but no details or timetables
were ever given. Considering that many people on the Panel were among those who
expressed surprise and dismay when this was all introduced, I would think that
those meetings would indeed have been an ideal place to breach the subject with
the members at large.
| We do address catalog policy when it comes up, but it's definitely a sideline
issue, as are all issues that relate to other BrickLink teams, like Marketplace
and Studio. Panel meetings are not the place to debate proposed variant merges.
The Forum is, and there was plenty of debate and even opportunity for more debate.
|
Perhaps it was not the place to discuss the exact specifics of each part being
looked at. But it would have been good to know how the project would be introduced
and carried out. We are supposed to be looking out for the community and sharing
out expertise after all.
Thanks,
~Jen
|
|
|
| | | | | | | | | |
| | | | | | Author: | Stellar | Posted: | Apr 17, 2024 11:21 | Subject: | Re: Variants Thread - April 16 | Viewed: | 66 times | Topic: | Catalog | |
|
| In Catalog, jennnifer writes:
| In Catalog, Admin_Russell writes:
| |
We definitely could have talked about it on the catalog panel if the catalog
panel had EVER been consulted about this.
|
The catalog panel was informed of this merge project months before it was announced
publicly. But the purpose of the panel is to bring community voice to the development
team, not contribute to catalog policy.
|
Unless there was a meeting I missed somehow, I do not recollect that we were
informed of this project or asked to give any input or suggestions. There was
a brief mention that there was a variant project but no details or timetables
were ever given. Considering that many people on the Panel were among those who
expressed surprise and dismay when this was all introduced, I would think that
those meetings would indeed have been an ideal place to breach the subject with
the members at large.
|
The only thing I recollect is talking about the need to tackle the variants on
the catalog, but nothing specific, I must have missed it too.
|
| We do address catalog policy when it comes up, but it's definitely a sideline
issue, as are all issues that relate to other BrickLink teams, like Marketplace
and Studio. Panel meetings are not the place to debate proposed variant merges.
The Forum is, and there was plenty of debate and even opportunity for more debate.
|
Perhaps it was not the place to discuss the exact specifics of each part being
looked at. But it would have been good to know how the project would be introduced
and carried out. We are supposed to be looking out for the community and sharing
out expertise after all.
Thanks,
~Jen
|
|
|
|
| | | | | | | | | | | | | |
| | | | | | | | Author: | axaday | Posted: | Apr 17, 2024 20:35 | Subject: | Re: Variants Thread - April 16 | Viewed: | 75 times | Topic: | Catalog | |
|
| In Catalog, Stellar writes:
| In Catalog, jennnifer writes:
| In Catalog, Admin_Russell writes:
| |
We definitely could have talked about it on the catalog panel if the catalog
panel had EVER been consulted about this.
|
The catalog panel was informed of this merge project months before it was announced
publicly. But the purpose of the panel is to bring community voice to the development
team, not contribute to catalog policy.
|
Unless there was a meeting I missed somehow, I do not recollect that we were
informed of this project or asked to give any input or suggestions. There was
a brief mention that there was a variant project but no details or timetables
were ever given. Considering that many people on the Panel were among those who
expressed surprise and dismay when this was all introduced, I would think that
those meetings would indeed have been an ideal place to breach the subject with
the members at large.
|
The only thing I recollect is talking about the need to tackle the variants on
the catalog, but nothing specific, I must have missed it too.
|
| We do address catalog policy when it comes up, but it's definitely a sideline
issue, as are all issues that relate to other BrickLink teams, like Marketplace
and Studio. Panel meetings are not the place to debate proposed variant merges.
The Forum is, and there was plenty of debate and even opportunity for more debate.
|
Perhaps it was not the place to discuss the exact specifics of each part being
looked at. But it would have been good to know how the project would be introduced
and carried out. We are supposed to be looking out for the community and sharing
out expertise after all.
Thanks,
~Jen
|
|
He only claims that we were informed of the project and that is the truth. We
were told that it existed.
|
|
|
|
|
|
|