[01:38:56] <audiodude>	 is there a way to connect to enwiki_p without being a member of a toolforge tool account?
[01:39:06] <AntiComposite>	 what are you trying to do
[01:39:26] <audiodude>	 the use case is, I want to offer a "dev" environment for my tool, that people can hack on without necessarily becoming part of the project
[01:39:45] <audiodude>	 maybe that's a nonstarter
[01:39:50] <Reedy>	 I think it would be
[01:40:19] <Reedy>	 You might be allowed to have two tools for that, but I'm not sure if there's a pattern of doing that
[01:40:35] <audiodude>	 okay
[01:40:52] <audiodude>	 I just pictured like me telling people about the project and them being able to git clone and try it out without committing
[01:40:55] <Reedy>	 And they'd still need manually adding etc to the -dev project
[01:41:06] <audiodude>	 even if they had to sign up for a toolforge account
[01:41:21] <audiodude>	 and by committing I mean making a commitment, not git commit
[01:41:44] <audiodude>	 hmm, ok
[01:41:56] <Reedy>	 Is the barrier to entry that high for your project?
[01:42:07] <Reedy>	 Maybe focusing your time on reducing that might be more beneficial
[01:42:41] <audiodude>	 no, I just wanted to encourage casual engagement
[01:44:02] <audiodude>	 also from my perspective, if random_wikipedian_1234 wants to try hacking on the tool, do I really want to give him or her write access to our tools database?
[01:44:20] <AntiComposite>	 probably not
[01:44:26] <audiodude>	 which seems to be another argument for the -dev tool
[01:44:29] <audiodude>	 but that seems messy
[01:45:23] <audiodude>	 also I'm probably overblowing the level of interest in this project right? Like there's one person I have in mind and I'm pretty sure I can trust him as a member of the project, if he's so inclined.
[01:45:31] <AntiComposite>	 depending on what your project is though, you might not need any db for most contributions (outside of testing)
[01:45:48] <audiodude>	 really? tell me more
[01:46:11] <audiodude>	 I already have 96% test coverage using a local MySQL test db
[01:46:14] <AntiComposite>	 it all depends on what your project does, which you haven't told us
[01:46:30] <audiodude>	 it's https://toolsadmin.wikimedia.org/tools/id/enwp10
[01:46:47] <audiodude>	 it reads from enwiki_p and builds a record of the quality/importance ratings of articles in WikiProjects
[01:46:47] <Reedy>	 >Creating a toolinfo description is required for new tools and recommended for all tools.
[01:46:50] <Reedy>	 Doesn't really tell us :p
[01:46:51] <audiodude>	 lol
[01:49:16] <AntiComposite>	 but yeah, it sounds to me like you're trying to optimize prematurely
[01:50:02] <AntiComposite>	 audiodude, can I PM you about something?
[01:50:24] <audiodude>	 sure
[17:18:43] <wm-bot>	 !log tools.quickcategories <lucaswerkmeister> deployed db2a7c16ae (Python 3.7, 2020 Kubernetes cluster), includes venv rebuild; tool had apparently been broken before for about half a month
[17:18:45] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.quickcategories/SAL
[22:06:23] <Zppix>	 is anyone in the cloud services team around for a quick pm?