Get snapcraft-gui merged into the Snapcraft source code #4

Open
tsimonq2 opened this Issue Sep 10, 2016 · 4 comments

Comments

Projects
None yet
3 participants
Collaborator

tsimonq2 commented Sep 10, 2016

This might involve a rewrite in PyQt5 (for unit tests and such) but ideally you would work with the Snapcraft team to get this merged into the source. Here is the source code.

This way, any regular snapcraft user can use the GUI.

This might involve:

  • FIRST: ping the Snapcraft team (sergiusens, kyrofa, elopio on freenode) asking for their input on having a Snapcraft GUI. If they don't like the idea, then continue as a separate project and close this issue. Or, suggest it be moved to https://github.com/snapcore/snapcraft-gui if they don't want it in the Snapcraft source and volunteer to maintain it. Adjust the rest of the steps accordingly.
  • They might want a rewrite in PyQt5 if it does in the Snapcraft source, which shouldn't be that hard
  • Find a way to write unit tests for this that they would accept
  • Write unit tests
  • Adding the snapcraft-gui package to the Debian packaging of Snapcraft, which would install the executable
  • Ensure this tool has all the same functionality as the Snapcraft CLI tool.
  • Work with the Snapcraft team to get it merged, close this issue, then make sure you keep it up-to-date. It might help to automate some things.

If you do get a chance to move this along, respond to this issue.

Collaborator

keshavbhatt commented Sep 10, 2016

@tsimonq2 i will contact the team about the same and provide all these points as input.
I will update this after getting their feedback.
Thanks

The only problem with moving things to the snapcore organization is that they all fall under Canonical's CLA. Remaining independent means that signing that is not required and the DCO can be used instead.

Collaborator

keshavbhatt commented Sep 15, 2016

@Conan-Kudo what's wrong in Canonical's CLA.

@keshavbhatt

See this post from the Software Freedom Conservancy about why CLAs are bad.

@bkuhn goes into greater detail on his personal blog.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment