Skip to content
This repository has been archived by the owner on May 30, 2023. It is now read-only.

Lowering the barrier to contribution #14543

Open
ariya opened this issue Sep 15, 2016 · 9 comments
Open

Lowering the barrier to contribution #14543

ariya opened this issue Sep 15, 2016 · 9 comments
Labels

Comments

@ariya
Copy link
Owner

ariya commented Sep 15, 2016

This is related to #13861 and #14541.

There are many different ways to contribute to PhantomJS: fix a defect, propose an enhancement, triage issues, write documentation, help setting up infrastructure, or even fund someone to work on PhantomJS.

If you would like to contribute to PhantomJS but you haven't done that yet, please let us know why. Even better if we can start the discussion on how to lower those barriers.

@zackw
Copy link
Collaborator

zackw commented Sep 15, 2016 via email

@jesg
Copy link
Contributor

jesg commented Sep 15, 2016

my use case

i use phantomjs to run automated selenium tests on linux. the 2.1.1 upgrade was rough i ended up applying d038837 (cookie fix) plus a full ugrade to the selenium atoms in ghostdriver. the docker build was useful when putting this together.

for me learning how to build the project from source took the longest. the project does not always build from source on linux which can be frustrating. (1) stable reproducible build.

ghostdriver has not been updated in phantomjs for 2 years. i understand that the contributors don't have the time to integrate changes from ghostdriver upstream. though it would be nice if there was a streamlined flow to getting ghostdriver changes into phantomjs. (2) integrate changes from ghostdriver

that said i would be interested in contributing changes to ghostdriver. let me know if there is any way i can contribute.

@JamieMcNaught
Copy link

I'd like to contribute / help, but I can't currently build master on Ubuntu 14.04 - it seems to need QT5.6 to build, but won't work without QTwebkit but QT 5.6 includes QTWebEngine - at which point I get confused. I've looked thought many bugs, wiki pages, etc.

To start helping, I need to be able to build it.

@gsouf
Copy link

gsouf commented Sep 22, 2016

@ariya I setup a slack chanel: https://phantomjs.slack.com/

It would be awesome to promote it on the website homepage (imo it can replace mailing list because people get more and more used to work with instant chat instead of email lists) let me now your opinion

@thoop
Copy link

thoop commented Sep 22, 2016

@gsouf don't you have to manually invite people to a slack channel? I think that would make a slack channel less useful here.

@gsouf
Copy link

gsouf commented Sep 22, 2016

@thoop No, everyone should be allowed to join, that just requiring they give an email and a password for the first connection. If you like something more open, we might try gitter instead

@jakehm
Copy link

jakehm commented Oct 5, 2016

Use a 'good first bugs' label.

@brainwane
Copy link

For something a bit more open, Zulip would work.

@vitallium
Copy link
Collaborator

I will create something like https://raw.githubusercontent.com/nodejs/node/master/tools/bootstrap/windows_boxstarter for setting up the development environment on Windows.

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

No branches or pull requests

9 participants