Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Be more contributor-friendly #17

Open
ghost opened this issue Oct 18, 2016 · 15 comments
Open

Be more contributor-friendly #17

ghost opened this issue Oct 18, 2016 · 15 comments

Comments

@ghost
Copy link

ghost commented Oct 18, 2016

  • I think README.md can be rewritten, especially the Contributing section, maybe adding a CONTRIBUTING.md will be better.
  • We can make some improvements in bindings.py so generating binding templates will be easier. see Use command line arguments in bindings.py #14
  • More issues and more labels. We can open issues for unimplemented or semi-implemented components and add some labels to new issues, so new contributors can easily find them.

Any ideas?

@joaoventura
Copy link
Owner

I would leave the contribution text on the readme for now. When the project reaches stability, we can move it to a less relevant section, such as contributing.md.

I run all my python code in PyCharm, so it is perfectly natural for me to change a file and run it, like to generate the bindings. But I guess we can be flexible and allow for more use cases, like running in a CLI.

I agree with opening issues. Can you do it? I'll give you commit rights on this project, so that you can do it.

@waghanza
Copy link
Collaborator

We can also enable CI to check each PR and else stability.
I have enable CI on my fork https://travis-ci.org/waghanza/pylibui
I'll be glad to open a PR to enable CI

@joaoventura
Copy link
Owner

Hi @waghanza, CI is something that we have in our plans, so yes, we welcome any PR regarding that matter! 👍

@waghanza
Copy link
Collaborator

waghanza commented Dec 23, 2016

@joaoventura done with PR #54

I plan to enable also windows, but only osx / linux on both py27 and py35 are tested

@joaoventura
Copy link
Owner

Merged #54 👍

@waghanza
Copy link
Collaborator

awesome, we can also add a status badge on README

@joaoventura
Copy link
Owner

@waghanza, I was just writing that, can you build a PR with a status badge on the README?

@waghanza
Copy link
Collaborator

@joaoventura #55

@waghanza
Copy link
Collaborator

@joaoventura can you relaunch travis build ? due to our parallel work I think travis build the project before #54 was merge

@joaoventura
Copy link
Owner

I'm searching how to do it, but cannot seem to find the relevant information..

@joaoventura
Copy link
Owner

Done!

@waghanza
Copy link
Collaborator

I also added documentation with PR #56, however I consider using this repository as a reference for documentation hosting

@waghanza
Copy link
Collaborator

Hi all,

I'm not sure enabling OS X tesing was a good idea.

For me, multi-platform tests should rely on libui

@rubyFeedback
Copy link

A big issue in regards to libui is lack of documentation. I don't think this can be fixed
anymore; andlabs doesn't invest that much time into libui, which is understandable.

Hopefully some hero can take the good parts and good idea of libui and create a new
project that tackles the existing issues AND the documentation. Because the idea behind
libui is great and it works on windows just fine. In fact: because it works on windows I
use it more so than I use, say, fxruby+fox on windows, simply because using it for a
quick GUI is soooooooo super convenient.

@rubyFeedback
Copy link

(Just to clarify in regards to my nick: I use python as well. Ruby and Python are
very much in the same "boat". The use cases and niches are so similar that,
despite the differences syntax-wise and philosophy-wise, I feel that the
"scripting" families ultimately fight a battle together rather than against one
another, even if evidently every language tries to garner more users
than other languages naturally.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants