Status of driver molecule-lxd #3036
-
|
Am I correct that the current implementation of the molecule-lxd is non-functional? PR #5 (Add default playbooks) seems to address some issues but I don't believe it was ever applied. Why not and what would it take to make it work? |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 1 reply
-
|
Do you want to be maintainer of molecule-lxd @snesbittsea? Because I think it just needs people to get on it. |
Beta Was this translation helpful? Give feedback.
-
|
I am considering it. Here are some of my concerns that are making me hesitate. I would appreciate any input from you. There's no point in appointing me maintainer if I don't have the expertise needed:
Unfamiliarity with Molecule 3 especially with respects to internals, coding conventions, architecture, backward compatibility (with respect to the new Collections framework). I've poked around for documentation, but haven't really found anything. I am concerned that out of ignorance I will implement something sub-optimal or out-of-sync with the overall architecture. It would be nice to tap into the Molecule team for code review for example.
Complete lack of knowledge of Travis and the CI framework. I am concerned about how much effort/hours would be required to put this in place and maintain it.
Expectations on developing unit and integration tests. I'm a big believer in them and would want to put them in place, but I don't have the time currently to spend extensive time writing them.
Unstated and thus unfulfillable expectations with expect to code quality, on-line presence, etc. What does the Molecule team expect from their maintainers.
As I stated, I'm not adverse to becoming the maintainer. I just want to make sure we - me and the Molecule team - are clear on expectations and we have good prospects for a win-win situation.
…-steve
---- On Sun, 17 Jan 2021 10:40:33 -0800 decentral1se <[email protected]> wrote ----
Do you want to be maintainer of molecule-lxd https://github.com/snesbittsea? Because I think it just needs people to get on it.
—
You are receiving this because you were mentioned.
Reply to this email directly, #3036 (comment), or https://github.com/notifications/unsubscribe-auth/ADKGZRWRO2F6OOJ5PS7SVTDS2MVKDANCNFSM4WELTMHQ.
|
Beta Was this translation helpful? Give feedback.
-
|
There isn't really a molecule team. There are no obligations except maybe turn up once in a while. Honestly, if you spent the time that it took you to write this issue on literally anything to do with getting this driver working, that would be enough. So, feel free to dive in. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, I'll give it a go and take on responsibility as maintainer. I can't be any worse than none
Let me know when I have the necessary github permissions.
…-steve
---- On Tue, 19 Jan 2021 07:50:31 -0800 decentral1se <[email protected]> wrote ----
There isn't really a molecule team. There are no obligations except maybe turn up once in a while. Honestly, if you spent the time that it took you to write this issue on literally anything to do with getting this driver working, that would be enough. So, feel free to dive in.
—
You are receiving this because you were mentioned.
Reply to this email directly, #3036 (comment), or https://github.com/notifications/unsubscribe-auth/ADKGZRRFTPQX4WG4O355OM3S2WS4PANCNFSM4WELTMHQ.
|
Beta Was this translation helpful? Give feedback.
-
|
Send some PRs and reference this issue and then we can open it up. |
Beta Was this translation helpful? Give feedback.
-
|
PR #7 is ready to go.
…-steve
---- On Tue, 26 Jan 2021 14:33:02 -0800 decentral1se <[email protected]> wrote ----
Send some PRs and reference this issue and then we can open it up.
—
You are receiving this because you were mentioned.
Reply to this email directly, #3036 (reply in thread), or https://github.com/notifications/unsubscribe-auth/ADKGZRWSSJOOSFVX5IKHGGTS347J5ANCNFSM4WELTMHQ.
|
Beta Was this translation helpful? Give feedback.
There isn't really a molecule team. There are no obligations except maybe turn up once in a while. Honestly, if you spent the time that it took you to write this issue on literally anything to do with getting this driver working, that would be enough. So, feel free to dive in.