Small, bite sized, tasks are good for a few reasons: 1) Does not take much effort on either party
2) Allows for deployment or work by those who can do task 3) Could be rolled up to more complex activity From: chris snow [mailto:chsnow...@gmail.com] Sent: Saturday, June 21, 2014 10:36 AM To: dev Subject: RE: Stratos mentors Hi Dale, thanks for the interest! At the moment, I'm thinking that mentoring should be on a task by task basis, and that we have a wiki page with a table to track tasks that need to be done. The table could have headings like this: - Task overview - JIRA link (if applicable) - What are the benefits of the task to stratos? - What you need to do the task (e.g. Environment and knowledge) - What you will learn from doing the task - Approx effort of task - Mentor and contact email - Mentee (when assigned) What do you think? Cheers, Chris On 21 Jun 2014 13:33, "Dale Chalfant" <dchalf...@greaterbrain.com<mailto:dchalf...@greaterbrain.com>> wrote: Hello Team: I have been tracking Stratos for about a year now off and on and chiming in every now and then. More or less, though, I have been reading the eMails going by. I appreciate what you all are doing, and I would like to dedicate some time to the effort. I would like to volunteer as a mentee with a sustainable budget of 7 hours a week. This could be an hour a weekday, and two on Saturday. We could figure out the program together from the viewpoint of the mentor and mentee. I expect there would be multiple tracks for various roles, but that would be part of the discovery. But step at a time… What would be required from an equipment/software perspective. A bit about me: I am 50/50 Business and IT. I am an Enterprise Architect with competency in 1) Business architecture 2) Solution architecture 3) Information architecture 4) Technical architecture And the specialty architectures: 1) Service architecture 2) Product architecture 3) Security architecture From the EA perspective: 1) Governance 2) Policy, standards, exception to policy (waivers) 3) Reference model 4) Reference architectures 5) Ontology 6) Frameworks 7) SDLC It has been years since I have programmed (so be patient with me), but formerly I did in: 1) Java 2) C 3) Perl 4) SQL 5) PL/SQL 6) COBOL 7) Assembler 8) JCL, REXX, CLISTS 9) BASIC (GW, Waterloo, VB, VBA) My databases: 1) Oracle (kept most up to date) 2) SQL/Server 3) DB2 4) IMS 5) Berkeley DB 6) DBXML I have also written course materials for SOA. Kind regards, Dale Chalfant +1-248-835-4523<tel:%2B1-248-835-4523> [http://greaterbrain.com/Pages/signature.png] From: Nirmal Fernando [mailto:nirmal070...@gmail.com<mailto:nirmal070...@gmail.com>] Sent: Saturday, June 21, 2014 7:57 AM To: dev Subject: Re: Stratos mentors On Sat, Jun 21, 2014 at 3:50 PM, chris snow <chsnow...@gmail.com<mailto:chsnow...@gmail.com>> wrote: Hi Devs, I just added a JIRA ticket for an improvement that will allows users to install stratos from releases artifacts [1], and it got me thinking that this task (and a few others I have added to JIRA) would be ideal projects for new developers coming to Stratos. I'm still a Stratos newbie (relatively speaking), but I would be interested in mentoring other newcomers who want to contribute to Stratos. Has this been tried before? Would anyone else be interested in mentoring Stratos contributors? Good idea Chris! I'd like to help. Maybe we could have a page in the wiki listing some tasks and the task mentors? Cheers, Chris --- [1] https://issues.apache.org/jira/browse/STRATOS-680 -- Best Regards, Nirmal Nirmal Fernando. PPMC Member & Committer of Apache Stratos, Senior Software Engineer, WSO2 Inc. Blog: http://nirmalfdo.blogspot.com/
