Sorry just getting back to this now... Thanks for the redmine tickets, and
also for the questions. I wrote some on the tickets, including the desire
for the sqlite database on the sqlite ticket here:
https://pulp.plan.io/issues/3359
re: the confusion about the class/function names in pulp_file.
>
> - a database picture would be helpful to show off the data layer objects,
> foreign keys, and attributes.
>
>
> Yes! We really need to publish an ER diagram. I'm overdue on an action
> item to produce one.
>
https://pulp.plan.io/issues/3369
totally missed this one
--
milan
Thanks for providing this feedback, Brian.! Good stuff.
On 02/12/2018 03:57 PM, Brian Bouterse wrote:
At the Foreman Construction day [0] last Wednesday, we had our first
code focused plugin writer's workshop. About 6 people were actively
engaged as we talked through the plugin API, example
Brian,
thanks for the summary!
I took the liberty to go thru this list and file Redmine issues where I
found the description to be straightforward; please see links inline.
My intention is to be able to track and triage these so that the invaluable
plug-in writer feedback isn't lost.
Cheers,
You forgot to mention the huge amount of fun, we had while debugging
the designated pulp3 development environment.
But i agree, that focussing on one environment (that fits all,
including core and plugin development) sounds reasonable. And the
vagrant setup with ansible roles sounds like my first
