Librarybase could now do with a project on Phabricator to help with coordination. Could we just get a standard component project with description: "Librarybase is a wikibase installation for storing bibliographic and citation data"
Description
Related Objects
- Mentioned In
- T103700: LOG: Phabricator project creation
Event Timeline
Hi @Tarrow, is there a web page where to find more information about this project, in order to link from the Phabricator project description and allow people find the code base?
librarybase.wmflabs.org is probably the best place to go. It is where the actual wikibase is hosted and is also where we are documenting things. Thanks!
It runs on pretty much vanilla mediawiki and wikibase. There isn't really 'code'; its value is really just the data stored within it. Maybe I shouldn't have asked for a component type project and should have asked for an umbrella (?) but we don't really have distinct subcomponents either (we're using wikibase, and a clone of the wikidata query service as well as some custom scripts for data importing etc.. but these aren't centralised)
Name?: #Librarybase-on-Labs
Description?: A wikibase installation to develop structured bibliographic data and citation data around the citations that appear on Wikipedia.
Without knowing what "Librarybase" is and having projects like Librarization in place, I'd love to make it a bit easier for anybody to not incorrectly file tasks under Librarybase. If that makes sense. (I'm basically copying the Tool-Pageviews and #xTools-on-Labs approach.)
Just wanted to create this (sorry that I dropped the ball on this) but URL seems to be down? :(
502 Bad Gateway
@yuvipanda is reporting that there is a problem with the Labs instance. More information soon.
@Aklapper, will Librarybase's current downtime prevent the creation of a Phabricator project?
@Harej Nope. Just please fix or expand following info:
Project type: Component
Name: Tool-Labs-tools-Librarybase
Project description: Librarybase is a Wikibase installation for storing bibliographic and citation data
Visible To: Public (no login required)
Editable By: All Users
Joinable By: All Users
I guess Librarybase is more suited as an Umbrella than a discrete component.
The issue with the name is that Librarybase is its own Labs instance; it is not on Tool Labs.
Everything else looks fine.
Is it going to have subprojects?
The issue with the name is that Librarybase is its own Labs instance; it is not on Tool Labs.
Aha. I was just following the previous discussion...
Therefore VPS-project-Librarybase.
I changed my mind here and I would simply go for #Librarybase - it's totally fine and we have no strict scheme about "on Labs" vs "on Tool-Labs" etc.
Stole this task from Danny as I still had that tab with data prefilled open anyway...
Requested project VPS-project-Librarybase has been created: https://phabricator.wikimedia.org/project/view/2155/
Please encourage interested people to visit the project and to join the project as members, and to watch the project in order to receive updates!
Recommended practices for project and workboard management in Phabricator are available.
And if for some reason you ever want to rename the project, please check the guidelines first.
@Danny_B: I don't think we have a consistent naming scheme (Labs-project-*) in place, and I assume you prefer to have one. Are the advantages outlined / documented somewhere?