All times shown according to UTC.
Time | Nick | Message |
---|---|---|
00:08 | sivoais joined #openhatch | |
00:40 | YesCT joined #openhatch | |
00:42 | Kowiz joined #openhatch | |
00:46 | skay__ joined #openhatch | |
00:53 | amyrlam joined #openhatch | |
01:05 | tier joined #openhatch | |
01:14 | tier joined #openhatch | |
02:46 | Kowiz2 joined #openhatch | |
02:47 | Guest38864 joined #openhatch | |
02:55 | JD|cloud joined #openhatch | |
03:09 | dlitz joined #openhatch | |
03:14 | grantbow joined #openhatch | |
03:21 | Kowiz3 joined #openhatch | |
03:23 | IShadowed joined #openhatch | |
03:23 | IShadowed joined #openhatch | |
03:26 | Niharika joined #openhatch | |
03:35 | phildini joined #openhatch | |
03:42 | deace joined #openhatch | |
03:55 | paulproteus | Today I wrote https://github.com/sandstorm-i[…]wiki/Get-Involved |
04:05 | Feedback very welcome. | |
04:18 | YesCT joined #openhatch | |
04:23 | terri_offline joined #openhatch | |
04:45 | willingc joined #openhatch | |
04:47 | amyrlam joined #openhatch | |
04:58 | terri_offline joined #openhatch | |
05:07 | kevix joined #openhatch | |
05:25 | terri_offline joined #openhatch | |
05:35 | britta | paulproteus: i think your intro sentence could be better. usually when i'm reading a 'get involved' page i'm not 100% committed yet to getting involved, i'm just curious what opportunities are available |
05:37 | so an intro sentence for me could be something like "hi! if you are interested in getting involved, there are lots of opportunities for people of different skills and types of interest; we're in an early stage so there is a lot of room for cool people to do really cool things" or something | |
05:40 | and like "we're in an early stage and we really want to make sure people who are interested can find something that matches their interests; if you're not sure what to try, you can use x method to talk to us and we can figure out something fun for you to work on" | |
05:40 | stuff like that | |
05:41 | i wrote this long careful explanation at https://localwiki.org/islavist[…]e_to_LocalWiki_IV recently but i don't think it's as effective as just like "come join the discussion group or send britta a message and talk about the project with her" | |
05:42 | i mean i feel like i need to have the long careful list of things as examples that show people that many skills are welcome, but like i am getting the feeling that 'make friends with the people working on it' is really the core thing i need to describe | |
05:44 | i am looking forward to running my first in-person event for that project so i can talk to interested people and make a better version of that page that addresses what is actually holding them back | |
05:47 | p.s. i am reviewing http://opensource-events.com/ to help me plan my in-person event | |
05:48 | yay openhatch | |
06:02 | lotia joined #openhatch | |
06:03 | Sixmsj joined #openhatch | |
06:39 | amyrlam joined #openhatch | |
06:55 | tmh1999 joined #openhatch | |
06:57 | tmh1999 joined #openhatch | |
07:00 | tmh1999 joined #openhatch | |
07:03 | tmh1999 joined #openhatch | |
07:06 | tmh1999 joined #openhatch | |
07:37 | FHaag joined #openhatch | |
07:46 | hollandais joined #openhatch | |
07:47 | drovka joined #openhatch | |
07:50 | amyrlam joined #openhatch | |
08:21 | dlitz joined #openhatch | |
08:37 | terri_offline joined #openhatch | |
09:00 | bmispelon joined #openhatch | |
09:06 | jpich joined #openhatch | |
09:49 | kevix joined #openhatch | |
09:54 | Niharika joined #openhatch | |
10:03 | drovka joined #openhatch | |
10:30 | drovka left #openhatch | |
12:17 | terri_offline joined #openhatch | |
12:28 | terri_offline joined #openhatch | |
12:33 | pdurbin | britta: I agree that a personal connection is nice. |
12:35 | terri_offline joined #openhatch | |
12:51 | terri_offline joined #openhatch | |
13:22 | terri_offline joined #openhatch | |
13:25 | bmispelon joined #openhatch | |
13:42 | Niharika joined #openhatch | |
13:59 | tier joined #openhatch | |
14:10 | Niharika joined #openhatch | |
14:11 | YesCT joined #openhatch | |
14:15 | willingc joined #openhatch | |
14:26 | willingc | ehashman, paulproteus: Interesing post by nedbat that may help if rate limiting still issue with GH trackers http://nedbatchelder.com//blog[…]nd_webhookdb.html |
14:29 | pdurbin | willingc: that reminds me of the bug impacting impaktor: https://github.com/openhatch/o[…]nline/issues/1515 |
14:30 | willingc | pdurbin: yes I hope that this might help with that |
14:30 | pdurbin: one day closer to lightsabers | |
14:31 | pdurbin | tomorrow! |
14:33 | willingc | Have fun. I'm frequently entertained by the creative ideas of the kids that come to the Fab Lab. |
14:36 | pdurbin | my 8 year old is in the "build a box" club in Extended Day. she's loving it. drew me pictures last night of all the pieces of wood and the nails |
15:00 | fossdevil joined #openhatch | |
15:03 | willingc | pdurbin: love it ^^ Save those designs :) |
15:09 | raniere joined #openhatch | |
15:13 | eMBee joined #openhatch | |
15:15 | eMBee joined #openhatch | |
15:32 | bmispelon joined #openhatch | |
15:52 | willingc joined #openhatch | |
15:53 | jpich joined #openhatch | |
16:03 | Nightrose joined #openhatch | |
16:44 | pdurbin | she scribbled over it but yeah, I hear ya |
17:12 | wolftune joined #openhatch | |
17:14 | v20 joined #openhatch | |
17:14 | decause joined #openhatch | |
17:17 | andrew_______ joined #openhatch | |
17:24 | Nightrose joined #openhatch | |
18:04 | kwurst joined #openhatch | |
18:04 | triposorbust joined #openhatch | |
18:07 | Elvano joined #openhatch | |
18:23 | openhatch_5870 joined #openhatch | |
18:23 | amyrlam joined #openhatch | |
18:25 | openhatch_5870 | hello. I am new out here and to feild of contribution. may i get any help on how and from where to begin with. ? |
18:27 | impaktor | openhatch_5870: Hi! I'd guess you need to specify what you want to do? Some special skill you have, or want to learn? |
18:27 | Some special project you want to contribute to? | |
18:29 | openhatch_5870 | I know python and django. m good at python. I was planning to start contributing in for python . But I don't know how and from where to start to. Right now am just reading out documentations from various source to start it. |
18:31 | impaktor | Are you using any software that you like, that is written in python. Then you could start looking at contributing to such projects. |
18:32 | terri_offline joined #openhatch | |
18:32 | FHaag joined #openhatch | |
18:35 | impaktor left #openhatch | |
18:35 | willingc | howdy impaktor and openhatch_5870 |
18:36 | openhatch_5870 | no. excatly what kind of software? |
18:36 | impaktor joined #openhatch | |
18:37 | Sixmsj joined #openhatch | |
18:37 | openhatch_5870 | willingc : hi ! |
18:39 | Elvano joined #openhatch | |
18:41 | willingc | openhatch_5870: Each open source project has its own process for contributions and its own timeline for learning how to contribute. |
18:41 | impaktor, I believe was politely suggesting that sometimes it is easier and more productive to contribute to a project that is smaller than CPython | |
18:42 | The CPython developer guide is found here: https://docs.python.org/devguide/ | |
18:43 | It outlines the process for contributing to CPython. | |
18:44 | YesCT joined #openhatch | |
18:47 | willingc | openhatch_5870: impaktor gave sound advice to try to find a smaller project that you are interested in and perhaps consider contributing to it |
18:47 | As an FYI OpenHatch's code base, oh-mainline, uses Python and Django. | |
18:48 | openhatch_5870 | willingc : thankyou i found the link you suggested and it do have all the basics . and yes impaktor was polite and i am sorry if I sounded otherwise but i didn't mean to. |
18:50 | willingc | openhatch_5870: you were polite as was impaktor. It's your choice where to begin. We were just providing insight from our experiences. |
18:51 | impaktor: still looking to get your tracker working...sorry it's taking a while :( | |
18:56 | soulshake left #openhatch | |
18:57 | openhatch_5870 | willingc : can you guide me little more in this thing.. ? |
18:57 | its really confusing . :( | |
18:58 | deasea joined #openhatch | |
18:59 | impaktor | Wo-ha, I'm getting pinged like crazy here. |
18:59 | willingc | When you say thing: do you mean the CPython web guide? |
18:59 | impaktor | willingc: no problem. I'm patient. |
18:59 | willingc | impaktor: we missed you :) |
18:59 | impaktor | Not sure if I missed something during my 2 minute Emacs restart, but everyone's polite here, as far as I can tell. |
19:00 | AND DON'T YOU DARE DISAGREE WITH ME! | |
19:00 | ;) | |
19:00 | willingc | impaktor, all good :) |
19:01 | openhatch_5870 | yes CPython web guide. (and all stuff of contribution :P ) |
19:01 | deasea | Can someone provide a bit of guidance on setting stuff up on events.openhatch.org? |
19:03 | willingc | openhatch_5870: would this be your first contribution to an open source project? |
19:03 | shauna: are you around to answer deasea's questions? | |
19:03 | howdy deasea :) | |
19:03 | ArcTanSusan_ joined #openhatch | |
19:04 | terri_offline joined #openhatch | |
19:04 | deasea | hiya! |
19:04 | openhatch_5870 | yes. actually I am far away from my "first contribution". But yes first. |
19:06 | willingc | openhatch_5870: As a first major contribution to open source, my personal opinion is that CPython would be a steeper learning curve than other projects since it is a large code base. |
19:07 | I would suggest looking at the developer documentation for OpenHatch (or another project) and try to make a couple of contributions and then move into the CPython world | |
19:08 | The openhatch docs are here: http://openhatch.readthedocs.org/en/latest/ | |
19:11 | deasea: I need to be on a conference call but want to make sure that your questions are answered. Perhaps ask the question and wait until someone who knows about events.openhatch.org is free to answer :) | |
19:11 | openhatch_5870 | i do agree. well, i should check out the openhatch docs first. |
19:12 | deasea | Sure! |
19:13 | I am coordinating the upcoming Toronto event (dcwalk on discourse), having trouble authenticating to events.openhatch.org. Is this a known issue? | |
19:14 | Sorry, authenticating with another service. If I go ahead an sign up with a new acct will I be able to manage events or does that require permission? | |
19:23 | deasea joined #openhatch | |
19:26 | amyrlam joined #openhatch | |
19:37 | deasea | willingc: shauna: I've got to head off, but will send the same question RE: trello. |
19:37 | deasea left #openhatch | |
19:54 | wolftune joined #openhatch | |
19:59 | amyrlam joined #openhatch | |
20:10 | openhatch_5870 | hello again :) well i have just finished all the cloning and installation part and have the site running locally on my machine.. |
20:11 | may i ask how should I proceed next ? | |
20:13 | carol_w joined #openhatch | |
20:24 | willingc | openhatch_5870: The next step would be to find an issue that you would like to work on. There are a few approaches to finding a suitable issue. |
20:24 | https://github.com/openhatch/oh-mainline/issues lists openhatch oh-mainline issues | |
20:25 | Some of the issues are labeled bitesized that are suitable to newer contributors. Read through the list to see if there are issues that interest you. Our documentation uses restructuredtext and sphinx so docs, as well as tests are a reasonable coding place to start. | |
20:26 | You should check in the issues comments to see if anyone has already said that they were working on it. If you are unsure if an issue is suitable, please feel free to ask here on IRC. | |
20:28 | Many of us support multiple projects so please do not be discouraged if you do not get an immediate response. We're a helpful bunch :) | |
20:32 | openhatch_5870 | yes i do understand that you all are busy so i will be patient.. :) so bitesized issues are particularly for new people. is there nothing sort of easy issues or hard issues? |
20:34 | willingc | openhatch_5870: You may choose to work on any open unclaimed issues. Bitesized issues are also available to all. Also, looking at closed issues will give you a sense of the variety of issues and the code needed to resolve the issue. |
20:35 | Bitesized are issues that someone familiar with the code base felt was a good issue for newcomers to openhatch :) | |
20:36 | ArcTanSusan_ joined #openhatch | |
20:41 | openhatch_5870 | oh. well then i would begin with looking at closed issues for better understanding. |
20:43 | Kowiz joined #openhatch | |
20:44 | openhatch_5870 | thankyou for yor help willingc and impaktor. see you soon again tomorrow with new set of questions :P |
20:53 | ArcTanSusan_ joined #openhatch | |
21:24 | amyrlam joined #openhatch | |
21:27 | ArcTanSusan_ joined #openhatch | |
21:31 | amyrlam_ joined #openhatch | |
21:49 | sivoais joined #openhatch | |
22:46 | FHaag joined #openhatch | |
22:48 | tier joined #openhatch | |
22:51 | sivoais joined #openhatch | |
23:08 | FHaag joined #openhatch | |
23:22 | tier joined #openhatch | |
23:23 | heidie joined #openhatch | |
23:30 | willingc joined #openhatch | |
23:36 | wolftune joined #openhatch | |
23:41 | amyrlam joined #openhatch | |
23:44 | kevix1 joined #openhatch |