Embedded Files
Project documentation and project portfolio
Project documentation and project portfolio
All CRI projects and initiatives should be documented
All CRI projects and initiatives should be documented
Currently, many student and staff work for months on projects, which cannot be continued once they leave. This includes workshops, student collective or individual projects, aborted startup projects, CRI Labs projects, IT projects...
This is a net loss of time, visibility and even credibility for CRI, since our financing organizations cannot see the full impact of our activities. The core mission of CRI is to change education on a global scale ; to achieve this, we have to ensure that our experiments and projects can be replicated.
Documenting can be done in many forms and on many platforms :
- Code sharing on GitHub for IT / Technical projects
- Wiki to document collaborative knowledge
- Blogs illustrated with pictures and videos on a blog platform
- Web sites, on Google Web Sites or on Wordpress
- Bizagi diagrams and Google Docs to document processes
- Rhizi diagrams to document networks and relationships
All projects should be documented, this documentation can take many forms, but we should be able to find it easily.
That's why the CRI community needs a Project portfolio describing the key points of all CRI projects and pointing to its documentation and resources.
The third CRIBOOT workshop will be dedicated to defining this project portfolio platform.
Project management
Project management
Currently used applications :
Currently used applications :
- Wrike,
- BaseCamp,
- Trello,
- Taïga
What we need :
What we need :
- A single shared tool for everyone.
- A project portfolio, simple and clean, to present all project on a grid.
- A tool to manage projects : team, tasks, status, timetables, budget...
Recommandation :
Recommandation :
Wrike has a limited user adoption and costs a lot (8€/user by month). Taïga is a more powerful, user-friendly and open-source solution that we should investigate. Migration might be automated.
File sharing
File sharing
We use them to share files within and outside CRI.
What we need :
What we need :
- Security
- Sending very large files (up to a TB?)
- Saving and archiving documents
- Backup our personal computers
Currently used applications :
Currently used applications :
- Dropbox,
- Drive
Recommandation :
Recommandation :
DropBox should not be used for professional needs, as we have better security garanties with Google Drive Pro and unlimited file storage. Documents and folders can be shared with external emails.
IT team can also help you to setup a client software synchronizing your personal computer hard drive with your CRI Google Drive.
Teamwork
Teamwork
Currently used applications :
Currently used applications :
- Slack is used by several teams within CRI ; it is loved by some and hated by others.
- Mattermost
- Discourse
What we need :
What we need :
- A powerful communication tool who can be connected with other apps
- Clear organisation of datas and communications
- Something not too expensive per user
- Compatible with many plateforme (mobile ready)
Recommandation :
Recommandation :
Slack adoption within CRI teams is only partial and its pricing will grow to be a problem. Mattermost and Discourse could be interesting open-source alternatives that we can integrate to all our tools through APIs.
Code Editor
Code Editor
Currently used applications :
Currently used applications :
- SublimeText,
- Cloud9,
- Atom,
- Notepad++,
- Visual Studio,
- Vim,
- Codeanywher,
- Koding,
- Spyder,
- Komodo
Recommandation :
Recommandation :
Each team can use its own code editor. However, its code has to be commented properly and shared on a single platform managing versions and forks. GitHub is the dominant platform and can be used either for internal projects or for open-source projects with massive communities outside CRI.
Report abuse