Re: [DISCUSSION] Encouraging more contributions

That's an interesting experiment. From new contributor's aspect, I would see more small feature project ideas (just like rust community do). Since existing beginner issues give new contributors a vague roadmap what they should do next. On Thu, Jun 29, 2017 at 1:53 PM, Sourabh Bajaj <

Re: [DISCUSSION] Encouraging more contributions

The Rust community is trying an interesting experiment for encouraging more diversity in the contributors: https://blog.rust-lang.org/2017/06/27/Increasing-Rusts-Reach.html On Fri, Apr 28, 2017 at 12:05 PM Sourabh Bajaj wrote: > I think they can probably reach out to

Re: [DISCUSSION] Encouraging more contributions

These are the ones I've come across so far, are there others? * Dynamic DoFn https://s.apache.org/a-new-dofn ** Splittable DoFn (Obsoletes Source API) http://s.apache.org/splittable-do-fn ** State and Timers for DoFn: https://s.apache.org/beam-state * Lateness

Re: [DISCUSSION] Encouraging more contributions

You're right Kenn, discussing the "table of contents" is a good start. WDYT about having this table of contents audience and code package oriented? something like 1. SDK writers 1.1 Core components 1.1.1 Transforms 1.1.2 Metrics 1.2 IO components

Re: [DISCUSSION] Encouraging more contributions

general +1 to the concept, including driving down assigned-but-not-actually-being-worked-on items. I also really like the idea of having a mentor on tickets. Etienne, Re: specific help for I/Os - is the I/O Authoring docs not a good answer? https://beam.apache.org/documentation/io/io-toc/ (or

Re: [DISCUSSION] Encouraging more contributions

For 6. I think having them in one page on the website where we can find the design docs more easily would be great. 7. For low-hanging-fruit, one thing I really liked from some Mozilla projects was assigning a mentor on the ticket. Someone you can reach out to if you have questions. I think this

Re: [DISCUSSION] Encouraging more contributions

Same also for Slack, github comments, etc. From a Apache perspective, it should happen on the mailing list, eventually referencing a central wiki/faq/whatever. Regards JB On 04/24/2017 06:23 PM, Mingmin Xu wrote: many design documents are mixed in maillist, jira comments, it would be a big

Re: [DISCUSSION] Encouraging more contributions

many design documents are mixed in maillist, jira comments, it would be a big help to put them in a centralized list. Also I would expect more wiki/blogs to provide in-depth analysis, like the translation from pipeline to runner specified topology, window/trigger implementation. Without these

Re: [DISCUSSION] Encouraging more contributions

Got it. By experience on other Apache projects, it's really hard to maintain ;) Regards JB On 04/24/2017 02:56 PM, Etienne Chauchot wrote: Hi JB, I was proposing a FAQ (or another form), not something about IDE setup. The FAQ could group in the same place Q/A like for example "what is a

Re: [DISCUSSION] Encouraging more contributions

Hi JB, I was proposing a FAQ (or another form), not something about IDE setup. The FAQ could group in the same place Q/A like for example "what is a source, how do I use it to implement an IO" Etienne Le 24/04/2017 à 14:19, Jean-Baptiste Onofré a écrit : Hi Etienne, What about the

Re: [DISCUSSION] Encouraging more contributions

Hi Etienne, What about the contribution guide ? I think it's covered in the IntelliJ and Eclipse setup sections. Regards JB On 04/24/2017 02:12 PM, Etienne Chauchot wrote: Hi all, I definitely agree with everything that is said in this thread. I might suggest another good to have: to

Re: [DISCUSSION] Encouraging more contributions

Hi all, I definitely agree with everything that is said in this thread. I might suggest another good to have: to ease the work of a new contributor, it would be nice to have some sort of programming guide but not oriented to pipeline writers but to sdk/runner/io/... writers. I know that

Re: [DISCUSSION] Encouraging more contributions

Hi Ismaël, Honestly, for 4, I think it's not so bad and we clearly improved in the past months. It's definitely an area where we have to keep improving, but I think we do a good job (especially comparing to other projects). For 5, agree. For example, I limit myself to 3 or 4 pull requests:

Re: [DISCUSSION] Encouraging more contributions

+1 Great idea Aviem, thanks for bringing this subject to the mailing list. I agree in particular with the freeing JIRA part, I think we shouldn’t keep assigned JIRAs that are things that we don’t expect to solve in the next weeks. (note the exception for this are the long features). I would add

Re: [DISCUSSION] Encouraging more contributions

Hi, I think we already tag the newbie jira ("low hanging fruit" ;)). Good idea for domain of interest/concept. Regards JB On 04/24/2017 09:01 AM, Ankur Chauhan wrote: Might I suggest adding tags to projects based on area of intetest, concept and if it's a good "first bug". Sent from my

Re: [DISCUSSION] Encouraging more contributions

Hi All, I can take few things. I have planned to contribute towards beam SQL DSL but members can assign more things and will be happy to contribute towards those tasks. Regards, Tarush On Sat, 22 Apr 2017 at 8:40 PM, Mingmin Xu wrote: > Good point, could also disable the

Re: [DISCUSSION] Encouraging more contributions

Good point, could also disable the auto assignment when creating JIRA ticket. Now it goes to component leader directly. Sent from my iPhone > On Apr 22, 2017, at 7:34 AM, Ted Yu wrote: > > +1 > >> On Sat, Apr 22, 2017 at 7:31 AM, Aviem Zur wrote: >>

Re: [DISCUSSION] Encouraging more contributions

+1 On Sat, Apr 22, 2017 at 7:31 AM, Aviem Zur wrote: > Hi all, > > I wanted to start a discussion about actions we can take to encourage more > contributions to the project. > > A few points I've been thinking of: > > 1. Have people unassign themselves from issues they're