Wikilambda talk:Wikilambda/Tasks
Abstract Wikipedia & Wikidata
Task P2.3: Abstract Wikipedia Create a new namespace in Wikidata and allow Content to be created and maintained there.
I don't think having abstract Wikipedia within a Wikidata namespace is a good idea. Abstract Wikipedia has different concerns when it comes to notability then Wikidata. It would be better if it has it's own domain, policies and admins. ChristianKl ❪✉❫ 22:21, 17 May 2020 (UTC)
Script error: No such module "Reply to". Wouldn't the notability policy of Wikidata always be more inclusive than of any Wikipedia, including the Abstract Wikipedia content? --denny (talk) 01:25, 18 May 2020 (UTC)
- @Denny: That's the point Wikidata's notability policy is more inclusive then what would be good for Abstract Wikipedia. As a result there will be a problem when Abstract Wikipedia tries to reuse Wikidata's notability policy. I don't think writing the policy for Abstract Wikipedia would be a good job for Wikidata. I think it needs it's own jurisdiction. ChristianKl ❪✉❫ 21:05, 19 May 2020 (UTC)
- @Denny: That's the point Wikidata's notability policy is more inclusive then what would be good for Abstract Wikipedia. As a result there will be a problem when Abstract Wikipedia tries to reuse Wikidata's notability policy. I don't think writing the policy for Abstract Wikipedia would be a good job for Wikidata. I think it needs it's own jurisdiction. ChristianKl ❪✉❫ 21:05, 19 May 2020 (UTC)
Script error: No such module "Reply to". Ah, I understand your point. Because that would, for any wiki that does implicit integration, mean they would transfer their decision on whether to have an article on a topic to Wikidata, instead of a new project that would start fresh to make that decision.
- We have the whole first project year to decide whether Abstract Wikipedia should be part of Wikidata or not, so I don't think we should decide it now, but why do you think it would not be a good idea to leave this decision to the Wikidata community? I don't really see the arguments of why a new project or Wikilambda would be better places. --denny (talk) 21:43, 19 May 2020 (UTC)
- I don't have a problem with doing the decision via a Wikidata RfC, as a Wikidata Admin I would however surprised if the RfC ends up resulting in Wikidata wanting to be the place for managing Abstract Wikipedia.
- Abstract Wikipedia likely wants to write their policies with Wikilambda, which needs specific skills most in the Wikidata community won't have and won't be interested in.
- It's very unlikely that EnWiki will display any free text from Abstract Wikipedia in the next ten years. It's still good to have those articles on a website people can find via Google. ChristianKl ❪✉❫ 18:40, 20 May 2020 (UTC)
- We have the whole first project year to decide whether Abstract Wikipedia should be part of Wikidata or not, so I don't think we should decide it now, but why do you think it would not be a good idea to leave this decision to the Wikidata community? I don't really see the arguments of why a new project or Wikilambda would be better places. --denny (talk) 21:43, 19 May 2020 (UTC)
Script error: No such module "Reply to". Writing policies with Wikilambda is probably a bit further away than writing content (but a pretty neat idea, in fact for all the multilingual projects, including Wikidata, Meta, and Commons, eventually!)
- Having an RfC on Wikidata within the first year of the project is a good idea, to decide about whether the Content should be stored in Wikidata or not. I think it is a good idea, and you gave enough reasons that warrant a wider discussion. I made two changes to the proposal to capture this. --denny (talk) 22:39, 24 May 2020 (UTC)