Ricerous, A Community Project About Ricing

This thread is to keep track of a project.

Introduction:

We've tried to pull out many community projects in the past and they all failed
to fulfill their purpose. Recently, on irc, some of us were discussing this
matter and tried to give new ideas for a solid project. The main concern was
that to regroup the community we needed a project that everyone could
contribute, had knowledge about, and liked. The word "ricing" came to our mind
and we started brainstorming what projects we could all work on, that would
touch this subject, that would help other people, and that would, in a sense,
regroup the community.

The Idea

A kind of portable wiki diary program about ricing. It regroups altogether what
can be riced with useful information and link about it. It also let the user
notes/comments in each sections to keep track of what has been done. The notes
can then be exported/imported in multiple formats.

Goal

• [X] Make it easy to redo another person's setup.
  [X] Remove the mystification around the word "ricing".
  [X] Easily share one's setup on forums/boards.
  

User Base

Beginner ricers that don't know where to start.
Advanced users that get lost when they want to share info about their setup.

Scratch pad

etherpad
The information

Requirements

• [X] Easily browsable definition/links/info of things by sections
  [X] Easy way to recognize what has been selected and re-browse through it
  
• Links should be visible
  [X] Save config/setup of the program
  [X] Editable output format (to stdout)
  [X] Editable places (comments) to keep track of custom actions
  [X] Pluggable/easy to add new things (programming side)
  [X] Local / Portable
  

Use Cases

• Open the Program Presented with the last section visited
  
• Search for a keyword (only if the interface is bad)
  [X] Go into a specific section and check the info/links/description
  [X] Tick a box as it being in the current install
  [X] Add comments to section that can be exported/imported
  [X] Load / Save configs/setup/comments(of the program) in a sharable manner
  
• add a new section/edit --> send it online for approval ~~most tricky one
  

Mainly 2 cases:
[X] "I don't know what I'm doing what's that thing called a shell... oh that's it, let's see what I can do and add it in the comments" or
[X] "I wanna keep track of what I did config in my shell, ah yeah I forgot to add my aliases"

Mock-ups & User Interface Designs

In the same order as in the scratch pad, meaning in the same order that they
have been done. You can follow up the conversation about them on the pad to
argue about them.

• (z3bra)
  
• (venam)
  
• z3bra2 (z3bra)
  
• (venam)
  
• (dotdev)
  
• (jolia)
  

Class Diagrams

Same thing as with the UI, to get more info read the pad.

• (venam)
  
• (kirby)
  

Implementation
Here is the community repo: https://github.com/nixers-projects/ricerous

[/list]
List Of Riceable Things And Info
Please refer to this pad.

What Needs To Be Done

• Test/Debug the Program (Doesn't need programming knowledge)
  

What Has Been Done
[X] Means that it has been fulfilled in the above requirements and expectations.
Here are some screenshots of the program:





How To Test
Install kivy.
Continue on with the tutorial & sharing thread http://nixers.net/showthread.php?tid=1579

Contributors

• Z3bra
  
• Dami
  
• Foggalong
  
• pizzaroll1 (kaashif-hymabaccus)
  
• Jolia
  
• Kirby
  
• DotDev
  
• Dcli
  
• Venam
  
• Vompatti
  
• Earsplit
  

The rest of the community for giving ideas, opinions, and helping choose a name.