From: "Michael Honkoop" <administrator@comsolve.nl>
To: <pve-devel@lists.proxmox.com>
Subject: [pve-devel] intro'ing myself
Date: Sat, 05 Dec 2020 00:47:22 +0100 [thread overview]
Message-ID: <5FCACA8A02000088000040E7@mail.comsolve.nl> (raw)
In-Reply-To: <5FCACA8A02000088000040E7@mail.comsolve.nl>
Hi all,
First of all nice to meet you,
As both a new participant on the list aswell as someone who is trying to step in/up/learn-by-doing i expect my future posts to contain a lot of questions and struggles trying to find a/the structure.
My (personal) goal is to enhance skills and produce a working oauth extension, which i have seen was already requested back in 2017.
As PVE as product means multiple disciplines i hope i can be directed in the right direction, as currently i see the code (individually (per-file)), but i am lacking the linkage.
I mean an extension of a base something i can understand/comprehend, but some stuff like schema seems to be burried deep somewhere and havent figured out how to add stuff.
If i somehow violate/inappropriately ask or post, please do tell/explain to me :)
best regards,
Michael Honkoop
next parent reply other threads:[~2020-12-04 23:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 23:47 Michael Honkoop [this message]
2020-12-09 11:23 ` Dominik Csapak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5FCACA8A02000088000040E7@mail.comsolve.nl \
--to=administrator@comsolve.nl \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox