What is this?
This post serves as the project proposal for me and my team’s Humanitarian Free and Open Source Software Development “Community Architecture” project (shortened to CommArch)!
In this project proposal, we take a preliminary look at the project we’re looking at analyzing, Tahrir, and the different criteria we are assigned to look at.
|Bobby Pruden||[email protected]|
|Wilfried Hounyo||[email protected]|
|Stephen Garabedian||[email protected]|
|Justin W. Flory||[email protected]|
Tahrir by the Fedora Project
Team Member Roles
Justin and Wilfried
- Project Report I-R
Stephen and Bobby
- Project Report A-H
- Calloway Coefficient of Fail
Source Code Repository URL
|Ralph Bean (threebean)||[email protected]|
|Remy DeCausemaker (decause)||[email protected]|
|Pierre-Yves Chibon (pypingou)||[email protected]|
The following methods of communication are ordered in the most preferred way to the least.
What are the easy parts?
- Project is fairly small (even though it is part of a larger project)
- People to ask for help when needed
- Git-by-a-bus is going to make analytics of contributors super easy
- Distribution of work will allow us to complete the project in a timely manner
What are the hard parts?
- Lack of a frame of reference for some team members who have never worked with open source projects in the past (e.g. we are unable to compare activity or its community to other projects)
- Since the project is a smaller project inside of a larger one (Fedora Project), it will be challenging to look at it in a modular sense
- Separation of dependencies from project requirements (Open Badges requirements and Tahrir requirements)
How will you overcome both?
- We have two people who are more advanced at hacking who can hopefully guide the two who aren’t through the project, effectively eliminating the lack of reference point.
- Three of our members are not people involved in the Fedora Project, and as such won’t be distracted by its involvement with Fedora and will only look at the project itself.
- Read up on the existing documentation and test the various endpoints of the project to identify what is needed with Open Badge and what the project is implementing itself.