5

In Should we dissolve the smart-contracts tag? Joris did excellent work to burninate the smart-contracts tag:

The tags contract-design, contract-development, contract-invocation and contract-debugging should jointly cover most usage.

All uses of the smart-contracts tag are retagged. Now we need to figure out what to do with the contracts synonym and smart-contracts itself.

He was able to retag everything appropriately, and everyone benefits from a more precise tag.

Should we put in a request to blacklist the smart-contracts tag ? How should we make tag blacklist requests?

4
  • From the link you posted: There are a lot of burninate-requests posted to various meta sites that are... To put it gently... A complete and utter waste of everyone's time. :-P
    – q9f
    Commented May 20, 2016 at 21:50
  • @5chdn We actually burninated already in the past, so need to do step2, 3... of meta.stackexchange.com/questions/239189/…
    – eth Mod
    Commented May 20, 2016 at 22:07
  • Ok, we are in step #3 then. So let's use this thread to re-evaluate why the tag should be disallowed. And if there is consensus.
    – q9f
    Commented May 20, 2016 at 22:15
  • I edited the question to reflect we are in step3. Thanks
    – eth Mod
    Commented May 20, 2016 at 22:32

1 Answer 1

Reset to default
3

Yes it is too generic, and all the technical aspects are well covered by the other tags. So I can see why this one should be buried.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .