Pagina in lingua inglese

Differenze tra le versioni di "Empowering Italian GLAMs/Tech evaluations"

Da Wikimedia Italia.
Jump to navigation Jump to search
(+pagina info da Discussione:Server)
 
(+info)
 
(23 versioni intermedie di 2 utenti non mostrate)
Riga 1: Riga 1:
Informazioni sul tool per [[Empowering Italian GLAMs]].
+
{{Inglese}}
 +
Technical documentation about the tool related to [[Empowering Italian GLAMs]].
  
== Specifiche ==
+
Please read also [[phabricator:T320369]] ("Help evaluating Toolforge or VPS to empower Italian GLAMs").
  
;Dominio: Ancora da identificare.
+
== Toolforge administrators ==
  
; Accesso riga di comando:Non dovrebbe essere necessario.
+
https://toolsadmin.wikimedia.org/tools/id/glams
  
; Spazio richiesto: 30G (1000 musei, 20 foto, 1.5M/foto)
+
== Toolforge domain ==
; Dipendenze
 
: * PHP che esegue comandi Python
 
: * MySQL
 
: * Python
 
  
;Server disponibili:
+
Our Toolforge domain is very short. If you think this should not have happened, please contact us. Anyway this was more or less our attempts:
* lessema: abbastanza spazio ma sarebbe dedicato a CiviCRM
 
* <s>beta: non è nostro</s>
 
* <s>delta: non è nostro</s>
 
* <s>epsilon: non è nostro</s>
 
* <s>horror: è dedicato ai backup</s>
 
* <s>intreccio: poco spazio</s>
 
* <s>manoscritto: poco spazio, ed è dedicato a ZNUNY</s>
 
* oppure nuovo server - Il fornitore attuale {{Fornitore link|vh}} costa circa max. 400€ anno a server, backup automatici compresi - da allocare
 
  
== Gruppo di lavoro ==
+
* <code><s>https://musei-su-wikipedia.toolforge.org/</s></code>
 +
*: Problem: this username is forbidden by Toolforge since it contains "wikipedia"
 +
* <code><s>https://musei-su-itwiki.toolforge.org/</s></code>
 +
*: Opinion: too long and "itwiki" is too weird (by iopensa)
 +
* <code><s>https://empowering-italian-glams.toolforge.org</s></code>
 +
*: Opinion: too long and weird (by iopensa)
 +
* <code><s>https://italian-glam.toolforge/</s></code>
 +
*: Opinion: too long and weird (by iopensa)
 +
* <code>https://glams.toolforge.org/</code>
 +
*: Opinion: weird but very short: wooow cute! (by iopensa)
 +
*: Opinion: ASD (by Valerio Bozzolan)
  
;Sviluppatori:
+
In short, we picked "glams" since "musei-su-wikipedia" was not available. If you're upset about "glams," I'm sorry. Domains have always been undemocratic.
* [[Utente:Adert]]
+
 
 +
== Requirements ==
 +
{{Tracked|T320369}}
 +
 
 +
;Considerations:
 +
 
 +
* [[phabricator:T320369]] - Help evaluating Toolforge or VPS to empower Italian GLAMs (Wikimedia IT)
 +
 
 +
; Command line access: Should be not required.
 +
 
 +
; User storage needed: 40G (1000 musei, 20 foto, 2M/foto)
 +
; Dependencies
 +
* PHP <s>(executes Python commands)</s>
 +
* MySQL database
 +
* <s>Python</s>
 +
 
 +
;Available servers:
 +
* <s>Cloud VPS - not needed</s>
 +
*: [[m:wikitech:Wikitech:Cloud Services Terms of use]]
 +
* <s>server from current provider {{Fornitore link|vh}} - average cost max. 400€ / server, automated backups already included</s>
 +
* <s>lessema: enough storage but it's dedicated to CiviCRM - not enough separation</s>
 +
* <s>beta: not owned by WMIT</s>
 +
* <s>delta: not owned by WMIT</s>
 +
* <s>epsilon: not owned by WMIT</s>
 +
* <s>horror: dedicated to backups - not enough separation</s>
 +
* <s>intreccio: not enough storage</s>
 +
* <s>manoscritto: not enough storage - not enough separation with ZNUNY</s>
 +
* <s>toolforge: not enough storage</s> - https://t.me/wmcloudirc/44175 (this comment was super-seeded)
 +
* Toolforge: OK - [[phabricator:T320369]]
 +
 
 +
== FAQs ==
 +
 
 +
; About unclear copyright status files on Wikimedia Cloud servers
 +
<pre>
 +
<bozzy> there is a person who verifies a scanned piece of paper in which a museum manager authorizes the release in free license, before uploading on Commons.
 +
<bozzy> This way the Commons community does not receive an avalanche of problematic data. We felt it was more respectful to them.
 +
[29/08/22 17:10]
 +
<taavi> you can't store material with unclear copyright status on WMCS either..
 +
</pre>
 +
 
 +
Answer: This has since been clarified, the materials are released by the museums in bona-fide with a free license, the problem is that the museum could be not so skilled about copyright, so it's better to double-check before uploading them to Wikimedia Commons.
 +
 
 +
; About uploading directly on Commons
 +
<pre>
 +
<bozzy> The tool will be a sort of "image uploader". Kind of "pre-Commons" for a GLAM-related project in a specific country.
 +
[29/08/22 17:00]
 +
<bd808_> Why not upload to commons and then mark the "unuseful" things for deletion? Commons will have more storage and better performance than almost any Cloud VPS project.
 +
<bd808> https://commons.wikimedia.org/wiki/Commons:Volunteer_Response_Team is exactly for things like reviewing and validating image releases as well. I'm not saying I know enough to say that there is no need for a staging process, but this all sounds like things that the community knows how to deal with.
 +
</pre>
 +
 
 +
Answer: it's too difficult to train 3000 museums to upload something in Wikimedia Commons without doing mistakes. The community should not fix our import mistakes. It's better to do things in the good way, with a simple and dedicated wizard, oriented for our goals.
 +
 
 +
== Repository ==
 +
 
 +
https://gitlab.wikimedia.org/repos/wikimedia-it/wmit-empowering-italian-glams
 +
 
 +
== Tech Team ==
 +
 
 +
;Original author:
 +
* [[Utente:Adert]] (consultant)
 +
 
 +
;Code sprint and code review
 +
* [[Utente:Mte90]] (consultant)
 +
 
 +
;Repository maintainer
 +
* [[Utente:Valerio Bozzolan]] (volunteer)

Versione attuale delle 12:35, 12 ott 2022

Technical documentation about the tool related to Empowering Italian GLAMs.

Please read also phabricator:T320369 ("Help evaluating Toolforge or VPS to empower Italian GLAMs").

Toolforge administrators

https://toolsadmin.wikimedia.org/tools/id/glams

Toolforge domain

Our Toolforge domain is very short. If you think this should not have happened, please contact us. Anyway this was more or less our attempts:

In short, we picked "glams" since "musei-su-wikipedia" was not available. If you're upset about "glams," I'm sorry. Domains have always been undemocratic.

Requirements

Considerations
Command line access
Should be not required.
User storage needed
40G (1000 musei, 20 foto, 2M/foto)
Dependencies
  • PHP (executes Python commands)
  • MySQL database
  • Python
Available servers
  • Cloud VPS - not needed
    m:wikitech:Wikitech:Cloud Services Terms of use
  • server from current provider 💼 vh - average cost max. 400€ / server, automated backups already included
  • lessema: enough storage but it's dedicated to CiviCRM - not enough separation
  • beta: not owned by WMIT
  • delta: not owned by WMIT
  • epsilon: not owned by WMIT
  • horror: dedicated to backups - not enough separation
  • intreccio: not enough storage
  • manoscritto: not enough storage - not enough separation with ZNUNY
  • toolforge: not enough storage - https://t.me/wmcloudirc/44175 (this comment was super-seeded)
  • Toolforge: OK - phabricator:T320369

FAQs

About unclear copyright status files on Wikimedia Cloud servers
<bozzy> there is a person who verifies a scanned piece of paper in which a museum manager authorizes the release in free license, before uploading on Commons.
<bozzy> This way the Commons community does not receive an avalanche of problematic data. We felt it was more respectful to them.
[29/08/22 17:10]
<taavi> you can't store material with unclear copyright status on WMCS either..

Answer: This has since been clarified, the materials are released by the museums in bona-fide with a free license, the problem is that the museum could be not so skilled about copyright, so it's better to double-check before uploading them to Wikimedia Commons.

About uploading directly on Commons
<bozzy> The tool will be a sort of "image uploader". Kind of "pre-Commons" for a GLAM-related project in a specific country.
[29/08/22 17:00]
<bd808_> Why not upload to commons and then mark the "unuseful" things for deletion? Commons will have more storage and better performance than almost any Cloud VPS project.
<bd808> https://commons.wikimedia.org/wiki/Commons:Volunteer_Response_Team is exactly for things like reviewing and validating image releases as well. I'm not saying I know enough to say that there is no need for a staging process, but this all sounds like things that the community knows how to deal with.

Answer: it's too difficult to train 3000 museums to upload something in Wikimedia Commons without doing mistakes. The community should not fix our import mistakes. It's better to do things in the good way, with a simple and dedicated wizard, oriented for our goals.

Repository

https://gitlab.wikimedia.org/repos/wikimedia-it/wmit-empowering-italian-glams

Tech Team

Original author
Code sprint and code review
Repository maintainer