[wp-meta] [Making WordPress.org] #5555: Introduce deploy keys for SVN
Making WordPress.org
noreply at wordpress.org
Mon Dec 21 14:26:39 UTC 2020
#5555: Introduce deploy keys for SVN
------------------------------+---------------------
Reporter: Clorith | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Plugin Directory | Resolution:
Keywords: |
------------------------------+---------------------
Comment (by Clorith):
Yeah, an automatically generated user was my thought process here as I
suspected there would be limitations in the SVN setup, so that would
basically make it function as today, only that a second committer is
automatically added for a new user that's generated on plugin approval.
I'd say that making it a part of the automated process that happens when a
plugin is approved could be great, here, I'm honestly not sure what the
best approach would be for existing entries though, might need a bit more
thought in that regard. I guess my use of "key" was confusing here, it
would be more "its own user which has a normal password, but since it's a
separate user, it's not tied in to your regular account".
I do remember the mention of the GitHub pull, I see benefits of a WPPD app
to auth, we should find out which approach (between app and action) has
the best route to a MVP, but also which one offers the best flexibility
moving forward.
With an action, it is much easier to open source it, and some may feel
more comfortable with that than an application which they don't know the
inner workings of 🤔
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/5555#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list