View source

You do not have permission to edit this page, for the following reason:

You can view and copy the source of this page:

'''Joshua C. Nwokeji''' Dr. Joshua C. Nwokeji is an assistant professor of Information Systems at the Department of Computer and Information Science (CIS), Gannon University Erie, Pennsylvania. He completed his Ph.D., in June 2016, and joined CIS Dept., in August 2016. Click here to view my [[http://www.gannon.edu/FacultyProfiles.aspx?profile=nwokeji001 My Homepage]]. As a faculty in early career stage, Joshua is seeking and willing to collaborate in research that will lead to high quality publications and attract funding. Please feel free to [[http://www.gannon.edu/FacultyProfiles.aspx?profile=nwokeji001 get in touch]]. Joshua is interested in these broad research areas: *Software Requirements Engineering, *Goal oriented requirements engineering (GORE); *Enterprise Modeling and Agility; *Systems Analysis and Design; *Requirements Engineering Education; *Enterprise Architecture. Currently, Joshua has few publications in these areas, some of which are available in [https://scholar.google.com/scholar?hl=en&as_sdt=0%2C39&q=joshua+nwokeji&oq=Joshua Google Scholar]. ==<span id="Alternate Section Title"></span>Stage 1 Activities== ===Intro to IRC: Deliverables === * How do people interact? ::''Interactions are generally via instant messaging.'' * What is the pattern of communication? ::''Not sure, but based on my experience in using IRC, I would say that communication is linear, formal and can be a mix one to many, and one to one.'' * Are there any terms that seem to have special meaning? ::''It appears that terms such as 'startmeeting', 'action', 'info', topic, 'endmeeting' etc., have special meaning.'' * What advantages might IRC have over other real-time communication methods (like Google Chat or Facebook Messenger?) Are there potential disadvantages? ::''I think IRC is more structured and can ensure anonymity more than the others. Keeping track of who left the meeting is really cool.'' * Commands: ::''/whois','/quit', '/me', etc. ===Sugar Labs Project === *Summarize the roles that you think would be most applicable for your students. ::''Designer--My students can contribute to requirements development and management (any requirements development team?).'' *What are the commonalities across roles? What are the differences? ::''Each role specifies a set of skills, projects and teams, specific tasks, and contact person.'' ::''Some roles include links to mentors and mailing list.'' *Describe the general process for submitting a bug. ::Step 1: ''Find the activity that relates to the bug in the repository using this [[https://github.com/sugarlabs link]]'' ::Step 2: ''In the repository page select 'issues'.'' ::Step 3: ''Click on 'New Issues''' ::Step 4: ''Login into GitHub if you already have account else create account first'' ::Step 5: ''Enter title, describe the issues and submit.'' *Indicate the types/categories of tickets listed on this page as well as the information available for each ticket. ::''Issues; pull request.'' *Last Commit. ::''September 8, 2017'' *Describe how the release cycle and roadmap update are related. ::''I think that roadmap update is the herald of, or provide detail information about, a release cycle.'' ===The Sahana Eden Project=== *Community **POSSE and students can contribute to any of the following roles:Developers; Testers (Bug Marshals); Community Outreach; Designers; Documenters; GIS Specialists; System Administrators; and Translators **In general, roles have similar structure to the Sugar Lab project and include information that can be useful to prospective volunteers. But, some roles provide more support for newbies than others. For instance, the 'Developer Role' has a mailing list, virtual training environment,and developers guidelines. *Tracker **I found tickets that relates to the following components of the software: Request Management; User Interface; GIS Mapping, Inventory, etc. Tickets are structured in tabular format containing the following columns: Ticket Number (appears to be a unique ID); summary (a brief description); component (I think component/module of the program where bug is found); priority, type, owner, and date created. *Repository **The last commit was done today October 5th 2017. *Release Cycle: I found three (3) milestones on this page: **Milestone 0.9.0 "Medway" is 92% completed with a total of 107 tickets, out of which 92 are closed and 7 are open. Some of the functionalities to be delivered in this milestone include: GIS, advanced interactive search, request management, and other. **Avon or Milestone 1.0 is 73% completed with

Return to User:Jnwokeji.